1. Appointment

1.1 Summary

1.1.1 Business Need

Defined users:

MRP doctors, residents, nurses, team assistants and other medical staff with the credentials and rights to access OSCAR web-site. General user is given administrative rights.
Super User/Administrator with full rights:

Add/Edit/Delete
Reactivate account
Access to admin part of the OSCAR

Main purpose of Appointment is:

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.

The Appointment Use cases are designed to enable a provider to access patient's demographic record from the scheduled appointment in Appointment page, to arrange a new appointment, to add an appointment's reason and notes in a patient's record, to flag an appointment as critical if necessary, to set two or more overlapping appointments, to display status of patients in clinic (in Waiting Room, Waiting for provider, etc).

1.1.3. Pre-action requirements/state:

OSCAR McMaster Test Version 12.1, system, and DB are up, configured and working as expected.

1.1.4. Post-action state:

OSCAR McMaster Test Version 12.1 is running and behaving as expected.
OSCAR McMaster Test Version 12.1 has all functionality prior to the change (outside of removing functionality intentionally)

1.2 Flow of Events

This section describes the main flow of the Use Case and system responses.

Access Demo/Chart

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	Access Demographic patient info	Access Patient Demographic from appointment in schedule	Demo/chart is accessible from appointment in schedule	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

Ability to record appointment reason

Num.	Step	Description	System Response	User
1	Connect to the OSCAR main page	Launch 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	Create an appointment	Complete “Make an appointment” form	From is completed	General User
4	Record appointment reason	Verify that appointment reason can be added when creating an appointment	Appointment reason form supports free-form text and can be added when creating an appointment	General User

Alternate Flow 2

Ability to record appointment note

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)	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

Alternate Flow 3

Ability to Flag appointments as critical

Num.	Step	Description	System Response	User
	Pre-condition:	1. A provider should have credentials with limited access 2. Appointment should be scheduled
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)	Verify that credentials are successfully associated to the account	General User
3	Create an appointment	Complete Make an appointment form	From is completed	General User
4	Flag appointment	Verify that appointment can be flagged as critical	Appointments can be flagged as critical and should be visually distinct	General User

Alternate Flow 4

Ability to ad-hoc double book

Num.	Step	Description	System Response	User
		Pre-condition: Appointment has been scheduled
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	Ad-hoc double appointment	Verify that two overlapping appointments can be created	Ad-hoc double appointment can be booked	General User

Alternate Flow 5

Status of Patient in clinic

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	Create an appointment	Complete Make an appointment form	From is completed	General User
4	Status in Clinic	Verify that selected Status of Patient in clinic shows from appointment in schedule	Status of Patient in clinic shows from appointment in schedule	General User

1.2.2 Exception Flows of Events (Negative)

N/A

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.