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:

  1. A single patient
  2. A defined patient cohort
  3. All patients (population export)

Export packages are delivered as a compressed ZIP archive.

  1. Export Package Structure

Each export ZIP contains:

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

Each export includes a manifest file containing:

  1. Export identifier
  2. Export timestamp
  3. Data cutoff timestamp
  4. MDJSON format version
  5. Schema reference URL
  6. Exporter software build version
  7. List of included files
  8. 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 your actual header )

  1. MDJSON Data Structure

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

Each patient record includes entity-based resources such as:

  1. patient (demographics)
  2. encounter
  3. medication
  4. allergy
  5. diagnosis
  6. procedure
  7. labs
  8. vital
  9. history
  10. 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 uploaded export )

  1. 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:

  1. A file reference within the export package, or
  2. Base64-encoded content within the MDJSON structure

Example metadata (from your note file ):

{

“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 unique NoteId and CreateAt timestamp.

No transformation or normalization of the original note content is performed. We display the latest CreateAt, while preserve older version of CreateAt within our system.

  1. 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.

  1. Format Documentation

The MDJSON schema is publicly documented at:

https://www.liquidemr.com/mdjsonschema

The schema version is included in each export header.