BULE HORA UNIVERSITY

COLLAGE OF BUSINESS AND ECONOMICS

DEPRATEMENT OF BUSINESS ADMINISTRATION AND

INFORMATION SYSTEMS

3rd YEAR FIRST SEMESTER

Project title: DESIGNING DATABASE FOR BHUTH PATIENT

INFORMATION MANAGEMENT SYSTEM

Prepared by.

Name Id. No.

1. Gelma Ermias....................................................RT.10026/15

2. Mohammed Aliyi……………………………...RU.4452/14

3. Amanuel Wandimu…………………………...RU.2127/14

4. Ibsa Adem……………………………………..RU.2425/14

5. Murad Adem………………………………….RU.2450/14

Submitted to instructor: TESFAYE T.

SUBMITTEDDATE:

BULE HORA ETHIOPIA

 ACKNOWLEDGMENT
First of all, we want to thanks our GOD. We would like to extend our heartfelt gratitude to all
those who contributed their time, effort, and expertise to the success of our projects. Special
thanks to instructor Tesfaye whose insightful ideas and diligent work significantly enriched our
project outcomes. Furthermore, I would like to acknowledge the contribution of the Bule Hora
University teaching hospital employees and managements .we also want to express our gratitude
to our group member who has a great role and carefully to design and edit this paper. In
conclusion, Thank you all once again for your outstanding contributions.

Page i of xxiv
ACRONYMS
BHUTH……………BULE HORA UNIVERSITY TEACHING HOSPITAL

Page ii of xxiv
Contents
ACKNOWLEDGMENT..............................................................................................................................i
ACRONYMS..............................................................................................................................................ii
1. INTRODUCTION...................................................................................................................................1
2. BACKGROUND OF THE ORGANIZATION.......................................................................................1
3.1. PROBLEMS WITH THE CURRENT SYSTEM.............................................................................2
3.2 METHODS OF DATA COLLECTION............................................................................................3
3.2.1. Interviewing...............................................................................................................................3
3.2.2. Observation...............................................................................................................................3
3.2.3. Documents.................................................................................................................................3
4. Functional requirements (basic functions of the system).........................................................................3
5. Non-Functional requirements (additional functions of the system).........................................................4
5.1 Security Requirements.......................................................................................................................4
5.2 Performance Requirements...................................................................................................................4
5.3 Availability Requirements...................................................................................................................4
5.4 Accuracy Requirements...................................................................................................................4
5.5 Ease accessibility Requirements......................................................................................................5
5.6 System portability Requirements.....................................................................................................5
5.7 Efficiency Requirements...................................................................................................................5
6. Entities, attributes, Relationships and Constraints on data.......................................................................5
6.1 Identify Entities.................................................................................................................................5
6.2. Identify Attributes.............................................................................................................................5
6.3. Identify Relationships.......................................................................................................................8
7. ENTITY RELATIONSHIP DIAGRAM OF BHUTH (ER- DIAGRAM).............................................10
8 .Relational schema (logical schema........................................................................................................10
9. NORMALIZATION..............................................................................................................................11
10. The Final class Diagram......................................................................................................................14
11. PHYSICAL DATABASE DESIGN..............................................................................................................14

Page iii of xxiv

Page iv of xxiv
Page v of xxiv
1. INTRODUCTION
In this project we wanted to focus on the Bule Hora university Teaching Hospital patient
information management system ( BHUTH-PIMS). in this project we define the background of
the organization and also we will see how it organization is work in patient information
management system. Patient information refers to any information related to an individual’s
health and medical history. It includes personal details, such as name, age, and contact
information, as well as medical records, diagnoses, treatments, and test results .

2. BACKGROUND OF THE ORGANIZATION

Bule hora university teaching hospital (BHUTH) is one of the public and teaching Hospital, it
was established in 1987 E.C. in Hagere Mariam Town. The hospital giving Service are clinical,
laboratory, diagnostic and other services.

The hospital has capacity of 300 beds and is equipped with some modern facilities and
equipment. The hospital has a team of experienced medical professionals, including doctors,
nurses, and other support staff. The hospital offers 24 hours’ services to its staff and the
entire population. The hospital are giving the service for different inpatient and
outpatients , inpatient are the patient that are who stay in a hospital while receiving
medical care or treatment and outpatient a patient whose treatment does not require an
overnight stay in a hospital or clinic.

The service offered by BHUTH are clinical, laboratory, diagnostic and other Service .the
clinical service offered by Bule Hora university teaching hospital are OPD Service, Adult
OPDs, pediatric, Emergency, MCH Service, HCT, Dental clinic, psychiatry clinic, Ophthalmic
clinic, ART, TB, IPD service, surgical medical, pediatric, OBGYN, NICU, Burn MDR.
The OPD Service are offered in BHUTH include. Doctor consultations, Diagnostic tests, Routine
check-ups, Minor surgeries and procedures Treatments for severe medical conditions which need
intensive care and treatment
The pediatric Service are diagnosing and treating common childhood ailments and minor
injuries, recommending patients for further treatments and to specialists when needed ,providing
preventative care including the recommendation of vaccines, recording and maintaining the

Page 1 of 24
health and development information of their patients, effectively communicating their patients’
health, nutritional, and fitness needs to their guardians.

the laboratory service offered by BHUTH are bacteriology, AFB, Gen-xpert, parasitological,
chemistry, hematology, serology, fluid analysis, urine analysis, skin snip test, CD4,blood cross
match. The diagnostic service are radiology, x-ray, ultrasound and the other service provide by
BHUTH are non-clinical service, environmental health, medico legal certification, food supply,
human resource, laundry, finance, security service.

3. THE DESCRIPTION OF EXISTING SYSTEM

The existing system that Bule Hora University teaching hospital currently uses is
manual system to perform all their tasks and registration of new patients as well as search for
existing patient record its also results in loss of the data, unsatisfactory of customers, lack of
security of data, wastage of time, customer large volume of paper work, wastage of too many
hardware material and loss of their files.

3.1. PROBLEMS WITH THE CURRENT SYSTEM

(The existing system drawbacks)

We observe so many problems that affect the patients of the that use their service .

 Wastage of working materials like papers and cards.

 Data are not placed securely.

 Time wastage on recording data.

 Some of the data may be captured more than once.

 The hand writing (calligraphy) on the card might not be readable which leads
to recording incomplete data (the required data is not fully captured).

 Lack of prompt updating.

 Lack of immediate information retrievals.

Page 2 of 24
 3.2 METHODS OF DATA COLLECTION

3.2.1. Interviewing This means that we took information about Bule hora university

teaching hospital its establishment as well as what it does and how it treats patients
and so on in the form of interviews.
3.2.2. Observation: observation is information about how the patient is treated and
what is done in the hospital, how the patient is receiving treatment and the
relationships between the doctor and the patient. A follow up was made to
determine the time it took to carry out the patient information management system.
We observed the systems weaknesses like it was vulnerable to errors.

3.2.3. Documents document is what we have taken from the existing

written form of what the background of the hospital looks like

4. Functional requirements (basic functions of the system)

The functional requirements deal with the functionality of the new system. It
describes the interaction between the system and different users independent of
its implementation. Therefore the following functional requirements are state for the new
automated system.
The basic functionality of BHUTH are:-
 Provide different user account: The new systems provide account and permits
users to login according to their privilege.
 Update and modify patient information: The authorized users of the system canard, delete,
modify or change patient’s information whenever possible.
 Provide some information about the hospital: T h e n e w s y s t e m s p
r o v i d e i n f o r m a t i o n about Bule Hora hospital include background, vision, and
mission.
 Show patient information (viewing and accessing): The system can display or show
the stored basic information of the patients.

Page 3 of 24
  Provide referral to specialized medical institutions: T h e n e w s y s t e m a l l o w
t r a n s f e r patient to specialized medical institutions.
-Provide appointment for Out-Patient.
-Provide laboratory test results Provide X-ray test result.
- Provide Ultra sound test result.
 Register new patient: This new system allow to registers each patient records and their basic
information on database.
 Search for existing patient from database: This enables the users of the system to find patient
information from database which is previously registered.
 View Appointment; This new system display patient appointment
d a y a n d patient can view their appointment.
 View Noticeboard send from admin:-T h e n e w s y s t e m a l l o w p a t i e n t t o
v i e w m e s s a g e when admin send message by using noticeboard

5. Non-Functional requirements (additional functions of the system)

Non-functional requirements are also known as quality requirements which impose
constraint on the design or implementation. It describes about the non-functional requirement
of the system like security, performance, availability, accuracy and etc.

5.1 Security Requirements

Security: Security becomes crucial issue in the new system. A user must login to the system
with user name and password. The system allow login to only authorized users.

5.2 Performance Requirements

Performance: The system have networked database. So, this can tell that the system can be
used by different users. This allows many users can perform their actions simultaneously.

5.3 Availability Requirements

Availability: The system is easily available at any desired time.

5.4 Accuracy Requirements

Accuracy: The system give valid result, if no data is found with the specified criteria the
system should not give invalid response.

Page 4 of 24
5.5 Ease accessibility Requirements
Ease accessibility: web based patient information management system is easily accessible.

5.6 System portability Requirements

System portability: ability to use the system anywhere, any time with any browsing device.

5.7 Efficiency Requirements

Efficiency: The systems provide easy and fast access for staff with less cost and time.

6. Entities, attributes, Relationships and Constraints on data

6.1 Identify Entities

 Entity:-is the real world physical or logical objects.

In our patient information management system we have the following entities.

 Hospital
 Patient
 Doctor
 Medical record

6.2. Identify Attributes

 Attribute is properties used to describe each entity or real world object.

Attributes of patient entities

Patient entities is one of the patient information management system entities which contains the

Following attributes.

 Pname
 Paddress
 Pid.
 Age

Page 5 of 24
  Sex

Attributes of Hospital Entities

Hospital entity contains the following attributes such as.

 Hosp_name
 Hosp_id
 Hosp_address
 Phone

Page 6 of 24
 Attributes of Doctor Entities

The following are the attributes of the Doctor entity which are.

 Dname
 Doc_id
 Qualification
 Address
 Salary

Attributes of Medical record Entities

The following are the attributes of the Medical record entity which are.

 Record_id
 Problem
 Date_of_examination

Page 7 of 24
 6.3. Identify Relationships
 Relationship is the condition or fact of being entity related to connected/
associated.

Here are relationships that can exist between the above entities.

Patient and Doctor: Many doctors can treat one patient.

Hospital and Patients: Hospital holds many patients.
Hospital and Doctors: hospital holds set of doctors.
Medical record and patient: patient may have various tests
o The cardinality of each entity relationship
 Many –to-one:-Relationship between patient and doctor.

 One-to-Many:-Relationship between hospital and patient.

Page 8 of 24
  One-to-Many:-Relationship between hospital and doctor.

 Many-to-one:-Relationship between medical record and patient.

7. ENTITY RELATIONSHIP DIAGRAM OF BHUTH (ER- DIAGRAM)

Page 9 of 24
8 .Relational schema (logical schema)

 Relation schema: is a list of attribute and their corresponding domains and its
description.

1. Patient entity

Pid Pname Paddress Age Sex

City Kebele

2. Hospital Entity

Hosp_name Hosp_id phone Hosp_address

Page 10 of 24
3. Doctor Entity

Doc_id Dname Address Qualification Salary

4. Medical record entity

Record_id Problem Date_of_examination

9. NORMALIZATION
 We are going to normalize each table based on insertion, updating, and deletion for each
entity that wants normalization we have to normalize each table by using normalization
rules to optimize the table.

The tables that need normalization are.

Patient
Hospital
Doctor

1. First normal form.

 No duplicate value meaning that each set column must have a unique value.
 Relation should have a primary key.
2. Second normal form.
 No partial dependency of column on primary key.
3. Third normal form.
 Elimination of transitive dependency.
 If non key- attribute determines another non key attribute create a separate table
to eliminate that attribute.

 Normalization of the patient table

Page 11 of 24
1st Normal form

Patient (PID, Pname, Paddress, Age, sex).

Table should contain atomic attributes and should also have a primary key, which in our
case is Pid for the patient table.

2nd Normal form

Patient (PID, Pname, Paddress, Age, sex).

There is no partial dependency since we have a single primary key.

i.e. Patient (Pid, Pname, Paddress, Age, sex).

3rd Normal form

Patient (Pid, Pname, Paddress, Age, sex).

There is no transitive dependency in the relation so this relation fulfill the 3 rd normal
form.
Patient (Pid, Pname, Paddress, Age, sex).
 Normalization of the hospital table

1st Normal form

Hospital (Hosp_id, phone,Hosp_address(city,kebele)).

The table should contain atomic values for its attributes so we need to normalize this table
to the form in which it contain atomic values.
The normalized relation will be.

Hospital (Hosp_id, phone,Hosp_address(city,kebele)).

2nd Normal form

Hospital (Hosp_id, phone,Hosp_address(city,kebele)).

There is no partial dependency since the relation only contains a single primary key.

Page 12 of 24
 Hospital (Hosp_id, phone,Hosp_address(city,kebele)).

3rd Normal form

Hospital (Hos_id, Hos_id, phone, city, kebele)).

Again there is no transitive dependency in this relation, so there is no need of creating

other derived relation from this table.

i.e Hospital (Hos_id, Hos_id, phone , city,kebele).

 Normalization of the Doctor table

1st Normal form

Doctor (Doc_id, Dname, address, qualification, salary)

The table should contain a single/ atomic value and also should contain a primary key in
which in our case our table does.

Doctor (Doc_id, Dname, address, qualification, salary)

2nd Normal form
Doctor (Doc_id, Dname, address, qualification, salary)
There should be no partial dependency, which our table has already satisfied by only
having a single primary key.

i.e Doctor (Doc_id, Dname, address, qualification, salary)

3rd Normal form

Doctor (Doc_id, Dname, address, qualification, salary)

There is the dependency between some non- key attributes, which are found in the
address attributes, so we need to normalize the relation using the 3rd normal form.

D_address (Doc_id, Region, city, kebele).

Page 13 of 24
10. The Final class Diagram

Page 14 of 24
11. PHYSICAL DATABASE DESIGN

Page 15 of 24
Page 16 of 24