Scribd
Upload
170 views6 pages

HealthOne Medical Project

This document provides instructions for developing a conceptual data model for a medical database. It includes identifying key entities like patients, doctors, hospitals, prescriptions and their attributes. Relationships between entities such as each patient having one primary doctor, doctors treating multiple patients, and prescriptions being prescribed by one doctor for a patient are also to be identified. The conceptual model will form the basis for the medical database to track patient, doctor and prescription information.

Uploaded by

Edda Shkurti
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
170 views6 pages

HealthOne Medical Project

This document provides instructions for developing a conceptual data model for a medical database. It includes identifying key entities like patients, doctors, hospitals, prescriptions and their attributes. Relationships between entities such as each patient having one primary doctor, doctors treating multiple patients, and prescriptions being prescribed by one doctor for a patient are also to be identified. The conceptual model will form the basis for the medical database to track patient, doctor and prescription information.

Uploaded by

Edda Shkurti
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/ 6

HealthOne Medical Project

Edda Shkurti
Determining entities, attributes, UIDs

Based on the business scenario stated above you will identify the
database needs,
and then create a conceptual data model to support these needs.
1. Review the types of information a medical database may contain. Read
articles
and check
the internet to understand the challenges of tracking this information.
2. Research medical information to better understand your topic. Look
for the type of
information you will need to track.
3. Build a list of business needs, rules and assumptions based on your
scenario,
research, and objectives.

Ex) Each patient can only have one primary care doctor at a time.
Develop a list of potential entities including their attributes, the attribute’s optionality as
well as a possible UID for each entity.

# Patient ID
* Name
HOSPITAL
* Address
# Hospital ID
* Phone
* Name
* Email
* Address PRESCRIPTION
* Insurance ID
* Contact Number # Prescription ID
#Doctor ID
#Patient ID
* Prescription Name
DOCTOR * Prescription Date
# Doctor ID * Repeat P
* Name * Dosage
* Address *Time scale
* Contact info * Side Effects
* Benefits
Step 2: Supertypes and subtypes
Step 3 : Relationships
While creating your entities you should have been thinking about what relationships
the entities would have with each other. Create the relationships between your
entities including the relationship’s optionality and cardinality.

1. Write out the ERDish for each of the relationships.

Each PATIENT must have one and only one DOCTOR (their primary
doctor)
Each DOCTOR may treat one or more PATIENT.
Each DOCTOR may have one or more HOSPITAL AFFILIATION.
Each HOSPITAL AFFILIATION must be for one and only one DOCTOR.
Each HOSPITAL may have one or more HOSPITAL AFFILIATION.
Each HOSPITAL AFFILIATION must be for one and only one HOSPITAL.
Each PATIENT may be given one or more PRESCRIPTION.
Each PRESCRIPTION must be for one and only one PATIENT.
Each PATIENT may have one or more OFFICE VISIT.
Each OFFICE VISIT must be for one and only one PATIENT.
Each DOCTOR may preside over one or more OFFICE VISIT.
Each OFFICE VISIT must be presided over by one and only one DOCTOR.
Each DOCTOR may prescribe one or more PRESCRIPTION.
Each PRESCRIPTION must be prescribed by one and only one DOCTOR.

You might also like