Patient Information Export

Air provides a dedicated Electronic Health Information (EHI) Export feature that lets a practice export a patient’s electronic health information in a computable, standards-based format, as required by ONC §170.315(b)(10). This page is both the user guide for that feature and the Export Format Documentation a recipient needs to read, parse, and computably consume the exported data without contacting Commure (d/b/a Athelas). The feature supports two export modes defined by the criterion:

Single-patient EHI export — §170.315(b)(10)(i)(A): export the complete EHI for one patient.
Patient-population EHI export — §170.315(b)(10)(i)(B): export the EHI for all patients in the practice.

Stable public URL for this page (embedded in every export): https://trainings.air.athelas.com/air_developer/patient_information_export/patient_information_exportAir emits two file types per export:

claims.csv — billing and encounter-level claim data (UTF-8 CSV)
*.xml — clinical content as a HL7 Consolidated CDA R2.1 (C-CDA) Continuity of Care Document (UTF-8 XML)

Permissions

The EHI Export feature is restricted to Providers and Admins:

Single-patient export (providers and admins) — runs in-app and is available to any provider or admin with access to the patient whose record is being exported.
Patient-population (site-wide) export (admins) — requested by an account Admin on behalf of the practice.

Access is enforced by Air’s role-based access controls (ONC §170.315(d)(1)). Every export action is recorded in the tamper-resistant audit log (§170.315(d)(2)). See the Mandatory Disclosure page for the full list of certified capabilities.

Single-patient EHI export

Air offers two self-service single-patient exports from the application: a claims CSV (billing/encounter data) and a clinical C-CDA XML (USCDI clinical data). Together they make up the complete single-patient EHI export. The detailed schema for each file is documented under Data structure documentation.

Export claims for a single patient (CSV)

The Claims page export produces a claims.csv file containing every claim row visible after the filter is applied. To export claims for one patient:

Open the Claims page from the left navigation.
Click Filter at the top of the page.
Filter by Patient and select the patient whose claims you want to export.
Apply the filter — the table now shows only that patient’s claims.
Click Export to download claims.csv.

What’s included: every claim row for the selected patient — claim/encounter identifiers, status, provider, facility, date of service, payers, charges, payments, adjustments, and balances. See the Claims CSV column reference.
Output format: UTF-8 CSV (claims.csv).
File location: downloads through your browser to its default Downloads folder as claims.csv.

Note: The exported CSV contains exactly the columns and rows that are currently visible after filtering. Apply any additional column or date filters before exporting if you need a narrower slice.

Export the clinical record for a single patient (C-CDA XML)

The C-CDA download produces a single .xml file conforming to the HL7 Consolidated CDA R2.1 Continuity of Care Document (CCD) standard — covering allergies, medications, problems, encounters, immunizations, lab results, vital signs, social history, procedures, and the other USCDI v3 sections. To download a patient’s C-CDA:

Open the Inbox tab from the left navigation.
Select the C-CDA tab.
Search by patient name in the search bar.
Click into the matching patient.
Click Download to save the C-CDA .xml file.

What’s included: the patient’s USCDI clinical data — demographics plus the clinical sections listed in Export contents.
Output format: HL7 C-CDA R2.1 UTF-8 XML (one .xml file per patient).
File location: downloads through your browser to its default Downloads folder as a .xml file.

Note: Clinical sections with no recorded data for the patient are still present in the file, emitted with nullFlavor="NI" so a recipient can detect their presence. See Considerations & error conditions.

Patient-population (site-wide) EHI export

For an EHI export covering all patients in your practice (population-level export per §170.315(b)(10)(i)(B)), an account Admin requests the export from Commure (d/b/a Athelas) support.

How to request a population export

Email: support@athelas.comInclude your practice name and the date range you need.

Processing details:

Support compiles the export and delivers it as a single encrypted ZIP archive via a secure, expiring download link sent to the requesting Admin.
Typical turnaround is within 5 business days of the request.
The secure download link expires after a limited period; request a new link from support if it lapses before you download the archive.

Package structure: The archive bundles the same file formats as the single-patient export — one C-CDA .xml per patient plus a practice-wide claims.csv. The archive is named EHI_Export_YYYYMMDD.zip (where YYYYMMDD is the export date), and each patient’s C-CDA file is named by the patient’s first and last name:

EHI_Export_YYYYMMDD.zip
├── claims.csv              # all claims across the patient population (same schema as the single-patient CSV)
├── Jane Doe.xml            # one C-CDA Continuity of Care Document per patient, named "First Last.xml"
├── John Smith.xml
└── ...

Output formats: identical to the single-patient export — UTF-8 claims.csv and HL7 C-CDA R2.1 UTF-8 XML. Both are fully specified under Data structure documentation.

Export contents — EHI data classes & supported formats

The export carries the EHI/USCDI data classes below. Each class is identified by where it appears in the export so a recipient can confirm coverage.

EHI / USCDI data class	Where it appears in the export	Format
Patient demographics	C-CDA `recordTarget` header (name, DOB, sex, race, ethnicity, language, address, telecom, marital status)	C-CDA XML
Allergies & intolerances	C-CDA Allergies & Intolerances section	C-CDA XML
Medications	C-CDA Medications section	C-CDA XML
Problems	C-CDA Problem List section	C-CDA XML
Encounters	C-CDA Encounters section + `claims.csv` (Date of Service)	C-CDA XML + CSV
Immunizations	C-CDA Immunizations section	C-CDA XML
Laboratory (results & tests)	C-CDA Results section	C-CDA XML
Vital signs	C-CDA Vital Signs section	C-CDA XML
Smoking status / social history	C-CDA Social History section	C-CDA XML
Procedures	C-CDA Procedures section + `claims.csv` (CPT)	C-CDA XML + CSV
Goals	C-CDA Goals section	C-CDA XML
Health concerns	C-CDA Health Concerns section	C-CDA XML
Assessment & plan of treatment	C-CDA Assessments + Plan of Treatment sections	C-CDA XML
Care team members	C-CDA `documentationOf` / `serviceEvent` + author/authenticator	C-CDA XML
Functional & mental status	C-CDA Functional Status + Mental Status sections	C-CDA XML
Medical equipment / implantable device (UDI)	C-CDA Medical Equipment section	C-CDA XML
Reason for referral	C-CDA Reason for Referral section	C-CDA XML
Provenance (author/custodian)	C-CDA header (`author`, `custodian`, `legalAuthenticator`)	C-CDA XML
Billing / claim & encounter data	`claims.csv` (charges, payments, adjustments, balance, payer)	CSV

Supported file formats:

claims.csv — UTF-8 comma-separated values.
C-CDA .xml — HL7 Consolidated CDA R2.1 Continuity of Care Document (UTF-8 XML), aligned to the USCDI v3 data classes.

Data structure documentation

This section is the data dictionary and schema for each exported file — sufficient for a recipient to interpret the data without further reference.

Claims CSV (`claims.csv`)

Property	Value
File extension	`.csv`
MIME type	`text/csv`
Encoding	UTF-8
Delimiter	Comma (`,`)
Quote char	Double-quote (`"`) around values containing commas or quotes
Line ending	LF (`\n`)
Header row	Yes — the first row is the column header
One row per	Claim

Column reference (in order):

Column	Type	Description
Claim ID	Integer	Unique identifier for the claim within Air.
Status	String	Current claim status (e.g., `Self pay: Unpaid`, `Submitted`, `Paid`, `Denied`).
Stage	String	Workflow stage of the claim (e.g., `Patient`, `Insurance`, `Closed`).
Patient	String	Patient full name as `First Last`.
Provider	String	Rendering provider full name.
Facility	String	Name of the facility / place of service.
Facility ID	Integer	Internal facility identifier.
Date of Service	Date (`MM/DD/YYYY`)	The date the service was rendered.
Insurances	String	Pipe-separated list of payers on the claim. `UNRECOGNIZED INSURANCE` indicates a self-pay or unmapped payer.
Charges	Decimal	Total billed charges in USD.
Allowed Amount	Decimal	Total allowed amount per the remittance.
Ins. Paid	Decimal	Total amount paid by insurance(s).
PR Paid	Decimal	Total patient responsibility paid.
Total Adj.	Decimal	Total adjustments (contractual write-offs, courtesy adjustments, etc.).
Balance	Decimal	Remaining outstanding balance on the claim.
Tags	String	Comma-separated list of tags. `-` denotes no tags.
Assignees	String	Comma-separated list of users assigned to the claim.

Example row:

Claim ID,Status,Stage,Patient,Provider,Facility,Facility ID,Date of Service,Insurances,Charges,Allowed Amount,Ins. Paid,PR Paid,Total Adj.,Balance,Tags,Assignees
5818970,Self pay: Unpaid,Patient,Jane Doe,Dr. Sample Provider,MAIN OFFICE,2349,06/04/2048,UNRECOGNIZED INSURANCE,0.0,0.0,0.0,0.0,0.0,0.0,-,Casey Admin

Parsing notes:

Decimal values use . as the decimal separator and never include a thousands separator or a currency symbol.
Dates are always in MM/DD/YYYY format in the local time zone of the practice.
Empty string fields appear as an empty value between two commas; - is used specifically for the Tags column when no tags are present.
The Insurances column can contain multiple payers separated by | (space-pipe-space).

Clinical C-CDA XML

The clinical export is a HL7 Consolidated CDA R2.1 Continuity of Care Document (CCD) — the same format used for B.1 (Transitions of Care) and B.6 (Data Export). It is a single XML file per patient.

Property	Value
File extension	`.xml`
MIME type	`application/xml` (or `text/xml`)
Encoding	UTF-8
Standard	HL7 CDA Release 2
Implementation guide	C-CDA R2.1 (Consolidated CDA Release 2.1, 2015 Edition)
Document type	Continuity of Care Document (CCD)
US Realm Header templateId	`2.16.840.1.113883.10.20.22.1.1` (ext `2015-08-01`)
CCD templateId	`2.16.840.1.113883.10.20.22.1.2` (ext `2015-08-01`)
Document code	LOINC `34133-9` — Summarization of Episode Note

Root element & namespaces:

<ClinicalDocument
    xmlns="urn:hl7-org:v3"
    xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
    xmlns:voc="urn:hl7-org:v3/voc"
    xmlns:sdtc="urn:hl7-org:sdtc">
  ...
</ClinicalDocument>

Top-level header elements (present in every export):

recordTarget — patient demographics (name, DOB, gender, race, ethnicity, address, telecom, language, marital status)
author — software/device that produced the document
dataEnterer — user who entered the data
custodian — organization responsible for the source document
informationRecipient — intended recipient
legalAuthenticator — provider attesting to the document
authenticator — additional attestation
documentationOf / serviceEvent — care team and effective time range
componentOf / encompassingEncounter — encounter context

Sections included in the structured body: Each section is represented as a <component><section>...</section></component> block. Sections that are not applicable to the patient are emitted with nullFlavor="NI" (“No information”) so recipients can still detect their presence.

Section	LOINC code	Section templateId
Allergies & Intolerances	`48765-2`	`2.16.840.1.113883.10.20.22.2.6.1` (ext `2015-08-01`)
Medications	`10160-0`	`2.16.840.1.113883.10.20.22.2.1.1` (ext `2014-06-09`)
Problem List	`11450-4`	`2.16.840.1.113883.10.20.22.2.5.1` (ext `2015-08-01`)
Encounters	`46240-8`	`2.16.840.1.113883.10.20.22.2.22.1` (ext `2015-08-01`)
Immunizations	`11369-6`	`2.16.840.1.113883.10.20.22.2.2.1` (ext `2014-06-09`)
Results (Lab)	`30954-2`	`2.16.840.1.113883.10.20.22.2.3.1` (ext `2015-08-01`)
Vital Signs	`8716-3`	`2.16.840.1.113883.10.20.22.2.4.1` (ext `2015-08-01`)
Social History	`29762-2`	`2.16.840.1.113883.10.20.22.2.17` (ext `2015-08-01`)
Procedures	`47519-4`	`2.16.840.1.113883.10.20.22.2.7.1` (ext `2014-06-09`)
Functional Status	`47420-5`	`2.16.840.1.113883.10.20.22.2.14` (ext `2014-06-09`)
Assessments	`51848-0`	`2.16.840.1.113883.10.20.22.2.8`
Plan of Treatment	`18776-5`	`2.16.840.1.113883.10.20.22.2.10` (ext `2014-06-09`)
Goals	`61146-7`	`2.16.840.1.113883.10.20.22.2.60`
Health Concerns	`75310-3`	`2.16.840.1.113883.10.20.22.2.58` (ext `2015-08-01`)
Reason for Referral	`42349-1`	`1.3.6.1.4.1.19376.1.5.3.1.3.1` (ext `2014-06-09`)
Mental Status	`10190-7`	`2.16.840.1.113883.10.20.22.2.56` (ext `2015-08-01`)
Medical Equipment	`46264-8`	`2.16.840.1.113883.10.20.22.2.23` (ext `2014-06-09`)

Vocabularies / code systems referenced:

Code system	OID	Used in
LOINC	`2.16.840.1.113883.6.1`	Section codes, lab observations, document type
SNOMED CT	`2.16.840.1.113883.6.96`	Problems, allergies, reactions, findings
RxNorm	`2.16.840.1.113883.6.88`	Medication codes
CPT-4	`2.16.840.1.113883.6.12`	Encounter and procedure codes
NUCC Provider Taxonomy	`2.16.840.1.113883.6.101`	Provider specialty
CDC Race & Ethnicity	`2.16.840.1.113883.6.238`	Patient race / ethnicity
HL7 ActCode	`2.16.840.1.113883.5.4`	Severity, encounter codes, assertions
HL7 ActClass / Concern	`2.16.840.1.113883.5.6`	Concern act class
NCI Thesaurus	`2.16.840.1.113883.3.26.1.1`	Route of administration

Section entry pattern (example — Allergy): Each clinical entry follows the C-CDA “Concern Act → Observation → (optional) Reaction / Severity Observation” nesting:

<entry typeCode="DRIV">
  <act classCode="ACT" moodCode="EVN">
    <!-- Allergy Concern Act (V3) -->
    <templateId root="2.16.840.1.113883.10.20.22.4.30" extension="2015-08-01"/>
    <id root="86495477-d7d5-55a7-9812-f75bfcc4266b"/>
    <code code="CONC" codeSystem="2.16.840.1.113883.5.6"/>
    <statusCode code="active"/>
    <effectiveTime><low value="19850620"/></effectiveTime>
    <entryRelationship typeCode="SUBJ">
      <observation classCode="OBS" moodCode="EVN">
        <!-- Allergy observation (V2) -->
        <templateId root="2.16.840.1.113883.10.20.22.4.7" extension="2014-06-09"/>
        <value xsi:type="CD" code="414285001" displayName="Allergy to food"
               codeSystem="2.16.840.1.113883.6.96" codeSystemName="SNOMED-CT"/>
        <participant typeCode="CSM">
          <participantRole classCode="MANU">
            <playingEntity classCode="MMAT">
              <code code="256349002" displayName="Peanut"
                    codeSystem="2.16.840.1.113883.6.96"/>
            </playingEntity>
          </participantRole>
        </participant>
        <!-- nested reaction + severity observations omitted for brevity -->
      </observation>
    </entryRelationship>
  </act>
</entry>

Parsing notes:

Every entry is identified by a UUID in <id root="...">. UUIDs are stable across re-exports of the same record.
Dates use the HL7 v3 TS format: YYYYMMDD or YYYYMMDDHHMMSS±ZZZZ.
Coded values appear as <value xsi:type="CD" code="..." codeSystem="..." displayName="..."/>.
Narrative text in each section’s <text> element is the human-readable rendering and references the structured entries via <reference value="#id"/>.
Sections with nullFlavor="NI" contain no structured entries — only a <text> placeholder such as "No Lab Test required. No Lab results.". Treat these as “data not available” rather than “data absent.”

Recommended validation tools:

HL7 C-CDA R2.1 IG
ONC C-CDA Scorecard — validates structure, templates, and vocabulary bindings

Considerations & error conditions

Condition	What to expect
Filtered CSV scope	`claims.csv` contains exactly the columns and rows visible after filtering. Clear or adjust filters before exporting if you need a different slice.
Self-pay / unmapped payers	Claims with no recognized payer show `UNRECOGNIZED INSURANCE` in the `Insurances` column.
Empty clinical sections	C-CDA sections with no data for the patient are present but carry `nullFlavor="NI"` — interpret as “data not available,” not “section omitted.”
Empty export	If no records match the current filter (single-patient) or date range (population), the export contains headers/structure but no data rows. Verify your filters and date range.
Browser download blocked	Single-patient downloads open through your browser. If nothing downloads, allow pop-ups/downloads for the Air domain and retry.
Population export turnaround	Population exports are not instantaneous — they are compiled by support and delivered via a secure link (see Patient-population export).
Secure link expiry	The population-export download link expires after a limited period. Request a fresh link from support if it lapses before you download.
Large population exports	Very large practices may receive the export split into multiple batches; follow the instructions in the delivery email to assemble them.

FAQ

Who can run an EHI export?

The EHI Export feature is limited to Providers and Admins. Single-patient exports can be run in-app by any provider or admin with access to the patient. The patient-population (site-wide) export is requested by an account Admin through support. Every export is recorded in the audit log.

What's the difference between the claims.csv and the C-CDA .xml file?

claims.csv holds billing and encounter-level data — claim status, providers, facilities, dates of service, payers, charges, payments, adjustments, and balances.
C-CDA .xml holds the clinical record — demographics plus allergies, medications, problems, encounters, immunizations, lab results, vital signs, social history, procedures, and the other USCDI v3 data classes.

Together they form the complete EHI export for a patient.

How do I export all of my patients at once?

Population (site-wide) exports are requested by an Admin emailing support@athelas.com with your practice name and date range. Within 5 business days, support returns an encrypted ZIP (EHI_Export_YYYYMMDD.zip) via a secure download link, containing a practice-wide claims.csv and one C-CDA .xml per patient (named First Last.xml). See Patient-population (site-wide) EHI export.

How do I validate the C-CDA file?

Use the ONC C-CDA Scorecard to validate structure, templates, and vocabulary bindings, and the HL7 C-CDA R2.1 Implementation Guide as the authoritative reference. The file is a HL7 C-CDA R2.1 Continuity of Care Document encoded in UTF-8 XML.

Are the export files USCDI-compliant?

Yes. The clinical C-CDA export is aligned to the USCDI v3 data classes. The Export contents table identifies each EHI/USCDI data class and where it appears in the export.

Documentation Index

​Permissions

​Single-patient EHI export

​ Export claims for a single patient (CSV)

​ Export the clinical record for a single patient (C-CDA XML)

​Patient-population (site-wide) EHI export

​ How to request a population export

​Export contents — EHI data classes & supported formats

​Data structure documentation

​ Claims CSV (claims.csv)

​ Clinical C-CDA XML

​Considerations & error conditions

​FAQ

Permissions

Single-patient EHI export

Export claims for a single patient (CSV)

Export the clinical record for a single patient (C-CDA XML)

Patient-population (site-wide) EHI export

How to request a population export

Export contents — EHI data classes & supported formats

Data structure documentation

Claims CSV (`claims.csv`)

Clinical C-CDA XML

Considerations & error conditions

FAQ