Management Information System (MIS)

HealthCare Management System

System Overview:

The Healthcare Management System (HMS) is a digital platform used by hospitals/clinics to

manage patient information, appointments, doctor availability, medical records, billing, lab tests,
and reports.

Actors (Users):

1. Patient

2. Doctor

3. Receptionist / Front Desk

4. Lab Technician

5. Pharmacist
6. Admin

Key Functional Modules and Use Cases:

1. Patient Management

• Register/Login

• View/Edit profile

• Book an appointment

• Cancel appointment
• View doctor list and schedule

2. Doctor Management

• View appointments

• Add/Edit prescriptions

• Access patient history

• Refer to another doctor

3. Appointment Scheduling
• Patient books appointment
 • System shows doctor availability

• Receptionists can manually assign slots

4. Billing & Payment

• Generate bill (automated)

• Pay bill (online or offline)

• View payment history

5. Electronic Medical Record (EMR)

• Store visit notes

• Lab results

• Prescriptions

• Patient treatment history

6. Laboratory Module
• Receive test requests

• Upload reports

• Notify patient/doctor

7. Pharmacy Module

• Check prescription

• Issue medicines

• Update inventory
8. Admin Panel

• Add users (doctors, lab staff, receptionist)

• Monitor appointments and billing

• Access all reports and logs

Context Data Model:

Figure 1: Context Data Model of HMS

This context diagram represents a high-level view of the Healthcare Management System (HMS)
and its interaction with external users.

• Patients can register, book appointments, and view reports.

• Doctors view their schedules and add prescriptions.
• The receptionist manages appointments, while lab technicians upload lab reports.
• Pharmacists verify prescriptions and dispense medicine.
• Lab Technicians can upload reports.
• The admin oversees system operations by managing users and viewing logs.
Each actor directly communicates with the HMS, which acts as the central processing system. This
diagram clearly defines system boundaries and identifies how each stakeholder contributes to and
interacts with the system, supporting smooth hospital or clinic operations.
E-R Model:

Figure 2: E-R Model of HMS

This E-R model captures both the medical workflow (appointments, prescriptions, lab tests) and
the administrative flow (billing, staff management) with precise cardinality notations, ensuring
relational integrity and full coverage of the HMS data architecture.
Key Relationships:

• A Patient (1) can book multiple Appointments (0..*), but each appointment is linked to
only one Patient.

• A Doctor (1) can be associated with many Appointments (0..*), where they consult or
attend.

• An Appointment (1) can create multiple Prescriptions (0..*), but each prescription is
tied to only one Appointment.

• Each Prescription (1) can include many Medicines (0..*) through a junction entity
called Prescription_Medicine, supporting many-to-many relationships.

• Each Medicine (1) can be used in multiple Prescriptions (0..*).

• Each Appointment (1) generates one Bill (1), while a Patient (1) may receive many
Bills (0..*) over time.

• A Doctor (1) can order many LabTests (0..*), while each LabTest is linked back to a
Patient (1) and an Appointment (1).

• The Admin (1) entity oversees the system and can manage multiple Doctors (0..*),
audit LabTests (0..*), and review Bills (0..*).
Data Flow Diagram:

Figure 3: Data Flow Diagram of HMS

This Data Flow Diagram (DFD) depicts the data flow within a Healthcare Management System
using four processes, two data stores, and three external entities. Here's a detailed explanation in
points:

External Entities

1. Patient

o Provides personal details for registration.

o Requests appointments.
o Receives registration card, appointment slip, prescriptions, and bill.

2. Receptionist

o Enters patient details.

o Schedules appointment times.

o Provides appointment slip.

o Processes payment.

3. Doctor
o Examines patients.
 o Views patient history.

o Provides treatment and prescriptions.

Processes

1. 1.0 Register Patient

o Input: Personal Details (from Patient/Receptionist).

o Output: Registration Card (to Patient).

o Stores: Patient Info in D1: Patient Database.

2. 2.0 Book Appointment

o Input: Patient ID (from Register Patient) and Request Appointment (from Patient).

o Output: Appointment Slip (to Patient via Receptionist).

o Updates: D2: Appointment Database with appointment info.

o Retrieves: Schedule (from Appointment Database).

3. 3.0 Medical Checkup

o Input: Patient History (from Doctor), Get Patient Data (from D1), and Appointment
Info (from D2).

o Output: Prescription and Health Info (to Patient).

o Updates: Treatment Details (to Process 4.0 Generate Bill).

4. 4.0 Generate Bill

o Input: Treatment Details (from Process 3.0).

o Output: Bill (to Patient) and Payment Processing (by Receptionist).

Data Stores
1. D1: Patient Database

o Stores patient info from registration.

o Provides patient data to the Doctor during checkup.

2. D2: Appointment Database

o Stores appointment info.

o Allows schedule lookup during appointment booking and checkups.
Data Flows

• Patient → Registration → Appointment Booking → Medical Checkup → Billing.

• Continuous flow between entities and processes ensures data availability, medical services,
and billing operations.

Key Functions

• Patient Lifecycle: Register → Book Appointment → Get Checked → Pay Bill.

• Interconnected Modules: All processes share and update centralized databases.

• Roles are Clear: Receptionist handles admin tasks, Doctor manages clinical tasks, Patient
interacts with the system.