Optimal Outcomes, or ​O2, is an electronic medical records system developed by The University of Kansas Hospital. It is based on ​EPIC, and it is one of the primary HERON data sources.

Epic is also rolling out to the KUPI clinics, so HospitalEpicSource is becoming a misnomer.

With a 1st cut at demographics, diagnoses, labs, and meds, from a Sep 2010 snapshot, we declared victory on milestone:EpicAlphai2b2. With the addition of flowsheets and automated system access policies, we reached milestone:EpicAlphai2b2. We're working on a Jan 2010 snapshot; see HeronLoad.

Epic Clarity Relational Store

The ​Epic online documentation Galaxy explains two different data models within Epic:

• ​clarity - a modern relational model, but batch-updated so that it lags real-time state by up to a day
  • see also: ​Clarity Training Companions
• ​chronicles - the underlying data store, using technologies such as ​cache and ​MUMPS

Arvinder has been working with hospital database folks to get so-called "build" data; see source:heron/clarity_build_instance and Clarity Spring 2008 data model.

​Clarity Training Companions explain ADT, Inpatient, etc.

We may explore chronicles access in the future (#20).

We can find the Clarity column name and the description of a item from Hyperspace by doing a Ctrl+left click in the item box.

Other sites using Epic and i2b2

UC Davis Clinical and Translational Science Center (CTSC), Larry Errecart

Here's our primary script we use to build our patient_dimension, visit_dimension and observation_fact tables.

-- Larry Errecart <larry.errecart@…> 9/15/2010 12:29 PM

Cincinnati, Keith Marsolo

• ​Managing Clinical Data for Research Using Epic and I2b2: A Case Study from Cincinnati Children's Hospital (Keith Marsolo, Oct 2009 AUG meeting)
• ​FAQ | i2b2 Research Data Warehouse

Additional information from Keith Marsolo at Cincinnati on how they extract from EPIC:

On Sun, 2010-09-19 at 12:03 -0400, Keith Marsolo wrote:

All,

We've posted ​some documentation that describes our work with the Epic Clarity database.

The first document: ​Moving Data from Epic to I2B2.docx describes, well, our approach to moving data from Epic to i2b2. It's not complete, but it provides an overview of how we load demographics, diagnoses, and medications. There's some information on how we create metadata XML for each content type. This is similar to the upcoming "modifier" functionality in version 1.6. Until we release our code, it's more or less CCHMC-specific, but the content would be applicable to either approach.

The other document ​epic_dw_master_tables.pdf details some of the steps used to create our "Master" Epic datamart that we provide to users for reporting and other purposes. Not all of the tables are included, but we've provided a few of the more frequently used ones. The scripts provide an overview of what columns/tables to use to look for certain content.

Words of "wisdom":

1. The tables/columns in Epic may have misleading names. Always check the Epic UserWeb/Clarity data dictionaries [e.g. Clarity Spring 2008 data model] to determine the true purpose of the field.
2. Never assume that the Epic documentation is accurate and/or complete. Each institutions Epic implementation is different, and data may be in unique locations, particularly if that data is fed by an interface. To verify the data you are working with is correct (i.e. what you think it means), I would encourage you to work with your Clarity Reporting Team or end users to ensure that the data in the database matches what appears on the screen.

Thanks.

Keith