William Barajas

Mercedes Garcia
Eric Ybarra
Part 1: Project Description

1) Summary of the scope of project:

Our organization consists of various clinic/urgent care facilities. The idea is that
there are four different clinics in a town that see patients either as “walk-ins” or as a
scheduled appointment with a primary care doctor. The patient can go to any of the four
clinics, and will have the same patient ID for all. It will be interchangeable, so if a patient is
seen in clinicA and then is later seen at clinicB, all of the patient’s information (medical
records or billing info) will be viewable to clinicB. The purpose of this database is to have all
the information of each branch/clinic, patient info, and purpose of the visit. It will enable all
the different branches to have current patient information, such as visit history, treatment
history, billing information, and keeps track of the different providers in the various clinics.
Questions that need to addressed is what different tables or entities we will need to
organize all the data. We will need to know what useful information is needed from the
patient and visits. We will also need to know how to relate all this information together.

2)
 3) Currently out database is in 2nd Normal Form (2NF)
This is based on that all attributes are dependent on the key. We have modified our
database by removing out “records” table since it held the same columns as our “DOS”
table. It was redundant data, so we omitted it. We also added a manager_name to our
“branch” table in order to have more data on the different branches. We decided
manager_id was not enough information. We also created a new table “appointments”
which holds visit_Id which is like an account number that can be used to add charges to it,
depending on the treatments from that specific visit. We are still in the process of working
around the different data we will need for the clinics. In addition, we will have to investigate
further as to how we can better relate the tables to eachother.

Name of Table Description

Branch The hospital information
Providers The doctors information and specialty for the patient
Patient Used for information on the patient
Billing Table used for keeping track of the charges of patient
Records Table of records of patients
 Date of Service Used for the type of visit, treatment and medication needed for patient

Branch
Name DataType Constraints Nullable
branch_id int Primary Key No
manager_id int No
address varchar(45) Yes
phoneNum int Yes
Providers_providerID int No

Providers
Name DataType Constraints Nullable
providerID int Primary Key No
firstName varchar(45) No
lastName varchar(45) No
Specialty varchar(45) Yes
Branch_id int No
Patient_id int No
Patients_patient_id int No

Patient
Name DataType Constraints Nullable
patient_id int Primary Key No
pFirstName varchar(45) No
pLastName varchar(45) No
Provider_id int No
Insurance_company varchar(45) Yes
balance int Yes

Billing
Name DataType Constraints Nullable
patient_id int Primary Key No
charges int Yes
payments int Yes
balance int Yes
Insurance_portion int Yes
Patients_patient_id int No

Appointments
Name DataType Constraints Nullable
visit_id int Primary Key No
provider_id int Foreign Key No
patient_id int Foreign Key No
Date of Service
Name DataType Constraints Nullable
date_of_service int Primary Key No
Visit_type varchar(45) Yes
Provider_id int No
Patient_id int No
diagnosis varchar(45) Yes
rx varchar(45) Yes
treatment varchar(45) Yes
Branch_id int No
Branch_branch_id int Foreign Key No
Patients_patient_id int Foreign Key No