Final Project Report
Relational Database Management
CNET 323
Centennial College
Computer Systems Technology-Networking
April 28, 2018
Submitted to:
Prof. Rukmani Ramasubbaralyalu
Submitted by:
Harshita Gupta (300896538)
Sushmitha Devi Revuri (300907102)
Sukhdeep Kaur (300918329)
Prasad Avulam (300908435)
1
Table of Contents
Project Definition………………………………………………………………….3
Project Analysis…………………………………………………………………....4
Fact Finding………………………………………………………………....5
Business Rules………………………………………………………………6
Database System Users……………………………………………………...7
Data Requirements………………………………………………………………....8
Users Data Requirements……………………………………………………8
Relationship Table…………………………………………………………...9
Entity-Relationship Diagram……………………………………………….10
Normalization……………………………………………………………………..14
Entity Diagram…………………………………………………………………….16
Conclusion………………………………………………………………………...18
References………………………………………………………………………...19
2
Project Definition
This is a document that is made to provide project proposal on Hospital Management System.
This system is used to manage the hospital database, there are certain operations that needs to be
considered such as reception desk, main office, inventory, security, medicine, and more. Hospital
management is important because of number of reasons. There is a need to keep track of records
of patients, doctors, nurses and staff of hospital. But if these records are maintained on paper, it
is very hard to manage all the records properly. It is not only time-consuming process but also
not reliable and efficient. Therefore, this automated system will be very useful in maintaining the
records and keeping track of all activities.
The hospital database contains patient details such as patient identity, name, sex, address, date
admitted, date discharged, contact number etc. All reports related to patient such as laboratory
information, check-up report is also stored in the database. In addition to that, doctor’s
information like name, specialization, consultation timings, classification (permanent, trainee,
visiting) is also included in the management database.
3
Problem Analysis
MedCan Hospital established in 1997, receiving services from the DocSmart for their database
management since its establishment. They are currently managing their database activities using
spreadsheet and paper-based systems that is not reliable and convenient way to managing data.
MedCan is looking for an automated system that can manage their data or records quickly and
efficiently.
The proposed database management system will improve the reliability, integrity and timely
management of the hospital database which can enhance the operations of the hospital.
Objectives of proposed system:
• Easy Record Management – It is easy to maintain and keep track of record of doctors,
patients, nurses and more.
• Data Automation - All the information either regarding patient, doctor or hospital will
be computerized irrespective of size and can be accessed online.
• Automated inventory – This proposed system will provide automated updates or
notifications on the stock expiry, availability. It will notify the status of inventory if stock
is about to finish.
• Appointment – It is easy to book appointments as it is just a matter of 2-3 clicks. Both
patients as well as doctors can manage their appointments conveniently.
• Security- This provides a secure system where only authorized user can access the data.
Data is safe as authorization is required to access it.
• Disaster Recovery- This provides automatic and manual backup of the database.
4
Fact Finding
Hospital is having over 130 employees including 15 doctors. There are total 45 rooms including
25 patient rooms, 1 operation theatre. Hospital is having 5 ambulances which are in service.
Hospital is serving in an average of 300 patients per day in patient and out patients collectively.
Patient Details:
· Patient ID
· Name
· Contact no.
· Email
· Address
· Sex
· Date admitted
· Date discharged
· Room allocated
Room Details:
· Room id
· Room type
· Period the room is allocated
Employee Details:
· Employee ID
· Employee name
· Contact no.
· Email
· Employee Address
· Sex
5
· History
· Salary
Receptionist maintains:
· Record No.
· Patient id
· Description
· Appointment
Business Rules
· An entry must be made into the records when any room is allocated to a patient.
· Each user whether he/she is a doctor, nurse, patient or other staff member must have
individual ID and password
· User must log in to the system to access any record
· Only Administrator can delete records
· Server must be running for the system to function
· Any technical issues should be reported to the IT department
6
Database System Users
Admin
Admin is the one who has full access to the system and able to add, modify or delete the records.
Key functions:
• Manage patient and employee record
• Manage doctors
• Manage salaries
• Generate reports
• Manage ambulances
• Allocate resources
• Administer the charges
Employee
Employee is one who often interacts with the system in order to provide service to users.
Key functions:
• Keep track of details of patients
• Maintain bill details
• Keep track of progress of patients
• Keep track of test details
• Manage inventory
• Make ambulance reservations
7
Users Data Requirements
User data Users Fields
requirements
Add patient Employee Name, PID, Address, date of admission, date of
information discharge, contact info, sex
Add Doctor Admin NAME, DID, Address, date of joining, date of
information relieving, contact info, sex, specialization, type,
consulting timings
search Booking Employee Booking ID, PID, Patient name, doctors name,
information contact number, time of booking, booking through,
booking done by
Ambulance Employee Ambulance ID, Type, Time of booking, patient ID,
reservation Contact details
Book an Employee Booking ID, patient name, PID, doctors name,
appointment contact number, time of booking, booking through,
booking done by
Search patient Employee Name, PID, Address, date of admission, date of
record discharge, contact info, sex, room no. Patient
reports, bill
Add ambulance Admin Ambulance ID, Equipment, Type, Vehicle No,
Vehicle registration
8
Relationship Table
Table Name Relationship Table Name
Patient 1:M PatientDiagnosis
Patient M:1 PatientRoom
Patient 1:M PatientRecords
Doctor M:1 PatientRecords
Doctor M:M Staff
PatientBills 1:M BillItems
Staff M:1 PatientRecords
PatientRecords 1:M PatientBills
Reception 1:M PatientRecords
9
Entity-Relationship Diagram (E-R)
Patient PatientDiagnosis Doctor
PK Patient_ID PK Diagnosis_Num PK Doctor_ID
Patient_FirstName Date Doctor_Name
Patient_LastName Remarks Doctor_Address
Patient_Age FK Patient_ID Doctor_Department
Patient_Gender
Patient_Address
PatientRecords
Patient_Contact Staff
PK Record_ID
PK Staff_ID
FK Patient_ID
PatientRoom Staff_Name
Patient_Admit_Date
PK Room_Num Staff_Gender
Medical_Condition
Staff_Department
FK Patient_ID Condition_Updates
FK Doctor_ID
Date_Stay_From FK Recep_ID
Date_Leave_At FK Doctor_ID
Floor FK Staff_ID
Bill_Item
Reception PK Item_Sequence
PatientBills
PK Recep_ID FK Bill_Num
PK Bill_Num
Recep_Name Item_Quantity
Bill_Title
Recep_Contact Item_Cost
Amount
FK Record_ID
10
Database Constrains
• Primary key field should not be empty.
• Each row and column should have its unique value.
• Patient and reception tables, contact fields cannot have null value.
Metadata Information
Table Name: Patient
Attribute key type Description Data Type Required
Primary Unique auto-number
Patient ID Key Auto Number yes
Patient_FirstName First Name of Patient Short text yes
Patient_LastName Last name of Patient Short text yes
Patient_Age Age of a Patient Number yes
Patient_Gender Gender of a Patient Drop Down yes
Patient_Address Address of Patient Long Text yes
Patient_Contact Contact number of Patient Number yes
Table Name: Patient Diagnosis
Attribute key type Description Data Type Required
Diagnosis_Num Primary Key Unique auto-number Auto Number yes
Date Date of Diagnosis/test Date yes
Detailed description of the
Remarks condition of patient Long text yes
Patient_ID Foreign key From Patient Table Number yes
Table Name: Doctor
Attribute key type Description Data Type Required
Primary Unique auto-number Auto
Doctor_ID Key Number Yes
Doctor_Name Name of the Doctor Short text Yes
Address of the Doctor which
could be used in emergency
Doctor_Address consultation. Short Text Yes
Type of treatment done by
Doctor_Department Doctor like physician Short text Yes
11
Table Name: Patient Room
Attribute key type Description Data Type Required
Room_Num Primary Key Unique auto-number Auto Number Yes
Patient_ID Foreign key From Patient Table Number Yes
Patient stayed/admitted in the
Date_stay_From room Date Yes
Date_Leave_at Patient discharged from the room Date Yes
Floor Floor in which patient room is Number Yes
Table Name: Patient Records
Attribute key type Description Data Type Required
Record_ID Primary Key Unique auto-number Auto Number yes
Patient_ID Foreign Key From the Patient table Number yes
Patient_Admit_Date When patient got admitted Date yes
Condition of patient health,
Medical_Condition either critical or normal Long text yes
Updating the Patient health
condition for every 24
Condition_Updates hours at least Short text yes
Recep_ID Foreign Key From the reception Table Number Yes
Doctor_ID Foreign Key From the Doctor Table Number yes
Staff_ID Foreign Key From the Staff Table Number Yes
Table Name: Staff
Attribute key type Description Data Type Required
Staff_ID Primary Key Unique auto-number Auto Number Yes
Staff_Name Name of the Staff Short text Yes
Staff_Gender Gender of the Staff Drop Down No
To know in which department
Staff_Department they work Short text Yes
Doctor_ID Foreign key From the Doctor table Number Yes
12
Table Name: Reception
Attribute key type Description Data Type Required
Recep_ID Primary Key Unique auto-number Auto Number Yes
Recep_Name Name of the Staff Short text Yes
Reception contact number for
Recep_Contact enquiries Number Yes
Table Name: Patient Bills
Attribute key type Description Data Type Required
Bill_Num Primary Key Bill number of the patient Auto Number Yes
Brief description of
Bill_Title Treatment/medicine bills Long text Yes
Total cost of medicines
Amount purchased Number Yes
Record_ID Foreign key Form the Patient Record Table Number Yes
Table Name: Bill_Item
Attribute key type Description Data Type Required
Sequence number of each
Item_Sequence Primary Key medicine Auto Number Yes
Bill_Num Foreign key From the Patient bills table Number Yes
How many items/medicines
Item_Quantity purchased Number Yes
Total sold items and its gross
Item_Cost value. Number Yes
13
Normalization
We have submitted ER diagram, Constrains and metadata information of Hospital Management
System in the Phase 2. Phase 3 would be very helpful to explain in detail in its Normalization
forms. As 3NF implementation of tables is very easy and convenient, we used in Phase 3.
Moreover, it helps in removing the integrity problem.
The following graph design is 3NF:
Each field could be easily identified as we used different Colors:
Primary key: Rose
Other field: Light Blue
Foreign key: Orange
3NF NORMALIZATION RESULTS
Table Name: Patient
Patient Patient_Firstnam Patient_LastName Patient_Ag Patient_Gender Patient_Address Patient_
ID e e Contact
Table Name: Patient Diagnosis
Diagnosis_Num Patient_ID FK Date Remarks
Table Name: Doctor
Doctor_ID Doctor_Name Doctor_Address Doctor_Department
14
Table Name: Patient Room
Room_Num Patient_ID FK Date_stay_From Date_Leave_at Floor
Table Name: Patient Records
Record_ID Patient_ID_FK Patient_Admit_Date Medical_Condition Condition_Updates
Recep_ID Doctor_ID Staff_ID
Table Name: Staff
Staff_ID Doctor_ID Staff_Name Staff_Gender Staff_Department
FK
Table Name: Reception
Recep_ID Recep_Name Recep_Contact
15
Table Name: Patient Bills
Bill_Num Record_ID Bill_Title Amount
FK
Table Name: Bill Item
Item_Sequence Bill_Num FK Item_Quantity Item_Cost
Entity Diagram
16
Doctor Table
Patient Table
17
Conclusion
This course helped us in acquiring more knowledge in database design, coding skills in a real-
world scenario, and advanced our interpersonal skills such as team work, time management,
report delivery during the development and implementation of this project. This data base has
been created in such a way that future developments can be incorporated with ease. Our team
was successful in developing the database with all the requirements of the client.
18
References
• Use a command button to start an action or a series of actions. (n.d.). Retrieved from
https://support.office.com/en-us/article/use-a-command-button-to-start-an-action-or-a-series-of-
actions-c7bf2827-2f3e-42b8-83d6-6c4f0de78990
• How to Create a Login Form for MS Access. (2016, November 07). Retrieved from
http://accesshosting.com/create-login-form-ms-access
• Baycon Group, Inc. (n.d.). Creating Reports. Retrieved from
http://www.baycongroup.com/access2007/07_access.html
19
