TAJAMAL HAYAT FA20-BCS-083 SEC

List Of Contents
CH#01 ............................................................................................................................................................ 2
Hospital Management System .................................................................................................................. 2
Introduction .............................................................................................................................................. 2
1.1 Problem Statement ........................................................................................................................... 3
1.2 Scope ................................................................................................................................................. 3
1.3 Process Model ................................................................................................................................... 3
CH#02 ............................................................................................................................................................ 3
Required Engineering process .................................................................................................................. 3
2.1 Functional Requirements .................................................................................................................. 3
2.1.1 Undertaking various registration................................................................................................ 3
2.1.2 Check out .................................................................................................................................... 4
2.1.3 Generating various reports......................................................................................................... 4
2.1.4 Database ..................................................................................................................................... 4
2.2 Non-functional requirements ........................................................................................................... 4
2.2.1 Security ....................................................................................................................................... 4
2.2.2 Performance ............................................................................................................................... 4
2.2.3 Maintainability............................................................................................................................ 4
2.2.4 Reliability .................................................................................................................................... 5
CH#03 ............................................................................................................................................................ 5
Required Model ........................................................................................................................................ 5
3.1 Context Model................................................................................................................................... 6
3.2 Interactional Model........................................................................................................................... 6
3.2.1 Use Case Model .......................................................................................................................... 6
3.2.1 Sequence Model ......................................................................................................................... 8
3.3 Data Flow Diagram ............................................................................................................................ 8
3.3.1 Zero Level ................................................................................................................................... 9
3.3.2 One Level .................................................................................................................................... 9
3.3.3 Second Level ............................................................................................................................. 11
CH#04 .......................................................................................................................................................... 15
Architecture Design ................................................................................................................................ 15
4.1 ER Diagram ...................................................................................................................................... 15
TAJAMAL HAYAT FA20-BCS-083 SEC

List of Figures
Figure 1 process model ................................................................................................................................. 3
Figure 2context diagram ............................................................................................................................... 6
Figure 3Use case diagram ............................................................................................................................. 7
Figure 4 Sequence diagram........................................................................................................................... 8
Figure 5 Level 0 DFD...................................................................................................................................... 9
Figure 6level 1 DFD ..................................................................................................................................... 10
Figure 7Level 2 REG..................................................................................................................................... 11
Figure 8Level 2 Login................................................................................................................................... 12
Figure 9 Level Appointment ........................................................................................................................ 13
Figure 10level 2 ADD Prescription .............................................................................................................. 14
Figure 11 ER Diagram .................................................................................................................................. 15

CH#01

Hospital Management System

Introduction
My project Hospital Management system includes registration of patients, storing their
disease details into the system. My software has the facility to give a unique id for every patient
and stores the details of every patient. The Hospital Management System can be used by entering
respective username and password. It is accessible either by an administrator or receptionist. Only
the respective person can add data in the database. The data can be retrieved easily. The interface
is very user-friendly. The data are well protected and data processing is very fast, accurate and
relevant.
TAJAMAL HAYAT FA20-BCS-083 SEC

1.1 Problem Statement

A hospital management system is a software designed to manage all the areas of a hospital
such as medical, financial, administrative and the corresponding processing of services.
1.2 Scope
Daily functions like patient registration, managing admission and overall management of
various departments can be easily performed with higher accuracy after the installation of hospital
software. The modules of hospital management software are user-friendly and easy to access.

1.3 Process Model

Hospital Management System follows INCREMENTAL MODEL because initially software
requirements are reasonably well defined but the overall scope of development effort is a purely linear
process.

Figure 1 process model

CH#02
Required Engineering process

2.1 Functional Requirements

Hospitals have various types of functional requirements from patient registration, to scheduling
consultations, to report generation. HMS helps in several functional requirements of a hospital, a few of
which are as follows.
2.1.1 Undertaking various registration
HMS is able to facilitate various registration needs in a hospital. The system not only records
all relevant information about the patient but also assigns a specific ID that uniquely identifies the
individuals throughout the patient lifecycle in the hospital. This essentially means the operators in all
subsequent departments, say diagnostics, IPD registration, physiotherapy or rehabilitation care, pharmacy,
TAJAMAL HAYAT FA20-BCS-083 SEC
etc need not again record patient data but retrieve the information from the unique ID. This helps in uniquely
integrating the entire treatment lifecycle, health data, and information pertaining to an individual
automatically, thereby building transparency, reducing redundant and cyclical activities, infusing
efficiency, and saving time and money by automating processes.
2.1.2 Check out
Similarly, during checkout, the HMS helps healthcare facilities in ensuring all formalities and
commitments from hospitals to patients and vice versa are fulfilled. It thereafter is able to close the case
during the checkout of patients. Hospitals can choose either of the two options: The first is that they can
close the case during checkout but keep the patient ID intact and retrieve the ID and information in a follow-
up visit. Or they can choose to delete the ID altogether and generate a new ID on a fresh visit.
2.1.3 Generating various reports
Hospitals need to generate various reports which include those that are related to patients and those
that are pertaining to administration. By integrating all information flow and data recording through HMS,
the generation of various reports becomes rather easy. HMS, therefore, helps record relevant information
and relays them as per need, helping both treatments of patients and administration of hospitals.
2.1.4 Database
HMS helps in maintaining the database of patient information and health data in a transparent,
secure, and accurate way. It makes recording and storage of the information rather easy. The platform
facilitates almost instantaneous retrieval of data when required.
2.2 Non-functional requirements
Every hospital has some non-functional requirements, such as security, performance, maintenance,
reliability, and so on. These are essential aspects of the entire healthcare delivery ecosystem, as they are
not limited to one or few functions but are overarching requirements. HMS is able to cater to these non-
functional requirements as well.
2.2.1 Security
HMS oversees humongous volumes of data generation, information exchange, storage, and analysis
at every level of hospital functioning. As it is based on Cloud and other advanced digital technologies, it
offers strong, multi-layered security to all data exchanges, and thereby protects the system from misuse or
loss of information. The HMS platforms usually comply with the most stringent data security and privacy
policies set in a country. As HMS is hosted on Cloud-based servers which are located away from the
premises, it remains protected from cyberattacks on hospital systems. Overall HMS promotes transparency,
protects the confidentiality, prevents data theft, and offers a safe and secure ecosystem for hospitals
operations to continue.
2.2.2 Performance
By streamlining and integrating multiple processes, HMS infuses much speed, agility, and
efficiency into the system. The platform has specially designed modules for various functions such as OPD
management, IPD management, Cath Lab and diagnostics management, emergency care response, billing
and payments, and operations. It has the ability to offer role-based control to users to allow them the use of
one part of the function or multiple functions and help them monitor and track every activity necessary for
healthcare delivery. Due to such intra-operability and flexible properties, HMS boosts the performance and
capabilities of a healthcare facility in treating patients.
2.2.3 Maintainability
Good HMS technologies are easy to maintain. They are usually SaaS-based platforms that can be
upgraded and improved upon remotely without hindering the daily activities of hospitals. Its maintenance
activities can be pre-scheduled in parts considering when the activity is lowest, and it doesn’t take long to
upgrade.
TAJAMAL HAYAT FA20-BCS-083 SEC

2.2.4 Reliability
Being software as a service, HMS is highly resilient to any technology disruptions, downtime, or
crashes experienced by other technology systems. It has a certain capacity to work offline. It is highly secure
from a data safety point of view. Furthermore, good HMS has a highly instinctive and intelligent user
interface which makes them convenient to use.

CH#03

Required Model
TAJAMAL HAYAT FA20-BCS-083 SEC

3.1 Context Model

Figure 2context diagram

3.2 Interactional Model

3.2.1 Use Case Model

TAJAMAL HAYAT FA20-BCS-083 SEC

Figure 3Use case diagram

TAJAMAL HAYAT FA20-BCS-083 SEC

3.2.1 Sequence Model

Figure 4 Sequence diagram

3.3 Data Flow Diagram

Its three types

 0 Level
 1 level
 2 level
TAJAMAL HAYAT FA20-BCS-083 SEC

3.3.1 Zero Level

Figure 5 Level 0 DFD

3.3.2 One Level

TAJAMAL HAYAT FA20-BCS-083 SEC

Figure 6level 1 DFD

TAJAMAL HAYAT FA20-BCS-083 SEC

3.3.3 Second Level

Figure 7Level 2 REG

TAJAMAL HAYAT FA20-BCS-083 SEC

Figure 8Level 2 Login

TAJAMAL HAYAT FA20-BCS-083 SEC

Figure 9 Level Appointment

TAJAMAL HAYAT FA20-BCS-083 SEC

Figure 10level 2 ADD Prescription

TAJAMAL HAYAT FA20-BCS-083 SEC

CH#04

Architecture Design

4.1 ER Diagram

Figure 11 ER Diagram
TAJAMAL HAYAT FA20-BCS-083 SEC