...
To access demo/chart
To record appointment reason
To flag appointments as critical
To access free-form text note associated with appointment
To allow ad-hoc double booking
To show status of patient in clinic
Appointment 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 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 appointment functionality.
1.1.2 Description
Appointment use cases are presenting the summary of the business flow, outlining user’s roles and presenting numerous scenarios of using Oscar Appointment functionality. It also includes preconditions and post conditions and detailed flow of events.
...
Num. | Step | Description | System Response | User |
1 | Connect to the OSCAR main page | Open in Internet browser web page: http://192.168.1.202 | 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) | Verify that credentials are successfully associated to the account
| General User |
3
| Create an appointment | Complete Make an appointment form | Form is completed | General User |
4 | Record appointment note | Verify that form supports free-form text note associated with appointment and it is separate from appointment Reason form | Appointment Note form supports free-form text and it is separate from the appointment Reason form | General User |
...
1.2.2 Exception Flows of Events (Negative)
N/A