...
| Gliffy |
|---|
| imageAttachmentId | att478609425 |
|---|
| baseUrl | https://openspecimen.atlassian.net/wiki |
|---|
| macroId | 65c0d71a-f9fe-4772-997f-d68f82b2b419 |
|---|
| name | EMR Integrationb |
|---|
| diagramAttachmentId | att478609420 |
|---|
| containerId | 101286018 |
|---|
| timestamp | 1649122074125 |
|---|
|
Handling Matches
User enters the patient identifier fields (like MRN) to search for matching participants.
OpenSpecimen displays matching participants from EMR
Data fetched from EMR will be displayed in read-only format
User selects the match and proceeds to the next step.
Handling No Match
If no match is found, then you have two options:
Let the user create a new participant (useful in cases where you recruit external patients)
Disable creating new participants (i.e. patient has to be in EMR)
Steps to Configure Two-step participant registration process
...
You need to add the "spring bean name" to the 'Participants LookUp Workflow' in the system's setting to allow OpenSpecimen to LookUp participants on the staging table.
Go to Homepage → Settings → Search 'LookUp'.
Image ModifiedSelect property 'Participants LookUp Workflow ' → Add value 'bean: stagedParticipantsDbLookup' → 'Update'.
Image Modified
B. JSON Configuration
The fields that need to be used for lookup have to be set with property: "participantLookup": true on your JSON workflow. The JSON can be configured on any of the following levels: individual CP or system.
...
| Expand |
|---|
| title | Set up JSON configure for a specific CP |
|---|
|
Go to the CP overview page → More → Export Workflows. Open the file on the editor of your choice → Set the property: "participantLookup": true for the fields that need to be used for lookup as shown below in the JSON example→ Save it. Go back to the CP overview page → Import Workflows → Upload the updated file → Import.
|
Steps to set up JSON configure at the System level
| Expand |
|---|
| title | Set up JSON configure for a specific CP |
|---|
|
Go to the Homepage → Settings → Search 'System Workflows' →Download the workflow.  Image ModifiedOpen the file on the editor of your choice → Set property: "participantLookup": true for the fields that need to be used for lookup as shown below in the JSON example→ Save it. Go back to the “System WorkFlows” →Upload the updated file → Update.
|
JSON Example
Lookup JSON for MRN and MRN Site
...
| Expand |
|---|
| title | Steps to register EMR participants |
|---|
|
Go to the CP List view page → Add Participant.  Image ModifiedEnter the MRN site and MRN number for the participant → LookUp.  Image ModifiedIf a match is found, it will show a message saying ‘Following participant found. Please review the details and save'. You can review the details and click on 'Add Partcipant’ to register the participant.  Image ModifiedIf a match is not found, it will give an error saying 'No matching participant is found'.  Image Modified
|
Allow non-EMR patient registration
...
| Expand |
|---|
| title | Steps to allow registration of non-EMR patients |
|---|
|
Go to Homepage → Settings → Search 'Add Participant on No Match'.  Image ModifiedSelect property ‘Add Participant on No Match' → Select 'Enabled’ → 'Update'.
 Image Removed Image Added
|
When registration of non-EMR patients is not allowed
...
You can make data pulled from EMR "read-only". Refer this page to lock the participant fields.