> ## Documentation Index
> Fetch the complete documentation index at: https://docs.athelas.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Patient Information Export

> EHI Export feature and export format documentation for ONC §170.315(b)(10) Electronic Health Information (EHI) Export — covers single-patient and patient-population exports produced by Air, their contents (including patient attachments), data dictionary, permissions, and implementation considerations.

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.

<Info>
  **Stable public URL for this page** (embedded in every export):
  `https://trainings.air.athelas.com/air_developer/patient_information_export/patient_information_export`

  Air emits the following across its exports:

  * **`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)
  * **`attachment/`** — the documents uploaded to a patient's chart (faxes, scans, PDFs, images, etc.), exported in their original file formats inside the export ZIP
</Info>

## 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**](/air_developer/onc_certification/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 download** (USCDI clinical data). The C-CDA download is delivered as a **ZIP archive** containing the patient's C-CDA `.xml` plus an `attachment/` folder with the documents uploaded to their chart. Together these make up the complete single-patient EHI export. The detailed schema for each file is documented under [Data structure documentation](#data-structure-documentation).

### <Icon icon="file-csv" iconType="duotone" color="#F9345F" size={23} />  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:**

1. Open the **Claims** page from the left navigation.
2. Click **Filter** at the top of the page.
3. Filter by **Patient** and select the patient whose claims you want to export.
4. Apply the filter — the table now shows only that patient's claims.
5. 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](#claims-csv-claims-csv).
* **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.

### <Icon icon="file-code" iconType="duotone" color="#F9345F" size={23} />  Export the clinical record for a single patient (C-CDA XML + attachments)

The C-CDA download produces a **ZIP archive** containing 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 — plus an `attachment/` folder holding the documents uploaded to the patient's chart in their original file formats.

**To download a patient's C-CDA:**

1. Open the **Inbox** tab from the left navigation.
2. Select the **C-CDA** tab.
3. Search by **patient name** in the search bar.
4. Click into the matching patient.
5. Click **Download** to save the C-CDA ZIP — the C-CDA `.xml` plus the patient's `attachment/` folder.

* **What's included:** the patient's USCDI clinical data — demographics plus the clinical sections listed in [Export contents](#export-contents-ehi-data-classes-supported-formats) — and the documents uploaded to the patient's chart, exported as original-format files under `attachment/`.
* **Output format:** a ZIP archive containing one HL7 C-CDA R2.1 UTF-8 XML file plus an `attachment/` folder of original-format attachments.
* **File location:** downloads through your browser to its default **Downloads** folder as a `.zip` 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](#considerations-error-conditions).

**Note:** The `attachment/` folder holds the patient's uploaded documents (faxes, scans, PDFs, images, etc.) in their original file formats. If the patient has no attachments on file, the folder is empty or omitted. See [Patient attachments](#patient-attachments).

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

### <Icon icon="globe" iconType="duotone" color="#F9345F" size={23} />  How to request a population export

<Info>
  **Email:** [support@athelas.com](mailto:support@athelas.com)

  Include your **practice name** and the **date range** you need.
</Info>

**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 content as the single-patient export — one C-CDA `.xml` per patient, a practice-wide `claims.csv`, and an `attachment/` folder holding each patient's uploaded documents (one subfolder per patient). The archive is named `EHI_Export_YYYYMMDD.zip` (where `YYYYMMDD` is the export date); each patient's C-CDA file is named by the patient's first and last name, and each patient's attachment subfolder uses the same `First Last` naming:

```
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
├── ...
└── attachment/             # patient attachments, one subfolder per patient
    ├── Jane Doe/           # documents uploaded to Jane Doe's chart, in their original formats
    │   ├── referral.pdf
    │   └── insurance_card.jpg
    ├── John Smith/
    │   └── intake_form.pdf
    └── ...
```

**Output formats:** identical to the single-patient export — UTF-8 `claims.csv`, HL7 C-CDA R2.1 UTF-8 XML, and patient attachments in their original file formats. All are fully specified under [Data structure documentation](#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                                      |
| **Patient attachments / documents**              | `attachment/` folder (per-patient subfolders in the population export)                                    | Original file formats (PDF, image, etc.) |

**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.
* **Patient attachments** — the patient's uploaded documents (e.g., PDF, JPEG, PNG, TIFF), stored unmodified in their original upload formats inside the `attachment/` folder.

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

### <Icon icon="table" iconType="duotone" color="#F9345F" size={23} />  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:**

```csv theme={null}
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).

### <Icon icon="file-code" iconType="duotone" color="#F9345F" size={23} />  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:**

```xml theme={null}
<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:

```xml theme={null}
<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](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492)
* [ONC C-CDA Scorecard](https://site.healthit.gov/scorecard/) — validates structure, templates, and vocabulary bindings

### <Icon icon="paperclip" iconType="duotone" color="#F9345F" size={23} />  Patient attachments

Patient attachments are the documents uploaded to a patient's chart — scanned forms, faxes, referral letters, clinical PDFs, photos, and similar files. They are exported **in their original file formats, byte-for-byte unchanged**, inside an `attachment/` folder in the export ZIP.

| **Property**             | **Value**                                                                                                                                                                                  |
| :----------------------- | :----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| **Location**             | `attachment/` directory inside the export ZIP                                                                                                                                              |
| **Organization**         | **Population export:** one subfolder per patient, named `First Last` (matching the C-CDA file naming). **Single-patient C-CDA ZIP:** the patient's files sit directly under `attachment/`. |
| **Filenames**            | Original uploaded filenames, preserved as-is                                                                                                                                               |
| **Formats / MIME types** | Heterogeneous — whatever was uploaded (e.g., `application/pdf`, `image/jpeg`, `image/png`, `image/tiff`). Determine each file's type from its extension or magic bytes.                    |
| **Encoding**             | Binary — files are stored unmodified                                                                                                                                                       |

**Folder layout — population export:**

```
attachment/
├── Jane Doe/               # one subfolder per patient, named "First Last"
│   ├── referral.pdf
│   └── insurance_card.jpg
├── John Smith/
│   └── intake_form.pdf
└── ...
```

**Folder layout — single-patient C-CDA download:**

```
<C-CDA export>.zip
├── Jane Doe.xml
└── attachment/             # the patient's uploaded documents, in their original formats
    ├── referral.pdf
    └── insurance_card.jpg
```

**Parsing notes:**

* Files are exported unmodified; determine each file's type from its extension or magic bytes rather than from any assumed naming convention.
* A patient with no attachments on file has **no subfolder** (population export) or an **empty/omitted** `attachment/` folder (single-patient C-CDA ZIP). Treat this as "no documents on file," not an error.
* In the population export, attachments are grouped into per-patient subfolders named `First Last` — the same naming convention used for each patient's C-CDA `.xml` file.

## 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."                                                      |
| **No attachments on file**       | A patient with no uploaded documents has no subfolder under `attachment/` (population export) or an empty/omitted `attachment/` folder (single-patient C-CDA ZIP). Treat as "no documents on file."  |
| **Attachment formats vary**      | Files under `attachment/` are exported in their original upload formats (PDF, image, etc.) and original filenames. Determine each file's type from its extension or magic bytes, not a fixed format. |
| **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](#patient-population-site-wide-ehi-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

<Accordion title="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.
</Accordion>

<Accordion title="What's the difference between the claims.csv, the C-CDA .xml, and the attachments?">
  * **`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.
  * **`attachment/`** holds the **documents uploaded to the patient's chart** — faxes, scans, referral letters, PDFs, and images — in their original file formats. In the single-patient export these are bundled in the C-CDA download ZIP alongside the `.xml`.

  Together they form the complete EHI export for a patient.
</Accordion>

<Accordion title="Are patient attachments (uploaded documents) included in the export?">
  Yes. Documents uploaded to a patient's chart — faxes, scans, referral letters, PDFs, images — are exported in their **original file formats** inside an `attachment/` folder.

  * In the **single-patient** export, the `attachment/` folder is bundled in the **C-CDA download ZIP** alongside the patient's `.xml`.
  * In the **population (site-wide)** export, the `attachment/` folder sits inside `EHI_Export_YYYYMMDD.zip` with **one subfolder per patient**, named `First Last`.

  If a patient has no attachments on file, their subfolder is omitted (population) or the `attachment/` folder is empty (single-patient). See [Patient attachments](#patient-attachments).
</Accordion>

<Accordion title="How do I export all of my patients at once?">
  Population (site-wide) exports are requested by an **Admin** emailing [support@athelas.com](mailto: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`, one C-CDA `.xml` per patient (named `First Last.xml`), and an `attachment/` folder with each patient's uploaded documents (one subfolder per patient). See [Patient-population (site-wide) EHI export](#patient-population-site-wide-ehi-export).
</Accordion>

<Accordion title="How do I validate the C-CDA file?">
  Use the [ONC C-CDA Scorecard](https://site.healthit.gov/scorecard/) to validate structure, templates, and vocabulary bindings, and the [HL7 C-CDA R2.1 Implementation Guide](http://www.hl7.org/implement/standards/product_brief.cfm?product_id=492) as the authoritative reference. The file is a HL7 C-CDA R2.1 Continuity of Care Document encoded in UTF-8 XML.
</Accordion>

<Accordion title="Are the export files USCDI-compliant?">
  Yes. The clinical C-CDA export is aligned to the **USCDI v3** data classes. The [Export contents](#export-contents-ehi-data-classes-supported-formats) table identifies each EHI/USCDI data class and where it appears in the export.
</Accordion>
