Hospital management system project
that runs, with an ER diagram and viva prep

Admin

Adds departments, doctors, wards and charges; sees every report.

Receptionist

Registers patients, books and cancels appointments, admits and discharges, takes payments.

Doctor

Sees their own appointments, writes diagnoses and prescriptions, discharges their patients.

Patient

Signs in to see only their own appointments, prescriptions and bills.

Nine entities. A patient has many appointments; an appointment can lead to one prescription with many lines; an admission puts a patient in one bed. Generate the app and compare its tables with this: a difference is a good viva answer.

Relationships

• department employs doctor (one to many)
• patient books appointment (one to many)
• doctor attends appointment (one to many)
• appointment results in prescription (one to one)
• prescription lists prescription_line (one to many)
• patient is admitted in admission (one to many)
• bed holds admission (one to many)
• patient pays bill (one to many)
• admission is charged on bill (zero or one to many)

Mermaid source

Paste it into mermaid.live, draw.io (Arrange, Insert, Advanced, Mermaid) or any Markdown editor that draws Mermaid to get the diagram for your report.

erDiagram
  DEPARTMENT ||--o{ DOCTOR : "employs"
  PATIENT ||--o{ APPOINTMENT : "books"
  DOCTOR ||--o{ APPOINTMENT : "attends"
  APPOINTMENT ||--|| PRESCRIPTION : "results in"
  PRESCRIPTION ||--o{ PRESCRIPTION_LINE : "lists"
  PATIENT ||--o{ ADMISSION : "is admitted in"
  BED ||--o{ ADMISSION : "holds"
  PATIENT ||--o{ BILL : "pays"
  ADMISSION |o--o{ BILL : "is charged on"
  PATIENT {
    uuid id PK
    text patient_no UK
    text name
    date date_of_birth
    text gender
    text blood_group
    text phone
  }
  DEPARTMENT {
    uuid id PK
    text name
  }
  DOCTOR {
    uuid id PK
    uuid department_id FK
    text name
    text specialisation
    numeric consultation_fee
  }
  APPOINTMENT {
    uuid id PK
    uuid patient_id FK
    uuid doctor_id FK
    timestamp starts_at
    text status
    text diagnosis
  }
  PRESCRIPTION {
    uuid id PK
    uuid appointment_id FK
    text notes
  }
  PRESCRIPTION_LINE {
    uuid id PK
    uuid prescription_id FK
    text medicine
    text dose
    int days
  }
  BED {
    uuid id PK
    text ward
    text bed_no
    numeric daily_charge
  }
  ADMISSION {
    uuid id PK
    uuid patient_id FK
    uuid bed_id FK
    timestamp admitted_at
    timestamp discharged_at
  }
  BILL {
    uuid id PK
    uuid patient_id FK
    uuid admission_id FK
    numeric total
    numeric paid
    date issued_on
  }

This builds on Refinar's booking starting point, because appointments in time slots are the heart of the project. Everything else, from prescriptions to wards and bills, comes from the prompt.

The prompt it starts with

A hospital management system for a final-year project, in English: patients with a unique patient number; doctors with department and weekly consulting hours; appointments in free slots that cannot be double-booked; a visit record where the doctor writes the diagnosis and a prescription of medicines with dose and days; wards and beds with admission and discharge; a bill per visit or admission with consultation, bed and medicine charges, and payments. Roles: admin, receptionist, doctor and patient, where a patient sees only their own appointments, prescriptions and bills.

• A lab module: tests ordered by the doctor, results entered by the lab, shown to the patient.
• A pharmacy stock that reduces when a prescription is dispensed.
• A queue screen for the waiting room, showing the token being seen by each doctor.
• Reports: patients per department per month, average stay, revenue by service.

• Library management systemCatalogue, copies, issue and return with due dates, fines and reservations.
• Student management systemStudents, courses, attendance, marks and results, fees and a student login.
• Hostel management systemRooms and beds, allocation, fees, out-passes, visitors and complaints.
• Pharmacy management systemMedicines, batches and expiry, purchases, sales bills and stock alerts.
• E-commerce websiteStorefront, cart, checkout, orders with status, customer accounts and a stock admin.
• Event management systemEvents with ticket types, registration, QR check-in at the door and feedback.