OpenSpecimen Epic integration

Overview

Epic contains demographics and clinical data about patients. Integrating Epic with OpenSpecimen will ensure high-quality data, avoid manual data entry errors, and save end-users’ data entry time. 

This document explains the different integration options between Epic and OpenSpecimen.

HL7 based integration

Epic will send HL7 messages (ADT) to OpenSpecimen for every patient add, edit, merge, and delete. Since most of these patients will not have specimens collected, the plugin stores the data in a staging table. When an end-user registers a new participant in OpenSpecimen, it will look up the staging table based on MRN. If it finds a match, the system moves to the patient from staging to the OpenSpecimen database.

Nightly data export from Epic

Epic will export patient demographics into a database table or CSV file every night. This data is imported into the OpenSpecimen staging tables and used when an end-user registers a new patient in OpenSpecimen.

Staging table purge

The staging table is purged once in 180 days to avoid the staging table continuously growing.

Locking information in OpenSpecimen

Any data field imported from Epic is not editable in OpenSpecimen to ensure a “single source” of information.

Leave a Reply

Your email address will not be published. Required fields are marked *

This site uses Akismet to reduce spam. Learn how your comment data is processed.