Tables


EHI Export Format For {{databaseName}}{{#schemaName}}.{{schemaName}}{{/schemaName}}

Documentation Explanation

This is the documentation for the ONC (2015) ยง170.315(b)(10) Electronic Health Information export feature in OpenEMR

The Electronic Health Information Export files are all contained inside a zip folder where each zip contains a batch of 1 or more patients. A single patient export will contain only 1 patient in the batch.

Zips are between aproximately 1MB-4GB in size which is configurable at the time of export. Each zip file is structured as follows

ehi-export-<UNIQUEID>.zip

  • /images/ - Contains any images that are used as part of the data export such as the visual pain map form. If a data element stores images in this directory it will be specified in the Table's column comments description.
  • /documents/<pid>/ - Holds the exported patient documents stored in the patient document storage system. Each patient will have their own folder where the folder name is the unique patient identifier (pid) stored in the patient_data.pid column. Document meta information will be found in the documents table stored in the documents.csv file. If the exporter chose to skip documents being exported or there are no patient documents in the system, this folder will not be present in the zip file.
  • README - The readme file that includes the links to this documentation
  • <table_name>.csv - For each table name that patient data was found to be exported for the given batch there will be a corresponding file in comma separated value (CSV) format. The definition of the data and its relationships are described in this documentation site. If a patient does not have data for a specific table there will be no CSV file for that table in the zip file.

The definitions of each of the data elements, their data types and any relevant comments on interpreting the data element can be found by reading the table definition documentation on this page or finding the specific column in the Columns page.

A visual representation of the relationships between the data elements can be found on the Relationships

Every batch zip file is self-contained and can be used to import that batch of patients into another EHR. Zip files will have duplicate data for supporting entity elements such as insurance companies, list_options, users, etc. These supporting table elements will need to have duplicate checks added when importing an entire patient population

{{#description}}

{{{description}}}

{{/description}} XML Representation for each of the EHI table elements that are being exported
Insertion Order - Useful for knowing the order of loading data into a database Deletion Order - Useful for knowing the order of purging data from a database
TABLES {{tablesAmount}}
COLUMNS {{columnsAmount}}
{{#catalog}} {{#catalog.comment}}

Catalog {{catalog.name}}

{{{catalog.comment}}}

{{/catalog.comment}} {{/catalog}} {{#schema}} {{#schema.comment}}

Schema {{schema.name}}

{{{schema.comment}}}

{{/schema.comment}} {{/schema}}

Tables

{{#displayNumRows}} {{/displayNumRows}} {{#tables}} {{#displayNumRows}} {{/displayNumRows}} {{/tables}}
Table / View Children Parents ColumnsRows Comments
{{table.name}} {{table.maxChildren}} {{table.maxParents}} {{table.columns.size}}{{table.numRows}} {{{comments}}}