In Chapter $3,$ we learned about databases, including $$data modeling$.$ In this assignment, you will design a

data$/$database model in the form of an entity$-$relationship diagram $($ERD$)$ that will define the requirement and

structure for a database to be built.

A healthcare facility has hired you to create a new Patient Appointment Management System $($PAMS$).$ The purpose of

PAMS is for office receptionists to create appointments. These appointments will include information of patients, the

physician they are going to see, the date and location it is going to be held. After the appointment, physicians will

update the appointment record with notes about what occurred during the appointment. Information on insurance

companies will be recorded as well.

Business Rules and Relations:

$$ A patient must have one or many appointments; An appointment can only be taken by one and only

one patient.

$$ A patient may have one and only one insurance company. $($They can have multiple but do not worry

about that for this exercise$)$; An insurance company covers one or many patients.

$$ A physician may attend one or many appointments; An appointment is attended by one and only

one physician.

$$ An appointment is held at one and only one facility; A facility may hold one or many appointments.

$$ A nurse is assigned to one or many physicians; A physician works with one and only one nurse.

Attributes:

Patient $($PatientID$,$ FName, LName, DOB, Street, City, State, ZIP, Phone, Email, InsuranceID$)$

Appointments $($AppointmentID$,$ PatientID, PhysicianID, AppDate, AppTime, FacilityID, Note$)$

Physician $($PhysicianID$,$ FName, LName, DOB, Specialty, NurseID$)$

Nurse $($NurseID$,$ FName, LName, DOB, Specialty$)$

Insurance $($InsuranceID$,$ InsuranceType, ProviderName$)$

Facility $($FacilityID$,$ Street, City, State, Zip, Purpose$)$

Instructions:

Read the business rules above and create an ERD with the entities, relationships and attributes.