Ass 1 Database
Ass 1 Database
Case Study:
At the core of the HMS, patients are the focal point of care. Each patient may undergo multiple
interactions and procedures during their hospital stay.
Patients undergo various diagnostic tests to aid in their diagnosis and treatment,
each patient may require multiple tests.
Laboratories within the hospital perform diagnostic tests requested by healthcare
providers. Labs perform tests for multiple patients
After tests are conducted, patients receive reports detailing their diagnostic
findings
Each patient has a unique medical history, which is vital for healthcare providers
to make informed decisions.
Patients are billed for the services they receive, including tests, treatments, and
accommodations. patients may have multiple bills for various services.
Patients requiring hospitalization are assigned beds. Each patient has allocated a
single bed
Wards within the hospital contain multiple beds for patient accommodation.
Patients receive various treatments during their hospital stay to address their
medical needs.
Each doctor has a unique schedule outlining their availability for appointments.
Attributes:
Labs:
Location,Test,Contact_No, LabID
Patient
Name,Age,Gender,Contact_No,Email,Medical_History,Bill,Bed,Appointment,Treatment,Report
Wards
Beds,Ward_type,Ward_Capacity,WardID
Doctor
Name,Specialization,Year_Of_Experience,Contact_No,Email,Appointment,Treatment,Schedule,Doct
or_ID
Reports
Report_Details,Report_Date,Report_ID,Patient_ID
MedicalHistory
Past_Illness,Allergies,Family_MedicalHistory,History_ID,Patient_ID
Bills
Amount,Payment_method,Payment_status,Bill_ID,Patient_ID
Bed
Bed_Type,Bed_Status,Bed_ID,Ward_ID
Treatment
Tr_Details,Start_Date,End_Date,Prescription,Treatment_Id,Doctor_Id
Pharmacy
Prescription,Medicine,Stock,Prescription_Id,Pharmacy_Id
Schedule
Working_Hours,Day-Offs,Doctor_Id,Schedule_Id
Prescription
Medicine,Dosage,Frequency,Prescription_Id,Treatment_Id
Appointments
Date,Time,Status,Appointment_Id,Patient_Id,Doctor_Id
Tests
Name,Cost,Result,Test_Id,Lab_Id
MedicalHistory entity seems to be a weak entity type as it does not have a unique
identifier of its own but relies on the association with the Patient entity for identification.
The attribute History_ID likely serves as a partial key, but it is not sufficient for uniquely
identifying instances of MedicalHistory without the Patient_ID