Covered by this topic
This document is intended for those requesting data migration (DM) into Enterprise Health ( EH ), and should be used for surveying any and all requirements for that purpose. Data migration is defined as the movement, or transference of data from one system to another. For example, the moving of data from a legacy application (i.e. Medgate, UL/OHM, etc.) or spreadsheet, to a solution such as Enterprise Health , is understood as data migration.
This section is intended to provide an overview of the current state of data, its storage, and potential restrictions.
Where do you store legacy data that is being considered for data migration?
- List and describe the purpose of all legacy EMRs or commercial applications in use.
- List and describe the purpose of all custom applications storing data that may need migrated to EH .
- List and describe the purpose of all spreadsheets storing data intended for migration.
- Are there any data shares of files outside of the legacy applications or data sources that should be considered? For example, scanned images, results, opinion letters, and so on may be stored outside of an application but requested for migration.
For each of the legacy data sources, are the data or applications hosted locally or off-site? Specifically, do you perform your own data backups and extractions, or will a request need to be made from a third party that supports the application or data storage?
If the legacy data above is in a database, what database version is used for each data application or source (e.g. Oracle 12c, MSSQL 13.0, MySQL 5.7.17, etc.)?
How will the data be delivered? For example, previous clients have performed their own backup or data extraction, and via SFTP, the data is then uploaded to our secure data center or, if applicable, to standalone hardware provided by EH .
Are there any restrictive permissions with sharing your data? Most clients provide full database backups of the legacy system(s) requested for migration; however, we have had instances where the client was severely restricted in what could be released. Please verify what data restrictions, if any, may be present for each data source or application, prior to the data migration kickoff call.
We’d like to know everyone that has a voice in this project. Everyone with decision-making ability needs to be trained in our product. This will help them in decision-making when we have questions about what data is required and how it will be migrated.
Identify key stakeholders in the data migration project and describe their role(s) in the project.
Identify any relevant Subject Matter Experts (SMEs) and/or any key personnel and their titles/roles, if not already listed as a key stakeholder. Examples include:
- Medical Director
- Clinical SMEs
- Report Writers (for each data source)
- Interface Engineers (for each data source)
- Any other SMEs requiring engagement for non-clinical workflows or data migrations
Please provide an organizational chart, if possible. This allows for a better understanding of the parties involved, while reducing planning time and determining resource availability.
Identify the individuals responsible for data validation.
- Is there a user-acceptance process?
Identify the SME for each data source, or the individual(s) best suited to address questions regarding the location and function of specific records or fields during the data migration.
- What is their availability for potential questions or concerns?
- typically encounters the following common data migrations from legacy data source(s). Which of the following data will your migration require? Also briefly describe any relevant reports for the legacy data, including the frequency of use and whether or not you analyze trends in historical data. When considering reports, please consider those used by not only clinical teams, but also caseworkers, medical directors, executives, and anyone else who may be accessing this data.
|NOTES OR COMMENTS
|Case Management (wellness visits or injury- and illness-related cases)
|Health Surveillance (membership and due dates)
|Pulmonary Function Testing
|Respirator Fit Testing
|Scanned images or flat files (e.g. ECGs, Word, Excel, or PDF documents), scanned charts, or employee photos
|Absence Management (Work Restrictions & Accommodations)
|Medical Suitability for Expatriate Assignment evaluations
To ensure a full scope of the project is at hand, are there any additional migrations needing considered?
Some followup questions regarding the above items:
- If you track cases, such as injuries, illnesses, or visits, and discrete data is intended to be moved, is there an established method for differentiating open and closed cases? For example, some workflows dictate that data is not entered into the system until a resolution is determined; whereas some workflows will begin a case as soon as the employee walks into a clinic.
- If you track Health Surveillance (HS) membership and due dates, please list and briefly discuss the HS programs you track.
- If you track HS membership and due dates, what determines the next due date? For example, previous clients have chosen a medical anniversary date corresponding to the employee’s date of birth, date of hire, Cost Center, or Organizational Unit. Most clients, however, use the last test date, and then schedule the next due date at the time of the last exam.
Is there a need to store sensitive data, and if so, are there any controls that need considered in its migration? Examples may be, but are not limited to: Employee Assistance Program (EAP) information, Fit For Duty evaluations, Psychological notes, or data related to highly placed executives/officials.
- With regard to sensitive information, is there a need for relationship mapping, or security rules, intended to limit access to specific data?
Identify and describe any custom reports or tools used to extract data for workflows.
What interfaces (electronic or manual) interact with your legacy data source(s)? Are they inbound, outbound, or bidirectional? Briefly describe each interface. If there are any forms or requirements associated with these interfaces, please include examples.
Will there be a Human Resources (HR) interface? If so, will there be any demographic information that will be required beyond what comes over the HR interface? Please consider dependents, applicants, contractors, and other non-employees that may be seen in a clinic, but not included on the HR feed.
If the answer is Yes above, please consider the following questions around your HR Interface:
- What is your source system and version number?
- Do you host your HR application?
- Will you be providing the periodic data extraction? Or will there be a 3rd party?
Data Format: CSV
- Confirm delimiter (comma, tab, and vertical bar are most common). Choose something not present within any of the data fields for the HR data file.
- What population will be included in each file? Everyone or only people who have had demographic updates since the last extraction (deltas)?
- Frequency of the data file: daily, weekly, etc.
Standard connectivity for HR interfaces include MIE hosting FTPS (preferred) or SFTP.
- What IP Address or Range(s) will be used to connect to MIE’s interface server to deliver the data file?
Please discuss any items from the Workflow Considerations section of the informational document provided with this questionnaire.
- Confirm that the Employee ID passed as the first Medical Record number is 100% populated, never changes, and is never reused.
- Termination procedure
- Applicant procedure
- File name convention
- EG: eh_workday_dev_20170628095942.csv or eh_sap_prod_20170420000000.csv
- Are there any workflows that may be unique to your situation? Or do you have special input screens to facilitate a workflow in your legacy data systems?
- Will different employee/patient populations need to be restricted from certain clinical personnel? For example, would you want to restrict clinicians to work only with employees and personnel by country, person type (i.e. employee, applicant, contractor, etc), or employer organization (e.g. company, subsidiary, contractor, agency, prime, etc)?
- What documentation exists for the legacy data sources? Please provide any documentation available (e.g. diagrams, schemas, videos, tutorials, screenshots, specifications, third-party interface requirements, etc.).
- If Crystal Reports or similar database connections are used to extract or mine data, or the database has a custom front-end (e.g. MSSQL or Access often have these), please provide the queries for common reports and key screens on the front end. These queries are used to identify key discrete data in your systems and understand workflow.
- Can you supply de-identified data of 15-20 complex or “interesting” patient/employee charts/histories/data, which can provide a good representation of all the different types of data intended for migration? This is crucial for understanding data early on as well as for validating data during the migration.
- Though this will be detailed outside of this questionnaire, it is important to understand that workflow discovery is critical to configuration and data migration. Please provide any available workflow diagrams or documentation, to allow for immediate review and preparation. Be sure to consider the workflows of all users of the system including clinicians, caseworkers, report writers, directors, and executives.
- What details/criteria may be needed to configure the employer organizations (e.g., companies, subsidiaries, contractors, agencies, primes, etc)?
- Please discuss, generally, not only what data will be extracted from your legacy source(s), but how much? For example, consider data retention rules around retirees, applicants who never became employees, test charts, etc., which may be unnecessary data to migrate.