Database Management Systems
Database Management Systems
Student Name:
Student Number:
Professor:
Date:
Part A
Introduction
its business operations including storing patient and administrative data. As part of this initiative,
a conceptual data model has been designed to represent the center’s key operations using the
Entity-Relationship (ER) model. The ER diagram generated and shown below is specifically
aimed at digitizing and saving essential operations and data of the medical center, including
doctor and patient details, consultations, prescriptions, referrals, and different types of payments.
To ensure diversity in billing methods, the Payment entity has a generalization hierarchy which
splits the entity into two specific subtypes: BulkBilling and FullUpfront. This generalization is
disjoint, meaning that a payment instance must be either a bulk-billing or a full-upfront payment.
Entities and Attributes.
The core entities in the system include Doctor, Patient, Consultation, Prescription,
Referral, and Payment. Each entity is defined with distinguishable attributes and primary keys, as
follows:
Qualifications(multi-valued),
Specializations (multi-valued)
DateOfBirth, Gender,
TelephoneNumbers (multi-
valued), MedicareNumber,
PrivateHealthCoverNumber,
PrivateHealthCoverCompany
DateOfBirth, Gender,
TelephoneNumbers (multi-
valued), MedicareNumber,
PrivateHealthCoverNumber,
PrivateHealthCoverCompany
MedicineName) SpecialInstructions
EssentialOrOptional
(subtype of Payment)
Payment)
have zero or many consultations while each consultation is conducted by one doctor.
can have multiple consultations but each consultation is linked to exactly one patient.
mixed payment methods including bulk billing and full upfront payments.
Assumptions
Mixed payments are stored as two distinct Payment records rather than a new, separate
entity.
Model Limitations
The use of the mentioned ER model seems helpful in depicting the structural and the
Notably, it does not support procedural logic or rule enforcement. For example, the model cannot
validate whether a patient is eligible for Medicare or determine the exact conditions that trigger a
mixed payment. Such logic would need to be implemented in the application or business logic