Unit Learning Outcomes

This assessment is relevant to the following Course Learning Outcomes:

$$ ULO a: Discuss database management systems' concepts, types, functions, and

architecture.

$$ ULO b: Apply systems analysis and data modelling techniques to examine business processes and

information requirements.

$$ ULO c: Design a logical database using modern development standards, database

query language and tools.

Part A: Entity$-$Relationship Modelling

You have just been employed as a database designer at SOFTLOGIC, a well$-$established software

development firm. Your first job is to design and implement a database system for MEDI$-$CINE, a Medical

Centre in Melbourne. Following the data$-$gathering process and the analysis of the current practices of

MEDI$-$CINE, the following activities around their business practice have been identified.

$$ The system records information about the doctor$$s work at the medical centre. Doctors have

unique registration numbers. In addition to the registration number for each doctor, the system

records the name, date of birth, gender, qualifications, and specialisations. Doctors can have

multiple qualifications and multiple specialisations.

$$ The system keeps a record of each patient. When a new patient comes to the medical centre, the

patient is given a registration form to be filled. The information gathered in this form will be stored

in the system. When this information is entered into the system, a serial number is assigned to

each patient. The registration form captures the following information: name, address, date of

birth, gender, telephone numbers $($multiple numbers are allowed$),$ Medicare number $($if any$),$

private health cover number $($if any$),$ and private health cover company $($if any$).$

$$ When a patient attends a consultation with a doctor, the following information is recorded:

consultation number, date, time, description, symptoms, and special remarks. Symptoms are a multivaluedattribute.

$$ A number of prescriptions can be recommended after each consultation. For each prescription,

the following information is recorded: name of the medicine, dosage, number of repeats, and

special instructions. None of these attributes are unique. However, for a given consultation,

medicine is prescribed only once.

$$ The doctors sometimes make referrals for other procedures, such as X$-$rays, MRI, and

physiotherapy. The system should be able to record such referrals made at Computer Science

and Information Technology consultations. For each referral, the following information is

recorded: name of the procedure, short description, referred practitioner, and whether this

procedure is essential or optional. Like prescriptions, a referral for a given procedure is only

made once in a consultation.

$$ The system should be able to keep accounting information. In particular, the system should be able

to store payments made for the consultations. There are three possibilities:

$1.$ Bulk$-$billing: Some Medicare patients $($disabled and seniors$)$ are bulk$-$billed. This means that

the patient is not required to pay anything up$-$front. The medical Centre will bulk$-$bill Medicare

$($the government agency that deals with healthcare services in Australia$)$ the costs associated

with the consultation. The medical Centre will record the payment number, timestamp,

amount, and Medicare reference number for such transactions.

$2.$ full up$-$front payments $($cash or card$)$: Patients with no Medicare benefits are required to

pay the full cost of the consultation up$-$front. The medical Centre will record the payment

number, timestamp, amount paid, and payment method for such payments.

$3.$ settling part of the invoice using a Medicare benefit and the balance in cash or card:

Some Medicare patients must make a top$-$up payment $($gap fee$).$ That means part of the

consultation fee is covered by Medicare benefits, and the patient pays the rest up$-$front. For

such transactions, two payment records are created and stored. $($They both are linked to one

consultation$).$ The first record will be similar to $(1)$ above. The second is similar to $(2)$ above.

Based on your gathered information, model your MIDECINE$$s business activities and present your

model as an Entity$-$Relationship $($ER$)$ diagram. Carefully state any assumptions that you make. In your

ER diagram, you must adequately denote all applicable concepts, including weak or strong entities,

keys, composite or multi$-$valued attributes, relationships and their cardinality and participation

constraints.

If you cannot represent any of the information in the ER model, clearly explain what limitations in the ER

model restrict you from representing your model.

You must draw your diagram using UML notation and the diagramming tool LucidChart. Your diagram

must be drawn to a high standard with minimal clutter. You are not required to map the ER model to the

relational model.

A special note: This is an open$-$ended question with many different models th