MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 1
ONC Certification Criterion: §170.315(b)(10) – Electronic Health Information (EHI) Export
Product Version: MD4Front EMR V3.0 | CHPL ID: [_______] | Last Updated: November 07, 2025
Table of Contents
Overview | Introduction | Access Control | Single Patient Export | Population
Export | File Format & Structure | File Naming | EHI Data Elements | XML Element
Mapping | XSL Stylesheet | Security & Compliance | Performance | Versioning &
Updates | FAQ | Support
1.1 Overview
MD4Front EMR V3.0 fully supports §170.315(b)(10) by enabling authorized users to
export complete Electronic Health Information (EHI) in a standardized, machine-readable
format for:
Single patient – on-demand, no developer assistance
Entire patient population – all patients stored in the system
Exports include:
All EHI the system can produce at time of certification
Metadata, provenance, and audit logs (where available)
Human-readable HTML + machine-readable XML + XSL stylesheet
No third-party software required. All functionality is native to MD4Front EMR.
1.2 Introduction
This documentation satisfies ONC Health IT Certification Program requirements
under §170.315(b)(10)(iii) for:
MD4Front EMR V3.0 – Electronic Health Information (EHI) Export
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 2
Publicly accessible description of export format, structure, and content
Location of all required data elements
Standards used (C-CDA-inspired XML, XSLT)
Interpretation and use of exported data
Public URL: https://md4front.com/md4front-ehi-export
This page is accessible without authentication, login, or preconditions.
1.3 Access Control & Permissions
Export functionality is restricted via role-based access control (RBAC):
Permission Name: Patient Clinical Data Export
Default: Disabled for all users
Activation: Only by System Administrator
Compliance with (b)(10)(i)(C): Access is limited to a specific set of identified
users via permission.
1.4 Single Patient EHI Export
1.4.1 Step-by-Step Workflow
1. Login with valid credentials
2. Navigate to: Reports → Patient Clinical Data Export
3. Click Generate CCDA (top right)
4. In the modal:
o Schedule Type: One-time
o Patients: Search and select one patient
o Date Range: Optional
o Providers: Optional
5. Click Run Export
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 3
6. Monitor status in Export Grid
7. When status = Completed, click Download Icon
No developer assistance required. Fully user-executable per (b)(10)(i)(B).
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 4
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 5
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 6
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 7
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 8
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 9
1.5 Patient Population EHI Export
Uses the same interface as single patient export:
Select “All Patients”
Optionally filter by:
o Date range (patients seen in period)
o Provider(s)
Schedule one-time or recurring
Each patient is exported in a separate subfolder within a single ZIP archive.
1.6 Export File Format & Structure
Exports are delivered as a ZIP archive:
EHI_Export_20251107_123456.zip
└── export_001/
├── patient_1000456/
│ ├── patient_1000456.html
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 10
│ ├── patient_1000456.xml
│ └── patient_1000456.xsl
├── patient_1000457/
│ ├── patient_1000457.html
│ ├── patient_1000457.xml
│ └── patient_1000457.xsl
└── manifest.txt
1.6.1 File Types
File
Purpose
Standard
.xml
Machine-readable EHI
C-CDA R2.1 inspired
.html
Human-readable view
Rendered via XSL
.xsl
Stylesheet (format definition)
XSLT 1.0
manifest.txt
List of included patients
Plain text
1.7 File Naming Convention
patient_[MedicalRecordNumber].xml
patient_[MedicalRecordNumber].html
patient_[MedicalRecordNumber].xsl
Example: patient_1000456.xml
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 11
1.8 Included EHI Data Elements
Exports include all EHI producible at time of certification, including:
Demographics: Name, DOB, sex, race (granular), ethnicity, language,
addresses
Identifiers: MRN, Account #, Referring Provider
Encounters: ID, date, location, diagnosis, provider
Clinical: Problems, Meds, Allergies, Immunizations, Vitals, Labs, Imaging
Notes: H&P, Consults, Procedure notes, Assessments
Metadata: Document ID, Set ID, Version, Timestamp
Provenance: Author, Authenticator, Source System
Audit Logs: Where maintained
1.9 XML Element Mapping
Root: <ClinicalDocument>
<ClinicalDocument xmlns="urn:hl7-org:v3">
<realmCode code="US"/>
<typeId root="2.16.840.1.113883.1.3" extension="POCD_HD000040"/>
<templateId root="2.16.840.1.113883.10.20.22.1.1"/>
<id root="2.16.840.1.113883.19.5" extension="export_001"/>
<code code="34133-9" codeSystem="2.16.840.1.113883.6.1"
displayName="Summarization of Episode Note"/>
<title>Patient Clinical Summary</title>
<effectiveTime value="20251107123000"/>
<recordTarget>
<patientRole>
<id extension="1000456" root="2.16.840.1.113883.19.5"/>
<patient>
<name><given>John</given><family>Doe</family></name>
<administrativeGenderCode code="M"/>
<birthTime value="19700101"/>
</patient>
</patientRole>
</recordTarget>
<author>...</author>
<documentationOf>...</documentationOf>
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 12
<component><structuredBody>...</structuredBody></component>
</ClinicalDocument>
1.9.1.1 Key Sections in <structuredBody>
Section
Template ID
XPath
Problems
2.16.840.1.113883.10.20.22.2.5.1
//component/structuredBody/component
[section/templateId/@root='2.16.840.1.113883.10.20.22.2.5.1']
Medications
2.16.840.1.113883.10.20.22.2.1.1
//section[templateId/@root='2.16.840.1.113883.10.20.22.2.1.1']
Allergies
2.16.840.1.113883.10.20.22.2.6.1
//section[templateId/@root='2.16.840.1.113883.10.20.22.2.6.1']
XSL Stylesheet (Format Specification)
The .xsl file is both:
Included in every export
The official format definition
Applies XSLT 1.0 transformation to render XML → HTML.
1.10 Security & Compliance
Exports are generated server-side with full audit logging
Download links are time-limited and user-specific
PHI is encrypted in transit (HTTPS)
Compliance: HIPAA, ONC, 21st Century Cures Act
1.11 Performance & Scalability
Single patient: < 30 seconds
Population (10,000 patients): ~15–45 minutes
Background processing with status updates
MD4Front EMR - Version 3.0| All Rights Reserved | Rev 11/2025 P a g e | 13
1.12 Frequently Asked Questions
Q: Do I need developer help?
A: No. Fully self-service.
Q: Is the format standardized?
A: Yes. C-CDA-inspired XML with XSL rendering.
Q: Are audit logs included?
A: Yes, where available.
Q: Can I schedule exports?
A: Yes — one-time or recurring.