Paid Plugin
This is a paid plugin. Please email contact@krishagni.com for more details
Goals - Why integrate with Epic?
- Improve productivity by reduced manual data entry
- Better data quality
- Powerful reporting (E.g. demographics, consents, surgical pathology reports, etc.)
Implementation Options
There are many ways OpenSpecimen can be integrated from Epic.
- HL7 messages
- Nightly database dumps
Which option to take depends on the institute's Epic IT team (i.e. not by OpenSpecimen team). OpenSpecimen is capable of accepting data in all formats.
Workflows
Adding a new participant
- Login to OpenSpecimen
- Enter an MRN
- OpenSpecimen looks-up Epic data and returns match.
- If no match found, error.
- If the match found, the user can review and confirm that the patient is correct.
- Once created, the details pulled from Epic cannot be edited in OpenSpecimen.
Editing a participant
- A participant is edited in Epic
- Information is sent to OpenSpecimen (via HL7 or nightly dump)
- OpenSpecimen will update its records for the updated information
HL7 based integration
- Epic sends an HL7 message to OpenSpecimen for ADT for patient add/edit.
- OpenSpecimen stores them in a staging table.
- When an end-user looks up an MRN, OpenSpecimen will look-up the staging table.
- Unused HL7 messages are purged after 90 days
The following msg types are supported:
Msg | Description |
---|---|
ADT_A01 / ADT_A28 | Add patient |
ADT_A04 / ADT_A31 / ADT_A08 | Edit patient |
ADT_A40 | Merge patient |
List of fields populated from the HL7 messages:
- First name
- Last name
- Middle name
- Date of birth
- Gender
- Race
- Ethnicity
- MRN
- Death date
Nightly database export
- Every night, the Epic team provides a CSV or a database view/table with all the patient information.
- The schema for the table will be provided by OpenSpecimen.
- This table will be used as the "staging patient table" which will be used for lookup whenever a user enters MRN in the user interface.