1. Patient Demo Screen/ Contacts
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:
...
Patient Demo Screen/ Contacts 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. Patient Demo Screen/ Contacts Use cases are created to meet the EMR Requirements of Appendix A – EMR Specification v4.0 (2.2.1.1.1 - Patient Identification, 2.2.1.1.2 – Patient Contact Information) for Oscar application and to validate the application patient demo screen functionality.
1.1.2. Description
Patient Demo Screen/ Contacts use cases are presenting the summary of the business flow, outlining user’s roles and presenting numerous scenarios of using Oscar Patient Demo Screen functionality. It also includes preconditions and post conditions and detailed flow of events.
Patient Demo Screen/ Contacts use cases are designed to display all mandatory patient identification (last name, first name, date of birth, etc) and contact information (phone, city, province, etc) data, to review previous enrollment status, to include drug interaction preferences.
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.
...
Num. | Step | Description | System Response | User |
| Pre-condition | Patient records are added in database |
|
|
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
| Patient search | Access Patient Search Results from Search Tab | Patient search results is accessible from Search Tab by Patient's name | General User |
4 | Patient detail info | Access Patient Demo Screen from Patient Search page | View Patient demo screen | General User |
5 | Verify all mandatory OMD fields | Verify that all OMD mandatory Patient Identification data is included in Master record | All OMD mandatory data is included | 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 previous enrolment status
Num. | Step | Description | System Response | User |
| Pre-condition | Patient Master record has enrollment updates |
|
|
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
| Patient search | Access Patient Search Results from Search Tab | Patient search results is accessible from Search Tab by Patient's name | General User |
4 | Patient detail info | Access Patient Demo Screen from Patient Search page | View Patient demo screen | General User |
5 | View Enrollment Status | Verify that previous Enrollment Status is listed | Previous Enrollment Status is listed | General User |
Alternate Flow 2
Drugref preferences
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
| Patient search | Access Patient Search Results from Search Tab | Patient search results are accessible from Search Tab by Patient's name | General User |
4 | Patient detail info | Access Patient Demo Screen from Patient Search page | View Patient demo screen | General User |
5 | Verify that drugref preference is available | Verify that Rx Interaction Warning Level section is included in Master record | Rx Interaction Warning Level is included in Master record | General User |
Alternate Flow 3
Display Patient's Contact data
...