Hospital Management System

Hospital Management System

OOSD Assignment 1

Object Oriented AnalysisPresented by Group 4:

Vivek Sachdeva

Nesa Simon David

Eric

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

A new payment was entered, linking to the Customer and the Payment.

Post conditions:

A valid patient ID exists.Preconditions:

NoneOutput:

If the combination of Payment ID, Payment Method and patient ID is not valid, indicate that it was an error.

Exceptions:

SystemType:

Enter patient payment into the systemResponsibilities:

Enter payment(Amount, Payment ID, Payment Method, Payment Date, Patient ID)

Name:

Contract

PaymentPackage

System ContractsContract for the Store Payment

A new patient payment was stored, linking to the Customer and Payment.

Post Conditions:

The combination of payment ID, payment Method and patient ID is valid.

Preconditions:

Display “Payment has been stored”Output:

NoneExceptions:

SystemType:

Store patient payment into the systemResponsibilities:

Store PaymentName:

Contract

PaymentPackage

System ContractsContract for the Send Payment

Payment details have been sent to the bank system.Post Conditions:

Patient payment must be stored in the system.Preconditions:

Message payment has been sent to the bank system.Output:

If the bank doesn’t exist, indicate that it was an error.Exceptions:

SystemType:

Send the stored patient payment to the bank systemResponsibilities:

Send Payment (Payment Date, Payment Method, Amount, Customer Name, Customer Account Number)

Name:

Contract

PaymentPackage

System ContractsContract for the Confirmation

Confirmation of payment has been madePost Conditions:

Patient payment must be sent by hospitalPreconditions:

Display “Payment has been confirmed”Output:

If the Payment details are not valid, indicate that it was an error.

Exceptions:

SystemType:

Confirmation of the payment detailResponsibilities:

ConfirmationName:

Contract

PaymentPackage

System Contracts

Contract for the Print Receipt

Print out the receiptPost Conditions:

Confirmation must be done by the bank systemPreconditions:

ReceiptOutput:

If the printer does not work, indicate that it was an error.Exceptions:

SystemType:

Print the Patient payment receiptResponsibilities:

Print ReceiptName:

Contract

PaymentPackage

System ContractsContract for the Create Report

A new instance of report from dermatology was created.Post Conditions:

Patient, doctor, symptoms, prescription must be know to the system.

Preconditions:

An object of report from DermatologyOutput:

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.

Exceptions:

SystemType:

Create a Report from DermatologyResponsibilities:

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

Contract

System ContractsContract for making payment through the web interface

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

Post Conditions:

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

Preconditions:

confirmation from payment processorOutput:

Patient does not exist; credit card authentication errorExceptions:

SystemType:

To allow the patient to pay through the web interfaceResponsibilities:

Make Payment (Patient, Amount)Name:

Contract

Conclusion

Project will take approx 1 year to complete

Project will be developed modularly

We use Event – driven method.

Q&A