Electronic Health Information Export Format

Scribe Mutual publishes this page as a public reference for Electronic Health Information export format documentation under ONC 2015 Edition §170.315(b)(10).

Public format documentation reference

This page identifies the authoritative technical documentation URL used by Scribe Mutual EHI export packages and provides context for single-patient and patient-population export scopes.

Authoritative technical documentation

Format specification

https://app.scribemutual.com/ehi-export-format/ndjson-v1

The authoritative technical format documentation: package structure, manifest schema, NDJSON rules, resource types, coding systems, field definitions, and conformance checklist. Publicly accessible without authentication.

Data dictionary & field definitions

https://app.scribemutual.com/ehi-export-format/ndjson-v1/data-dictionary

Companion field-level reference: every data element, field name, data type, coding system, and interpretation guidance for all 18 FHIR R4 resource types and 4 supplemental file types included in the export.

Compatibility alias

https://app.scribemutual.com/public/ehi-export-format/ndjson-v1

The compatibility alias resolves to equivalent content and canonical metadata for verification workflows.

Export format and scope

Format version

Current documented format version: NDJSON v1 (revision 2026.06.24-r4), served from the public technical documentation URL above.

Single-patient EHI export

Single-patient export packages all Electronic Health Information associated with one patient in computable FHIR R4 NDJSON format for authorized workflows.

Patient-population EHI export

Patient-population export packages Electronic Health Information for all patients in the system where authorized by role and policy controls.

Data elements included

Exports include 18 FHIR R4 resource types (Patient, Encounter, Condition, Observation, MedicationRequest, AllergyIntolerance, Procedure, Immunization, DiagnosticReport, DocumentReference, CareTeam, Consent, EpisodeOfCare, List, Media, Provenance, Communication, Appointment) plus supplemental clinical notes, C-CDA XML, Direct message attachments, and raw HL7 v2 messages. Coded data uses nationally recognized terminology systems including SNOMED CT, LOINC, RxNorm, CVX, and ICD-10.

Access controls and data-safety notes

  • The public documentation page is designed to be reachable without sign-in.
  • Actual EHI export operations are permission-controlled and require authorization in the application.
  • This public page should not contain PHI. Any examples used in documentation should remain synthetic.
  • Detailed end-user screenshots and step-by-step operator instructions are planned for a later documentation phase.

How authorized users obtain EHI exports

This page documents the format reference. Export operations themselves are initiated by authorized users in the application environment.

  • Sign in with an account that has the appropriate export permissions for the requested scope.
  • Initiate either a single-patient or patient-population export from authorized application workflows.
  • Retrieve the generated export package and confirm it includes the public format reference (manifest.json and export-format-url.txt).
  • Use the canonical documentation URL on this page to validate parsing and structure expectations.

Detailed synthetic screenshots and UI step walkthroughs are planned for a later documentation update.

Versioning and maintenance

  • Current format: NDJSON v1
  • Public reference URL: https://app.scribemutual.com/ehi-export-format/ndjson-v1
  • Last updated: 2026-06-25
  • When export format behavior changes, technical documentation and public references should be updated together so external reviewers are never reading stale format guidance.