Question

You must create an ERD diagram for medical office wait times for patients with the following minimum requirements.

Your ERD diagram must include your Business Rules with a min. of 10 rules

At least 5 entities. These may be real (e.g. a person, vehicle, etc.) or abstract concepts (e.g. course, enrollment, categories, etc.)

• There must be logical relationships between the entities.

• Aim for all entities to have a minimum of seven attributes, but no fewer than 3 entities should meet this requirement.

Must be in MS Visio

Answer 1

ERD diagram for medical office wait times for patients

Business rules

1. The patient must register with the informations fist name, last name, gender, date of birth, phone number and email. A unique id for the patient is created after the registration.

2. A patient may have one or more illness and the start date and status of each illness is recorded.

3. There are a number of departments in the medical office. Each department has a department id and name.

4. Each department has a number of doctors works for that department.

5. The details of a doctor include fist name, last name, gender, address, phone number and email. Each doctor is identified using a unique id.

6. A doctor works for only one department.

7. A doctor may have one or more qualifications. The qualifiction code, name, date and university for each qualification are recorded.

8. A patient makes an appointment for a doctor. The date and time of appointment and status of appointment are recorded. Each appointment has a a unique id.

9. A patient can make one or more appointments on the same date.

10. A doctor may have one or more appointments on the same date.

ERD

• Patient has relationship with MedicalHistory and it is a one-to-many relationship. PatientID is given in the MedicalHistory as foreign key to referer the primary key of Patient.
• Doctor has relationship with Qualification and it is a one-to-many relationship. DoctorID is given in the Qualification as foreign key to referer the primary key of Doctor.
• Department has relationship with Doctor and it is a one-to-many relationship. DepartmentID is given in the Doctor as foreign key to referer the primary key of Department.
• Doctor has relationship with Appointment and it is a one-to-many relationship. DoctorID is given in the Appointment as foreign key to referer the primary key of Doctor.
• Patient has relationship with Appointment and it is a one-to-many relationship. PatientID is given in the Appointment as foreign key to referer the primary key of Patient.