Medical/Dental Professionals

Data Migration Demystified

You have maintained a valuable record of your patients’ health, and you have strategic goals in terms of quality, safety and satisfaction centered on those health records. Data migration employs state-of-the-art tools to ensure that your critical data is available to you on time and in budget.

While data migration is a key component of the Great Lakes Integrated Medical Record (GLIMR) Expand project, it is not quite as broadly understood as the other solution work in the project. There are a number of reasons for that. Data migration means different things to different projects, and the scope and scale of a migration can vary widely from project to project.

Our Cerner consultants are working with the Great Lakes Health teams to select specific demographic and clinical data to be extracted from source systems at the General Physician, PC (GPPC), UBMD and ECMC clinics for import into the GLIMR system, while identifying and working around data from those clinics’ systems that might already be present within GLIMR.

At present the GLIMR Expand data migration team is using modified Millennium Foreign System Interface (FSI) tools and processes to migrate formatted data from legacy systems to GLIMR.

The typical path for a data migration project is to first establish a person-centric foundation via Master Person Index (MPI) analysis and design using person data from each legacy system, and comparing that index to GLIMR. Defining what MPI demographics need to be imported to GLIMR helps create a population that the clinical data can then attach to.

Design, build and testing efforts for data migration culminate in the validation and import of specific subsets of data. The remaining source system data is sent to an archive system. Subsets of data for migration are selected using both retention ranges (one year, three years, etc.) as well as defining specific groups of data to move based on result or document type. Mapping those data elements from the legacy systems to GLIMR, for each data set in scope, comprises the main build effort for a migration project.

GLIMR validation of the source system data that was defined and extracted is the testing event for each data set in a migration. It leads to approval for the final import process to a production domain, in preparation for the go-live event.

The archive vendor selection process at Kaleida Health is in progress. Any legacy system data that is not directly loaded into GLIMR will be available in this archive system, viewable via PowerChart MPage.