Scribd
Upload
6 views1 page

Home4 2025 Updated

The document outlines the requirements for designing an Entity-Relationship (E-R) diagram for a small clinic database, detailing the entities involved such as patients, doctors, medications, procedures, insurance companies, policies, and claims. It specifies the attributes for each entity and the relationships between them, including visits, treatments, prescriptions, and insurance policies. The assignment is due by 11:59 pm (CST) on March 12, 2025.

Uploaded by

kwtjtrd229
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
6 views1 page

Home4 2025 Updated

The document outlines the requirements for designing an Entity-Relationship (E-R) diagram for a small clinic database, detailing the entities involved such as patients, doctors, medications, procedures, insurance companies, policies, and claims. It specifies the attributes for each entity and the relationships between them, including visits, treatments, prescriptions, and insurance policies. The assignment is due by 11:59 pm (CST) on March 12, 2025.

Uploaded by

kwtjtrd229
Copyright
© © All Rights Reserved
We take content rights seriously. If you suspect this is your content, claim it here.
Available Formats
Download as PDF, TXT or read online on Scribd
You are on page 1/ 1

CSC4402 Homework4 Due 11:59 pm (CST) Wednesdy March 12, 2025

Entity-Relationship modeling:

Design an E-R diagram for modeling a small clinic database. The database models the patients, doctors, the
patient’s visits to the doctors, the prescription of medications by the doctors to the patients, the procedures
for treatment/test of the patients, and the patient’s insurance policies, the insurance companies, and the
claims filed on the policy.

You should draw the full E-R diagram such that all attributes for any entity set should be drawn: namely the
E-R diagram should NOT be the simplified version.

Assume the following:

(1) Each Patient is modeled by the attributes P_ID, name, age, address and phone_number.
(2) Each Doctor is modeled by D_ID, name, and speciality.
(3) Each Medication is modeled by M_ID, name, dosage, and price.
(4) Each Procedure is modeled by Proc_ID, name, cost.
(5) Each insurance Company is modeled by Com_ID, name, address, and phone_number.
(6) Each insurance Policy is modeled by Policy_ID, name_of_insured, and effective_date.
(7) Each Claim is modeled by Claim_ID, amount, date_claim, date_paid, status (submitted/ pro-
cessed/paid).
(8) Note that for the above items (1) through (7), each should be modeled as an ENTITY SET. You can
use the word in bold-face above as the name for each such entity set.
(9) Each patient can visit ONE or more doctors. For each patient and doctor (P_ID, D_ID) pair, the pa-
tient (P_ID) can visit the doctor (D_ID) multiple times (but each visit is on a distinct DATE): so you
need to model the date (as an attribute) for the visit (which should be modeled as a relationship).
Here we assume that a patient visits the same doctor at most ONCE in the same day: otherwise you
would need a "time" attribute for the "visit" relationship. Each doctor can be visited by ZERO or
more patients.
(10) The "treatment" is an m-m-m relationship among doctors, patients and procedures, although you can
also model "treatment" as an entity set. For each treatment, you want to model the date of the treat-
ment.
(11) There is a one-to-one relationship between treatment and claim.
(12) The "prescription" is an m-m-m relationship among doctors, patients and medications. Alternatively
you can also model "prescription" as an entity set. For each prescription, you want to model the date
of the prescription and quantity of the medications prescribed.
(13) Each patient has one or more insurance policies, and each policy insures exactly one patient
(name_of_insured). So there is a one-to-many relationship between Patient and Policy.
(14) Each policy is issued by exactly one insurance company, and each company may issue many policies.
This means that there is a one-to-many relationship between insurance Company and Policy.
(15) Each insurance policy has zero or more claims. Each claim identifies exactly ONE policy. Namely,
there is a one-to-many relationship between Policy and Claim.

You might also like