Tables


EHI Export Format For openemr.openemr

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

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 128
COLUMNS 2524

Tables

Table / View Children Parents Columns Comments
patient_tracker 1 4 11

Patient appointment events that occur in the system. Used in the patient flowboard and for patient data reporting

groups 17 1 3

Represent groups of users in the system

form_functional_cognitive_status 0 1 12

Holds information about assessments, evaluations, or observations of a patient’s functional and cognitive abilities.

onsite_messages 0 0 7

Patient secure chat messages to and from clinical staff for real time communication

form_eye_mag_orders 0 1 10

This table is used to track eye-related orders, such as eyeglass or contact lens orders.

questionnaire_response 1 5 20

Holds questionnaire results for a patient

form_track_anything 1 2 4

Clinical note form that allows clinicians to provide point in time and longitudinal tracking of any data element they configure

form_eye_external 0 1 30

This table is used for recording external eye examination findings.

claims 0 3 13

Insurance Billing Claims - Used for tracking and submission of billing claims to payers

procedure_answers 0 2 6

Answers to questions that are requested to be answered for a given procedure by a procedure provider (lab, or other provider)

shared_attributes 0 4 6

Dynamic patient, encounter, and transaction table properties created via LBF/LBT mechanism

insurance_companies 5 1 15

Insurance company

lists 4 11 36

Patient issues list including allergies, medical problems, medications, medical devices, surgeries, and dental issues. Type of issue is in the type column.

form_care_plan 0 1 20

Patient Clinical Care Plans

facility 9 0 39

The facility table holds all of the facilities that provide healthcare in the EMR. It contains the primary billing location and other service locations/organizations that are not insurance companies tracked inside the EMR

document_templates 0 1 2

Digital document templates that are assigned to patients

form_phq9 0 4 4

Encounter form that holds patient results for the PHQ9 assessment

form_eye_hpi 0 1 35

This table stores the history of present illness (HPI) information related to eye conditions.

amendments_history 0 4 5

Contains clinicinan comments regarding an amendment request

immunizations 1 13 30

Patient Immunizations

procedure_order_code 0 2 16

Holds individual procedure / labs ordered from the procedure_type table for a given procedure order. It contains also the individual diagnosis code that is related to the ordered procedure

rule_patient_data 0 3 7

Patient Reminders that the Clinical Decision Support system is configured to run for this specific patient.

prescriptions 0 7 48

Internal and External prescription information

form_note 0 2 2

Work/School note written by a provider for a patient to provide documentation of their medical condition to their work or school

users 62 2 64

Contains actors in the system that are not patients. This includes providers, employees, and external organizations/contacts records as well as system processes. This does not include API actors

form_sdoh 0 4 4

Encounter form that holds results for the Social Determinants of Health Screening Tool

patient_access_onsite 0 1 8

Holds patient portal onsite credentials, username information and login meta information

esign_signatures 0 1 9

Holds the digital author signature records for encounters and individual charted forms in the system.

pro_assessments 0 2 12

Contains Patient Reported Outcome assessment results as delivered via the PROMIS assessment delivery system

layout_options 3 2 21

Holds the layout settings for a specific dynamic field in the system

form_CAMOS_category 0 3 3

Note categories used in the CAMOS note generator

immunization_observation 0 3 12

Individual observations for a specific immunization

lbt_data 0 2 3

Dynamic Field values that an installation can use to extend the data stored in the transactions table

form_ros 0 1 142

Review of Systems observations of the patient. Providers can use this form or the form_reviewofs

form_CAMOS_item 0 3 4

CAMOS patient chart templates for a single item inside a CAMOS subcategory

form_groups_encounter 1 8 24

Represents the information related to a group of patient’s visit to a healthcare provider. This is different than an appointment as this table tracks the actual service of care for a therapy group

form_transfer_summary 0 2 2

Records transfer summary of care and is an alternative to recording referrals in the transactions table

clinical_plans 0 1 7

The Clinical Quality Measures that are being applied to a specific patient to track. This is used in the clinical reminders system

ar_session 1 6 17

Accounts Receivable overall payment made towards a patient invoice/claim and is the main table that holds the patient payments ledger

form_eye_mag_dispense 0 1 55

Stores information related to eye prescriptions and dispensing for both the left (OS) and right (OD) eyes

drug_sales 0 3 19

Product/Drug sales to Patients

drugs 2 0 24

Contains information about drugs that are dispensed/prescribed to patients. Also holds product inventory information if providers are internally managing their own drugs/medical supplies

billing 0 7 30

Patient billing records for billing codes - Used for Claims Processing

form_bronchitis 0 3 89

Records symptoms, diagnosis, and recommended treatments for bronchitis in a patient

form_prior_auth 0 2 2

Patient Prior Authorization records

onsite_signatures 0 2 16

Patient portal digital signatures used for patient documents and anywhere else a signature is required in the portal

procedure_questions 1 2 11

Information/questions that should be answered for a given procedure as requested by the procedure service provider. Created as part of the procedure compendium import/creation process.

extended_log 0 1 7

Holds the disclosures of EHI made to third parties for a given patient

form_eye_vitals 0 1 27

This table is used for recording vital signs and measurements related to the eye.

eligibility_verification 1 1 8

Insurance Eligibility Verification Tracking

external_encounters 0 1 7

Holds data on encounters that exist outside of this EMR that were in a patient CCDA import

form_eye_base 0 1 7

Eye form base container record that all other eye forms are connected to

history_data 0 2 91

Contains patient eating,sleeping,drinking,drug habits as well as other patient health history information

insurance_type_codes 1 0 3

Contains a list of different insurance types or categories that an insurance company is related to. This type includes both public and private payer types

therapy_groups_participant_attendance 0 3 4

Track patient attendance to a therapy group session as contained in the Used by the form_group_attendance table

patient_data 86 5 127

Main patient record that contains patient demographic information

form_misc_billing_options 0 1 33

Contains encounter claims billing options that modifies the claims submitted for this encounter

openemr_postcalendar_events 2 10 39

Holds records for Patient Appointment/Calendar information

amendments 1 5 10

Holds requests to amend health care information typically initiated by the patient or an insurance company

insurance_data 1 2 34

Patient Insurance information

patient_history 0 2 14

Contains previous historical entries of the patient’s care team (providers and facilities) as well as patient previous name information

form_eye_neuro 0 1 81

This table includes numerous fields for recording the results of neurological tests and assessments, such as near and distant vision, motility measurements, comments, and various neurological parameters.

layout_group_properties 2 0 20

Record of the grouped fields used in dynamic layout based forms (LBF)

form_track_anything_type 0 0 5

Represents the category grouping / track of the data element being tracked via the track_anything form

form_observation 0 1 25

Used for recording observations related to patients during medical encounters

form_eye_refraction 0 1 65

This table is used for recording eye refraction details, including sphere, cylinder, axis, prism, and base measurements.

form_physical_exam_diagnoses 0 0 0

Physical Exam Diagnosis for a physical exam that was conducted

form_questionnaire_assessments 0 5 16

Holds questionnaires results for a patient entered in by a provider as a patient charted form

procedure_order 3 13 31

A procedure order is an encounter form within a patient visit representing an order for one or more procedures and its associated report/results for the procedure. Orders can be for either internal or external procedure providers

patient_tracker_element 0 4 6

Used for tracking individual state changes in the appointment/encounter of a patient

lists_medication 0 2 8

Holds additional data about patient medications.

procedure_providers 2 0 23

This table holds both internal and external laboratories as well as other organizations that provide lab testing, results, and other procedures that can be ordered by a provider

form_dictation 0 1 9

Patient chart note that holds notes created from a provider’s speech dictation software

onsite_documents 0 4 21

Digital documents that have been assigned to a patient from a document_template that the patient has saved or submitted for review by clinical staff

form_clinical_instructions 0 1 7

Patient clinical instructions chart note

form_eye_biometrics 0 1 18

This table stores biometric data related to the eye, including axial length, pupil diameter, and other measurements.

form_eye_antseg 0 1 39

This table is used to store data related to anterior segment eye examinations, which typically include details about the front portion of the eye, such as the cornea, lens, iris, and pupil.

form_soap 0 1 11

Holds Subjective, Objective, Assessment, and Plan (SOAP) notes

procedure_result 0 2 16

The table stores the actual results and findings from medical procedures and tests, such as laboratory tests, radiology reports, diagnostic imaging, and other clinical tests.

form_vital_details 0 3 4

Record of a specific vital sign measurement, including its interpretation, and reason of the measurement

pnotes 0 7 16

Patient Messages about the healthcare treatment of the patient

rule_action_item 4 2 5

Patient Reminders configuration for Clinical Decision Support individual rule settings

pharmacies 2 0 6

Contains records of pharmacies that a patient uses, or that providers interact with

form_eye_acuity 0 1 30

This table is related to recording visual acuity measurements for different eye conditions.

form_eye_locking 0 1 9

Used for tracking the editing status of a form and whether it is currently being edited by a user

form_encounter 14 1 35

Represents the information related to a patient’s visit to a healthcare provider. This is different than an appointment as this table tracks the actual service of care

form_ankleinjury 0 3 24

Represents a provider’s evaluation of an ankle injury including x-ray information, diagnosis, and recommended treatments

form_group_attendance 1 5 8

Group encounter form for tracking the attendance of therapy participants to a group session encounter

onsite_mail 0 0 22

Patient asynchronous messages to and from clinical staff

ar_activity 0 4 22

Accounts Receivable item entries in invoice/claim activity

medex_recalls 0 3 8

Tracks Patient Recalls. Recalls are when a patient should be reached out to or contacted for a healthcare followup.

patient_reminders 0 5 14

Patient Reminders generated from the clinical decision support engine that are sent via a communication medium to the patient

form_treatment_plan 0 4 4

Patient treatment plan form

form_eye_ros 0 1 15

This table stores review of systems (ROS) information related to various aspects of the eye and its associated systems.

issue_types 1 0 10

Contains the list of issue types that medical health issue can be.

form_track_anything_results 0 1 7
therapy_groups_counselors 0 2 2

Contains the relationships between the counselors in a therapy group and the group

list_options 46 0 16

Contains lists of unique value sets that a record’s property can be. Individual values/options in the list may be linked to a specific codesystem

form_reviewofs 0 1 115

Review of Systems observations of the patient. Providers can use this form or the form_ros.

procedure_report 1 3 13

Procedure order overall report container for an ordered procedure result in procedure_order_codes which represents findings, conclusions, and recommendations for the procedure order

issue_encounter 0 3 4

Links patient medical issues in the lists table with patient service encounters

form_eye_postseg 0 1 25

This table is used for storing data related to posterior segment eye examinations, which typically involve the back of the eye, including the retina, optic disc, macula, and blood vessels.

documents 2 4 33

Stores all of the digital documents that are connected to a patient.

transactions 2 1 7

Represents patient referrals, and transactional records for billing, legal, and requests from the patient or their physician

form_physical_exam 0 1 3

Physical Examination clinical note

notes 0 2 6

Clinical notes and comments for individual patient documents

form_clinical_notes 0 3 18

Patient clinical notes with support for USCDI V1 standardized note types

procedure_type 2 1 20

This table holds a compendium of possible procedures and labs that can be ordered by the procedure ordering system within OpenEMR

questionnaire_repository 2 0 17

Holds questionnaires that providers or patients fill out for healthcare information collection and/or assessment.

onsite_portal_activity 0 1 14

Patient portal activity (document submission, and other activities) that requires review before they are accepted into the patient chart

form_eye_mag_wearing 0 1 41

This table is used to record information related to wearing eyeglasses or contact lenses.

form_gad7 0 4 4

Encounter form that holds patient results for the GAD7 assessment

therapy_groups_participants 0 2 6

Connects the patient participants to a therapy group

therapy_groups 6 0 10

Contains all of the therapy groups that exist in the system

form_CAMOS_subcategory 0 1 2

CAMOS patient chart sub categories inside a single category

voids 0 3 12

Tracks a voided receipt or checkout for a patient

openemr_postcalendar_categories 3 0 20

Contains the types / categories a patient scheduled appointment can be

form_taskman 0 1 13

This table holds eye related tasks for providing care to the patient.

form_CAMOS 0 1 5

Computer Aided Medical Ordering System notes that are part of a patient’s chart

external_procedures 0 2 9

Holds data on external procedures that exist outside of this EMR that were in a patient CCDA import

form_aftercare_plan 0 3 18

Table for chart notes on patient aftercare plans, including Acute Intoxication/Withdrawal, Emotional/Behavioral Conditions and Complications, and Relapse Potential for patients’ care plans.

forms 13 6 14

Patient chart forms that are connected to a patient’s encounter visit. Serves as the base record containing all of the common form encounter properties where each sub-type form has data records contained in a table that is named CONCAT(‘form_’,formdir)

form_painmap 0 4 5

Patient pain map form. Pain map image for mapping this form is stored in the EHI zip export at images/painmap.png

benefit_eligibility 0 1 18

Holds the eligible patient benefits for a specific insurance as received from an eligibility verification

form_clinic_note 0 1 1

Holds patient history, provider examination conducted, patient treatment plan, and follow up status

form_eye_mag_impplan 0 1 11

Stores implementation plans for eye-related activities.

form_vitals 1 3 29

Records of patient vital sign assessment

lbf_data 0 2 3

Dynamic Field values that are part of the following forms: Demographics, Facility Specific User Information, History Form, and custom dynamically generated encounter forms