Use Cases Administration/ Merge Demographics
Glossary
1 | EMR | Electronic Medical Record |
2 | HIN | Health Insurance Number |
3 | MRP | Most Responsible Physician |
4 | OMD | Ontario Medical Documentation |
1. Administration/ Merge Demographics
1.1 Summary
1.1.1 Business Need
Defined users:
Super User/Administrator with full rights:
Add/Edit/Delete
Reactivate account
Access to admin part of the OSCAR
Main purpose of Administration/ Merge Demographics is:
To notify permanence of the merge
To confirm merge
Not be able to undo merge
1.1.2. Description
Demographic merge allow to merge demographics where patient data has been entered into several separate charts by mistake.
Merge Demographics use cases are designed to notify the user of permanence of merge and user must to confirm the action. There is no requirement to be able to undo merge.
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.
User must be notified of permanence of merge and must be able to confirm the action
Num. | Step | Description | System Response | User |
| Pre-condition | Several demographics records have been created for one patient |
|
|
1 | Connect to the OSCAR main page | Launch URL: http://192.168.1.202:8080/Oscar12_1/index.jsp | OSCAR main page with the login is opened | Super 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 | Super User |
3 | Access Merge Patient Records screen | Select Administration Tab → Data Management → Merge Patient Records | Merge Patient Records page appears in a new window | Super User |
4 | Search patient' s demographics records | Search patient's demographics records by name, address, phone, HIN or DOB | Search results based on keywords are listed | Super User |
5 | Accept notification message of permanence of merge | Select records and click on Merge Selected records | Verify that notification message displays of permanence of merge | Super User |
6 | Merge notification message | Verify that notification message displays of permanence of merge | Notification message displays of permanence of merge | Super User |
7 | Merge records | Confirm the action | Records are permanently merged | Super 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.
Alternative Flow 1
There is no requirements to undo merge
Num. | Step | Description | System Response | User |
| Pre-condition | Patient Demographics records have been merged |
|
|
1 | Connect to the OSCAR main page | Launch URL: http://192.168.1.202:8080/Oscar12_1/index.jsp | OSCAR main page with the login is opened | Super 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 | Super User |
3 | Access Merge Patient Records screen | Select Administration Tab → Data Management → Merge Patient Records | Merge Patient Records page appears in a new window | Super User |
4 | Search for patient' s merged demographics records | Verify that Merged patient's demographics records are available | Search results based on keywords are listed | Super User |
5 | User is not able to undo merge | Verify that there is no requirement to be able to undo merge | User is not able to undo merge | Super User |
1.2.2 Exception Flows of Events (Negative)
N/ A