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

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

Project Description


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

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
Contract for the Enter Payment Contract Name: Responsibilities : Type: Exceptions: Output: Preconditions: Post conditions:

Payment Package

Enter payment(Amount, Payment ID, Payment Method, Payment Date, Patient ID) Enter patient payment into the system System If the combination of Payment ID, Payment Method and patient ID is not valid, indicate that it was an error. None A valid patient ID exists. A new payment was entered, linking to the Customer and the Payment.

System Contracts
Contract for the Store Payment Contract Name: Responsibilities : Type: Exceptions: Output: Preconditions: Post Conditions: Store Payment

Payment Package

Store patient payment into the system System None Display Payment has been stored The combination of payment ID, payment Method and patient ID is valid. A new patient payment was stored, linking to the Customer and Payment.

System Contracts
Contract for the Send Payment Contract Name: Responsibilities: Type: Exceptions: Output: Preconditions: Post Conditions:

Payment Package

Send Payment (Payment Date, Payment Method, Amount, Customer Name, Customer Account Number) Send the stored patient payment to the bank system System If the bank doesnt exist, indicate that it was an error. Message payment has been sent to the bank system. Patient payment must be stored in the system. Payment details have been sent to the bank system.

System Contracts
Contract for the Confirmation Contract Name: Responsibilities: Type: Exceptions: Output: Preconditions: Post Conditions: Confirmation

Payment Package

Confirmation of the payment detail System If the Payment details are not valid, indicate that it was an error. Display Payment has been confirmed Patient payment must be sent by hospital Confirmation of payment has been made

System Contracts
Contract for the Print Receipt Contract Name: Responsibilities: Type: Exceptions: Output: Preconditions: Post Conditions: Print Receipt

Payment Package

Print the Patient payment receipt System If the printer does not work, indicate that it was an error. Receipt Confirmation must be done by the bank system Print out the receipt

System Contracts
Contract for the Create Report Contract Name: Responsibilities: Type: Exceptions: Create Report (patient, doctor, symptoms, prescription) Create a Report from Dermatology System 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. An object of report from Dermatology Patient, doctor, symptoms, prescription must be know to the system. A new instance of report from dermatology was created.

Output: Preconditions: Post Conditions:

System Contracts
Contract for making payment through the web interface Contract Name: Responsibilities: Type: Exceptions: Make Payment (Patient, Amount) To allow the patient to pay through the web interface System Patient does not exist; credit card authentication error

Output: Preconditions: Post Conditions:

confirmation from payment processor Patient has a debit balance, patient is able to pay with credit card, patient is logged in, invoice has been viewed by patient. Payment created, credit card authentication successful, confirmation from payment processor received, patient gets receipt..

Conclusion
  

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

Q&A