Kingdom Saudi Arabia

Academic year 1443-2022

Ministry of education
Second Semester
Bisha University
Systems analysis and design
College of computers and information technology
Department of Information Systems

project name :

HOSPITAL RECEPTION SYSTEM

ID names of students
‫نهى ناصر عمر الجبيري‬
-440802393

-440802390 ‫امجاد محمد علي االكلبي‬

-440802379 ‫سمية ظافر حزام الجبيري‬

-440800630 ‫لينا فهد فالح السبيعي‬

-440800587 ‫هوازن قاسم عبدهللا العتيبي‬

1
CONTENTS

About the project … … … … … … … … … … … … … … … …...

3
Use Case Explain … … … … … … … … … … … … … … … … … 4

Use Case Diagram … … … … … … … … … … … … … … … … …6

Context Diagram …………………………………………… 7
DFD ……………………………………………
7
DFD Level 0 Explain …………………………………………… 7
DFD Level 0 Diagram …………………………………………… 8
DFD Level 1 (3.0) Explain … … … … … … … … … … … … … … … … … …9

DFD Level 1 (3.0) Diagram … … … … … … … … … … … … … … … … … … 9

DLD Level 1 (4.0) Explain … … … … … … … … … … … … … … … … … …10

DFD Level 1 (4.0) Diagram … … … … … … … … … … … … … … … … … …11

DFD Level 2 (4.1) Explain … … … … … … … … … … … … … … … … … …12

DFD Level 1 (4.1) Diagram … … … … … … … … … … … … … … … … … … 12

SequenceDiagram...
… … … … … … … … … … … … … … … … …
13

Login Sequence Explain … … … … … … … … … … … … … … … … …14

…
Login Sequence Diagram … … … … … … … … … … … … … … … … … … 14
Add Patient Sequence Explain … … … … … … … … … … … … … … … … … … 15
Add Patient Sequence Diagram … … … … … … … … … … … … … … … … … … 15
Add Appointment Sequence Explain … … … … … … … … … … … … … … … … … … 16
Add Appointment Sequence Diagram ... … … … … … … … … … … … … … … … … … 16
Edit Appointment Sequence Explain ... … … … … … … … … … … … … … … … … … 17
Edit Appointment Sequence Diagram ... … … … … … … … … … … … … … … … … … 17
ER Modelling Explain... …………………………………………… 18

ER Modelling Diagram ….……………………………………

21… …
Class Diagram Explain … … … … … … … … … … … … … … … … … … 22

Class Diagram … … … … … … … … … … … … … … … … … … 23

2
About the project

In this project, we designed a small hospital receptionist system that receives patients to

make an appointment. The receptionist takes the patient’s information and adds it to the

system and then sets an appointment for him by adding the patient to the appointment, the

doctor and the bed, provided that they are available on time for the appointment.

3
Use Case Diagram
Usecasediagramsdescribewhatasystemdoesfromthestandpointofanexternal
observer. The emphasis is on
what a system does rather than how. in this use case for hospital's receptionist system

it'shastwoactor'sreceptionistandpatient,andhasseveralscenariosforinteract
system:
●Type External Actors:
1.Patient
2.Receptionist
● Use Cases
1.Request Appointment use case:

Description:Thisusecasedescribeshowtorequestappointmentbetweenpatientand
receptionist.
2.Login or logout use case:

Description: This use case describes patient login and logout.

3.Manage Patient use case:

Description:Thisusecasedescribeshowtomanagepatientswhenapatientrequestsan
appointment.Therearespecialsub-usecasesofthemanagepatientmainusecasethat
we use generalization:

3.1 Adding a patient

3.2 patient modification

3.3 Delete a patient

3.4 patient research

4.Manage Appointment Use Case

4
 Description:Thisusecasedescribeshowtomakeanappointmentwhenapatient
requests an appointment
●Normal Flow:
4.1 Add Appointment:

4.1.1 The patient logs onto the appointment portal.

4.1.2 The patient provides their info.

4.1.3 The patient chooses what his ideal time and doctor would be.

4.1.4Acceptanceoftheappointmentisonlydeterminedwhenadoctorandabedare
available, so an inclusion has been made for the connection between cases.
4.1.5 Receptionist provides confirmation or not.

4.2 Edit Appointment:

4.2.1 The patient provides their new info.

4.2.2 The patient chooses what his ideal new time and doctor would be.

4.2.3Acceptanceoftheappointmentisonlydeterminedwhenadoctorandabedare
available,
4.2.4 Receptionist provides confirmation or not.

4.3 cancel Appointment:

4.3.1 The patient gives his appointment number to canceled.

4.3.2 The receptionist search for the appointment number.

4.3.3 the receptionist canceled the appointment and deleted from database.

4.4 search Appointment:

4.4.1 The patient gives his appointment number to now his appointment date and time.

4.4.2 The receptionist search for the appointment number.

4.4.3 the receptionist gives the appointment date and time for patient.

5
Use Case Diagram

6
 Context Diagram

Data Flow Diagram (DFDS)

This diagram depicts the main operations of the system (level 0):

1- Request appointment:

The patient's external object requests an appointment through the process of

requesting appointment and the data flow are the patient's information, the time of
the appointment, and the doctor for the receptionist in the hospital.

2-Login:

The receptionist external object logs in to the system through the login process, and
the dataflow is the receptionist name and password.
The login process sends the information to the database and returns the verification
of the information through the dataflow of the login process and responds to the
receptionist.

3- Manage patient:

The receptionist adds, edits, deletes and searches for a patient through the main
process of managing a patient and sends and receives information through the
dataflow of the database.

4- Manage Appointment:

The receptionist adds, edits, deletes and searches for a patient through the main
process of managing a patient and sends and receives information through the
dataflow of the database.

7
DFD LEVEL 0

8
DFD Level 1 for Manage Patient (3.0)
3.1 Adding a patient:

The process of adding a patient receives the patient’s information from the receptionist
via Dataflow and adds it to the database and returns the response to the receptionist
that the patient was registered through Dataflow.

3.2 Edit Patient:

The process of editing a patient receives the identifier of the patient to be edit from the
receptionist through the data flow and searches for it in the database and responds
about the presence of the patient or not to the process of editing the patient and the
external object to receptionist and then if the patient is present, the receptionist enters
the new information to be edit and added to the database Data and response to the
receptionist that it has been modified.
3.3 Delete a patient:

The process of deleting a patient receives the patient's ID from the external entity, the
employee of use, and deletes it from the database, and responds to the receptionist that
it has been deleted.

3.4 Looking for a patient:

The process of searching for a patient receives the patient's ID, searches for it in the
database, and responds to the receptionist about the patient's information.

9
DLD Level 1 for Manage Appointment (4.0)

●4.1 Add Appointment:

The process of adding an appointment receives the patient ID, doctor ID and room
number from the external entity, the receptionist, provided that the doctor and the bed
are available, and adding the appointment to the database and responding to the
receptionist that the appointment has been added.
●4.2 Edit Appointment:
The process of editing an appointment receives the appointment ID or number from the
receptionist and searches for the appointment in the appointment table in database,
then the information to be modified is entered into the database.

●4.3 Cancel Appointment:

The process of cancel appointment receives the ID or number of appointment and
deleted from database.
●4.4 Search Appointment:
The process of searching an appointment receives the appointment ID or number from
the receptionist and searches for the appointment in the appointment table in
database, then reply the information of appointment to receptionist.

10
11
DFD Level 2 for Add Appointment (4.1)
●Add Appointment:
The process of adding an appointment receives the patient ID, doctor ID and room
number from the external entity, the receptionist, provided that the doctor and the bed
are available, and adding the appointment to the database and responding to the
receptionist that the appointment has been added.
●Add Patient:
The process of adding a patient receives the patient ID from the receptionist and adds it
to the appointment.
●4.1.2 Check Available Doctor:
Checking the availability of the doctor from the appointment table and doctor table in
the database, and if the doctor is available, he is added to the appointment, or a
message is returned that the doctor is not available to the receptionist.

●4.1.3 Check Available Bed:

Checking the availability of the bed from the appointment table and bed table in the
database, and if the bed is available, it added to the appointment, or a message is
returned that the bed is not available to the receptionist.

12
 SEQUENCE DIAGRAM

Login Sequence

This is the Login Sequence Diagram of hospital's reception System, where receptionist
will be able to login in their account using their credentials. After login user can manage
all the operations on, Appointment, schedule, Doctors, and patients.

13
Add Patient Sequence Diagram
This sequence diagram depicts The receptionist can add a new patient by taking the
patient's data such as the name,
Age, gender, blood type, etc. The patient will be entered into the system database.

14
Add Appointment Sequence Diagram
This sequence diagram example depicts the objects and messages for a scenario of the
Make Appointment use case, which describes the process by which a patient creates a
new appointment The receptionist is taking data from the patient and determining time
and ensuring that the presence of doctor. and provide a bed and confirmation of the

patient's reservation.

15
Edit Appointment Sequence Diagram
This sequence diagram example depicts the objects and messages for a scenario of the
Edit Appointment use case, which describes the process by which a patient creates a new

appointment The receptionist is taking data from the patient and determining time and

ensuring that the presence of doctor. and provide a bed and confirmation of the patient's

reservation.

16
 Entity Relationship Modelling

This ER (Entity Relationship) Diagram represents the model of Hospital Reception System
Entity. The entity relationship diagram of hospital reception System shows all the visual
instrument of database tables and the relations between Receptionist, patient,
Appointment, bed, Doctors.
It used structure data and to define the relationships between structured data groups of
Hospital Reception System functionalities. The main entities of the Hospital Reception
System Are Receptionist, Login, Patient, Doctors, Appointment, Bed.

Entities and their attributes:

●Receptionist Entity:
Recep_name, Recep_id, Sex, phone number.

●Login Entity:
Username, Password.

●Patient Entity:
Patient_Name, Patient_id, Address, Sex, Age, Phone_Number, Date_entry,
Date_Disharged.
●Doctors Entity:
Attributes of Doctors are doctor_id, Doctor_name, Phone number, Sex, Status
Address, Qualification.
●Appointment Entity:
Attributes of Appointment are appointment_id, appointment_number,
appointment_time, appointment_date, appointment_description.

● Bed Entity:

Bed_id, Bed_status.

● Dependent Entity:

17
Relationships between entities:

1.Receptionist and Patient

● Cardinality Ratio (one-t-many)
The receptionist registers one or more patients, and the patient is registered by one
receptionist.
● participation constraint:

The Receptionist participates partially in the relationship register; it is not mandatory

that each Receptionist Register Patient.
the Patients total participate in the relationship register, meaning that all entities
must participate in a relationship.

2.
Receptionist and Appointment
● Cardinality Ratio (one-t-many)
The Receptionist book an one or more APPOINTMENT, and the appointment is book
ِ
by one receptionist.
● participation constraint:

The Receptionist participates partially in the relationship (Book An), It is not

mandatory that each Receptionist Book an appointment.
the Appointment is total participate in the relationship (Book AN), It is mandatory
that each appointment Book an by Receptionist.

3.
PATIENT and APPOINTMENT
● Cardinality Ratio (one-t-many)
The Patient assigned to one or more Appointment, and the Appointment appoints
one Patient.
● participation constraint:

The Patient is total participates in the relationship Assigned, it is mandatory that

each Patient has an Appointment.

18
 the APPOINTMENT is total participate in the relationship Assigned, it is mandatory
that each appointment has an PATIENT.

DOCTOR and APPOINTMENT

● Cardinality Ratio (one-t-many)
The Doctor assigned to one or more Appointment, and the Appointment appoints
one Doctor.

participation constraint:

The Doctor is total participates in the relationship Assigned, it is mandatory that

each Doctor has an Appointment.
the Appointment is total participate in the relationship Assigned, it is mandatory
that each Appointment has a doctor.

BED and APPOINTMENT

Cardinality Ratio (one-t-many)
The Bed assigned to one or more Appointment, and the Appointment appoints one
Bed.
participation constraint:

The Bed is total participates in the relationship Assigned, it is mandatory that each
bed has an Appointment.
the Appointment is total participate in the relationship Assigned, it is mandatory
that each Appointment has n bed.

Receptionist and Dependent

Cardinality Ratio (one-t-many)
The Receptionist has one or more dependent, and the dependent has one
Receptionist.
participation constraint:

The Receptionist participates partially in the relationship register; it is not mandatory

that each Receptionist has dependent.

19
the Dependent total participate in the relationship has, meaning that all entities

must participate in a relationship.

20
Class Diagram
●Relationship between classes
1.Receptionist and Patient (Association)
Receptionist register one or more Patient.

2. Receptionist and Appointment (Association)

Receptionist Book an one or more Appointment.

3. Patient and Appointment (Aggregation)

Patient part of Appointment, The Patient assigned to one or more Appointment, and
the Appointment appoints one Patient.

4.Doctor and Appointment (Aggregation)

Doctor part of Appointment, The Doctor assigned to one or more Appointment, and
the Appointment appoints one Doctor.

5. Bed and Appointment (Aggregation)

Bed part of Appointment, The Doctor assigned to one or more Appointment, and the
Appointment appoints one Bed.

6.Dependent and Receptionist ((Association))

Receptionist has one or two Dependent; every Dependent has one Receptionist.

21
22