Glossary
1 | EMR | Electronic Medical Record |
2 | MRP | Most Responsible Physician |
3 | OMD | Ontario Medical Documentation |
4 | OHN | Ontario Health Number |
1. Create Patient
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 the Create Patient is:
To add a new patient record that includes all mandatory OMD demo data
To prevent creation of duplicate records by name and/ or by health card
Create Patient 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. Create Patient Use cases are created to meet the EMR Requirements of Appendix A – EMR Specifi
cation v4.0 (2.2.1.1.1 - Patient Identification) for Oscar application and to validate the application create patient functionality.
1.1.2 Description
Create Patient use cases are presenting the summary of the business flow, outlining user’s roles and presenting numerous scenarios of using Oscar Create Patient functionality. It also includes preconditions and post conditions and detailed flow of events.
The Create Patient use cases are designed to create the database for a specific patient's Demographic records including all mandatory OMD demo data (last name, first name, date of birth, etc.). It is important to enable the system to prevent user from creating duplicate records at minimum by name and /or health card.
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.
Create a New Demo Record when search by name
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
| Search for patient record by name (to prevent record duplication) | Access Patient Search Results page from Search Tab | Patient search results page is accessible from Search Tab by name | General User |
4 | Create a New Demographic record | Complete the “Add a Demographic Record” form | Form is completed | General User |
5 | Verify all mandatory OMD demo data | Verify that all mandatory OMD demo data is included in the form | All mandatory OMD demo data is included in the form | General User |
6 | Verify that record is not duplicated | System is confirming that record does not exist in OSCAR. | Record is successfully added and NOT duplicated. | 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
Create a New Demo Record when search by health card number
Num. | Step | Description | System Response | User |
| Pre-condition | Patient's Demographic record with OHN 1123581314 has been created |
|
|
1 | Connect to the OSCAR main page View Schedule for a Single User
| 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
| Search for patient record by health card (to prevent record duplication) | Access Patient Search Results page from Search Tab | Patient search results is accessible from Search Tab by Patient's health card number | General User |
4 | Create a new patient's record | Complete “Add a Demographic Record” form | Form is completed | General User |
5 | Verify all mandatory OMD demo data | Verify that all mandatory OMD demo data is included in the form | All mandatory OMD demo data is included in the form | General User |
6 | Verify that record is not duplicated | System is confirming that record does not exist in OSCAR. | Record is successfully added and NOT duplicated | General User |
1.2.2 Exception Flows of Events (Negative)
This section describes the exception flow of events based on variations in the main Use Case scenario that result in a Failed End Condition for completion of the Use Case.
Exception Flow 1
Create a Duplicate Demo Record when search by name
Num. | Step | Description | System Response | User |
1 | Connect to the OSCAR main page | Open 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
| Search for patient record by health card number (to prevent record duplication) | Access Patient Search Results page from Search Tab | Patient search results is accessible from Search Tab by Patient's health card number | General User |
4 | Create a new patient's record | Complete the “Add a Demographic Record” form | Form is completed | General User |
5 | Verify that creating duplicate record is prevented | System is confirming that record exist in OSCAR | Record is duplicated and error message is populated | General User |
Exception Flow 2
Create a Duplicate Demo Record when search by health card
Num. | Step | Description | System Response | User |
| Pre-condition | Patient's demographic record with OHN 1123581314 has been created |
|
|
1 | Connect to the OSCAR main page
| Open 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
| Search for patient record by health card (to prevent record duplication) | Access Patient Search Results from Search Tab | Patient search results is accessible from Search Tab by Patient's health card | General User |
4 | Create a new patient's record | Complete the “Add a Demographic Record” form | Form is completed | General User |
5 | Verify that creating duplicate record is prevented | System is confirming that record exist in OSCAR | Record is duplicated and error message is populated | General User |