What Is a Hospital Management System<\/strong><\/h2>\n\n\n\nA hospital management system (HMS) is software that manages all hospital operations digitally. It replaces paper records and manual tracking with organized, connected digital data.<\/p>\n\n\n\n
Core modules in a hospital management system:<\/strong><\/p>\n\n\n\n\nPatient Management:<\/strong> Registering patients, storing demographics and medical history<\/li>\n\n\n\nDoctor Management:<\/strong> Tracking doctor details, specializations, and schedules<\/li>\n\n\n\nAppointment Management:<\/strong> Booking, rescheduling, and tracking consultations<\/li>\n\n\n\nRoom and Ward Management:<\/strong> Allocating and tracking room availability<\/li>\n\n\n\nDepartment Management:<\/strong> Organizing hospital departments and assigned staff<\/li>\n\n\n\nBilling and Payments:<\/strong> Generating bills and recording payment history<\/li>\n\n\n\nMedical Records:<\/strong> Storing diagnoses, prescriptions, lab reports, and treatment history<\/li>\n\n\n\nPharmacy and Medication:<\/strong> Managing medicines prescribed and dispensed<\/li>\n<\/ul>\n\n\n\nAn ER diagram for a hospital management system captures all of these modules through connected entities.<\/p>\n\n\n\n
Step-by-Step: How to Design an ER Diagram for a Hospital Management System<\/strong><\/h2>\n\n\n\nFollow these steps every time you design an ER diagram for a hospital management system. This is the standard approach used in both exams and real projects.<\/p>\n\n\n\n
Step 1: Identify all entities<\/strong> List every major object that the system needs to track.<\/p>\n\n\n\nStep 2: Identify attributes for each entity<\/strong> For each entity, list all the data fields it needs. Mark the primary key.<\/p>\n\n\n\nStep 3: Identify relationships between entities<\/strong> Determine how each entity connects to others using action verbs like consults, belongs to, pays, and assigns.<\/p>\n\n\n\nStep 4: Determine cardinality<\/strong> For each relationship, decide if it is one-to-one, one-to-many, or many-to-many.<\/p>\n\n\n\nStep 5: Draw the diagram<\/strong> Place entities as rectangles, connect them with diamond-shaped relationship labels, and attach oval-shaped attributes.<\/p>\n\n\n\nStep 6: Review for completeness<\/strong> Check that every entity has a primary key, every relationship has a cardinality, and no important data field is missing.<\/p>\n\n\n\nCore Entities in an ER Diagram for a Hospital Management System<\/strong><\/h2>\n\n\n\n1. Patient<\/strong><\/h3>\n\n\n\nThe Patient entity is the most central entity in any ER diagram for a hospital management system. Every other entity connects back to the patient in some way.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Patient_ID<\/td> Primary Key<\/td> Unique identifier for each patient<\/td><\/tr> Name<\/td> String<\/td> Full name of the patient<\/td><\/tr> Date_of_Birth<\/td> Date<\/td> Used to derive age<\/td><\/tr> Age<\/td> Derived Attribute<\/td> Calculated from Date_of_Birth<\/td><\/tr> Gender<\/td> String<\/td> Male, Female, Other<\/td><\/tr> Blood_Group<\/td> String<\/td> A+, B+, O+ etc.<\/td><\/tr> Address<\/td> String<\/td> Residential address<\/td><\/tr> Phone_Number<\/td> Multivalued<\/td> Patient may have multiple contacts<\/td><\/tr> Medical_History<\/td> String<\/td> Previous conditions and surgeries<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n2. Doctor<\/strong><\/h3>\n\n\n\nThe Doctor entity stores all information about medical practitioners in the hospital.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Doctor_ID<\/td> Primary Key<\/td> Unique identifier for each doctor<\/td><\/tr> Name<\/td> String<\/td> Full name<\/td><\/tr> Specialization<\/td> String<\/td> Cardiology, Neurology, Pediatrics etc.<\/td><\/tr> Qualification<\/td> String<\/td> MBBS, MD, MS etc.<\/td><\/tr> Phone_Number<\/td> Multivalued<\/td> Doctor may have multiple contacts<\/td><\/tr> Availability<\/td> String<\/td> Days and time slots available<\/td><\/tr> Department_ID<\/td> Foreign Key<\/td> Links doctor to their department<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n3. Department<\/strong><\/h3>\n\n\n\nThe Department entity organizes the hospital into functional units.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Department_ID<\/td> Primary Key<\/td> Unique identifier for each department<\/td><\/tr> Department_Name<\/td> String<\/td> Cardiology, Radiology, Orthopedics etc.<\/td><\/tr> Location<\/td> String<\/td> Floor or block in the hospital<\/td><\/tr> Head_Doctor_ID<\/td> Foreign Key<\/td> The doctor who leads the department<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n4. Appointment<\/strong><\/h3>\n\n\n\nThe Appointment entity is a relationship-turned-entity (also called an associative entity) because it holds data about the interaction between a Patient and a Doctor.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Appointment_ID<\/td> Primary Key<\/td> Unique identifier for each appointment<\/td><\/tr> Date<\/td> Date<\/td> Date of the appointment<\/td><\/tr> Time<\/td> Time<\/td> Time slot booked<\/td><\/tr> Status<\/td> String<\/td> Scheduled, Completed, Cancelled<\/td><\/tr> Patient_ID<\/td> Foreign Key<\/td> Links to Patient<\/td><\/tr> Doctor_ID<\/td> Foreign Key<\/td> Links to Doctor<\/td><\/tr> Reason<\/td> String<\/td> Brief reason for the visit<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n5. Room<\/strong><\/h3>\n\n\n\nThe Room entity manages the physical spaces patients are admitted to.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Room_No<\/td> Primary Key<\/td> Unique room identifier<\/td><\/tr> Room_Type<\/td> String<\/td> General, ICU, Private, Semi-Private<\/td><\/tr> Status<\/td> String<\/td> Available, Occupied<\/td><\/tr> Capacity<\/td> Integer<\/td> Number of beds in the room<\/td><\/tr> Daily_Charge<\/td> Integer<\/td> Per day cost of the room<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n6. Medical Record<\/strong><\/h3>\n\n\n\nThe Medical Record entity stores the clinical history of each patient visit.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Record_ID<\/td> Primary Key<\/td> Unique identifier for the record<\/td><\/tr> Diagnosis<\/td> String<\/td> Doctor’s diagnosis<\/td><\/tr> Prescription<\/td> String<\/td> Medicines prescribed<\/td><\/tr> Test_Results<\/td> String<\/td> Lab or imaging results<\/td><\/tr> Date<\/td> Date<\/td> Date of the record entry<\/td><\/tr> Patient_ID<\/td> Foreign Key<\/td> Links to Patient<\/td><\/tr> Doctor_ID<\/td> Foreign Key<\/td> The doctor who created the record<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n7. Bill<\/strong><\/h3>\n\n\n\nThe Bill entity tracks all financial transactions in the hospital.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Bill_ID<\/td> Primary Key<\/td> Unique bill number<\/td><\/tr> Patient_ID<\/td> Foreign Key<\/td> Links to Patient<\/td><\/tr> Total_Amount<\/td> Integer<\/td> Total charges<\/td><\/tr> Doctor_Charge<\/td> Integer<\/td> Consultation fee<\/td><\/tr> Room_Charge<\/td> Integer<\/td> Room rental charges<\/td><\/tr> Medicine_Charge<\/td> Integer<\/td> Pharmacy charges<\/td><\/tr> Lab_Charge<\/td> Integer<\/td> Diagnostic test charges<\/td><\/tr> Payment_Status<\/td> String<\/td> Paid, Pending, Partially Paid<\/td><\/tr> Date<\/td> Date<\/td> Date of bill generation<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n8. Nurse<\/strong><\/h3>\n\n\n\nThe Nurse entity tracks nursing staff assigned to patients and wards.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Nurse_ID<\/td> Primary Key<\/td> Unique identifier<\/td><\/tr> Name<\/td> String<\/td> Full name<\/td><\/tr> Phone_Number<\/td> String<\/td> Contact number<\/td><\/tr> Shift<\/td> String<\/td> Morning, Evening, Night<\/td><\/tr> Room_No<\/td> Foreign Key<\/td> The room the nurse manages<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n9. Lab Report<\/strong><\/h3>\n\n\n\nThe Lab Report entity stores all diagnostic test information.<\/p>\n\n\n\n
Attributes:<\/strong><\/p>\n\n\n\nAttribute<\/strong><\/td>Type<\/strong><\/td>Notes<\/strong><\/td><\/tr>Lab_ID<\/td> Primary Key<\/td> Unique test identifier<\/td><\/tr> Patient_ID<\/td> Foreign Key<\/td> Links to Patient<\/td><\/tr> Doctor_ID<\/td> Foreign Key<\/td> Doctor who ordered the test<\/td><\/tr> Test_Name<\/td> String<\/td> Blood test, MRI, X-Ray etc.<\/td><\/tr> Result<\/td> String<\/td> Test findings<\/td><\/tr> Date<\/td> Date<\/td> Date the test was conducted<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nRelationships in an ER Diagram for a Hospital Management System<\/strong><\/h2>\n\n\n\nRelationship<\/strong><\/td>Entities Involved<\/strong><\/td>Cardinality<\/strong><\/td>Meaning<\/strong><\/td><\/tr>Consults<\/td> Patient, Doctor<\/td> Many-to-Many<\/td> A patient can consult many doctors. A doctor can treat many patients.<\/td><\/tr> Books<\/td> Patient, Appointment<\/td> One-to-Many<\/td> One patient can have many appointments.<\/td><\/tr> Has<\/td> Doctor, Appointment<\/td> One-to-Many<\/td> One doctor can have many appointments.<\/td><\/tr> Belongs To<\/td> Doctor, Department<\/td> Many-to-One<\/td> Many doctors belong to one department.<\/td><\/tr> Assigned To<\/td> Patient, Room<\/td> Many-to-One<\/td> Many patients can be assigned to a room over time.<\/td><\/tr> Manages<\/td> Nurse, Room<\/td> One-to-Many<\/td> One nurse can manage multiple rooms.<\/td><\/tr> Pays<\/td> Patient, Bill<\/td> One-to-Many<\/td> One patient can have many bills.<\/td><\/tr> Has Record<\/td> Patient, Medical Record<\/td> One-to-Many<\/td> One patient can have many medical records.<\/td><\/tr> Orders<\/td> Doctor, Lab Report<\/td> One-to-Many<\/td> One doctor can order many lab reports.<\/td><\/tr> Undergoes<\/td> Patient, Lab Report<\/td> One-to-Many<\/td> One patient can undergo many lab tests.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nCardinality Explained Simply<\/strong><\/h2>\n\n\n\nCardinality tells you how many instances of one entity can relate to instances of another entity.<\/p>\n\n\n\nCardinality Type<\/strong><\/td>What It Means<\/strong><\/td>Hospital Example<\/strong><\/td><\/tr>One-to-One (1:1)<\/td> One record in Entity A matches exactly one record in Entity B<\/td> One patient has one unique Patient_ID<\/td><\/tr> One-to-Many (1:N)<\/td> One record in Entity A matches many records in Entity B<\/td> One doctor has many appointments<\/td><\/tr> Many-to-Many (M:N)<\/td> Many records in Entity A match many records in Entity B<\/td> Many patients consult many doctors<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\nHow many-to-many relationships are handled:<\/strong><\/p>\n\n\n\nA many-to-many relationship cannot be directly stored in a database. It is broken down using an intermediate entity called an associative entity or junction table. For example, the many-to-many relationship between Patient and Doctor is handled through the Appointment entity which holds Patient_ID and Doctor_ID as foreign keys.<\/p>\n\n\n\n
Primary Key vs Foreign Key<\/strong><\/h2>\n\n\n\nThese two concepts are essential for understanding any ER diagram for a hospital management system.<\/p>\n\n\n\n
![\"Step-by-Step:](\"https:\/\/www.guvi.in\/blog\/wp-content\/uploads\/2026\/05\/image-325-1200x519.png\" "\\"\\"")
<\/figure>\n\n\n\n