Hospital Information System Analysis and Design

This report provides an analysis and design of the hospital information system. It identifies and gives a brief description of all the use cases involved in the hospital information system, it depicts the entities and processes involved in the hospital information system through a context diagram and a level 0 dataflow diagram, it identifies all the entities, with attributes and relationships, involved in the hospital information system’s database through an entity relationship diagram, it categorizes all the processes in the hospital information system as create, read, update or delete through the CRUD diagram and discusses the benefits of using DevOps in the development of the hospital information system.

Name
University
Course
Instructor

Table of Contents
Introduction...............................................................................................................................................3
Patient Registration Use case....................................................................................................................4
Use case description for patient registration use case.........................................................................4
Patient login use case.................................................................................................................................6
Use case description for patient login...................................................................................................6
Use case description for emergency patient registration....................................................................9
Store management use case.....................................................................................................................11
Use case description for store management use case........................................................................11
E-Prescription use case...........................................................................................................................13
Use case description for E-prescription use case...............................................................................13
Viewing patient medical records use case..............................................................................................15
Use case description for viewing patient medical records................................................................15
Hospital information system context Diagram......................................................................................17
Level 0 Data flow diagram for hospital information system................................................................18
Entity Relationship Diagram for hospital information system database............................................19
CRUD diagram for the hospital information system processes...........................................................20
Details of individual group member’s contribution..............................................................................21
Individual discussion on how Hospital Information system project would be done using DevOps. .21
Benefits of DevOps..............................................................................................................................22
Conclusion................................................................................................................................................22
References................................................................................................................................................23
2

Introduction
This report is an analysis and design of the hospital information system. It identifies and gives a
brief description of all the use cases involved in the hospital information system, it depicts the
entities and processes involved in the hospital information system through a context diagram and
a level 0 dataflow diagram, it identifies all the entities, with attributes and relationships, involved
in the hospital information system’s database through an entity relationship diagram, it
categorizes all the processes in the hospital information system as create, read, update or delete
through the CRUD diagram and discusses the benefits of using DevOps in the development of
the hospital information system.
3

Patient Registration Use case with reference to (Ibrahim et.al; 2010) and (Ibrahim et.al; 2011)
Use case description for patient registration use case with reference to (Sinha et.al; 2009) and
(Somé, 2009)
Use case name Patient registration
Participating Actors Patient
Flow of events 1. A patient visits the home page of the
hospital information system and
prompts the system for a registration
platform
2. The system displays the patient
4

registration form and prompts the
patient to enter details.
3. The patient enters registration details
4. The system validates the values
entered by the Patient. When the
values are not valid the system
prompts the patient to reenter values.
When the values are valid the system
displays a registration success
message.
Entry Condition A patient prompts the hospital information
system for the patient registration form
Exit Condition The system displays the patient has been
successfully registered.
Quality Requirements The Patient gets registered successfully.
5

Patient login use casewith reference to (Ibrahim et.al; 2010) and (Ibrahim et.al; 2011)
Use case description for patient loginwith reference to (Sinha et.al; 2009) and (Somé, 2009)
Use case name Patient Login
Participating Actors Patient
Flow of events 1. A patient visits the home page of THE
hospital information system and
prompts the system for a login form.
2. The system displays the login form
3. The patient enters login credentials
4. The system authenticates the patient
login credentials. If the patient login
credentials are wrong the system
displays wrong credentials message
6

and prompts the patient to reenter his
or her login credentials. If the patient
login credentials are correct, the
system logs the patients in.
Entry Condition The patient prompts the system for the login
form.
Exit Condition The patient is logged in.
Quality Requirements The system logs in the patient with correct
login credentials and does not log in the one
with the wrong login credentials.
7

8

Use case description for emergency patient registrationwith reference to (Sinha et.al; 2009)
and (Somé, 2009)
Use case name Emergency Patient Registration
Participating Actors Administrator
Flow of events 1. The administrator accesses the admin
login webpage.
2. The login webpage prompts the admin
to enter his or her login credentials.
3. Admin enters his or her login
credentials; username and password.
4. The system authenticates the validity
of the login credentials entered by the
admin. If the login credentials are
wrong the system displays an error
message and prompts the admin to
reenter login credentials. If the login
credentials are correct the system logs
in the admin.
5. Once logged in the admin clicks on
the manage user menu item.
6. The system displays the manage user
webpage
7. Admin clicks on the add user button.
8. The system displays the emergency
user registration webpage and prompts
the admin to enter patient registration
details.
9. Admin enters the patient registration
details.
10. The system validates the values
entered by the admin. If the values are
9

not valid the system displays an error
message and prompts the admin to
reenter values. If the values are correct
the system displays a registration
success message and saves the patient
details in the patient table.
Entry Condition Admin clicks on the add user button in the
manage user webpage.
Exit Condition The system displays the registration success
message and saves patient details in the
patient table.
Quality Requirements The system registers the patient in the
emergency
Store management use casewith reference to (Ibrahim et.al; 2010) and (Ibrahim et.al; 2011)
10

Use case description for store management use casewith reference to (Sinha et.al; 2009) and
(Somé, 2009)
Use case name Store management
Participating Actors Admin
Flow of events 1. Admin logs in to the system
2. Admin clicks on the manage store
menu item in the administrator home
page.
3. The system displays the manage store
webpage
4. The system displays the medical
products in stock and those out of
stock. The system displays the
medical products that are being
11

consumed slowly.
5. Admin deduces and inputs the order
quantity for medical products out of
stock.
6. The system saves the order quantity
and products that are being consumed
slowly.
Entry Condition Admin clicks on the manage store menu item
in the admin home page.
Exit Condition The system saves the order quantity for
medical products out of stock and keeps a
record of the medical products that are being
consumed slowly.
Quality Requirements The system displays medical products in
stock and those out of stock.
The system displays medical products that
are consumed slowly.
12

E-Prescription use casewith reference to (Ibrahim et.al; 2010) and (Ibrahim et.al; 2011)
Use case description for E-prescription use casewith reference to (Sinha et.al; 2009) and
(Somé, 2009)
Use case name E-Prescription
Participating Actors Patient and Physician
Flow of events 1. A patient logs into the system
2. The patient clicks on the E-
Prescription request menu item.
3. The system displays the E-prescription
request webpage and prompts the
patient to enter prescription request
details.
13

4. The system validates the E-
prescription request details entered by
the patient and saves the details.
5. A physician logs into the system.
6. The physician views the prescription
requests made by his or her patients
and makes a prescription according to
the symptoms of the patient.
7. The system saves the prescriptions
made by the physician.
8. The patient views the prescription
made by the Physician.
Entry Condition Patient clicks on the E-Prescription request
menu item
Exit Condition The patient views the prescriptions made by
his or her Physician
Quality Requirements A patient can successfully make an E-
prescription request.
A physician can successfully view E-
Prescription requests and make a prescription
A patient can view the prescription made by
his or her physician.
Viewing patient medical records use casewith reference to (Ibrahim et.al; 2010) and (Ibrahim
et.al; 2011)
14

Use case description for viewing patient medical recordswith reference to (Sinha et.al; 2009)
and (Somé, 2009)
Use case name Viewing patient medical records
Participating Actors Patient and Physician
Flow of events 1. A patient logs into the system
2. Once logged in the patient clicks on
the Electronic medical records menu
item.
3. The system displays the electronic
medical records webpage.
4. The system allows the patient to only
view his or her medical records.
5. The patient views his or her medical
15

records
6. A physician logs into the system
7. Once logged in the physician clicks on
the electronic medical records menu
item.
8. The system displays the electronic
medical records webpage and allows a
physician to view and edit his or her
patient’s medical record.
9. The physician views and edits his or
her patient’s electronic medical
records
Entry Condition A patient or a physician clicks on the
electronic medical records menu item
Exit Condition A patient views his or her electronic medical
records
A physician views and edits his or her
patient’s electronic medical records.
Quality Requirements A patient successfully views his or her
electronic medical records
A physician successfully views and edits his
or her patient’s electronic medical records.
Hospital information system context Diagramwith reference to (Li, and Chen, 2009)
16

The hospital information system has three entities; patient, physician, and administrator. The
patient can perform the following within the hospital information system; register for an account,
log into his or her account, view his or her medical records electronically, request for an
electronic prescription, and view the electronic prescriptions made by his or her physician. A
physician can perform the following tasks within the hospital information system; log in, view
and edit patient electronic medical records, and view and respond to the electronic prescription
requests made by his or her patients. An administrator can perform the following tasks within the
hospital information system; log in, register a patient in the emergency, and view and manage
store details.
17

Level 0 Data flow diagram for hospital information systemwith reference to (Li, and Chen,
2009)
Within the hospital information system, there are five subsystems; registration subsystem, login
subsystem, E-prescription subsystem, Electronic medical records subsystem and the store
management subsystem. The registration subsystem is accessed by patients and the admin. A
patient access it when registering for an online account and an admin accesses it when
registering a patient in an emergency. The login subsystem is accessed by a patient, a physician,
and an admin. The electronic prescription subsystem is accessed by a patient and a physician. A
patient access it when requesting for an electronic prescription and when viewing the
prescriptions made by his or her physician. The physician accesses it to view patient prescription
requests and make prescriptions.
The electronic medical records subsystem is accessed by a patient and a physician. A patient
access it to view his or her electronic medical records whereas a physician accesses it to view
and edit the electronic medical records for his or her patients. The store management subsystem
is accessed by the admin. The admin accesses the store management subsystem to view the
medical products in stock, the medical products out of stock and the medical products being
18

consumed slowly. The admin also deduces the order quantity for the medical products out of
stock with the help of the store management subsystem.
Entity Relationship Diagram for hospital information system databasewith reference to (Al-
Masree, 2015)
Hospital information system database has six entities; patient, medical record, admin, medical
product, physician, and electronic prescription. The patient entity has eight attributes; patientID,
PatientName, Phone, Location, Username, Password, MedicalrecordID, and PhysicianID.
PatientID is a primary key whereas MedicalrecordID and PhysicianID are foreign keys. The
physician entity has three attributes; PhysicianID, PhysicainName, and Department. PhysicianID
is the primary key. The medical record entity has three attributes; MedicalrecordID,
RecordName, and PhysicianID. The MedicalrecordID is the primary key whereas the
PhysicianID is the foreign key.
The electronic prescription entity has five attributes; E-prescriptionID, prescription details,
symptoms, patientID, and the physicianID. E-prescriptionID is the primary key whereas
patientID and PhysicianID are foreign keys. Admin entity has three attributes; AdminID,
AdminName, and PatientID. AdminID is the primary key whereas the PatientID is the foreign
19

key. The medical product entity has three attributes; ProductID, ProductName, and AdminID.
ProductID is the primary key whereas Admin is the foreign key.
The relationship between an administrator and a patient is one to many. One administrator can
register many patients in the emergency section (Li, and Chen, 2009). The relationship between
an administrator and a medical product is one to many. One administrator can manage many
medical products. The relationship between a physician and a patient is one to many. One
physician can serve many patients. The relationship between a physician and the electronic
encryption is one to many. One physician can view and give many electronic prescriptions to
patients. The relationship between a patient and an electronic medical record is one to one. One
patient can only have one electronic medical record in the hospital information system. The
relationship between a patient and an electronic prescription is one to many. One patient can
make and get many electronic prescriptions from his or her physician.
CRUD diagram for the hospital information system processes.
Process
Entity
Patient
Registration
E-
Prescription
Request
E-
Prescription
Update
Medical
Product
management
Medical
Record
Manage
users
Patient C C R
Physician R, U R, U
Admin C C,R,U,D C,R,U,D
CRUD diagram is a Create, Read, Update, Delete diagram (Khan, and Hoque, 2012). It depicts
the business processes that create a record in a database, read the database, updates the database,
and those that delete records in a database (Torim, 2012). Patient registration is a create business
processes because it creates a record of a new patient. The registration process is either done by
the patients or the admins for patients in the emergency section. The electronic prescription
request is a create business process because it creates a record of a new prescription request. This
is done by a patient. The electronic prescription update is a read and update process. The
physician reads the prescription requests made by his or her patients and updates their
prescriptions based on the requests.
20

Medical product management is a create, read, update and delete business process. An admin
can; create a record for a new medical product, read the medical product details saved in the
database, update records for the medical products available, and delete medical products records
in the database. Manage users is a create, read, update and delete business process. An admin
can; register a new patient in the emergency section, read patient registration details from the
system, update the patient and other users’ registration details, and delete patient registration
details or accounts they hold.
Details of individual group member’s contribution
Tasks were divided amongst the members of the group.
Member one was responsible for the identification, drawing, and description of the use case
diagrams.
Member two was responsible for the drawing of the context diagram, data flow diagrams, and
the brief description of what they represent.
Member three was responsible for developing the entity relationship diagram, depicting the
attributes of the entities and the relationship between entities.
Member four was responsible for depicting the types of business processes in the hospital
management system through the CRUD diagram.
The website design was a combined effort of all the group members involved in the group.
Individual discussion on how Hospital Information system project would be done using
DevOps
DevOps is an integration of software development and information technology (Ebert et.al;
2016). It also involves a team of developers being combined to have a single workforce directed
towards the development of a project.
Member 1
DevOps will have a system analyst, a programmer, a content writer, and the stakeholders
working together in a combined effort to fasten the development process. The team of
developers; system analyst, programmer, content writer, and the stakeholders work together from
the requirement analysis phase, to design phase, to coding phase, to testing phase and finally to
the implementation phase of the hospital information system. Through DevOps, the development
21

team would be able to attain system quality and best security with the hospital information
system.
Faster development. Using DevOps will quicken the software development life cycle to realize a
fully functional hospital information system in the shortest time possible.
Member 2
DevOps would put together the team involved in the development of the Hospital Information system
for better communication, task assignment and responsibility. Each of team players would perform his
or her role in the development; a system analyst to analyze the system requirements, a programmer
perform the coding of the system and the stakeholders provide resources.
Improved system security. With the use of DevSecOps, the team of developers can implement a
system with effective and efficient security (Riungu-Kalliosaari et.al; 2016).
Member 3
The development of hospital information system would be faster with the use of DevOps. All the team
players the system analyst, the programmer, the team leader and the stakeholders will perform their job
in close collaboration with other team players. DevOps will be fast, efficient, effective and would boost
the security of HIS.
Accelerated releases of hospital information system modules and updates (Gottesheim, 2015).
Through DevOps, a team of developers can release new features and fix errors in the hospital
information system. This would improve the hospitals’ competitive advantage.
Member 4
The team players work in close collaboration and communication with each other. The system analyst
would acquire most if not all of the hospital information system when working closely with stakeholders.
The frequent releases will also enable the programmers to capture all the requirements provided by the
system analyst and the stakeholders. Therefore the development of HIS utilizing DevOps would quicken
the software development life cycle.
Enhanced collaboration. DevOps has philosophies that value responsibility, accountability and,
communication. Each and every team player whether a system analyst, a programmer or a
content writer will be responsible and accountable for his or her tasks. Communication is also
key for team players.
22

Benefits of DevOps
Faster development. Using DevOps will quicken the software development life cycle to realize a
fully functional hospital information system in the shortest time possible.
Improved system security. With the use of DevSecOps, the team of developers can implement a
system with effective and efficient security (Riungu-Kalliosaari et.al; 2016).
Accelerated releases of hospital information system modules and updates (Gottesheim, 2015).
Through DevOps, a team of developers can release new features and fix errors in the hospital
information system. This would improve the hospitals’ competitive advantage.
Enhanced collaboration. DevOps has philosophies that value responsibility, accountability and,
communication. Each and every team player whether a system analyst, a programmer or a
content writer will be responsible and accountable for his or her tasks. Communication is also
key for team players.
Conclusion
Use of DevOps philosophy is the best way to implement the hospital information system.
DevOps puts together the efforts of different team players and channels it as a single effort
towards a faster implementation of the hospital information system. This enhances collaboration
and communication among the team of developers, enhances system security, enable faster
development, and accelerated module releases, and values system quality.
23

References
Al-Masree, H.K., 2015. Extracting Entity Relationship Diagram (ERD) from relational database
schema. International Journal of Database Theory and Application, 8(3), pp.15-26. Jordan.
Mutah University.
Ebert, C., Gallardo, G., Hernantes, J. and Serrano, N., 2016. DevOps. Ieee Software, 33(3),
pp.94-100. University of Navarra. IEEE
Gottesheim, W., 2015, February. Challenges, benefits and best practices of performance focused
DevOps. In Proceedings of the 4th International Workshop on Large-Scale Testing (pp. 3-3).
NY, USA. ACM.
Ibrahim, N., Ibrahim, R., Saringat, M.Z., Mansor, D. and Herawan, T., 2010, October. On well-
formedness rules for UML use case diagram. In International Conference on Web Information
Systems and Mining (pp. 432-439). Springer, Berlin, Heidelberg.
Ibrahim, N., Ibrahim, R., Saringat, M.Z., Mansor, D. and Herawan, T., 2011, April. Definition of
Consistency Rules between UML Use Case and Activity Diagram. In International Conference
on Ubiquitous Computing and Multimedia Applications (pp. 498-508). Springer, Berlin,
Heidelberg.
Khan, S.I. and Hoque, A.L., 2012, December. Scalability and performance analysis of CRUD
matrix based fragmentation technique for distributed database. In 2012 15th International
Conference on Computer and Information Technology (ICCIT)(pp. 567-562). Chittagong,
Bangladesh. IEEE.
Li, Q. and Chen, Y.L., 2009. Data flow diagram. In Modeling and Analysis of Enterprise and
Information Systems (pp. 85-97). Springer, Berlin, Heidelberg.
Li, Q. and Chen, Y.L., 2009. Entity-relationship diagram. In Modeling and Analysis of
Enterprise and Information Systems(pp. 125-139). Springer, Berlin, Heidelberg.
Riungu-Kalliosaari, L., Mäkinen, S., Lwakatare, L.E., Tiihonen, J. and Männistö, T., 2016,
November. DevOps adoption benefits and challenges in practice: a case study. In International
Conference on Product-Focused Software Process Improvement (pp. 590-597). Springer, Cham.
24

Sinha, A., Paradkar, A., Kumanan, P. and Boguraev, B., 2009, June. A linguistic analysis engine
for natural language use case description and its application to dependability analysis in
industrial use cases. In 2009 IEEE/IFIP International Conference on Dependable Systems &
Networks (pp. 327-336). Portugal. IEEE.
Somé, S.S., 2009. A Meta-Model for Textual Use Case Description. Journal of Object
Technology, 8(7), pp.87-106. Canada. University of Ottawa.
Torim, A., 2012. A visual model of the CRUD matrix. Inf. Model. Knowl. Bases, 23(237),
pp.313-320. Tallin, Estonia. IOS Press.
25