Reference no: EM13934956

Implement a relational database for a medical clinic using at least the following business rules:

Everyday this medical clinic handles several patients and hosts several doctors. Each patient needs to register before they can make an appointment with any of the doctors. During registration, several personal details of the patients are collected such as patient name, address, current medication, and information about chronic disease, known allergies, and an identification number in the form of a passport number or a driving license. A patient can make many appointments with one or more doctors in the clinic, and a doctor can accept appointments with many patients. However, each appointment is made with only one doctor, and each appointment references a single patient. Each appointment contains details such as time and venue. Emergency cases do not require an appointment. However, an emergency is entered into the appointment book as "unscheduled" for appointment management purposes. If kept, an appointment yields a visit with the doctor specified in the appointment. The visit yields a diagnosis and, when appropriate, treatment. Diagnosis information includes recommended tests, their results and the doctor's conclusions. A treatment includes prescribed medicines, exercises, and number of days for which treatment needs to be taken. Each visit updates the patient's records to provide a medical history. Each patient visit creates a bill which contains information such as date of the visit, particular doctor's fees, and service charge. Each patient visit is billed by one doctor, and each doctor can bill many patients. Each bill must be paid. However, a bill may be paid off in many installments, and a payment may cover more than one bill. A patient may pay the bill directly, or the bill may be the basis for a claim submitted to an insurance company. If the bill is paid by an insurance company, the deductible is submitted to the patient for payment.

Steps in Design (HINT)

· Design an Entity Relationship Diagram

o Identify the entities, attributes, relationships and cardinality

· Design a relational model using an Entity Relationship Diagram (Conversion Algorithm)

· Implement your tables in the database using SQL commands. You can use the database with your at alacritas/Lawson for creating tables.