Hospital Management System Data Flow Diagram Design

Posted by Anonymous and classified in Medicine & Health

Written on in English with a size of 4.58 KB

Hospital Management System: Context Level DFD

+-------------------+
|      Patient      |
+-------------------+
          |
          | Appointment / Details
          v
+--------------------------------------------+
|    (0) Hospital Management System          |
+--------------------------------------------+
          ^
          | Reports / Bills
+-------------------+
|  Doctor / Admin   |
+-------------------+
          ^
          |
+-------------------+
|  Pharmacy / Lab   |
+-------------------+

System Entities and Data Flow

This context diagram illustrates the primary interactions with the central system:

  • External Entities: Patient, Doctor/Admin, Pharmacy/Lab.
  • Central Process: The Hospital Management System (Process 0).
  • Data Flow: Information exchanged includes Appointment details, Reports, Billing information, and Medicine information.

Level 0 Data Flow Diagram (DFD)

+-------------------+
|      Patient      |
+-------------------+
      |      ^
Registration |      | Reports / Bills
             v      |
+------------------------------------------------+
|      (0) Hospital Management System            |
|------------------------------------------------|
| (1.0) Patient Registration                     |
| (2.0) Appointment Scheduling                   |
| (3.0) Doctor Consultation                      |
| (4.0) Billing & Reports                        |
+------------------------------------------------+
      |            |              |
      v            v              v
 Patient DB    Doctor DB      Billing DB

Core System Processes

The Hospital Management System is broken down into four main processes:

  1. Patient Registration (1.0): Handles the initial entry and creation of patient records.
  2. Appointment Scheduling (2.0): Manages booking, checking availability, and confirming appointments.
  3. Doctor Consultation (3.0): Facilitates the interaction between doctors and patients, including diagnosis and treatment planning.
  4. Billing & Reports (4.0): Generates invoices, handles payments, and produces necessary administrative and medical reports.

Data Stores Definition

  • Patient DB: Stores comprehensive patient details, including personal and medical history.
  • Doctor DB: Stores doctor details, credentials, and availability schedules.
  • Billing DB: Stores all financial transaction data, including bills, payments, and report generation data.

Detailed Process: Appointment Scheduling (2.0)

+---------+       +-------------------------+
| Patient |-----> | (2.1) Request Appt.     |
+---------+       +-------------------------+
                        |
                        v
                +-------------------------+
                | (2.2) Check Availability|
                +-------------------------+
                        |
                        v
                +-------------------------+
                | (2.3) Confirm Appt.     |
                +-------------------------+
                        |
                        v
                    +-----------+
                    | Doctor DB |
                    +-----------+

Sub-Processes of Appointment Scheduling

Process 2.0 involves the following steps:

  1. Request Appointment (2.1): The patient initiates the request for a consultation.
  2. Check Availability (2.2): The system verifies the doctor's schedule using the Doctor DB.
  3. Confirm Appointment (2.3): The appointment is finalized and recorded in the system, and the Doctor DB is updated.

System Data Files/Records

NameDescription
Patient FileStores patient personal and medical details.
Doctor FileStores doctor details and timings/schedules.
Appointment FileKeeps records of appointment dates, times, and associated patient/doctor details.
Billing FileStores all billing, payment, and financial transaction information.
Report FileKeeps records of lab reports, diagnostic results, and administrative reports.

Related entries: