Hospital Management System Requirements

This assignment delves into the functional requirements of a Hospital Management System. It outlines key aspects such as reliability, performance, accessibility, and usability, emphasizing the need for efficient functionality and user-friendly interfaces. The document includes specific details about user interface elements and sign-in validation procedures.

Author Name:
Project Name: Accessibility of Patient Services using an Online Medical System.
Client Name: Julius Smith.
Date: 14th August 2017
Version Control Table.
Version Date Author Comments
Draft 1 14th August 2017

Introduction
Business name: Northshore Medical Centre.
Logo:
Objective and Purpose
Northshore Medical Centre main objective is to provide the best quality, effective, efficient and
timely patient services and ensuring provision of patient-satisfactory services that in themselves
provide enduring healing effect.
The new system will facilitate 24/7 access of the patient services, will allow patients to book
appointments with doctors any time at any place and it will help in easy management of billing
and finance services(Narsaria, 2015).
Stakeholders
1. The Software Development Company – This is the company specializing in web-based
application development.
2. My colleague and I(Analyst) - We are employed by the Software Development
Company.
3. The client (Northshore Medical Centre) - This is the client that has contracted the
Software Development Company to develop a new system.

Users
1. Accountant
He or she is in-charge of all the finances of the business through the system. They receive
payments of the charges of the patient services from the patients. He is authorized to instruct
the system to make different billing reports (Ayatollahi, Nazemi & Haghani, 2016).
Step by Step Usage of the system
1. The accountant registers in the system with a specialization of accountancy and waits a
verification of authorization from the system's admin.
2. The accountant can login with a provided personal verification code.
3. A dashboard is provided with the following menu: My Profile, Patients Information,
Make Payments, Receive Payments, Pharmaceutical Payments, All Payments, Credit and
Debit and financial Reports.
2. Admin.
This the main and key user of the system that oversees everything that is run by the system.
He or she has all the privileges of the system. He can grant or deny access to any service of
the system to any user (Antsglobe, 2016).
Step by Step Usage of the system.
1. The admin registers in the system with a code given provided by the system's developer.
2. The admin Login into the system
3. A Dashboard is the first screen with the following menu: My Profile, Staff, Patients,
Appointments, Billing Services, Branches, Salary Payments, Pharmacy and Reports.

Scope and Constraints
Objectives.
1. Increase accessibility of the patient's services by providing a 24/7 access of the system
online.
2. Reduce average time between the patient's visiting the hospital to make appointments and
the actual approval of the appointments (Taylor Jr, 2011).
3. Easen the payment of charges of the patient's services through the flexibility of allowable
payment methods e.g. mobile payments.
4. Eliminate manual reports by automating the generation of all kinds or required reports at
any time.
However, the System does not include user manual on the first version.

Requirements
Functional Requirements
ID Requirement Description Priority
1 As a patient, I want to book
appointments so that I can
schedule my treatment with a
doctor.
High
2 As a patient, I want to pay my
outstanding bills via my
credit card so that I can be
flexible.
High
3 As a patient, I want to receive
my medical reports and via
notifications for easy
accessibility.
Medium
4 As an accountant, I want to
generate billing reports for
proper record tracking.
High
5 As an admin, I want to import
and export data from the
system for synchronizing
external data.
Medium
6 As an admin, I want to assign
or detach roles to users for
proper functioning of the
system.
High

7 As an admin, I want to view
all future appointments for
proper planning.
High
8 As a marketing officer, I want
to view the trends of
transactions for proper
planning.
Medium
9 As a pharmacist, I want to
view all the medicines'
consumption level for better
understanding of patients'
needs.
High
10 As an admin, I want to
authorize the salary payment
so that the employees are paid
accordingly.
High
Non-Functional Requirements
ID Requirement Requirement
Description
Priority
11 Reliability The system will
guarantee proper,
effective and efficient
functionality without
malfunction
(Eriksson, 2015).
High
12 Performance The system should
allow operations to
be conducted by the
users whereby given
High

certain input, it
processes the input
and give an
appropriate output.
13 Accessibility The system should
allow an
authenticated user to
perform any
operation at any time
at any place
(Constantinides, 2014).
High
14 Usability The system should
provide user-friendly
interfaces that allow
the users perform
operations with ease.
Medium
User Interfaces.
1. The design will use menus, buttons, input fields and date pickers (James Garrett’s, 2017).
2. The sign in validation includes a password checker for 8 characters, inclusive of numbers
and a special character, uppercase and lowercase (Mandel, 1997).

References
1. Narsaria, D. (2015). What is a Hospital Management System? - The Practo Blog for
Doctors. The Practo Blog for Doctors. Retrieved 16 August 2017, from
https://doctors.practo.com/hospital-management-system/
2. James Garrett’s, J. (2017). User Interface Elements | Usability.gov. Usability.gov.
Retrieved 16 August 2017, from
https://www.usability.gov/how-to-and-tools/methods/user-interface-elements.html
3. Mandel, T. (1997). The elements of user interface design. New York, NY [u.a.]: Wiley.
4. Eriksson, U. (2015). The difference between functional and non-functional requirements
| ReQtest. ReQtest. Retrieved 16 August 2017, from http://reqtest.com/requirements-
blog/understanding-the-difference-between-functional-and-non-functional-requirements/

5. Constantinides, C. (2014). Functional Requirements vs Non Functional Requirements.
OneDesk. Retrieved 16 August 2017, from http://www.onedesk.com/functional-
requirements-vs-non-functional-requirements/
6. Taylor Jr, J. (2011). Project Constraints: Scope - What is Scope and How Can It Be
Managed?. Brighthub Project Management. Retrieved 16 August 2017, from
http://www.brighthubpm.com/project-planning/9229-managing-scope-a-project-
constraint/
7. Ayatollahi, H., Nazemi, Z., & Haghani, H. (2016). Patient Accounting Systems: Are They
Fit with the Users' Requirements?. US National Library of Medicine National Institutes
of Health. Retrieved 16 August 2017, from
https://www.ncbi.nlm.nih.gov/pmc/articles/PMC4756055/
8. Antsglobe, A. (2016). Hospital Management Software - Hospital Management System,
Healthcare billing Software Service Provider from Nagpur. Antsglobe.com. Retrieved 16
August 2017, from http://www.antsglobe.com/hospital-managment-software.html