Hospital

Management
System
Presented by:

Guided by: Veena Udand

Mr.Jagdish Rathore Ranjita Rathod
Tulsiram Rathore
Vikas Arya
 Presentation
Outline
• Introduction
• Project description
• Package diagrams
• System sequence
diagrams
• Activity diagrams
• System contracts
 Introduction
Hospital Management System
– Patient details and registration
– Consultations
– Resource allocation
– Pharmaceuticals management
– Billing and payments
– User interface conforming to usability
guidelines
– Database with audio/visual and past
consultations
– Future extensions (web, remote a/v
consulting, etc)
– Management reports, security levels,
accounting, etc.
 Project
description
Patient details and registration
Patient related enquiries:-
• Ward Allotment
• Admission Details
• Payment Details and
• Discharge Details.
• Registration module include:-

• • Patient Registration Details

• Inpatient and Outpatient Registration
• Appointment Scheduling (Patient / Doctor
wise)
• Doctor's Schedule Summary
• Doctors Daily Schedule List
• Patient Visit History
 Billing and Payment
• Facilities cashier and billing
operations(inpatient/outpatient)
• Automatic posting of charges
Pharmacy module:-

• Pharmacy stores configuration

• Drug issue to patients and billing
• Unit dosage function
• Supplier information
• Maintenance of drug inventory
• Alerts on nearing expiry
• Goods receipt
 Activity
Diagrams

Pharmaceuticals Activity Diagram

Checking Stock
 Activity
Diagrams

Web Package
Remote doctor patient consultation.
Activity Diagram

Billing and payment:

Payment by Credit Card / Cash
Sequence Diagrams
 Sequence Diagrams

Payment Use
Case
 Use Case
Diagram
For hospital
reception
Use-case
Diagram
 System Contracts
Payment
Package
Contract for the Enter Payment

Contract

Name: Enter payment(Amount, Payment ID, Payment

Method, Payment Date, Patient ID)
Responsibilities Enter patient payment into the system
:
Type: System
Exceptions: If the combination of Payment ID, Payment Method
and patient ID is not valid, indicate that it was an error.
Output: None
Preconditions: A valid patient ID exists.
Post conditions: A new payment was entered, linking to the Customer
and the Payment.
 System Contracts
Payment
Package
Contract for the Store Payment

Contract

Name: Store Payment

Responsibilities Store patient payment into the system
:
Type: System
Exceptions: None
Output: Display “Payment has been stored”
Preconditions: The combination of payment ID, payment Method and
patient ID is valid.
Post A new patient payment was stored, linking to the
Conditions: Customer and Payment.
 System Contracts
Payment
Package
Contract for the Send Payment

Contract

Name: Send Payment (Payment Date, Payment Method, Amount,

Customer Name, Customer Account Number)
Responsibilities: Send the stored patient payment to the bank system
Type: System
Exceptions: If the bank doesn’t exist, indicate that it was an error.
Output: Message payment has been sent to the bank system.
Preconditions: Patient payment must be stored in the system.
Post Conditions: Payment details have been sent to the bank system.
 System Contracts
Payment
Contract for the Print Receipt
Package
Contract

Name: Print Receipt

Responsibilities: Print the Patient payment receipt
Type: System
Exceptions: If the printer does not work, indicate that it was an error.
Output: Receipt
Preconditions: Confirmation must be done by the bank system
Post Conditions: Print out the receipt
 System Contracts
Contract for the Create Report

Contract

Name: Create Report (patient, doctor, symptoms, prescription)

Responsibilities: Create a Report from Dermatology
Type: System
Exceptions: If the combination of patient, doctor, symptoms and
prescription is not valid, indicate that it was an error.
Object may not be found; method/operation may not be
found.
Output: An object of report from Dermatology
Preconditions: Patient, doctor, symptoms, prescription must be know to
the system.
Post Conditions: A new instance of report from dermatology was created.
 System Contracts
Contract for making payment through the web interface
Contract

Name: Make Payment (Patient, Amount)

Responsibilities: To allow the patient to pay through the web interface

Type: System
Exceptions: Patient does not exist; credit card authentication error

Output: confirmation from payment processor

Preconditions: Patient has a debit balance, patient is able to pay with credit card, patient is
logged in, invoice has been viewed by patient.

Post Conditions: Payment created, credit card authentication successful, confirmation from
payment processor received, patient gets receipt..