Bahir Dar University

Bahir Dar Institute of Technology

Faculty of Computing

Industrial project on Hospital Management System

for Addis Alem Hospital

Submitted to the faculty of computing in partial fulfillment of the requirements for the
degree of Bachelor of Science in software engineering
Group members

Name ID Number

1. KIDUS MARU BDU1102176

2. REDIET GASHAW BDU1108686

3. MEBRATU AWOKE BDU1102274

Advisor ፡ Mr. Tadele Mengistu

[2015]

Bahir Dar University, Bahir Dar Institute of Technology

i
 Declaration

The Project is our own and has not been presented for a degree in any other university and
all the sources of material used for the project have been duly acknowledged.

KIDUS MARU
Name Signature

REDIET GASHAW
Name Signature

MEBRATU AWOKE
Name Signature
Faculty: Computing

Program: Software Engineering

Project Title: Hospital Management System for Addis Alem Hospital

This is to certify that I have read this project and that in my supervision and the students’
performance, it is fully adequate, in scope and quality, as a project for the degree of Bachelor of
Science.

TADELE MENGISTU

Name of Advisor Signature

Examining committee members Signature Date

1. Examiner1 ___________________
2. Examiner2 __________________
Roles and Responsibilities of the Group Members
Task List of members

Kidus Maru Rediet Gashaw Mebratu Awoke


Requirement 
gathering
Analysis  
Design  

Implementation  

Testing  

iii
Acknowledgement
First of all, would like to thanks to God for the success of this project. Next to that project
team would like to thanks to our advisor (instructor) Mr. Tadele Mengistu for this valuable
guidance, unreserved advance and constructive comment through the project without any
hesitate and encouragement given to us would be realized and also the project team would
like to extend our gratefulness to Addis Alem hospital officers who greatly help us in
providing information considering the existence system and give us special orientation
about how the service in the Addis Alem hospital management is done.
Acronyms
AAHPMS: Addis Alem Hospital Management System
DBMS: Database Management System
MRN: Medical Record Number
OPD: Out Patient Department
PRPFHI: Palliative, Rehabilitative and Pain Free Hospital Initiative
UML: unified modeling language

v
Table of Figure
FIGURE 1.1 ORGANIZATION STRUCTURE OF ADDIS ALEM HOSPITAL .................................................................................................................. 9

FIGURE 2.1 SYSTEM USE CASE DIAGRAM FOR ADDIS ALEM HOSPITAL MANAGEMENT SYSTEM ................................................................ 15

FIGURE 2.2 USER INTERFACE PROTOTYPE .................................................................................................................................................................. 28

FIGURE 2.3 STATE DIAGRAM FOR DOCTOR IN HOSPITAL MANAGEMENT SYSTEMS FOR ADDIS ALEM HOSPITAL................................... 29

FIGURE 2.4 STATE DIAGRAM FOR PATIENT IN WEB-BASED HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM HOSPITAL ............. 30

FIGURE 2.5 ACTIVITY DIAGRAM FOR LOGIN .............................................................................................................................................................. 31

FIGURE 2.6 ACTIVITY DIAGRAM FOR MANAGE DRUG ............................................................................................................................................. 32

FIGURE 2.7 ACTIVITY DIAGRAM FOR MAKE PATIENT APPOINTMENT ................................................................................................................. 33

FIGURE 2.8 ACTIVITY DIAGRAM MANAGE EMPLOYEE ............................................................................................................................................ 34

FIGURE 2.9 ACTIVITY DIAGRAM TO REGISTER PATIENT ......................................................................................................................................... 35

FIGURE 2.10 ACTIVITY DIAGRAM TO REFER PATIENT.............................................................................................................................................. 36

FIGURE 2.11 ACTIVITY DIAGRAM TO LAB ORDER ..................................................................................................................................................... 37

FIGURE 2.12 ACTIVITY DIAGRAM TO PRESCRIBE DRUG .......................................................................................................................................... 38

FIGURE 2.13 SEQUENCE DIAGRAM FOR LOGIN .......................................................................................................................................................... 39

FIGURE 2.14 SEQUENCE DIAGRAM FOR SEND LAB RESULT .................................................................................................................................... 40

FIGURE 2.15 SEQUENCE DIAGRAM FOR GENERATE REPORT .................................................................................................................................. 40

FIGURE 2.16 SEQUENCE DIAGRAM FOR PATIENT APPOINTMENT .......................................................................................................................... 41

FIGURE 2.17 CLASS DIAGRAM OF HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM HOSPITAL............................................................ 42

FIGURE 2.17 CLASS DIAGRAM OF HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM HOSPITAL............................................................ 50

FIGURE 2.18 CONCEPTUAL CLASS DIAGRAM OF HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM HOSPITAL ................................. 50

FIGURE 3.1 SOFTWARE ARCHITECTURE FOR ADDIS ALEM HOSPITAL ................................................................................................................. 52

FIGURE 3.2 COMPONENT DIAGRAM OF ADDIS ALEM HOSPITAL MANAGEMENT SYSTEM .............................................................................. 53

FIGURE 3.3 DEPLOYMENT DIAGRAM OF HOSPITAL MANAGEMENT FOR ADDIS ALEM HOSPITAL................................................................ 54

FIGURE 3.4 DETAILED CLASS DIAGRAM OF HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM HOSPITAL ......................................... 56

FIGURE 3.5 ER DIAGRAM FOR ADDIS ALEM HOSPITAL ............................................................................................................................................ 56

FIGURE 3.6 USER INTERFACE FOR HOME PAGE ......................................................................................................................................................... 57

FIGURE 3.7 USER INTERFACE FOR PATIENT SIGNUP ................................................................................................................................................. 58

FIGURE 3.8 USER INTERFACE FOR LOGIN .................................................................................................................................................................... 59

FIGURE 3.9 USER INTERFACE FOR PATIENT REGISTRATION BY RECORD OFFICER .......................................................................................... 60
List of tables
TABLE 2.1 USE CASE DESCRIPTION FOR LOGIN PAGE .................................................................................. 16

TABLE 2.2 USE CASE DESCRIPTION FOR GENERATE REPORT PAGE .......................................................... 17

TABLE 2.3 USE CASE DESCRIPTION FOR MANAGE DRUG ............................................................................ 18

TABLE 2.4 USE CASE DESCRIPTION FOR MANAGE EMPLOYEE................................................................... 19

TABLE 2.5 USE CASE DESCRIPTION FOR REFER PATIENT ............................................................................ 19

TABLE 2.6 USE CASE DESCRIPTION FOR MAKE PATIENT APPOINTMENT ................................................ 20

TABLE 2.7 USE CASE DESCRIPTION FOR SUBMIT LAB ORDER .................................................................... 20

TABLE 2.8 USE CASE DESCRIPTION FOR VIEW LAB RESULT ....................................................................... 21

TABLE 2.9 USE CASE DESCRIPTION FOR DRUG PRESCRIPTION .................................................................. 21

TABLE 2.10 USE CASE DESCRIPTION FOR DISPENSE DRUG ......................................................................... 22

TABLE 2.11 USE CASE DESCRIPTION FOR VIEW DRUG PRESCRIPTION ..................................................... 22

TABLE 2.12 USE CASE DESCRIPTION FOR VIEW MEDICAL RESULT ........................................................... 23

TABLE 2.13 USE CASE DESCRIPTION FOR VIEW APPOINTMENT ................................................................. 23

TABLE 2.14 USE CASE DESCRIPTION FOR WRITE COMMENT ...................................................................... 23

TABLE 2.15 USE CASE DESCRIPTION FOR RECORD PATIENT....................................................................... 24

TABLE 2.16 USE CASE DESCRIPTION FOR MANAGE PATIENT DETAIL ...................................................... 25

TABLE 2.17 USE CASE DESCRIPTION FOR VIEW COMMENT ........................................................................ 25

TABLE 2.18 USE CASE DESCRIPTION FOR SEND LAB RESULT ..................................................................... 26

TABLE 2.19 USE CASE DESCRIPTION FOR VIEW HOSPITAL REQUEST FORM........................................... 26

TABLE 2.20 USE CASE DESCRIPTION FOR GENERATE PRICE LIST FOR PAYMENT ................................. 27

TABLE 2.21 USE CASE DESCRIPTION FOR ORDER BILL FOR PATIENT ....................................................... 27

TABLE 2.22 HARDWARE REQUIREMENTS IN HOSPITAL MANAGEMENT PROJECT FOR ADDIS ALEM

HOSPITAL ....................................................................................................................................................... 48

TABLE2.13 SOFTWARE REQUIREMENT IN HOSPITAL MANAGEMENT SYSTEM FOR ADDIS ALEM

HOSPITAL ....................................................................................................................................................... 49

TABLE 3.2 ACCESS CONTROL FOR ADDIS ALEM HOSPITAL ........................................................................ 61

vii
 Catalog
Declaration........................................................................................................................................................................................ ii
Roles and Responsibilities of the Group Members ..................................................................................................................... iii
Acknowledgement ...................................................................................................................................................................... iv
Acronyms ..................................................................................................................................................................................... v
Table of Figure............................................................................................................................................................................ vi
List of tables .............................................................................................................................................................................. vii
Abstract ....................................................................................................................................................................................... ix
CHAPTER ONE ............................................................................................................................................................................... 9
INTRODUCTION ............................................................................................................................................................................ 2
1.1 Background of the Project...................................................................................................................................................... 2
1.2 statement of the problem and justification ............................................................................................................................. 2
1.3 Objective of the project .......................................................................................................................................................... 3
1.4 Beneficiaries of project .......................................................................................................................................................... 4
1.5 Significance of project ........................................................................................................................................................... 4
1.6 Limitation of the project ........................................................................................................................................................ 5
1.7 System development Methodology ........................................................................................................................................ 5
1.8 Feasibility study .................................................................................................................................................................... 6
1.9 Scope of the project................................................................................................................................................................ 7
1.10 organization of the project .................................................................................................................................................. 9
CHAPTER TWO ............................................................................................................................................................................ 10
SYSTEM FEATURES ................................................................................................................................................................... 10
2.1 Existing system .................................................................................................................................................................... 10
2.2 Proposed system ................................................................................................................................................................. 11
2.3 Requirement Analysis .......................................................................................................................................................... 12
2.3.6 State Chart diagram ........................................................................................................................................................... 29
2.4 System Requirement ............................................................................................................................................................ 48
2.5 Key Abstraction with CRC Analysis.................................................................................................................................... 50
CHAPTER THREE ........................................................................................................................................................................ 51
SYSTEM DESIGN ......................................................................................................................................................................... 51
Introduction................................................................................................................................................................................ 51
3.1 Architectural Design ............................................................................................................................................................ 51
3.2. Design class Model ............................................................................................................................................................. 55
3.3 User Interface Design........................................................................................................................................................... 57
3.4 Access control and security .................................................................................................................................................. 60
CHAPTER FOUR .......................................................................................................................................................................... 62
IMPLEMENTATION ..................................................................................................................................................................... 62
4.1 Introduction:......................................................................................................................................................................... 62
4.2 Sample code: ........................................................................................................................................................................ 62
References ...................................................................................................................................................................................... 77
Appendix ........................................................................................................................................................................................ 78
 Abstract
When the project team investigates about the current system of Addis Alem hospital to
gathers information, project team have found some limitations with the existing system.
Those are the system use large usage of paper to record data which requires large space for
storage. The manual system that the hospital uses do not provide effective way to back up
data, as a result data can be permanently lost, damaged or misplaced. And also, it is
challenging and takes time to treat the patient with proper drug control because of
registration the patient data manually and moving the paper from one office to other and the
project team proposed to develop a system that solves the problem of the manual system.
These system record patient information that registered by record officer and by patients
themselves into database and the system also allows doctors to see histories of patient
repeatedly and it helps the doctor to change medicine for the patient from the recorded
history online. The proposed system allow patients to write comment about hospital
activity. To develop this system the project team used Iterative development model starting
from requirement phase, analysis and design phase, implementation and test phase and
review phase. Each phase guided the project team in the development of the project and
helped them to organize the work flow of each task. The development and implementation
of hospital management system for the Addis Alem hospital is beneficial for the patients
and for the employees who work at the hospital.

ix
 CHAPTER ONE

INTRODUCTION

1.1 Background of the Project

Addis Alem hospital was established in July 10/2007 E.C in Bahirdar city at Atse Tewodros
sub-city. The hospital had only few employees due to lack of workers every task of the
hospital was done by a few employees. Now a day the hospital has many employees. It
gives many activities for patients for example give drugs and treatments. The hospital has
no computerized system currently many activities are done manually.
The proposed hospital management system is designed for registering and managing of
patient records with easy access of record. The system will be used to assist the registered
lab technician, doctor, pharmacist, cashier, record officer and manager to store and manage
patient records in a hospital for easier access and reference. In the current system all these
activities are done manually and would be challenging for the employees. Therefore, there
is a need of an efficient and easy way to use management software that will help ease the
workload on employees in the hospital. The disadvantage of storing data manually is poor
handling of documents may lead to lose of data. The documents are not that much secure
and those documents have no back up once lost cannot be retrieved. Applying this system
in such institution will help to manage these records and preserve the information for long
period of time and also makes its access far much simpler and easier. it also ensures
accuracy and openness of the patient detail record.

1.2 statement of the problem and justification

While analyzing the overall working of the current hospital management system the project
team finds out many problems. These problems are: -
 Large space usage: use of paper to record growing amount of data requires large space
for storage over time and inefficient back up method.
 The current system specially doesn’t provide effective way to back up data and as a
result data can be permanently lost when data is damaged or misplaced.
 It takes time to treat the patient because moving paper based recorded data from one
office to another and also the information generated by various transactions takes time
and efforts to be stored at right place.
 The current system exposed to lack of security for the records, anyone may disarrange
the records of the patient card or patient’s history.
 The information is very difficult to retrieve and finding particular information like
finding out about the patient’s history is very tedious.
 The patient waste their time by waiting record officer to register their data and this may
lead to queuing of patients in record officer room and don’t get service quickly as they
arrive in the hospital.

1.3 Objective of the project

1.3.1 General objective

The general objective of this project is to develop hospital management system for Addis
Alem hospital.

3
1.3.2 Specific objective
 Study the existing manual system major functions and problem.
 Find out the functional and nonfunctional requirements.
 Design interactive user interface for Addis Alem hospital management system.
 Design database based up on analyzed data.
 Implement the proposed new system.
 Testing new system and make the required modification.

1.4 Beneficiaries of project

There are different bodies that will be benefited from this system. The main beneficiaries of
this system are listed below.
 Addis Alem hospital -get benefits from this project because the proposed system saves
cost that will be used manually.
 Lab technician: in the existing system it is hard for lab technicians to read the
handwriting of doctors and to send lab result for the doctors but by using this system the
project team solve these two problems by using this system.
 Pharmacist: like lab technicians it is hard for pharmacists to read the handwriting of
doctors so we provide online prescription to solve this.
 Doctors: they are the main beneficiaries of the system because the current system they
have load on ordering which patient should they serve first. The system help doctors to
prescribe drug for pharmacist and patient online.
 Patients: they are also beneficiaries of the system because system helps to register them
into the system for card to get queue before they go to the hospital or when they are at
home.

1.5 Significance of project

The hospital management system will improve hospital service for both employees and the
patients. The project is significant to employees since they would be able to register, update
delete and search information within the system. It is beneficial to the hospital since it could
improve their management through connecting all the existing computers in one system.
The project is important to the hospital patients since they could have medical information
without experiencing delays and incorrect information. If they wanted to access their
medical history they would not be going through a difficult process. For the doctors they
can view medical history of patient in this case.

1.6 Limitation of the project

Due to some constraint of time, resource and other external factor the project team should
not include some of the following functionality of the project.
 The project doesn’t include alert when various diseases occur more frequently on
patient to consider as epidemic.
 This system only works for outpatient department (OPD).
 The project doesn’t include human resource and facility management components.

1.7 System development Methodology

1.7.1 Requirement gathering methods

Project team collect relevant data from the organization is important tasks in determining
and analyzing the existing system. The data that project team need to develop the new
system are obtained from the following fact data gathering techniques.
Interview: to get the basic information about the background of the current working system
we conducted interview to the manager and other staff of the officers. The project team asks
the manager some question. From those questions the project team is able to answer
questions like
A. what are the problems of Addis Alem hospital are facing now while getting service from
the hospital.
B. how do the hospital fix those problems
C. what are the employees’ role in the hospital and
D. How the hospital employees perform their activity in the current system.
Observation: to get additional information about how the current system works Project
team done observation. The project team observe prescription paper, patient card paper with
folder summary sheet, medical History sheet, hospital request form, hospital referrals form
health center abstract register form.

5
1.7.2 Analysis and Design methodology
We used object-oriented analysis and design methodology because Object-oriented analysis
and design (OOAD) allows effective management of software complexity by the virtue of
module. All the interfaces between the objects cannot be represented in a single diagram. It
can be upgraded from small to large systems at a greater ease than in systems following
structured analysis.
Our project team analyses and design this project using UML tools because UML is a visual
language that provides a way for us to construct, document, and visualize software systems.
These visual representations help us to better understand potential outcomes or errors in
programs, saving time and enhancing collaboration among team members. This project will
be conducted based on the Iterative Development method. Iterative methodologies provide
a cyclical approach to software development. There are many reasons why we use Iterative
Development Method for this project useful where requirements change to response
quickly. Allow more flexibility for changes to solve unforeseen problems.

1.7.3 Implementation Methodology

Our project team implements the design of hospital management system using different
tools such as: -
1. visual studio code
2. MySQL
3. Window 10 Operating system
4. HTML, CSS, REACT, REACT NATIVE
5. NODE
6. WEB BROWSER (Google Chrome. Firefox, Microsoft Edge)

1.8 Feasibility study

1.8.1 Economic feasibility

This project is economically feasible according to the problem because the system will
decrease the tangible and intangible cost .
Tangible benefit: result from both increasing income and decreasing expense like
equipment cost, man power.
Intangible benefit: the benefit that is not measured by money like job satisfaction. User
friendly system improves employee’s job satisfaction and also patient’s satisfaction.

1.8.2 Operational feasibility

The management supports the project and they can use effectively after it has been
developed. It is easy function. When the project is completed, the patients will get fast and
reliable information. So, the project is operationally feasible.

1.8.3 Schedule feasibility

Our project members have a good intention and motivation towards the work. so, the
project will be completed at specified date.

1.8.4 Technical feasibility

In order to combine the system and existing system the management should use expertise
and train employee.

1.9 Scope of the project

 This system is capable of managing recorded patient’s history by avoiding redundant and
invalid data.

 The system capable of recording drug details information with their expired date, dosage
amount and frequency of usage.

7
 The system capable of recording employ details information with their job and
specialization.

 The system able users to know the hospital working activity through the process they get,
the service they provide and about employee activity in patient treatment.

 This system is done only for outpatient department that means the system doesn’t include
ward (patients that take bed in the hospital) because of this we don’t include nurse in the
system.

 The system doesn’t include human resource administration and facility management
component in the hospital.
1.10 Organization of the project

figure 1.1 organization structure of Addis Alem hospital

9
 CHAPTER TWO

SYSTEM FEATURES

2.1 Existing system

In the current system of Addis Alem hospital everything is done manually.
1. First the patient goes to record officer class to get patient card.

2. The record officer gives patient card with card number by registering his/ her history and
delegate to triage room.

3. nurses in the triage measure temperature and pressure of patient and decide the room the
patient must go and delegate patient to doctor class and the patient goes to doctor room and
the porter receive the patients medical record from record officer and give to the doctor.

4. The doctor who treats the patient, ask the symptom, what the patient feels, the doctor decide
the disease and write patient history based on his/her record .

5. If the symptom needs lab test, the doctor will send the patient to laboratory for checkup
with lab hospital request form that has to be tested by the lab technician.

6. The lab technician test lab order and send back the result to doctor then the doctor check the
result and order medicine with prescription paper.

7. If the symptom doesn’t need lab test or if it’s known, the doctor will send the patient to
pharmacist to get medicine with prescription paper.

8. The patient gives the prescription paper to pharmacist then the pharmacist checks the paper
and give medicine to patient with command of how he/she takes medicine.

9. If the hospital finished the medicine which they were asked the pharmacist tell to manager
to order from store.

10. If the hospital can’t treat a patient or the patients are on critical condition the hospital writes
refer to Felegehiwot referral hospital.
2.2 Proposed system
Project team observes the existing system and proposes a hospital management System for
Addis Alem hospital. This proposed system has the following purpose: -

1. The system allows for doctors to order one or more lab tests for patients.

2. In the pharmacy page the system will allow for pharmacists to give one or more medicines
for patients when prescribed by the doctor and show the expired medicine in red color for
pharmacist to remove that medicine from the drug store.

3. The system provides chat box for doctors and patients to communicate with each other.

4. The system will allow for patients to register themselves and to get order or queue of cards
(ካ ር ድ ማዉጣት እ ና ወ ረ ፋ መያ ዝ ) before they go to the hospital or when they are at home.
That means minimize the workload for record officer.

5. The system provides interactive user interface for its users (easy to use).

6. The system provides appropriate notification for the system users.

7. The system has a mobile app interface for patients that want to use the system service.

8. The system has payment integration for patients to pay for the service they get to the
cashier’s of the hospital.

11
2.3 Requirement Analysis

2.3.1 Functional requirements

The new system achieves some functional requirement that must include in the system to
achieve objectives and help to create acceptable system by the patients and employees.
Functional requirement defines what the system supposed to do.
 Manager
The system allows the manager to manage employees.
The system allows the manager to add a price list for the service .
The system allows the manager to view written comment by patient in hospital activity and
employee

 Doctors
The system allows the doctor to make patient Appointment.
The system allows the doctor to refer patient.
The system allows the doctor to view lab report.
The system allows the doctor to make drug prescription.
The system allows the doctor to submit lab order
The system allows the doctor to view appointment for patient.

 Patient
The system allows the patient to view medical result.
The system allows the patient to view medical prescription.
The system allows the patient to view appointment day.
The system allows the patient to give comment for hospital activity and about employee.
The system allows the patients to communicate with the doctors using chat-box.
The system allows the patient to register themselves to get service from the hospital.

 Pharmacist
The system allows the pharmacist to view medical prescription.
The system allows the pharmacist to dispense drug.
 The system allows the pharmacist to generate report.

 Lab Technician
The system allows the Lab Technician to send lab result.
The system allows the Lab Technician to generate report.
The system allows the lab technician to view lab order

 Record Officer
The system allows for record officer to record patient.
The system allows the Record officer to manage patient
The system allows the Record officer to assign room for patients to doctor

 Cashier
The system allows the cashier to order invoice to payment.
The system allows the cashier to take payment.
The system allows the cashier to view payment history of patient.

2.3.2 Non-functional requirement

Nonfunctional requirement is requirement specified conceptual that can be used to manage
the system operation rather than specifying behaviors. Qualities of the nonfunctional
requirement can be
2.3.2.1 Performance: the system available for users 24 hours of a day and short response
time for a given task because it uses local connection so it does not fail connection by
overcrowded
2.3.2.2 Scalability: The system can be scalable to support growth in the number of
employees. The elapsed duration of time required to produce any statement or report
showing information about transactions shall be based upon how much data is presented
rather than the total quantity of stored data. The system is scalable to accommodate its use
by an unlimited number of farmers.
2.3.2.3 Availability: This system is available everywhere (where internet service reaches) and at
all times for those who have access to use the system.

2.3.2.4 Reliability: The performance of the system is good which will increase the
13
reliability of the service. The system deploys on server computers and systems allow
multiple clients to access the server at the same time.
The system has a backup procedure to maintain and secure data of the employer, researcher, and
others. The system can handle invalid inputs and display error messages to users. This system is
likeability to work without failure for a given time period.

2.3.2.5 Security:
Security requirement are important factors in this system as classified data/information will be
stored in the database. User validation will be done during login to ensure that the user is valid
and that the user only has access to his/her permitted information.

2.3.2.6 Maintainability: The system is easily maintained because it uses backup method to

 Accept the new requirement.

 Allow changing the format.

2.3.2.7 Accuracy:
The proposed system has better reduction of error. All data can fill correctly if it does not
the system will notify.
2.3.2.8 Accessibility: we must make sure that the system be accessible for all authorized
staff and not accessibility by anyone else who don’t have the privilege to access.

2.3.2.9 Usability:
The system is user friendly and self-explanatory.
The menu must be clear for user.
The system must have functionalities like (edit, delete, update, next, search)
The system must be able to store and retrieve patient information.
The system must be able to provide error message.
The system must have good arrangement of objects.
The system must be consistence (ex. Color and line size)
2.3.2.10 Interoperability: Interoperability refers to the ability to share and manage
information between computer devices and information systems within and across
organizational boundaries. This system is interoperable because it exchanges the information to
user and from the users through user interface.

2.3.3 System Use case

A use-case model is a model of how different types of users interact with the system to solve a
problem. The most important model elements are: use cases, actors and the relationships between
them. A use-case diagram is used to graphically depict a subset of the model to simplify
communications.

2.3.3.1 Use case diagram

Figure 2.1 system use case diagram for Addis Alem hospital management system

15
2.3.3.2 Use case Documentation
The following consecutive tables show the use case description for each use cases. Each table

contains the use case name, the actor which initiates and interacts with the use case,

Use case Id UC 01
Use case name Login
Participating actor Patient, lab technician, Doctor, Pharmacist, Manager,
Record Officer.
Pre-condition The user must have username and password
The login page contains the login form to be displayed
Basic course of action The user wants to login into the system.
The system displays the form.
The user enters username and password, click on login
button.
The system verifies that the user is eligible to login into
the system.
The user must login into the system.

Alternative course of action If user login name or password is invalid go to 3.

The system displays invalid user name or password
message.
The user continues to fill user name and password again
Table 2.1 use case description for login page
Use case Id UC 02

Use case name Generate report

Participating actor Manager, Doctor, pharmacist, lab technician

Pre-condition Login into the system

Basic course of action Manager, Doctor, lab technician or pharmacist want to

Generate Report
must click Generate Report link
The system display Report form.
Manager, Doctor, lab technician or pharmacist must
fill correctly the form.
Manager, Doctor, lab technician or pharmacist clicks
submit button.
Alternative course of action If the Manager, Doctor or pharmacist not select the
form go to 2.
The system does not display anything.
The Manager, Doctor, lab technician or pharmacist
must select report form.
Post-condition Reports are generated successfully to the manager.
Table 2.2 use case description for Generate Report page

17
Use case Id UC 03
Use case name Manage Drug
Participating actor Pharmacist
Pre-condition Login into the system
Extends -------register, delete and update drug, edit,
Basic course of action 1. Pharmacist want to add drug, delete drug, update drug
information must click to manage drug link.
2. The system display manage drug link.
3. The Pharmacist can perform add drug, delete drug, or
update drug information.
4. The Pharmacist must fill the form when add drug and
request drug.
5. Pharmacist must clicks submit button to add drug,
delete drug, or request drug.
Alternative course of action If the Pharmacist makes the form empty go to 3
The system displays please fill the form.
The Pharmacist continues to fill form correctly
Post-condition Message are generated as the action performed properly or
not
Table 2.3 use case description for Manage Drug

Use case Id UC 04
Use case name Manage Employee
Participating Actor Manager
Pre-condition Login into the system
Extends -------register, delete and update employee
Best course of action Manager want to manage Employee
manager must click Manage Employee link
The system display Manage Employee form.
Manager can perform delete Employee, add employee and
update employee information
When manager want to add Employee manager must fill
the form
Manager clicks Add or delete and update button to perform
the action.
Alternative course of action If the manager makes the form empty go to 3
The system displays please fill the form correctly
The manager continues to fill the form

Post-condition Message are generated as the action performed properly or

not
Table 2.4 use case description for Manage Employee

Use case Id UC 05

Use case name Refer Patient

Participating Actor Doctor

Pre-condition Login into the system
Best alternative action Doctor wants to refer Patient
click Refer Patient link
The system display form to Refer Patient
The Doctor fills the refer form correctly.
The Doctor must submit refer Patient button
Alternative course of Action The system displays please fill the form correctly
The Doctor continues to fill form again
Post-condition Refer submitted successfully

Table 2.5 use case description for Refer Patient

19
Use case Id UC 06
Use case name Make Patient Appointment
Participating Actor Doctor
Pre-condition Login into the system
Best course of action Doctor wants to make appointment
click Appointment link
The system display Appointment form
The Doctor must fill Appointment form.
The Doctor must click submit button
Alternative course of action If the Doctor make the Appointment form empty
The system displays please fill Appointment form
correctly
The Doctor continues to fill Appointment form Again
Post-condition Message are generated appointment submitted
successfully
Table 2.6 use case description for Make Patient Appointment

Use case Id UC 07
Use case name Submit lab order
Participating Actor Doctor
Pre-condition Login into the system
Best course of action Doctor wants to send lab order
click Send lab order link
The system display lab order
The doctor must fill lab order Form correctly.
The doctor must click submit button
Alternative course of action If the Doctor make the lab order Form empty
The system displays please fill the lab order Form
correctly
The doctor continues to fill the lab order Form
Post-condition Messages generated lab order submitted successfully
Table 2.7 use case description for Submit lab order
Use case Id UC 08
Use case name View Lab Result
Participating Actor Doctor
Pre-condition Login into the system
Best course of action Doctor wants to view Lab Result click Lab Result link
The system display lab result Form
The Lab result displayed
Alternative course of action If there is no Lab Result the Page Became Empty
space
Post-condition The System Generate there is no Lab Result
Table 2.8 use case description for View Lab Result

Use case Id UC 09
Use case name Drug Prescription
Participating actor Doctor
Pre-condition Login into the system
Best course of action Doctor wants to prescribe drug must click Drug
Prescription link.
The system display Drug Prescription form.
The Doctor fills the Drug Prescription form.
The Doctor must submit Drug Prescription.
Alternative course of action If the Doctor make Drug prescription forms empty go
to 2.
The system displays please fill Drug Prescription form
correctly
The Doctor continues to fill Drug Prescription form
again
Post –condition Messages are generated drug prescription done
successfully
Table 2.9 use case description for Drug Prescription

21
Use case Id UC 10
Use case name Dispense Drug

Participating actor Pharmacist

Pre-condition Login into the system
Best course of action To dispense Drug for patient Pharmacist must click
dispense Drug link.
The system display drug dispenses form.
The Pharmacist must fill the form.
Pharmacist clicks submit button.
Alternative course of action If the Pharmacist make the Dispense Drug form Empty go
to 2.
The system displays please fill the form correctly
The Pharmacist continues to fill the dispense Drug form
again
Post-condition Messages are generated as drug dispensed
Table 2.10 use case description for Dispense Drug

Use case Id UC 11
Use case name View Drug Prescription
Participating actor Pharmacist, patient
Pre-condition Login into the system
Best course of Action Pharmacist and patient must click View Drug
Prescription link.
The system display Drug Prescription.
Alternative course of Action If no Drug Prescription the Page Became Empty space
Table 2.11 use case description for View Drug Prescription

Use case Id UC 12
Use case name View Medical Result
Participating actor Patient
Pre-condition Login into the system
Best course of Action Patient must click View medical result link.
The system display box.
The patient must enter their password
Alternative course of Action If no medical history sent the Page Became Empty space
Table 2.12 use case description for View Medical Result

Use case Id UC 13
Use case name View Appointment
Participating actor Patient
Pre-condition Login into the system
Best course of Action The system display box.
The patient must enter their password.
The patient click submit button.
Alternative course of Action If no Appointment the Page Became Empty space
Table 2.13 use case description for View Appointment

Use case Id UC 14

Use case name Write Comment

Participating actor Patient

Pre-condition Login into the system

Basic course of action Patient want to Write Comment

Patient must click Write Comment link
The system display Comment form.
Patient must fill correctly the form.
Patient clicks submit button.
Alternative course of action If the Patient make the form empty go to 2
The system displays please fill the form.
The Patient continues to fill form correctly.

Post-condition A comment is sends successfully.

Table 2.14 use case description for Write comment

23
Use case Id UC 15
Use case name Record Patient
Participating Actor Record officer
Pre-condition Login into the system
Best course of action To record patient record officer must select record patient
link.
The system display patient registration form.
The record officer must fill correctly record patient form.
Record officer clicks record patient button.
Alternative course of action If the record officer makes the record patient form empty go
to 2
The system displays message please fill the form correctly
The record officer continues to fill the record patient form
Post-condition The system displays a message that tells the patient recorder
successfully
Table 2.15 use case description for Record Patient

Use case Id UC 16

Use case name Manage patient detail

Participating Actor Record officer
Pre-condition Login into the system
Extends -------add, delete and update patient
Best course of action Record officer want to manage patient Record officer must
click Manage patient detail link
The system display form to manage patient detail.
Record officer can perform delete patient, search patient
and update patient information
When Record officer want to add patient Record officer
must fill the form
Record officer clicks Add, delete and update button to
perform the action.

Alternative course of action If the Record officer make the form empty go to 2
The system displays please fill the form correctly
The Record officer continues to fill the form

Post-condition Message are generated as the action performed properly

Table 2.16 use case description for manage patient detail

Use case Id UC 17
Use case name View Comment

Participating actor Manager

Pre-condition Login into the system

Best course of Action Manager must click View comment link.

The system display comment.

Alternative course of Action If no comment sent the Page Became Empty space

Post-condition The System Generate Empty comment that suggested

Table 2.17 use case description for view comment

25
Use case Id UC 18
Use case name Submit Lab Result
Participating Actor Lab Technician
Pre-condition Login into the system
Best course of action Lab Technician want to send lab result
select lab result link
The system display lab result Form
The Lab Technician must fill lab result Form correctly.
The Lab Technician must click submit button
Alternative course of action If the Lab Technician make the lab result Form empty
go to 2
The system displays please fill the lab result Form
correctly
The Lab Technician continue to fill the lab result Form
Post-condition Messages are generated as the action performed
properly
Table 2.18 use case description for Send Lab Result

Use case Id UC 19
Use case name View lab order
Participating Actor Lab Technician
Pre-condition Login into the system
Best course of action Lab Technician want to view lab order Form click
Hospital lab order link
The system display lab order Form
Alternative course of action If there is no lab order the Page Became Empty space
Post-condition The System Generate there is no lab order
Table 2.19 use case description for View hospital Request form

Use case Id UC 20
Use case name Generate price list for payment
Participating Actor Manager
Pre-condition Login into the system
Best course of action manager want to Generate price list for payment
select Generate price list for payment link
click Generate price list for payment link
The system display price list for payment Form
The manager must click submit button
Alternative course of action If the manager makes the Generate price list for
payment Form empty go to 2
The system displays please fill the Generate price list
for payment Form correctly
The manager continues to fill the Generate price list
for payment Form
Post-condition Messages are generated as the action performed
properly
Table 2.20 use case description for Generate price list for payment

Use case Id UC 21
Use case name Order Bill for patient
Participating Actor Cashier
Pre-condition Login into the system
Best course of action Cashier wants to Order Bill for patient
click Order Bill for patient
The system display Order Bill for patient Form
The cashier must click submit button
Alternative course of action If the Cashier make the Order Bill for patient Form empty go
to 2
The system displays please fill the Order Bill for patient
Form correctly
The cashier continues to fill the Order Bill for patient Form
Post-condition Messages are generated as the action performed properly
Table 2.21 use case description for Order Bill for patient

27
2.3.4 Business rules
Specific instructions or constraints on how certain day-to-day actions, operations,
definitions that applies to a hospital
Br1: the doctor must know the disease before giving drug prescription
Br2: The lab technician must test the requested lab before sending lab result.
Br3: Name of drug will be unique for every disease in the hospital.
Br4: Users can access their own history and no one can access other medical history.
Br5: New patients must be registered by record officer.
Br6: Patents ID must be unique.

2.2.5 User Interface Prototype

Figure 2.2 user interface prototype

2.3.6 State Chart diagram
A state diagram is the graphical representation of a state machine and one of the UML
diagrams types for software and systems used to show a behavioral model consisting of
states, state transitions and actions. State diagrams depict the permitted states and
transitions as well as the events that effect these transitions.

Figure 2.3 state diagram for doctor in hospital management systems for Addis Alem hospital

29
Figure 2.4 State diagram for patient in web-based hospital management system for Addis
Alem hospital
2.3.7 Activity diagram

Activity diagrams are used to document the logic of a single operation/method. It includes
modeling the sequential process.

Figure 2.5 Activity diagram for login

31
Figure 2.6 activity diagram for manage drug
Figure 2.7 Activity Diagram for Make Patient Appointment

33
Figure 2.8 Activity Diagram Manage Employee
Figure 2.9 Activity Diagram to register Patient

35
Figure 2.10 Activity Diagram to Refer Patient
Figure 2.11 Activity Diagram to lab order

37
Figure 2.12 Activity Diagram to Prescribe Drug
2.3.8 Sequence Diagram
The Sequence Diagram is collaboration of objects based on a time sequence. It shows how
the objects interact with others in a particular scenario of a use case. One of the primary
uses of sequence diagrams is in the transition from requirements expressed as use cases to
the next and more formal level of alteration.

Figure 2.13 sequence diagram for Login

39
Figure 2.14 sequence diagram for send Lab Result

Figure 2.15 sequence diagram for Generate Report

Figure 2.16 sequence diagram for patient Appointment

41
2.3.9 Analysis Class Model
Class diagram is a static diagram used to shows a collection of classes, interfaces,
associations, collaborations, and constraints. It is also known as a structural diagram.

Figure 2.17 class diagram of hospital management system for Addis Alem Hospital
2.3.10 Logical Model
1, Scenario name: Login.
Participating actor: Patient, Lab Technician, Doctor, Pharmacist, Manager, Record Officer.
Patient, Lab Technician, Doctor, Pharmacist, Manager, and Record Officer can login into
website by using their own username and password to perform tasks.
2, Scenario name: Generate Report.
Participating actor: Manager, Doctor, lab technician or pharmacist.
The Manager, Doctor or pharmacist must select generate report link.
The system displays Report form.
The Manager, Doctor or pharmacist can write report that he/she want to send
The Manager, Doctor or pharmacist must clicks submit button.
The system displays message that action performed properly or not.
3, Scenario name: View comment
Participating actor: Manager:
Manager must select View comment link.
The system display comment Form.
The Manager can see written comment.
4, Scenario name: Manage Employee.
Participating actor: Manager.
Manager must select manage employee link.
System display form to manage employee
The manager can perform deleting employee, registering employee update employee
information.
The manager must clicks submit button.
The system displays message that action performed properly or not.
5, Scenario name: Manage Drug.
Participating actor: Manager.
Manager must click Manage Drug link.
The system display form to Manage Drug.
Manager can perform deleting drug, adding drug, updating drug information.
The manager must clicks submit button.

43
 The system displays message that action performed properly or not.
6, Scenario name: Send Hospital Lab Request Form
Participating actor: doctor:
Doctor must select lab order link.
The system display lab order.
Doctor can write lab order for lab technician to test the sign of patient illness.
The doctor must click submit button.
The system displays message that action performed properly or not.
7, Scenario name: View lab Result
Participating actor: doctor:
Doctor must click on View lab Result link.
The system displays lab Result Form.
The Doctor can see lab result.
8, Scenario name: Refer-out Patient:
Participating actor: Doctor
Doctor must select refer patient link.
The system display form to refer patient.
The Doctor must fill refer form clearly.
The Doctor must click send button.
The message does not send, it put in database server because out of scope.
9, Scenario name: Prescribe Drug:
Participating actor: Doctor:
Doctor must select Prescribe Drug link.
The system display form to Prescribe Drug.
The Doctor must fill Drug Prescription form clearly.
The Doctor must click send button either for patient or pharmacist.
The system displays message that action performed properly or not.
10, Scenario name: Make Patient Appointment
Participating actor: Doctor:
Doctor must select Make Patient Appointment link.
The system displays Patient Appointment form.
 The Doctor must fill Patient Appointment form clearly.
The Doctor must click send button.
The message sent to patient
The system displays message that action performed properly or not.
11, Scenario name: Write Comment.
Participating actor: Patient.
The Patient must select Write Comment link.
The system displays Comment form.
The Patient can Comment that he/she want to send
The patient must click send button.
The system displays message that action performed properly or not.
12, Scenario name: View Medical Result:
Participating actor: patient:
Patient must select View Medical Result link.
The system displays Medical Result form.
The Patient can view his/her medical Result.
The patient can know their illness.
13, Scenario name: View Drug Prescription:
Participating actor: Patient, pharmacist:
Patient and pharmacist must select View Drug Prescription link.
System displays Drug Prescription.
The Patient and pharmacist can view Drug Prescription
14, Scenario name: Dispense Drug
Participating actor: Pharmacist:
Pharmacist must select Dispense Drug link.
System display form to Dispense Drug.
Pharmacist must write the form of Drug Dispassion
Pharmacist must clicking submit button for patient.
The system displays message that action performed properly or not.
15, Scenario name: Send Lab Result:
Participating actor: lab technician:

45
 Lab technician must click submit Lab Result link.
The system displays Lab Result form.
Lab technician must test the lab requested by the doctor.
Lab technician must write lab report clearly.
Lab technician must click submit button to doctor.
The system displays message that action performed properly.
16, Scenario name: View lab order
Participating actor: Lab Technician:
Lab Technician must select View lab order link.
The system display lab order Form.
The Lab Technician can see lab order.
17, Scenario name: View Appointment
Participating actor: Patient:
Patient must select View Appointment link.
The system display Appointment Form.
The Patient can see Appointment.
18, Scenario Name: Create Record Patient:
Participating actor: Record officer:
Record officer must click Create Record Patient link.
The system displays the form to Record Patient.
Record officer must fill the form correctly.
The Record officer must click record button.
The system displays message that action performed properly or not.
19 Scenario name: Manage patient detail.
Participating actor: Record officer.
Record officer must select manage patient detail link.
System display form to manage patient detail
The Record officer can perform deleting patient, registering patient, update patient
information and viewing patient information.
The Record officer must clicks submit button.
The system displays message that action performed properly or not.
20, Scenario name: Generate price list for payment.
Participating actor: Manager.
Manager must select Generate price list for payment link.
System display form to Generate price list for payment
The manager can perform registering price list, update price list information.
The manager must clicks submit button.
The system displays message that action performed properly or not.
21, Scenario name: Order bill for patient
Participating actor: Cashier:
Cashier must select Order bill for patient link.
System display form to Order bill for patient.
Cashier must write Order bill for patient
Cashier must clicking submit button for patient.
The system displays message that action performed properly or not.
22, Scenario name: Log Out.
Participating actor: Patient, Lab Technician, Doctor, Pharmacist, Manager,Record Officer.
Users are login to system and after finishing their task, they can log out.

47
2.4 System Requirement
After having all the required data different software and hardware tools are used.

2.4.1 Hardware Requirement

The project team needs different materials to develop the web-based hospital management
system for Addis Alem hospital and to run the system in the real world. The basic hardware
Tools are:
Hardware Tool Activities (Description)
Computer (Desktop or Laptop) Almost all the tasks of our project are
performed on the computer with the following
specification:
Processor: -Intel(R) Core (TM)i5-4200M
CPU@2.50GHz RAM 4.00 GB
Storages (hard disk)465GB Windows 10
operating system
Flash Required for transfer data from one PC to
another PC. We will use16GB flash and also
for backup and file transfer
Pen, paper. For writing all necessary documentation
associated with the project
Printer to print the document
Mobile phone We used a mobile phone to record sound
when we interview peoples and to use its
camera to capture different formats or recites.
Table 2.22 hardware requirements in hospital management project for Addis Alem hospital
2.4.2 Software Requirement

Software Tools Activities (Description) Why?

visual studio code For writing and editing program Easy to use any code
or code of the system
MySQL To create and design the Database server for PHP
database which used to store the
information of the organization
(Database Server)
Window 10 Operating system It will be used for the system Recently available operating
since it is readily available. system and easy to use
Draw.io For draw user interfaces Easy to draw any diagram
Nodejs Web Server Web server for node
Nodejs Server-side coding Understand by server
HTML,BOOTSTRAP5,CSS, Client-Side Coding It works with Nodejs
React, React Native
Web Browser (Google Chrome, For browsing and running the Better for displaying web pages
Firefox, and Microsoft edge) system Since our system is web
based, it is a very necessary
requirement
MS Word 2016 for documenting the Easy to use
corresponding deliverables
associated with the project
MS PowerPoint Presentation Better for presentation
MS Visio 2007 Modeling UML and design Easy to design diagrams
Snipping tools to screenshot the picture The software used for
screenshot
Adobe Photoshop CS5 Editing images Easy to use
CSS Style/beautify the content It works with HTML and Nodejs

Table2.13 Software requirement in hospital management system for Addis Alem hospital

49
2.5 Key Abstraction with CRC Analysis

2.5.1 Conceptual Modeling: Class diagram

Figure 2.17 class diagram of hospital management system for Addis Alem Hospital

Figure 2.18 conceptual class diagram of hospital management system for Addis Alem Hospital

2.5.2 Identifying change cases

Because of our system work only in English language, there will be a modification of
language in the future to work in local language like Amharic, Tigrigna, Oromo etc. The
language modification is very important to users to understand the system easily.
 CHAPTER THREE

SYSTEM DESIGN
Introduction
In this chapter we are going to describe the current and proposed system software
architecture and we specify design goals to improve the quality of the system by reducing
response time, increasing availability and improving its reliability to function correctly
under incorrect conditions. Software architecture is the process of defining a structured
solution that meets all of the technical and operational requirements, while optimizing
common quality attributes such as performance, security, and manageability. We describe
the Hardware/software mapping with deployment diagram, persistent data management,
subsystem decomposition or component, access control and security. Hardware/software
mapping is mapping subsystems to processors and components enable us to identify
potential concurrency among subsystems and to address performance and reliability goals.
We specify the boundary conditions for each subsystem by mentioning how the subsystems
initialized and terminates.

3.1 Architectural Design

Current software architecture
The existing system of the Addis Alem hospital management system is manual system and hence

there is no Existing software architecture that will be considered. As a result, we only describe

the software architecture of the newly proposed system.

Proposed software architecture

The architecture used for the system is a 3 tier Client/Server Architecture. The client tier is
the applications user interface containing data entry forms and client-side applications. It
displays data to the user. Users interact directly with the application through user interface.
The client tier interacts with the web/application server to make requests and to retrieve
data from the database. It then displays to the user the data retrieved from the server. A
client can use internet browsers to access the online report provided by the system within

51
the local area network of the hospital.
A web server is a program that runs on a network server (computer) to respond to HTTPS
requests. The web server used in this system is Node. HTTP is used to transfer data across
the internet. It is the standard protocol for moving data across the internet. The third tier,
called the data tier, maintains the applications data such as doctor data, manager data,
patient data… etc. It stores these data in a relational database management system
(RDBMS).

Figure 3.1 software Architecture for Addis Alem hospital

3.1.1 Component model

Figure 3.2 component diagram of Addis Alem hospital management system

53
3.1.2 Deployment diagram
Deployment diagrams are used to visualize the topology of the physical

components of a system, where the software components are deployed and used to

describe the static deployment view of a system.

Figure 3.3 deployment diagram of hospital management for Addis Alem hospital
3.2. Design class Model

55
Figure 3.4 detailed Class Diagram of hospital management system for Addis Alem hospital

3.2.1 ER Diagram

ER Diagram is a visual representation of data that describes how data is related to each
other using different ERD Symbols and Notations. Following are the main components and
its symbols in ER Diagrams: Rectangles: This Entity Relationship Diagram symbol
represents entity types. Ellipse symbol represent attributes.

Figure 3.5 ER Diagram for Addis Alem Hospital

3.3 User Interface Design
User interface (UI)- is the point at which human users interact with a computer, website or

application. The goal of effective UI is to make the user's experience easy and intuitive, requiring

minimum effort on the user's part to receive maximum desire.

Figure 3.6 User interface for home page

57
Figure 3.7 User interface for patient signup
Figure 3.8 User interface for login

59
Figure 3.9 User interface for patient registration by record officer

3.4 Access control and security

Access control describes the user model of the system which can do these tasks in terms of
access privilege. A privilege is a permission to perform an action. And also describes security
issues, such as the use of the encryption and mechanism, and selection of an authentication
mechanism
 Actor Privilege

Manager Manage employee ()

Generate Report ()
Generate Price-list ()
View Comment ()

Patient View Drug Prescription ()

View Medical Result ()
Write Comment ()
Pay()

Pharmacist Manage drug()

Dispense Drug ()
View Drug Prescription ()
Generate Report ()

Doctor Refer patient ()

View lab Result ()
Make Patient appointment ()
Send Hospital Lab Request Form ()
Drug Prescription ()
Generate Report ()

Lab Technician View Hospital Lab Request Form ()

Send lab result ()

Generate Report ()

Record officer Create patient Record ()

Manage patient detail ()

Cashier Order invoice for patient ()

View payment history of patient ()
Table 3.2 Access control for Addis Alem hospital

61
 CHAPTER FOUR

IMPLEMENTATION
4.1 Introduction:
Implementation is the stage of the project when the theoretical design is turned out into a

working system. It can be considered to be the most critical stage in achieving a successful new

system and in giving the user, confidence that the new system will work and be effective. The

implementation stage involves careful planning, investigation of the existing system and it’s

constraints on implementation, designing of methods to achieve changeover and evaluation of

changeover methods.

4.2 Sample code:

CODE for HOME Page
import React from 'react';
import './App.css';

import Footer from './Footer';

import Left_Nav from './Left_Nav';
import Layout from './Layout';
import Login from './Login';
import Signin from './Signin';
import Admin from './Admin';
import RecordOfficer from "./RecordOfficer"
import {Route,Routes} from "react-router-dom";
import Home from './Home';
import Patient from './Patient';
import Pharmasist from './Pharmasist';
import LabTechnitian from './LabTechnitian';
import PatientRecord from './PatientRecord';
import Doctor from './Doctor';
import Drug from './Drug';
import Casher from './Casher';
import Nurse from './Nurse';
import RadioGrapher from './RadioGrapher';

import Employ_reg from './Employ_reg';

import Add_drug from './Add_drug';
import Manage_Service from './Manage_Service';
import Add_Service_Price from './Add_Service_Price';
import Priscribe_drug from './Priscribe_drug';
import Comment from './Comment';
import Appointment from './Appointment';
import Order_Lab from './Order_Lab';
import AboutUs from './AboutUs';
import ContactUs from './ContactUs';
function App() {
return (
<div >
<Layout/>
<Left_Nav/>
<div className='df'>

<Routes>

<Route path="/" element={<Home/>} />

<Route path='Admin' element={<Admin/>} />

<Route path='Add_drug' element={<Add_drug/>} />
<Route path='Manage_Service' element={<Manage_Service/>} />
<Route path='AboutUs' element={<AboutUs/>} />

63
 <Route path='ContactUs' element={<ContactUs/>} />
<Route path='Add_Service_Price' element={<Add_Service_Price/>} />
<Route path="login" element={<Login />} />
<Route path="Employ_reg" element={<Employ_reg />} />
<Route path="Appointment" element={<Appointment />} />
<Route path="signin" element={<Signin />} />
<Route path="RecordOfficer" element={<RecordOfficer />} />
<Route path="PatientRecord" element={<PatientRecord/>} />
<Route path="Patient" element={<Patient/>} />
<Route path="Pharmasisit" element={<Pharmasist/>} />
<Route path="LabTechnitian" element={<LabTechnitian/>} />

<Route path="Doctor" element={<Doctor/>} />

<Route path="Order_Lab" element={<Order_Lab/>} />
<Route path="Comment" element={<Comment/>} />
<Route path="Priscribe_drug" element={<Priscribe_drug/>} />
<Route path="Drug" element={<Drug/>} />
<Route path="Casher" element={<Casher/>} />
<Route path="Nurse" element={<Nurse/>} />
<Route path="RadioGrapher" element={<RadioGrapher/>} />

</Routes>

</div>

</div>
 );
}
export default App;

//app css

.copy{

text-decoration: none;
color:rgb(1, 12, 24);
background-color: rgb(212, 212, 212);
font-family: sans-serif;
font-style: oblique;
border-radius: 7px;

}
.info{
margin-top: 40px;
font-size: 15px;
text-align: center;

}
.login{

text-align: left;
border: none;
border-radius: 5px;

65
}
.signin{

text-align: left;
margin-left: 150px;

border: none;
border-radius: 5px;

}
.pri{
margin-top: 20px;
margin-bottom: 20px;
text-align: center;

}
.privacy{

margin-right: 100px;
border: none;
border-radius: 5px;
}
.about,.head{

margin-left: 100px;
border: none;
border-radius: 5px;
}
button{
background-color: rgb(143, 175, 164);
 text-decoration: none;
color: inherit;
font-family: sans-serif;
font-style: oblique;
border: none;
border-radius: 7px;

h2{

text-decoration: none;
color:rgb(241, 246, 252);
font-family: sans-serif;
font-style: oblique;
border-radius: 10px;
margin-top: 60px;
margin-right: 100px;

}
h3{
font-family: sans-serif;
font-style: oblique;
border-radius: 10px;
}
h4{
color: rgb(249, 250, 252);
margin-top: 70px;
border: 1px solid #5666b6;
border-radius: 4px;

67
}

.df{
background-color: rgba(229, 233, 238, 0.493);
}
//end of app

//begining of home

import React from 'react'

import { Outlet, Link } from "react-router-dom";
import h_Anime from "../Image/h_Anime.mp4"
function Home() {
return (
<div >
<header className="BodyArea">

<div className="info">

<div>
<video
width="70%" height="60%" preload='auto' controls
muted
autoPlay={true}
preLoad="auto"
loop>
 <source src={h_Anime} type="video/mp4" />

something</video>

</div>
<p>
The platform supports the primary health-care provider at the community
level in diagnosis and treatment decisions.The provider can link the Patient
directly to the platform for a video consultation with a physician. If no diagnosis can be
made, the patient
is referred to a hospital associated with the platform.The platform is expected to
strengthen primary care and create a local
gatekeeping mechanism. Inspired by the Guangdong experience,
The directive encourages hospitals to provide primary care and a referral
system for patients with common conditions and chronic diseases through
online platforms. This approach also acts as a triage system for hospital services.

</p>
</div>

</header>
</div>
)
}

export default Home

.back{

69
 display: flex;
padding: 10px;

//end of home

// code for register patient client side

// start....
import Axios from 'axios';
import React , {useState}from 'react'
import "./PatientRecord.css"
function PatientRecord() {

// codes for state managment

const [profileImg, setProfileImg]=useState(

"https://th.bing.com/th/id/OIP.S171c9HYsokHyCPs9brbPwHaGP?pid=ImgDet&rs=1");
const [file,setFile]=useState();
const [firstName,setFirstName]=useState("");
const [MRN,setMRN]=useState(0);
const [imgName,setImgName] = useState("");
const [middleName,setMiddleName] = useState("");
const [lastName,setLastName] = useState("");
const [age,setAge] = useState(0);
const [phoneNumber,setPhoneNumber] = useState(0);
const [address,setAddress] = useState("");
const [id,setId] = useState();
const [patientStatus,setPatientStatus] = useState("");
const [gender,setGender] = useState("Male");
const register=()=>{
const url='http://localhost:3001/register'; // this URL for posting data to server
const formData= new FormData(); // and appends these data in server database
formData.append('MRN',MRN);
formData.append('firstName',firstName);
formData.append('middleName',middleName);
formData.append('lastName',lastName);
formData.append('age',age);
formData.append('phoneNumber',phoneNumber);
formData.append('address',address);
formData.append('patientStatus',patientStatus);
formData.append('gender',gender);
formData.append('imgName',imgName);
formData.append('image',file);
Axios.post(url,formData).then((response)=>{
console.log(response);

});
alert("registred")

}
const imageHandlerUI = (e) =>{
setProfileImg(URL.createObjectURL(e.target.files[0]));
setFile(e.target.files[0]);
console.log("img: "+file)
setImgName(e.target.files[0].name)
}
return ( // this returns form filed to register patient
<div className="BodyArea">

71
 <h3>
RECORD NEW PATIENT PAGE
</h3>

<div className="patientRecord">
<form>
<div className="Password">
<label for="MRN">Medical Record Number : </label>
<input id="MRN" name="MRN" type="text"
onChange={(event)=>{setMRN(event.target.value);}}/>
</div>
<div className="Password">
<label for="Name">Name :</label>
<input id="Name" name="Name" type="text"
onChange={(event)=>{setFirstName(event.target.value);}}/>
<label for="middleName">Middle Name :</label>
<input id="middleName" name="middleName" type="text"
onChange={(event)=>{setMiddleName(event.target.value);}}/>
</div>

<div className='Password'>
<label for="lastName"> Last Name :</label>
<input id="lastName" name="lastName" type="text"
onChange={(event)=>{setLastName(event.target.value);}}/>
<label for="sex"> Gender : </label>
<input id="male" name="sex" type="radio" defaultChecked={gender}
onChange={(event)=>{setGender("male");}}/>
<label for="male"> Male :</label>
<input type="radio" id="female" name="sex"
onChange={(event)=>{setGender("female");}}/>
<label for="female">Female</label>
 </div>
<div className='Password'>
<label for="date">Age :</label>
<input id="date" name="date" type="text"
onChange={(event)=>{setAge(event.target.value);}}/>
<label for="adress"> Adress :</label>
<input id="regon" name="region" type="text"
onChange={(event)=>{setAddress(event.target.value);}}/>

</div>

<div className="Password">
<label id="">Image : </label>
<img
src={profileImg}
alt=""
className="img"
value={profileImg}

/>
<input
name="image"
type="file"
id="input"
accept="image/*"
onChange={imageHandlerUI }
/>
<label htmlFor="input" >
Choose File
</label>
</div>

73
 <div className='Password'>
<label for="houseNumber"> House Number :</label>
<input id="houseNumber" name="houseNumber" type="text"
onChange={(event)=>{setId(event.target.value);}}/>
<label for="phoneNumber"> Phone Number :</label>
<input id="phoneNumber" name="phoneNumber" type="Number"
onChange={(event)=>{setPhoneNumber(event.target.value);}}/>
</div>

<div className='LoginReset'>
<button className='login' onClick={register}>Register </button>
<button className='reset'>Reset</button>
</div>

</form>
</div>
</div>
)
}

export default PatientRecord

// code register patient client side

// end....

code register patient backend side

// start....
//register patient
app.post('/register', type,(req, res)=>{
const MRN=req.body.MRN;
const firstName=req.body.firstName;
const middleName=req.body.middleName;
const lastName=req.body.lastName;
const age=req.body.age;
const phoneNumber=req.body.phoneNumber;
const gender=req.body.gender;
const address=req.body.address;
const patientStatus=req.body.patientStatus;
const imgName=req.body.imgName;

var tmp_path = req.file.path;

console.log(tmp_path);
var target_path = path.join(__dirname, 'Image/') + req.file.originalname;
var src = fs.createReadStream(tmp_path);
var dest = fs.createWriteStream(target_path);
src.pipe(dest);

//remove temp files

const directory = path.join(__dirname,'Image/temp/')
fs.readdir(directory, (err, files) => {
if (err) throw err;
for (const file of files) {
fs.unlink(path.join(directory, file), err => {
if (err) throw err;
});
}});
const registerPatient="insert into patient
(MRN,firstName,middleName,lastName,age,sex,imagePath,phoneNumber,address,patientS

75
tatus) values(?,?,?,?,?,?,?,?,?,?)";
db.query(registerPatient,[MRN, firstName,middleName, lastName, age, gender, imgName,
phoneNumber, address, patientStatus ],(err, result)=>{
if(err){
console.log(err);
}
else{
console.log(registerPatient," MRN = ",firstName," firstname = ",imgName);
// res.send("values inserted");
}
})
});

// code register patient backend side

// end....
References

[1] Addis Alem hospital (2009 E.C). Document of patient service management manual.
Bahirdar.

[2] I. E. Team, 30 march 2021. [Online]. Available: https://www.indeed.com/career-

advice/career-development/user-interface. [Accessed 24 may 2021].

[3] K. brush. [Online]. Available: https://searchsoftwarequality.techtarget.com/definition/use-

case. [Accessed 24 april 2021].

[5] I. E. Team, "user interface definition," 21 march 2021. [Online]. Available:

https://www.indeed.com/career-advice/career-development/user-interface. [Accessed 21

may 2021].

[6] k. Brush, "use case model definition," 20 april 2019. [Online]. Available:
https://searchsoftwarequality.techtarget.com/definition/use-case. . [Accessed 24 april 2021].

77
Appendix

Interview Questions to gather requirement for AAHMS:

When did AAH established?

How many workers were when the AAH officially starts facility service?

How many workers were when the AAH officially current facility service?

How the current AAH office works?

Are there problems with this? and what are the problems?

How much is the cost expense of the AAH to perform the task monthly and annually?

What type of service AAHMS provide

Sample of Working forms which are taken from the business to be automated

79
81
83
85