Question:

Create the EER diagram ( NOT UML ) for your design and states any assumptions that you made for your design choices and the Relational Schema of your EER diagram : The physicians they interact with, the consultations they attend, the insurance coverage they are enrolled in , and the medical facilities involved in their care. Here are the requirements for the database: 1 . The database will store information about each PHYSICIAN working at a HOSPITAL, the SPECIALITY associated with each physician, the COVERAGE _ POLICY each patient is enrolled in , and each CONSULTATION attended by a patient.  2 . The database tracks information for the APC Center used in a healthcare environment. Each PATIENT has a unique PSSN ( Patient Social Security Number ) , and attributes including PName ( patient ’ s name ) , Sex, Address, and DateOfBirth. 3 . For each PHYSICIAN, the database keeps track of PId ( unique physician ID ) , PName, Physician ’ s full name comprised of FName, LName, MInitial. Each physician is associated with one and only one HOSPITAL. The database will also maintain the relationship Specializes _ IN between a PHYSICIAN and one or more SPECIALITY. Each SPECIALITY has a unique SName. A physician may specialize in one or more SPECIALITY. APC has one or more PHYSICIANs that specialize in each of their SPECIALITY. 4 . Each HOSPITAL is represented with attributes including HId ( HospitalId unique identifier ) and HName ( Hospital Name ) . One HOSPITAL may employ many PHYSICIANs, but each PHYSICIAN is affiliated with only one HOSPITAL. A hospital may have one or more Locations. 5 . A PHYSICIAN is assigned primary for many PATIENTS. However, a PATIENT has only one PHYSICIAN assigned their primary ( ASSIGNED _ PRIMARY ) .  6 . Each PATIENT may attend multiple CONSULTATIONs over time. Each CONSULTATION is associated with exactly one PATIENT. A CONSULTATION has a CDate, CTime ( unique per patient ) , FDate ( FollowUpDate ) and FTime ( FollowUpTime ) . At times follow up Is not required. Since a CONSULTATION does not have a global identifier, it is additionally identified by the PATIENT  7 . A PHYSICIAN treats / consults during a CONSULTATION and gives one or more Diagnosis. A PHYSICIAN can treat / consult during different CONSULTATIONs, however, they are done one at a time. A PATIENT attends one consultation at a time to be treated by a PHYSICIAN.  8 . Each PATIENT may be ENROLLED _ IN one COVERAGE _ POLICY plan. A COVERAGE _ POLICY has attributes such as PoId ( unique ID ) , PoName, and PoType. A COVERAGE _ POLICY may apply to many PATIENTs. The system should support future extensions, such as tracking procedures, prescriptions, or patient lab results, but for this phase, focus will remain on modeling core data: physician assignments, patient consultations, insurance coverage, and healthcare facility affiliations