Purpose

Define the data elements to utilize Extract, Transformation and Load (ETL) to make sure the information is moved from current EHRs to ICE.

Background

A strategic goal for the Collaboration for Health Information Technology (Collaboration) is to promote standards when possible for all collaboration members and beyond.

Data migration is the process of transferring data between storage types, formats, or computer systems. It is a key consideration for any system implementation, upgrade, or consolidation. To achieve effective data migration, data on the old system is mapped to the new system to relate old data formats to the new system’s formats and requirements.

ETL is a discipline of data management. Its intent is to copy data using methods that assure data quality, completeness, reliability and other attributes with adequate performance.

Core dimensions of data quality are:

  • Completeness
  • Uniqueness
  • Timeliness
  • Validity
  • Accuracy
  • Consistency

It needs to be recognized that the data migration needs of each school will come from varied systems and sources. These needs will need to be addressed individually and outside of this Working Group.

Charge

Define data elements to migrate such that the quality achieves the core dimensions of the data in the source system.

Recognizing that each school has unique data migration needs and timelines, the school with the nearest implementation date will be the focus of the work performed by the Data Migration Working Group.

For each function in the “Good Enough to Go Live” ICE Health Systems electronic health record (EHR), the Data Migration Working Group should:

  1. Clarify the roles that the school and ICE plays in the migration process. It is anticipated that Extract and Transform will be performed by the school and Load will be performed by ICE.
  2. Select the content framework for data migration, and identify the open standards that the collaboration can easily use and sustain. Currently JSON [RFC7159] (JavaScript Object Notation) a lightweight data-interchange format is being considered.
  3. Define the data components that benefit from data migration, e.g., exclude one-time setup components.
  4. Define and verify the JSON scripts primarily for the school with the nearest implementation date.

Chair

Roger Gillie, University of Michigan (will change after U-M implementation)

Composition

1-2 IT professionals from up to six schools and non-voting liaison(s) from ICE Health Systems will comprise the Working Group. Working Group members will become consultants after their school’s implementation.

Meetings

One hour every two weeks.

timeframe

The Advisory Board recognizes that the work of the Data Migration Working Group is ongoing as new schools join the Collaboration and new functions are added to the EHR. Consequently, no time frame to complete work is set.

Reports

The Working Group should give quarterly updates to the Advisory Board. Reports should also include recommendations for next steps.

Acceptance

The Collaboration for Health IT approved this charge on December 6, 2016.