1. CSE5322 Fall 2011 Electronic OPMR Filing System(E-OPMR): TEAM 1 Patapatnam, Manasa Mannarkovil Subraman, Premchandran Doreswamy, Harsha Vyas, Kapil

2. Use Cases FILE TRACKING SUBSYSTEM

3. Use Cases by Subsystem ADMIN SUBSYSTEM

4. Use Cases by Subsystem VIEW SUBSYSTEM

5. Use Cases by Subsystem PENDINGDATE SUBSYSTEM

6. High Level Use Case: UC 2.1: Search File – Actor: Office Assistant – Noun: OPMR physical file – Verb: Search – System: File Transaction Sub-System – TUCBW: Office Assistant clicks File-Tracking button on the Main screen – TUCEW: Office Assistant views details of searched File UC 2.2: Check-Out File – Actor: Office Assistant – Noun: OPMR physical file – Verb: Check out – System: File Transaction Sub-System – TUCBW: Office Assistant clicks Check-Out button on the File Details screen – TUCEW: Office Assistant gets confirmation that file was successfully submitted for checked-out.

7. UC 2.3 Check-In File Actor: Office Assistant Noun: OPMR physical file Verb: Check in System: File Transaction Sub-System TUCBW: Office Assistant clicks Check-In button on the File Details screen TUCEW: Office Assistant gets message that file is now available for check-out. UC 2.4 Transfer File Actor: Office Assistant Noun: OPMR physical file Verb: Transfer System: File Transaction Sub-System TUCBW: Office Assistant clicks Transfer button on the File Details screen TUCEW: Office Assistant gets confirmation that file was successfully transferred to the named person High Level Use Case:

8. UC 2.5 View File History Actor: Office Assistant Noun: File History Verb: View System: View Sub-System TUCBW: Office Assistant clicks History button on the File Details screen TUCEW: Office Assistant views list of file transaction items on the File History screen UC 2.6 View Pending Dates Actor: Office Assistant Noun: Pending Dates Verb: View System: View Sub-System TUCBW: Office Assistant clicks Pending Dates button on the File Details screen TUCEW: Office Assistant views list of Pending Dates items on the Pending Dates screen

9. High Level Use Case: UC 2.7 View Today’s Pending Files Actor: Office Assistant Noun: Today’s Pending Files Verb: View System: View Sub-System TUCBW: Office Assistant clicks Today’s Pending Files button on the File Tracking screen TUCEW: Office Assistant views list of Pending File items for that day on the Today’s Pending Files screen UC 2.8 Modify Pending Date Actor: Office Assistant Noun: Pending Dates Verb: Modify System: Pending Dates Sub-System TUCBW: Office Assistant clicks required Pending Date Entry on the Pending Dates screen TUCEW: Office Assistant gets confirmation that pending date was successfully modified.

10. High Level Use Case: UC 2.9 Add Pending Date Actor: Office Assistant Noun: Pending Dates Verb: Add System: Pending Dates Sub-System TUCBW: Office Assistant clicks Add button on the Pending Dates screen TUCEW: Office Assistant gets confirmation that pending date was successfully added.

11. EXPANDED USECASE Actor: Office AssistantSystem: File Transaction Sub-System [0] The system displays the file tracking screen which has a File searching functionality [1] The Office Assistant enters the file identifier(s) and clicks on search button on the search file screen [2] The system displays: a)List of files that match search criteria or b)a message that the file is not available [3] The Office Assistant clicks on the desired file item [4] The system displays the File Details screen [5] Office Assistant views details of searched File UC 2.1: Search File

12. EXPANDED USECASE UC 2.2: Check-Out File Actor: Office AssistantSystem: File Transaction Sub-System [0] The system displays the File Details screen [1] TUCBW The Office Assistant clicks the check-out button on the File Details screen [2] The system displays the File Check- Out screen [3] Office Assistant fetches the physical file and fills out the details in the Check-Out screen with the following information, and clicks on submit: i.Who checked out the file? ii.When it should be returned. iii.Why it was checked out. iv.Set a reminder for expected check-in date. v.When was it checked out [4] The system displays confirmation that file is successfully submitted for check- out [5] TUCEW The Office Assistant sees the message and hands over the physical OPMR file to the person requesting it.

13. EXPANDED USECASE UC 2.3: Check-In File Actor: Office AssistantSystem: File Transaction Sub-System [0] The system displays the File Details screen [1] TUCBW The Office Assistant clicks the check-in button on the File Details screen [2] The system displays the File Check- In screen [3] Office Assistant fills in the check- in form, with the following details, and clicks on submit on the tracking screen: i.When was file checked in [4] The system displays a message that the file is now available for check- out [5] TUCEW The Office Assistant sees the message and returns the physical OPMR file back to its position

14. EXPANDED USECASE UC 2.4: Transfer File Actor: Office AssistantSystem: File Transaction Sub-System [0] The system displays the File Details screen [1] TUCBW Office Assistant clicks Transfer File button on the File Details screen [2] The system displays the Transfer File screen [3] Office Assistant fills out the details in the File Transfer screen with the following information, and clicks on submit: i.To whom was the file transferred ii.When it should be returned. iii.Why was it transferred iv.Set a reminder for expected check-in date. v.When was it transferred [4] The system displays confirmation that file is successfully submitted for transfer [5] TUCEW Office Assistant gets confirmation that file was successfully transferred to the named person

15. EXPANDED USECASE UC 2.5: View File History Actor: Office AssistantSystem: View Sub-System [0] The system displays the File Details screen [1] TUCBW Office Assistant clicks View History button on the File Details screen [2] The system displays the File History screen [3] Office Assistant fills out the date range in the File History screen to view File History details that occur between the date ranges and clicks the Display button. [4] The system displays a list of file transactions on the File History screen. A transaction can be transfer, check-in, or check-out event. Each file transaction item has the following information: i.Who transacted the file? ii.When did the transaction take place? iii.What was the reason? [5] TUCEW Office Assistant views list of file transaction items on the File History screen

16. EXPANDED USECASE UC 2.6 View Pending Dates Actor: Office AssistantSystem: View Sub-System [0] The system displays the File Details screen [1] Office Assistant clicks Pending Dates button on the File Details screen [2] The system displays the Pending Date screen. Each file transaction item has the following information: i.Who requested the file? ii.When is it pending? iii.What was the reason? [3] TUCEW: Office Assistant views list of Pending Dates items on the Pending Dates screen

17. EXPANDED USECASE UC 2.7 View Today’s Pending Files Actor: Office AssistantSystem: View Sub-System [0] The system displays the File Tracking screen [1] TUCBW: Office Assistant clicks Today’s Pending Files button on the File Tracking screen [2] The system displays the Pending Date screen. Each file transaction item has the following information: i.Who requested the file? ii.What was the reason? [3] TUCEW: Office Assistant views list of Pending File items for that day on the Today’s Pending Files screen

18. EXPANDED USECASE UC 2.8 Modify Pending Date Actor: Office AssistantSystem: Pending Dates Sub-System [0] The system displays the Pending Dates screen [1] TUCBW: Office Assistant clicks required Pending Date Entry on the Pending Dates screen [2] The system displays the Modify Pending Date screen. Each file transaction item has the following information: i.Who requested the file? ii.What was the reason? iii.When is it pending? [3] TUCEW: Office Assistant gets confirmation that pending date was successfully modified.

21. Classifying TSRH System Brainstorming ListClassification ResultRule Patient 1 (C) Patient1(a) DOB 1 (A) DOB1(e) has 8 (AS) has (Patient, OPMR file) (1, 1)8(a) Office Assistant 1 (C) Office Assistant1(a) OPMR file 1 (C) OPMR file1(a) Category 1 (A) Category1(e) Discharged 5 (V) “discharged”5(a) PRN 5 (V) “PRN”5(a) Pending 5 (V) “pending”5(a) Location 1 (A) Location1(e) State 1 (A) state1(e) Pending Date 1 (C) Pending Date1(a) Staff Name 1 (A) Staff Name1(e) Date 1 (A) Date1(e) Notes 1 (A) Notes1(e) Include 8 (AS) include (OPMR file, Pending Date) (1, 0...*)8(a)

22. Classifying TSRH System Transact3(AS) transact (Office Assistant, OPMR file)3 Transaction1(AC) Transaction(transact)1(c) Date1(A) date1(e) Staff Name1(A) staff name1(e) Check Out1(C) Check Out1(a) Return Date1(A) return date1(e) Notes1(A) Notes1(e) Check In1(C) Check In1(a) Transfer1(C) Transfer1(a) Return Date1(A) return date1(e) Notes1(A) Notes1(e) (I) ISA ( Check Out, Transaction)9 (I) ISA ( Check In, Transaction)9 (I) ISA ( Transfer, Transaction)9 Staff1(C) Staff1(a) Doctor1(C) Doctor1(a) Nurse1(C) Nurse1(a) (I) ISA ( Doctor, Staff) (I) ISA ( Office Assistant, Staff) (I) ISA ( Nurse, Staff) 9

23. DOMAIN MODEL

24. Package Diagam: File Tracking

25. Add Pending Dates

26. Check In

27. Check Out

28. View File History

29. Modify Pending Dates

30. Get Pending Dates

31. Search File

32. Get Today’s Pending File

33. Transfer

35. Requirements 1.The E-OPMR must allow the user create a new patient record from existing data in the EWS. 2.The E-OPMR must allow the user to search patient records using multiple patient identifiers. 3.The E-OPMR must allow the user to edit patient record. 4.The E-OPMR must allow the user to record patient test. 5.The E-OPMR must allow the user to record patient consultation. 6.The E-OPMR must allow the user to add alerts for general independent tasks such as phone 7.The E-OPMR must allow the User must be able to track the OPMR file. 8.The E-OPMR must allow the user to document a phone call to/from a patient. 9.The E-OPMR must allow the user to access this system from a remote location. 10.The E-OPMR should generate reports for the user.

36. Requirements Traceability Matrix UC2.1 Search File UC2.2 Checkou t File UC2.3 Check In UC2.4 Transfer File UC2.5 View File History UC2.6 View Pending Dates UC2.7 View Today’s Pending Dates UC2.8 Modify Pending Dates R01 R02X R03 R04 R05 R06X R07XXXXXXXX R08 R09 R10XXX

37. Patterns Used Singleton Controller Creator Expert

38. Thank you