1. Appointment/ Scheduling Screen
1.1 Summary
1.1.1 Business Need
Defined users:
...
Appointment/ Scheduling Screen requirements (Confluence link: https://oscaremr.atlassian.net/wiki/pages/viewpage.action?spaceKey=QA&title=OLD+OMD-based+testing+checklist&src=email) need to be aligned with Ontario MD EMR Specification document set that describes the high level and detail requirements central to the general EMR application. Appointment/ Scheduling Screen Use cases are created to meet the EMR Requirements of Appendix A – EMR Specification v4.0 ( 2.1.10 Scheduling Requirements) for Oscar application and to validate the application functionality regarding viewing, scheduling, updating or searching for the appointments.
1.1.2 Description
Appointment/ Scheduling Screen use cases are presenting the summary of the business flow, outlining user’s roles and presenting numerous scenarios of using Oscar Appointment Screen functionality. It also includes preconditions and post conditions and detailed flow of events.
...
1.1.3. Pre-action requirements/state:
OSCAR McMaster Test Version 12.1, system,
...
DB are up, configured and working as expected.
1.1.4. Post-action state:
...
Num. | Step | Description | System Response | User |
1 | Connect to the OSCAR main page | Open in Internet browser web page: http://192.168.1.202:8080/Oscar12_1/index.jsp | OSCAR main page with the login is opened | General User |
2 | Log In | Enter user's valid credentials (User Name / Password/2nd Level Pass code if applicable) | By entering right credentials user is getting system verification acceptance | General User |
3
| Select a group | Select a group from the drop down menu”Group” for multiple providers | Group providers' schedule is available to view | General User |
4 | View schedule | Verify that user can view daily, monthly, weekly, calender schedule | Daily, monthly, weekly, calender schedules are available to view | General User |
1.2.1 Alternate Flows of Events
This section describes the alternative flow of events based on variations in the main Use Case scenario that still result in a Successful End Condition at completion of the Use Case.
Alternate Flow 1
View schedule for an Individual Provider
...
Num. | Step | Description | System Response | User |
| Pre-condition: | 1. A provider should have credentials with limited access (E.g. Receptionist) 2. Appointment should be scheduled |
| Receptionist |
1 | Log In | Enter user's valid credentials (User Name / Password/2nd Level Pass code if applicable) | Verify that credentials are successfully associated to the account
| Receptionist |
2 | Verify that patient data is secure | Verify that patient name should show without patient data | Patient name displays on screen without patient data. | Receptionist |
Alternate Flow 4
Search for the next available appointment
...