Data Import Master List

This page provides an overview of the ways MIE imports data from a client’s legacy EMR (i.e., spreadsheets, custom databases, and other sources) into the  Enterprise Health ( EH ) system. Most information is imported using CSV files and an application program interface (API).

CSV refers to the type of file and format of data needed to import information into an EH system. API refers to how the data interacts with the EH system. See the Import Overview  page for a more detailed explanation of terminology.


The sections that follow should be presented to decision-makers or stakeholders interested in a general explanation of MIE’s import tools. Technical details are provided in the individual pages linked in each section.


The following sections represent different data types that may be imported into EH using MIE’s different tools and APIs. This page provides a brief description of the data, example functionality in EH , and links to specifications and other details on each API.

Standard features and EH product offerings are not discussed as part of this overview. Imports that require development include details on their respective pages.

Chart (Employee) Demographics

The Chart Data CSV API is used to import many types of chart data, from chart demographics to observations. It may also be used to set up relationships between charts. This API is used as part of MIE’s standard Human Resource Interface, but it may also be used for single imports of new charts or updates to charts.

Standard demographics display employee information such as name, DOB, gender, address, phone number, email address and employer information. Information in the HR import file is mapped to the appropriate demographic field. A history of revisions is stored indicating the date/time of the change.

Extended demographic fields are configurable based on customer requirements. Custom fields outside of what is listed in the HR import template are not included in the standard implementation. Customization requires a discovery call to scope and quote the work effort. Revisions are not stored on custom extended fields.

Administrative demographic fields are in a separate table and store specific employment information such as supervisor information, cost center, job description, and work schedule. A history of revisions is stored indicating the date/time of the change.

Organizational Hierarchy

The organizational hierarchy displays in the employee demographics chart tab and is also used as a filter for reporting purposes. Mapping organizational hierarchies is not included in the standard implementation and would be scoped and quoted separately.

Chart-to-Chart Relationships

A chart can represent a person, organization, or other entity. Chart-to-chart relationships are used by the Enterprise Health systems to connect a patient (employee) to another patient, employee group (patient population), or non-employees. The relationship link works with security restrictions to determine who has access to view information on specific charts. Relationships display in the demographics chart tab.

The Chart Relations CSV API imports various relationships between charts.

Encounters / Incidents / Cases

An encounter documents a visit with a employee, and is also known as a patient visit. An encounter is a template of specific items to be addressed, in part or completely, during an appointment including the subjective, objective, assessment and plan. The encounter records information collected during an appointment, and stores it in the final desired format: a visit report document.

All aspects of the visit are covered in the encounter, such as the history of present illness, case/incident information, past medical history, medications, allergies, review of systems, vitals, tests and procedures, physical exam, assessment, restrictions/accommodations, plan and follow up information.

The Clinical Encounter CSV API imports data related to an employee’s (patient’s) condition.

Related documents are included or linked to an encounter.

Restrictions and Accommodations

Encounters are used to document many types of employee visits, including workplace incidents and accommodations and restrictions.

In an EH system, a restriction (clinical restriction) refers to an activity that an employee is not permitted to do after an injury (incident). An accommodation is a modification that allows an employee to continue working, or lost time (worker’s comp plan) available for an employee who cannot work after an incident.

The Lost Time CSV API is used to import information related to an employee’s (patient’s) condition, accommodation, and lost time.

Discrete Chart Data

An observation in an MIE system is a means of storing repeated historic data, such as vital signs, lab results, measurements, and other discrete data. Any discrete data can be stored as an observation, but some is stored on other custom database tables, such as audiograms, demographics information, injections, medications, prescriptions, and allergies. The data in these other custom tables may also be stored as observations.


MIE systems store discrete data for occupational audiogram tests. Audio tests are linked to a chart through a document. Audiogram data contains a number of specific tests and baselines aggregated into a single document. Previous audiogram data can be aggregated to display graphically in a document.

The Audiometric Data CSV API imports audiometric and related data for an employee (patient).

Audiograms that are converted from other systems store the data discretely as an individual report document.

Audiogram questions are stored as observations in a flowsheet-like format ordered by date.

Respirator Fit Test

EH maintains records of all respirator masks an employee has tested for use. The Respirator Fit Test Data CSV API imports data related to respirator fit testing.

  • CSV import specification TBD
  • Respirator Fit Test CSV API TBD

Spirometry (PFT)

Spirometry, or pulmonary function tests (PFT), are stored for individual employees. Additional information on the employee’s height and weight is recorded to compare to predicted results. The comparison tool displays PFT information in a flowsheet format. The PFT Data CSV API imports data related to spirometry.

Lab Data

Lab results are stored in a chart as a document; a document may contain multiple lab results. HL7 messages send all of the information used to create a lab document. The common order segment (ORC) message with visit information (DOS) creates the document in the MIE system’s database. The observation request (OBR) message includes the order number and panel or test name to create the lab request. The observation segment (OBX) transmits the observed date, results, units, and range to create the observation. Revisions are stored as well as the date/time the results were received. All lab results are stored both as discrete date (for trending and flowsheet purposes) and as a document. Abnormal results are highlighted in red.

The Lab Results CSV API imports data related to lab data.

Converted lab results store as a document in a chart.

The discrete lab results also display as a flowsheet.


An observation is a means of storing repeated historic data, such as vital signs, lab results, questionnaire responses, etc. for an employee. Vitals display in a flowsheet format. The Observations CSV API imports data related to observations.

The vitals flowsheet displays in the Vitals chart tab and within the visit encounter.

Lab results store as a discrete data and display in a flowsheet format and as a document in the chart.

Health Surveillance


A panel defines a group of events or actions that will take place on certain profiles of people on a regular schedule in the Health Surveillance module of the MIE system. Panels are sometimes referred to as exposure groups, as panels are used for groups exposed to certain hazards due to their job roles. The panels table is also used to document regularly scheduled voluntary health screenings or checkups. A panel action refers to a procedure that is completed for an employee as part of a panel.

The Configuration Tool has been developed to import panel data into EH.

There is a CSV import/export template that may be used to setup surveillance panels and actions, however it is primarily used to copy data from one MIE system to another.

There is an editor built into the MIE system to initially setup the panels and actions.

  • CSV import specification TBD
  • Wiki page TBD

Panel Membership

The Panel Member CSV API is used during initial setup to import employees to the appropriate surveillance panel.

There is an editor to automate business rules for which employees should be added or removed from panel membership. In addition, a system administrator may also manually include or exclude specific employees from the panels.

Panel Status

The Panel Status CSV API is used for panels that use the “Panel Expiration” method of triggering orders. This method has the advantages that the import of previous completed order records is not necessary for HSP to function, and that only employees with status records provided will have new orders triggered. This allows for a phased roll-out of HSP programs. It also allows for fine-grained control of initial due dates, rather than relying on the system to calculate them.

Completed Orders

The last completed date is imported during the migration process using the Completed Orders CSV API to ensure that surveillance actions trigger with the appropriate due date.

There is a column that displays the source of the information. If the order completion information comes from a legacy system it will display the name of that system (i.e. HAMT Import).

During the migration process additional surveillance notification documentation may be imported as a document within the chart.

Orders Compendium

An order is a term used loosely when any method is used to request tests, labs, radiology studies, or E-Orders. Each lab vendor has specific test codes that they use to result ordered tests. The Order List Compendium CSV API loads them as orderable items in EH.

A standard orders compendium is included in the initial installation, however there is an editor for a system administrator to manually add/remove/edit orders and order pick lists within the MIE system.

In addition, all orders for lab facilities can store the order code, CPT code, and LOINC code.

Non-Discrete Documents

Summary documents are generated in an MIE system to display non-discrete information on a chart.

Summary Documents Using WC Query

Text is stored as document during a data migration. A description of each type of document is stored in the document type name, which allows the MIE system to display the document under the appropriate chart tab in a chart. The Custom Documents CSV API imports a number of summary, non-discrete data as a document.

Summary Documents Creating HTML Files

Case information may be stored as a document in a static 2-column format, which displays the field label and the value side-by-side. The document type name is specific to the type of information displays in the document, which allows the document to display in the appropriate chart tab within a chart. The Summary Documents CSV API imports a number of summary, non-discrete data as a document.


Questionnaire data is grouped together by date of service in a document. The document type name is stored as a questionnaire so it will display within the appropriate chart tab in a chart. In addition, questionnaire data may be linked to the encounter for that date of service.

  • CSV import specification TBD
  • Wiki page TBD


A number of external database tables are referenced to identify drugs for injections/immunizations and relate them to patients.

Injections data is stored as a document, and will display within the appropriate tab of a chart.

In addition, injections display within the Injections flowsheet chart tab as discrete data.

MIE File Import

The File Import CSV API  imports and stores a set of files (an archive) into EH as a document. A document is then associated with a chart. A chart is simply a way to collect different information on one topic, just like a physical patient chart would contain a variety of information on an individual.

Along with the files that are imported into the MIE File System, a discrete document record is created to associate the file with the correct chart in the MIE system. Although the content of the file is not stored as discrete data, the document record is stored discretely and features data such as the service date, enter date, service location, author, and document type (a way to group and classify documents in MIE’s system).

  • CSV import specification TBD
  • Wiki page TBD

Employee Photos

Employee photos are one example of files that may be imported with the File Import CSV API. Employee photos appear on the Summary and Demographics tabs in the employee’s chart.

Scanned Documents

Scanned documents are another example of files that may be imported with the File Import CSV API. PDF or TIF formatted files may be imported into the MIE system during the data migration process. As with every file import, each file has a header file to indicate the employee MR number, date of service and document type name these documents will display in the appropriate chart tab in the employee’s medical record. Documents that are not indexed may be imported into the WebScan module to allow a user to manually index those fields before uploading the images to the medical record.

ECG Flowsheet and Reports

Historical ECG data is imported as a document.

Specific discrete data fields may also be viewed in a flowsheet format.

Other Flowsheets and Reports

Vision Flowsheet and Reports

The vision flowsheet displays specific discrete data in order by date of service.

Historical vision data is imported as a document in a chart.

X-ray Flowsheet and Reports

Historical x-ray reports are imported as a document. Specific discrete data fields may also be viewed in a flowsheet format. In addition, the MIE system has the ability to store digital radiology (DICOM) images.

Discrete System Data

Pharmacy Filter

The pharmacy import template allows for a batch upload to the inventory module. Items are matched by Name, Strength and Lot # to determine if an existing item should be updated or a new item added to the MIE system.


There is an editor in the MIE system to manually add/edit schedules, appointment types and cancellation codes. The schedules may also be copied to a new entry. If appointments are uniquely identified during the data migration they will be stored in the appointment history in the chart. The Appointments CSV API imports data related to appointments and schedules.

Fee Schedules

Fee schedule information may be imported from a template. There is an editor within the MIE system to add/edit/remove CPT codes, descriptions and fee schedule information.


The Asset Management module includes the ability to import asset details via an Assets CSV API. The CSV defines each field and allows the ability to leave columns blank if the data is not available. This can be populated by the client and imported directly into their systems. All columns must remain in place with the header row in place.

Order Questions

Orders questions may be added using a template. There is also an editor within the MIE system to create orders questions.

Enterprise Health Documentation

Last Updated:

Last Build: Fri, 07 Jun 2024 13:13:36 EDT
WikiGDrive Version: dd69069d725fca5f553df7ded62e130a49d49ca6