LiquidEMR Data Export Request Policy

This page describes the operational procedures and service conditions related to requesting data exports from the LiquidEMR platform.

This policy supplements the LiquidEMR Electronic Health Information (EHI) export specification and explains the process for requesting export preparation and delivery.

The technical specification for the certified EHI export format is available at:

https://www.liquidemr.com/data-export-specification/

1. Standard Electronic Health Information (EHI) Export

LiquidEMR supports export of Electronic Health Information in accordance with the ONC Health IT Certification Program.

The certified export format is provided as a structured dataset in MDJSON format as described in the published export specification.

The EHI export capability is intended to support regulatory requirements for electronic health information portability.

The export dataset includes the categories of electronic health information defined in the published specification.

The EHI export is not intended to represent a full operational database backup of the LiquidEMR platform.

2. Export Preparation Process

Export packages are generated upon request through the LiquidEMR support team.

Export preparation involves system processing to assemble the dataset, package documents and structured data, and prepare the dataset for secure delivery.

Preparation and delivery timing may vary depending on:

  • dataset size
  • document volume
  • system processing requirements
  • operational scheduling

3. Export Preparation Fees

Preparation and delivery of export datasets requires system processing resources and administrative handling.

As permitted under applicable certification regulations, LiquidEMR may apply a reasonable service fee to cover costs associated with preparing and delivering export datasets.

Export preparation costs may vary based on factors such as:

  • dataset size
  • document storage volume
  • compute resources required to generate the export
  • packaging and secure transfer requirements

4. Custom Data Export Requests

Requests for datasets beyond the scope of the certified EHI export specification may include:

  • operational reporting datasets
  • revenue cycle data extracts
  • database-level backups
  • analytics datasets
  • custom data structures or formats

Such requests are not part of the certified EHI export capability.

Custom export requests are handled separately as professional data services engagements and may require consultation and scoping to determine feasibility and preparation effort.

5. Consultation and Scoping

Organizations requesting custom exports or specialized datasets may require consultation to define the requested data scope.

Consultation sessions used to evaluate or design custom data exports are treated as professional services engagements.

6. Backup and Continuity Clarification

The LiquidEMR Electronic Health Information (EHI) export capability is designed to support regulatory data portability requirements under the ONC Health IT Certification Program.
The EHI export should not be interpreted as a full operational database backup or disaster recovery mechanism for the LiquidEMR platform.
Healthcare organizations remain responsible for maintaining their own operational policies and procedures for data retention, continuity planning, and records preservation in accordance with applicable regulatory and organizational requirements.
LiquidEMR maintains internal system backup and disaster recovery processes as part of platform operations to support platform reliability and service continuity. These internal operational backups are not provided as client-accessible export datasets.

7. Export Request Submission

Export requests may be submitted through the LiquidEMR support team.

Requests should identify whether the organization is requesting:

  • the standard EHI export as defined in the export specification
  • or a custom export request outside the scope of the certified export

This helps ensure requests are processed appropriately.

8. Platform Backup and Disaster Recovery

LiquidEMR maintains internal platform backup and disaster recovery processes for system reliability and operational continuity.

These internal system backups are part of platform operations and are not provided as client-accessible export datasets.

9. Consultation and Export Scope Clarification

The LiquidEMR Electronic Health Information (EHI) export specification published on this website defines the scope, structure, and format of the certified export capability.
Questions regarding the general structure of the export package and the categories of data included in the export are addressed by the published export specification.
Organizations seeking clarification regarding implementation-specific data elements, operational workflows, field mappings, or other detailed interpretation of the export dataset may request consultation to review the export structure and dataset scope.
Such consultation may include discussion of topics such as:

  • interpretation of export dataset contents
  • implementation-specific field mappings
  • operational datasets outside the certified export scope
  • data extraction strategies for system migration or analytics

Consultation sessions are treated as professional services engagements and may be subject to applicable consultation fees.

10. Export Specification Authority

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.