Hms

2,825 views
2,492 views

Published on

for hospital management system

Published in: Education
1 Comment
1 Like
Statistics
Notes
No Downloads
Views
Total views
2,825
On SlideShare
0
From Embeds
0
Number of Embeds
7
Actions
Shares
0
Downloads
145
Comments
1
Likes
1
Embeds 0
No embeds

No notes for slide

Hms

  1. 1. Hospital Management System OOSD Object Oriented Analysis Presented by : MANISH MISHRA
  2. 2. Presentation Outline <ul><li>Introduction </li></ul><ul><li>Project description </li></ul><ul><ul><li>Scope </li></ul></ul><ul><ul><li>Assumptions </li></ul></ul><ul><li>Package diagrams </li></ul><ul><li>System sequence diagrams </li></ul><ul><li>Activity diagrams </li></ul><ul><li>System contracts </li></ul><ul><li>Conclusion </li></ul>
  3. 3. Introduction <ul><li>Parkside Hospital </li></ul><ul><li>Hospital Management System </li></ul><ul><ul><li>Patient details and registration </li></ul></ul><ul><ul><li>Consultations </li></ul></ul><ul><ul><li>Resource allocation </li></ul></ul><ul><ul><li>Pharmaceuticals management </li></ul></ul><ul><ul><li>Billing and payments </li></ul></ul><ul><ul><li>User interface conforming to usability guidelines </li></ul></ul><ul><ul><li>Database with audio/visual and past consultations </li></ul></ul><ul><ul><li>Future extensions (web, remote a/v consulting, etc) ‏ </li></ul></ul><ul><ul><li>Management reports, security levels, accounting, etc. </li></ul></ul>
  4. 4. Project Description <ul><li>Scope </li></ul><ul><ul><li>Patient registration </li></ul></ul><ul><ul><li>Appointments scheduling </li></ul></ul><ul><ul><li>Billing and payments (cash, CC, insurance) ‏ </li></ul></ul><ul><ul><li>Security of the whole system </li></ul></ul><ul><ul><li>Pharmaceutical drugs/equipment </li></ul></ul><ul><ul><li>Staff management (work roster, availability, scheduling, etc) ‏ </li></ul></ul><ul><ul><li>Management functions (report generation, accounting, etc) ‏ </li></ul></ul><ul><ul><li>System administration </li></ul></ul><ul><ul><li>Resource allocation (booking rooms, operating theatres, etc) ‏ </li></ul></ul><ul><ul><li>Comprehensive database </li></ul></ul><ul><ul><li>Web interface (proposed for future) ‏ </li></ul></ul>
  5. 5. Project Description <ul><li>Assumptions </li></ul><ul><ul><li>Patient provides CC/insurance details when registering </li></ul></ul><ul><ul><li>Appointments can be cancelled 24 hours in advance without penalty </li></ul></ul><ul><ul><li>Patient medical history can be viewed by concerned doctors at the hospital with approval of the patient </li></ul></ul><ul><ul><li>Hospital is covered by insurance policy </li></ul></ul><ul><ul><li>Staff are assigned roles to interact with the system </li></ul></ul><ul><ul><li>Staff have basic computer operating skills </li></ul></ul>
  6. 6. Package Diagram
  7. 7. Activity Diagrams Pharmaceuticals Activity Diagram Checking Stock
  8. 8. Activity Diagrams Web Package Remote doctor patient consultation.
  9. 9. Activity Diagrams Billing and payment: Payment by Credit Card / Cash
  10. 10. Activity Diagrams Billing and payment: Payment by Insurance
  11. 11. Activity Diagrams
  12. 12. Sequence Diagrams
  13. 13. Sequence Diagrams
  14. 14. Sequence Diagrams Payment Use Case
  15. 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. 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. 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. 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. 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. 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. 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
  22. 22. Conclusion <ul><li>Project will take approx 1 year to complete </li></ul><ul><li>Project will be developed modularly </li></ul><ul><li>We use Event – driven method. </li></ul>

×