Project 2a
BUS 141-05
th

In the hospital system, one of its main purpose is to ensure there is a continuous flow of patients coming in and out for diagnosis and treatment. Accurate patient information is a crucial piece for managing patients to ensure they get the right treatment from a designated provider (for example doctors and nurses). The information that the Doctor provides in terms of diagnosis, also needs to be accurate and recorded onto the correct patient file before a patient may proceed for treatment. As you can see, for a medical system to function smoothly there needs to be an accurate database that acts as a bridge to join these two entities of information together.
The purpose of this database design project is to first identify the key entities for a business process for the purpose of creating an Entity-Relationship Diagram (ERD).
The business process I have chosen to examine is the Hospital Operation Room and how a database maybe used to ensure that the right patient goes to the right doctor to get the right surgery. This initial structural database design will then facilitate the next project which is to transfer the information from the ERD diagram into a
Microsoft Access database file.
The structure of the database will answer the following questions.
 Who is the patient, and how do we identify them
 How do we contact the patient for surgery and follow up?
 Where does the patient live?
 What is the diagnosis?
 What is the description of the surgery?
 What is the patient encounter number for the hospital visit?
 When is the date of surgery?
 Who is the Doctor?
 What is the contact details for the Doctor?
 What area of specialty does the Doctor give service in?
 What is the Procedure ID number for the day of surgery?

My goals from the created database is to
 ensure that the right Patient gets the right Surgery from the right Doctor
 Surgery dates are not double booked
The Primary Entities for a Hospital Operation Room are Patient, Encounter, Doctor and Procedure.
Using this diagram I can describe the relationship between the four entities. Firstly, when a patient is encountered at the hospital, they are given one encounter number for that one visit. If they come back to the hospital the next day, they would be given a different encounter number for the next visit. Therefore, for every one patient, they may have many hospital encounters (1:M), and for every one doctor they may have many patient encounters to attend to(1:M). If the patient is coming into the hospital for surgery, besides the encounter number, they would also be given a procedure identification number as well. The relationship between encounter to procedure is one to one (1:1) meaning for every one hospital encounter there should only be one surgery procedure. Once the surgery is performed the patient is either discharged or become an inpatient; if they stay, they would then be given a new encounter number for the hospital ward they are admitted to. Each of the entities mentioned in the above diagram has its own unique set of attibutes and will be outlined on the Table Map.

The expanded table map includes the following fields (attributes):
PATIENT
PK Patient ID
First Name
Last Name
DOB
MRN #
PHN #
Gender
Street
City
Postcode
Province
Phone
Email
Next of Kin
Comment
ENCOUNTER
PK Encounter ID
FK Patient ID
Doctor ID
Diagnosis
Procedure ID
Surgery Date
Facility
Location
Encounter Status
Comment
FK
PROCEDURE
PK Procedure ID
Description
Comment
FK
DOCTOR
PK Doctor ID
First Name
Last Name
License #
Discipline
Phone
Email
Comment
PK : Primary Key
FK : Foreign Key

The following data dictionaries provide more detail on each entity and its attributes.
PATIENTS
Field Name
Patient ID
First Name
Last Name
DOB
MRN #
PHN #
Gender
Street
City
Postcode
Province
Phone
Email
Next of Kin
Comment
ENCOUNTERS
Field Name
Encounter ID
Patient ID
Doctor ID
Field Type
Autonumber
Number
Number
Diagnosis
Procedure ID
Surgery Date
Facility
Location
Memo
Number
Date/Time
Text
Text
Encounter Status Yes/No
Comment Memo
Field Type
Autonumber
Text
Text
Date/Time
Text
Text
Text
Text
Text
Text
Text
Text
Hyperlink
Text
Memo
Size Properties
Primary Key
20 includes patient first and middle name
20 patient last name patient birthday
20 Hospital Medical Record Number
30 Provincial Health Number - Care Card # choose (F)emale, (M)ale or (?)Unknown
30 patient address
20
6 format as A0A-0A0
2 from lookup: Canadian Provinces
10 Format as (250) 123-4567
30
30
May include Patient History
Size Properties
Primary Key
Foreign Key to Patient Table
Foreign Key to Doctor Table surgery ID number
Date of surgery
5 from lookup: building acroynm
5 from lookup: ward acroynm
Inpatient or Discharged
Other information not included above

DOCTOR
Field Name Field Type
Doctor ID Autonumber
First Name
Last Name
Text
Text
License #
Discipline
Phone #
Email
Comment text
Text
Text
Hyperlink
Memo
PROCEDURE
Field Name Field Type
Procedure ID Autonumber
Description Memo
Comment Memo
Size Properties
Primary Key
20 include first name and middle name
20
Medical License Number
100 Area of Speciality
10 In format (250) 123-4567
Physican's email
Other information not included above
Size Properties
Primary Key
Details of Surgery
Any information not included above