You are on page 1of 23

Hospital Management

System
Presented by Group 4:
Vivek Sachdeva
Nesa Simon David
Eric

OOSD Assignment 1
Object Oriented Analysis

Presentation Outline

Introduction
Project description
 Scope
 Assumptions





Package diagrams
System sequence diagrams
Activity diagrams
System contracts
Conclusion

etc.Introduction   Parkside Hospital 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. security levels. . accounting. remote a/v consulting. etc) Management reports.

operating theatres.Project Description  Scope  Patient registration  Appointments scheduling  Billing and payments (cash. availability. etc)  Comprehensive database  Web interface (proposed for future) . insurance)  Security of the whole system  Pharmaceutical drugs/equipment  Staff management (work roster. CC. etc)  System administration  Resource allocation (booking rooms. accounting. scheduling. etc)  Management functions (report generation.

Project Description  Assumptions  Patient provides CC/insurance details when registering  Appointments can be cancelled 24 hours in advance without penalty  Patient medical history can be viewed by concerned doctors at the hospital with approval of the patient  Hospital is covered by insurance policy  Staff are assigned roles to interact with the system  Staff have basic computer operating skills .

Package Diagram .

Activity Diagrams Pharmaceuticals Activity Diagram Checking Stock .

Activity Diagrams Web Package Remote doctor patient consultation. .

Activity Diagrams Billing and payment: Payment by Credit Card / Cash .

Activity Diagrams Billing and payment: Payment by Insurance .

Activity Diagrams .

Sequence Diagrams .

Sequence Diagrams .

Sequence Diagrams Payment Use Case .

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

linking to the Customer and Payment. payment Method and patient ID is valid. . Post Conditions: A new patient payment was stored.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.

Output: Message payment has been sent to the bank system. . Post Conditions: Payment details have been sent to the bank system. Customer Name. Preconditions: Patient payment must be stored in the system.System Contracts Payment Package Contract for the Send Payment Contract Name: Send Payment (Payment Date. Payment Method. Amount. 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: Display “Payment has been confirmed” Preconditions: Patient payment must be sent by hospital Post Conditions: Confirmation of payment has been made . indicate that it was an error.System Contracts Payment Package Contract for the Confirmation Contract Name: Confirmation Responsibilities: Confirmation of the payment detail Type: System Exceptions: If the Payment details are not valid.

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

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

Post Conditions: Payment created.System Contracts Contract for making payment through the web interface Contract Name: Make Payment (Patient. invoice has been viewed by patient. credit card authentication successful. patient gets receipt. patient is logged in. credit card authentication error Output: confirmation from payment processor Preconditions: Patient has a debit balance. . confirmation from payment processor received. patient is able to pay with credit card. Amount) Responsibilities: To allow the patient to pay through the web interface Type: System Exceptions: Patient does not exist..

.Conclusion  Project will take approx 1 year to complete  Project will be developed modularly  We use Event – driven method.

Q&A .