LiquidEMR EHI Export Specification (ONC §170.315(b)(10))

1. Overview

LiquidEMR provides electronic health information (EHI) export in a structured, computable MDJSON format. The export includes all electronic health information maintained in the system for the requested patient(s), in the same electronic format and version state as stored at the time of export.

Exports may be generated for:

  • A single patient
  • A defined patient cohort
  • All patients (population export)

Export packages are delivered as a compressed ZIP archive.

2. Export Package Structure

Each export ZIP contains:

  • manifest.json – Export metadata and file integrity information
  • mdjson/*.json – Structured MDJSON data files
  • Optional referenced document files (if applicable)
  • checksums.sha256 – SHA-256 integrity validation file

3. Manifest File

Each export includes a manifest file containing:

  • Export identifier
  • Export timestamp
  • Data cutoff timestamp
  • MDJSON format version
  • Schema reference URL
  • Exporter software build version
  • List of included files
  • SHA-256 checksum for each file

Example structure:

{
  "format": "MDJSON",
  "mdjsonVersion": "1.3.0",
  "schemaUrl": "https://www.liquidemr.com/mdjsonschema",
  "generatedAt": "2026-03-02T08:10:05Z",
  "dataAsOf": "2026-03-02T08:10:05Z"
}

(Aligned with the LiquidEMR MDJSON export header format.)

4. MDJSON Data Structure

The MDJSON file contains structured JSON objects grouped by patient identifier.

Each patient record includes entity-based resources such as:

  • patient (demographics)
  • encounter
  • medication
  • allergy
  • diagnosis
  • procedure
  • labs
  • vital
  • history
  • billing

Each resource includes original identifiers and timestamps as maintained in the system.

Example entity pattern:

{
  "entity": "encounter",
  "EncounterID": 267150,
  "PatientID": 2,
  "Date": "2010-06-09"
}

(Data model aligns with the LiquidEMR export dataset structure.)

5. Chart Notes and Document Content

Clinical notes are exported in their original electronic storage format.

If a note is stored as HTML, it is represented either as:

  • A file reference within the export package
  • Base64-encoded content within the MDJSON structure

Example metadata:

{
  "NoteId": "6048281",
  "CreateAt": "6/30/2022 2:37:36 PM",
  "Date": "2021-09-29",
  "FileName": "Test0517.html",
  "PatientId": "1"
}

All versions of notes are included, each identified by a unique NoteId and CreateAt timestamp.

No transformation or normalization of the original note content is performed. The export preserves the original stored content.

6. Data Integrity Verification

Each export includes SHA-256 checksums to allow the recipient to validate file integrity.

The checksum file allows verification that exported files were not altered during transfer.

7. Format Documentation

The MDJSON schema is publicly documented at:

https://www.liquidemr.com/mdjson-schema

The schema version is included in each export header.

8. Export Specification Authority

The LiquidEMR Electronic Health Information (EHI) export specification published on this page defines the scope and structure of the certified export capability.

The documentation provided here represents the authoritative description of the data elements, formats, and organization included in the LiquidEMR EHI export.

Questions regarding specific fields, workflows, or implementation details may vary depending on system configuration and use. The published export specification should be used as the reference for determining the contents of the export dataset.

LiquidEMR does not provide field-by-field confirmation of export contents outside the published export specification.

Requests for interpretation, clarification, or discussion of export dataset contents beyond the published export specification may require consultation to review the export structure and implementation context.

Consultation related to export dataset interpretation, system migration planning, or detailed data mapping may be treated as a professional services engagement as described in the LiquidEMR Export Request Policy.

9. Export Request Information

LiquidEMR provides Electronic Health Information (EHI) export in accordance with ONC certification requirements.

Requests for export preparation, delivery procedures, service fees, and custom data extracts are governed by the LiquidEMR Export Request Policy.

For operational details regarding export requests, preparation timelines, service fees, and custom export services, please see:

LiquidEMR Export Request Policy

https://www.liquidemr.com/data-export-request-policy/

Operational policies for export requests, preparation, and delivery are described in the LiquidEMR Export Request Policy.