R1. The E-OPMR must allow the user create a new patient record from existing data in the EWS. High Level Use Case: TUCBW: User clicks Create New Record button TUCEW: User receives message if system has successfully saved the file or not R2. The E-OPMR must allow the user to search patient records using multiple patient identifiers. High level use case: TUCBW: User enters the relevant identifiers and clicks the Search button TUCEW: User views record(or list of records) if the record(s) exists else the system notifies user that record was not found

R3. The E-OPMR must allow the user to edit patient record. High level use case: TUCBW: User clicks Edit button TUCEW: User receives message from the system if the edit was successfully submitted or not R4. The E-OPMR must allow the user to record patient test High Level Use Case: TUCBW: User clicks Add Test button TUCEW: User receives message from the system if the record was added successfully or not R5. The E-OPMR must allow the user to record patient consultation High Level Use Case: TUCBW: User clicks Add Consultation button TUCEW: User receives message from the system if the consultation was added successfully or not

R6. The E-OPMR must allow the user to add alerts for general independent tasks such as phone calls, reminders, etc. High Level Use Case: TUCBW: User clicks Alert button TUCEW: User receives message from the system when the alert goes off R7.1. The E-OPMR must allow the user to check-out the OPMR file location High Level Use Case: CHECK-OUT TUCBW: User clicks Check-Out button TUCEW: User gets confirmation that file was successfully submitted for checked- out R7.2. The E-OPMR must allow the user to check-in the OPMR file location High Level Use Case: CHECK-IN TUCBW: User clicks Check-In button TUCEW: User gets message that file is now available for check-out

R8. The E-OPMR must allow the user to document a phone call to/from a patient High Level Use Case: TUCBW: User clicks Record Phone Call button TUCEW: User gets message that phone call has been successfully recorded/documented or not R9. The E-OPMR must allow the user to access this system from a remote location. High Level Use Case: TUCBW: User enters login credentials and clicks Login button TUCEW: User gets messages that system was successfully logged out R10. The E-OPMR should generate reports for the user. High Level Use Case: TUCBW: User clicks Generate Report button TUCEW: User gets requested report