for hospital management system

1. Hospital Management System OOSD Object Oriented Analysis Presented by : MANISH MISHRA

6. Package Diagram

7. Activity Diagrams Pharmaceuticals Activity Diagram Checking Stock

8. Activity Diagrams Web Package Remote doctor patient consultation.

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

10. Activity Diagrams Billing and payment: Payment by Insurance

11. Activity Diagrams

12. Sequence Diagrams

13. Sequence Diagrams

14. Sequence Diagrams Payment Use Case

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

16. System Contracts Contract for the Store Payment Payment Package 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: None Exceptions: System Type: Store patient payment into the system Responsibilities: Store Payment Name: Contract

17. System Contracts Contract for the Send Payment Payment Package 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: System Type: Send the stored patient payment to the bank system Responsibilities: Send Payment (Payment Date, Payment Method, Amount, Customer Name, Customer Account Number) ‏ Name: Contract

18. System Contracts Contract for the Confirmation Payment Package Confirmation of payment has been made Post Conditions: Patient payment must be sent by hospital Preconditions: Display “Payment has been confirmed” Output: If the Payment details are not valid, indicate that it was an error. Exceptions: System Type: Confirmation of the payment detail Responsibilities: Confirmation Name: Contract

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

20. System Contracts Contract 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 Dermatology Output: 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: System Type: Create a Report from Dermatology Responsibilities: Create Report (patient, doctor, symptoms, prescription) ‏ Name: Contract

21. System Contracts Contract 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 processor Output: Patient does not exist; credit card authentication error Exceptions: System Type: To allow the patient to pay through the web interface Responsibilities: Make Payment (Patient, Amount) ‏ Name: Contract