One of the most important documents in a project is the kickoff presentation. Because this document formally begins, or "kicks off," project development, it can only be created after the project has b
Running Head: BUSINESS REQUIREMENT DOCUMENT 11
Individual: Business Requirement Document
Geoffrey Parker
CMGT/410
September 31, 2019
Rod Wells
1. Executive Summary
1.1 Project Overview
This project is a hospital management system. Currently, the hospital is using the manual system whereby when patients visit the hospital their file is searched, or a file is opened, and details about the patient are entered. The same file will be transferred to the doctor when the patient sees the doctor. Diagnosis details will be entered, and the file will be transferred to the pharmacy so that drug details can be entered. After the patient has been issued the drugs, the file is left with the pharmacy. When he/she visits again, the same process starts over. The hospital decided that this is a tedious process and at the moment they have huge volumes of files and searching a file for a particular patient is cumbersome and time-consuming. The hospital decided to come up with a management system that will help with this process of booking appointment, visiting the doctor, and also the system captures pharmacy details.
1.2 Purpose and scope of this specification
The purpose of the hospital management system is to ensure easy management of the hospital records and also payment
Scope
The scope of the hospital management system will include:
Coming up with a database that will store patient records in terms of appointments, diagnosis, doctor’s records, and drug records.
Making of the user interface
Incorporating online payment system whereby patients can decide to pay using visa cards or PayPal.
Out of scope
The system will not include supplier details and the products and drugs supplied by suppliers. The products supplied and the supplier details are information that needs to be accessed by the selected few so it should not be incorporated in a system that will be used by the entire hospital.
2. Product - Service Description
2.1 Product context
The hospital management system is a separate system from the hospital supply system which deals with the supply of products such as surgical blades and drugs. The only similarity between these two systems is the look and feel of the organization. That is, they will have the same logo, color, etc.
2.2 User characteristics
The audience of the hospital management system will be patients.
Doctors will use the system to enter diagnosis information
Pharmacists will use the system to enter drugs issued to a patient
The database administrator will use the system to perform database administration activities such as modifying tables and issuing of rights and privileges etc.
The system administrator will use the system to monitor performance among other administration activities
2.3 Assumptions
The system will be designed using Java Enterprise Edition (JavaEE), and this entails Servlets and Java Server Pages (JSP).
The system will be online-based and will be accessed using a browser
The database is MySQL
The server that will be used to host the system is known as Tomcat
2.4 Constraints
The system will need to be developed using the issued finances
The system will use Java as its main programming language, therefore, need an advanced Java programmer who understands core Java, and Java Enterprise Edition (Servlets and Java Server Pages)
Since the system will be accessed online and hosted on a server, the programmer also needs to know front-end technologies such as HTML, CSS, and JavaScript and maybe Bootstrap.
2.5 Dependencies
Our system will use Tomcat as a server. We will need to update Tomcat as new releases are released to the market
Our system is highly dependent on Java as a technology. We will need to update Java as new releases are released to the market.
Our database of choice is MySQL; we also need to update it as new releases are introduced to the market
3. Requirements
3.1 Functional requirements
Register
The patient needs to register to the system using his email address
The doctor also needs to register to the system using his/her employee number
The system and database administrator needs to register to the system using the administrative portal that is not available to other users using their employee number
The patients need to provide their details while registering, such as name, email, phone number, sex, age.
The doctors need to provide information such as name, specialty area, and availability, e.g. night or day.
Sign up
Input: details about the patient as mentioned in the register section
Output: confirmation of registration status
Processing: details will be checked, and when errors occur they will be displayed
Input: details of the doctor as mentioned in the register section
Output: confirmation of registration status
Processing: details will be checked, and if errors occur, they will be displayed on the screen
Login
Input: enter patients credentials
Output: patients can use the hospital management system
Input: enter doctor credentials
Output: the doctors can use the hospital management system
Appointment
Input: enter details of the appointment
Output: appointment details captured
Diagnosis
Input: enter diagnosis details
Output: diagnosis details captured
Drug issuance
Input: enter drug details
Output: drug details captured
Payment
Processing: payment processing is done
Output: a receipt is issued to the patient
3.2 User Interface Requirements
Patients interface
The patient's interface will show patients details, appointments booked, the preferred doctor assigned, and the preferred payment method. The look and feel will represent the organization’s colors.
Doctor’s interface
The doctor's interface will show the patients information, the diagnosis section whereby the doctor and enter the diagnosis information
Pharmacy interface
The pharmacy interface will show the patient’s details, the doctor assigned to a particular patient, the diagnosis details, and the recommended drugs. It will also show the payment details.
Administrator interface
The administrator interface will show the database whereby the database administrator can perform administrative duties such as modifying tables etc. The administrator interface will also have a section whereby the system can be monitored in terms of performance and also SQL performance.
3.3 Usability
The system will have menus that also contain icons and tooltips when hovered over to facilitate ease of use
The interface will have assistive technology for visually impaired users
The system will also be mobile responsive. That is, it will cater to mobile users.
Interface accessed using mobile devices will not have icons and tooltips due to the small width of mobile device screens
Mobile responsiveness will be tested using online mobile responsiveness testing tools such as mobiletest.me website.
3.4 Performance
3.4.1 Capacity
The system should handle 500 users in one second
3.4.2 Availability
The system will be available at all times (24/7)
The system will be distributed. That is, the system will run on different servers for performance improvement. When one server is down, the user will not know since the other server will be used.
3.5 Manageability/Maintainability
3.5.1 Monitoring
Monitoring will be done through the administrator interface. This interface will have monitoring tools for the system and the database.
3.5.2 Maintenance
The system will have two areas, one for the administrative area and the other one for the patients, doctors, and the pharmacy area. Having these two areas will make the system easy to maintain because we are not maintaining several components.
3.5.3 Operations
After a patient has taken drugs from the pharmacy, he/she will pay for the entire services rendered. The entire transaction will need to either succeed or fail.
Since we are dealing with sensitive information, the backup will occur automatically to the data center, and a full backup will be done every fortnight.
3.6 System Interface
3.6.1 Network and Hardware Interface
The hospital management system will be run from a web server that supports Java technology known as Tomcat. Therefore, the web server will run on port 443 that supports HTTPS.
The hospital management system will be accessed using a browser, so it entirely depends on the network
The database will be administered from the administrator portal and will be accessed through the network. Patient, doctors, and pharmacists will make changes to the database through the hospital management system.
By default, MySQL runs on port 3306. Our database will also run on this port.
3.6.2 System interface
The system is to be accessed through a browser. Therefore, it is meant to be used online. We will use HTML encoding, which is UTF-8.
3.7 Security
3.7.1 Protection
The system will use various protection methods, such as:
The data will be encrypted while at rest and also when it is transferred over the network
The encryption technology that will be used is the Advanced Encryption Standard (AES)
The system will have multifactor authentication. A user will need to enter a password and also a One Time Password (OTP) that will be sent to the user through Short Message Service (SMS).
3.7.2 Authorization and Authentication
The patients will have the least privileges. Patients can only access their data, and this includes their name, email, medical history, doctors assigned, payment method, and other details such as date of birth, etc.
3.8 Data Management
Password will only accept more than 15 characters and the characters should have a mixture of letters, numbers and special characters
Bank details will be encrypted, and full bank card numbers will not be shown. Only the first digit and the last three digits will be shown.
Patients can only modify their data, and they have the least privileges
3.9 Standards Compliance
The hospital management system will be compliant to the Health Insurance Portability and Accountability Act (HIPAA) and the General Data Protection Regulation (GDPR).
Appendices
Appendix A: Definitions, Acronyms, and Abbreviations
AES – Advanced Encryption Standard
This is a symmetric block cipher used by the U.S government to protect confidential information
CSS – Cascading Style Sheet
This is a coding language that gives an artistic presentation to web pages. It makes web pages look good
Java – this is an Object Oriented Programming language that is owned by Oracle, and it is used to program systems
JavaScript – this is a programming language that is used to give web pages behavior. For example, a tooltip is shown when a user hovers over a menu.
SQL – Structured Query Language
This is a language used to manipulate the database. For example, creating a table in a database
HTML – HyperText Markup Language
This is a coding language used to create websites
