Covered by this topic
The following columns display in standardized data import specifications:
Field Name - The name for the specific field and what should be the column header in the file. Often from the related database column name.
Type (Length)- Identifies what type of value should be sent in this field and the maximum length the field can hold. Updated information available in db model, otherwise follow link to model spreadsheet.
Required - Indicates if a field is required. Options include:
- R - required: Data is required for import to function.
- O - optional: Data is optional for import.
- BP - best practice: Data is not required, but provides better usability within EH.
- CR - conditionally required: Data is required based on conditions defined in spec. Include details for conditionally required data in this column as needed.
Description - Description of imported information. Retrieved from db model or model spreadsheet (see link under Type).
Example - Example field contents.
Data File Column Name Header - Name of column header in CSV file.
Displays in EH? - Yes/No - Indicates if field displays in the EH system.
Client Using - Indicates if client will use field in their EH system.
Client Notes - Open for client use to document questions.
MIE Notes - Open for MIE use to document questions.
MIE Wiki Link - URL to MIE Wiki page with related information.
MIE Legacy Field # - (Use if applicable.) Order of columns from older MIE spec.
Older specifications may display different columns or a different order. The standard specification template is available here.
CSV API wiki pages refer to data as it is named in the Field Name column of the specification, accompanied by the Data File Column Name Header in parentheses. This aides in tying together the details of the specification with the CSV template file used for the import. For example, Name Value Pairs (name_value.NAME)
The following fields require specific codes to represent specific values, and the data won’t be displayed properly in a MIE system if the specific codes are not used.
ISO 2 letter state code (ISO 3166-2) - https://www.iso.org/obp/ui/#iso:code:3166:US *
ISO 2 letter country code (ISO 3166-1-alpha-2) - http://www.iso.org/iso/country_codes/iso_3166_code_lists/country_names_and_code_elements.htm
CDC Race codes - http://www.cdc.gov/nchs/data/dvs/Race_Ethnicity_CodeSet.pdf
|Hawaiian / Pacific Islander
|Declined to Answer
CDC Ethnicity codes - http://www.cdc.gov/nchs/data/dvs/Race_Ethnicity_CodeSet.pdf
|Hispanic or Latino
|Not Hispanic or Latino
|Declined to Answer
Full/Part Time Employment Status
User ID Types
|Nation Provider ID
|Internal Webchart User ID
Patient ID Types
|Social Security Number (US)
|Social Insurance Number (Canada)
|Internal Webchart Patient ID
The following instructions detail how to import data into an EH system using a CSV file.
To access the data import template:
- Access the left side menu by clicking the menu icon.
- Click the Control Panel tab.
- Click the Data Import tab.
- Select the appropriate from the drop-down menu. (Example displays generic data import).
- Click the Go button.
Use the template file to establish the required columns and formats for the data import file. Click on the CSV Import Specification link for details about setting up the file.
The import file must be stored as a CSV. If prompted by Excel to save as a different format, make sure the file is saved as a CSV. It is best to first test with only a few rows of data before importing an entire file. Then, if the data imports successfully, delete the rows you just loaded from the original file so that they are not duplicated. To complete a test import:
Input the following information into corresponding fields to upload the form:
- Interface: hr_feed
- Verbose: Select the Verbose checkbox to see the logging of the import. Usually only needed if there are errors.
- Delimiter: select from drop list
- Choose/Upload File: Select the file you’re importing.
- Click the Upload button.
Any errors encountered during the import display on the import page. Click the Download Failed Generic Test Data File button to view the error file. This file is useful because it only contains the records from the data file that had issues. These issues can be identified and fixed and then the failed file can be uploaded to fill in the gap.