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

# Export Types

> Available export formats and their use cases

Carelane offers several export formats to meet different data extraction needs. Choose the format that best fits your use case.

## FHIR JSON Export

**Type Code:** `json-fhir-all-data`

### Description

Exports all study data in HL7 FHIR R5 JSON format. This is the most complete export format, preserving the full data structure.

### Contents

* ResearchStudy resource (study metadata)
* ResearchSubject resources (participants)
* QuestionnaireResponse resources (CRF data)
* Observation resources (findings)
* PlanDefinition resources (pathways, workflows)
* Questionnaire resources (form definitions)
* Audit events

### Use Cases

* Complete data backup
* Regulatory submission
* Data migration
* FHIR-compatible analysis tools
* Long-term archival

### Format

```json theme={null}
{
  "resourceType": "Bundle",
  "type": "collection",
  "entry": [
    {
      "resource": {
        "resourceType": "ResearchStudy",
        ...
      }
    },
    ...
  ]
}
```

<Tip>
  FHIR JSON preserves complete data structure and relationships. Use this format when you need full fidelity.
</Tip>

## Sites CSV Export

**Type Code:** `csv-all-sites-metadata`

### Description

Exports site information in CSV format for easy analysis in spreadsheet applications.

### Contents

| Column           | Description             |
| ---------------- | ----------------------- |
| Site ID          | Unique site identifier  |
| Site Name        | Site display name       |
| Status           | Current site status     |
| Location         | Address information     |
| Contacts         | Contact details         |
| Enrollment Count | Number of participants  |
| Activation Date  | When site became active |

### Use Cases

* Site performance tracking
* Geographic analysis
* Enrollment distribution
* Site management reporting

### Format

Standard CSV with headers:

```csv theme={null}
site_id,site_name,status,city,country,enrollment_count
001,Example Hospital,enrolling,Boston,USA,25
```

## Participants CSV Export

**Type Code:** `csv-all-participants-data`

### Description

Exports participant data in flattened CSV format with one row per participant or per visit.

### Contents

| Column Type  | Examples                       |
| ------------ | ------------------------------ |
| Identifiers  | Participant ID, Pseudonym      |
| Demographics | PHI fields (if enabled)        |
| Status       | Current status, status history |
| Arm          | Arm assignment                 |
| Visit Data   | Questionnaire responses        |
| Timestamps   | Created, updated, visit dates  |

### Use Cases

* Statistical analysis
* Data review
* Study progress tracking
* Site comparison

### Format Options

| Format   | Description                                |
| -------- | ------------------------------------------ |
| **Wide** | One row per participant, visits as columns |
| **Long** | One row per visit/response                 |

### Column Headers Across CRF Versions

CSV column headers are built from the field's stable identifier and name, **not** from the underlying FHIR resource id. As a result, an unchanged field is reported in the **same column** for participants on different [CRF versions](/study-design/pathway-versioning) of the same study.

* A field that exists in two CRF versions and was not renamed appears in **one** column for all participants, regardless of which version they are on.
* A field that was renamed in a new CRF version appears under **two** separate column headers — one per name — because renaming a field is treated as a structural change.

<Warning>
  Updating the data for an existing report changes the CSV header layout to match this behavior. Any saved filters, scripts, or downstream pipelines that reference the old per-version column names will need to be updated.
</Warning>

## Export Comparison

| Feature          | FHIR JSON | Sites CSV | Participants CSV |
| ---------------- | --------- | --------- | ---------------- |
| Complete Data    | Yes       | No        | Partial          |
| PHI Included     | Yes       | Limited   | Yes              |
| Easy Analysis    | No        | Yes       | Yes              |
| Regulatory       | Yes       | No        | Limited          |
| Interoperability | Yes       | No        | No               |

## Choosing an Export Type

### For Regulatory Submission

Use **FHIR JSON** for complete data with audit trails.

### For Analysis

Use **Participants CSV** for spreadsheet-based analysis.

### For Site Management

Use **Sites CSV** for site-level reporting.

## Related

<CardGroup cols={2}>
  <Card title="Export Management" icon="gear" href="/exports-reports/export-management">
    Create and manage exports.
  </Card>

  <Card title="Reports" icon="chart-bar" href="/exports-reports/reports">
    Built-in reporting features.
  </Card>
</CardGroup>