---
title: "Register EHI Export request"
method: POST
path: "/bridge/fhir/ehi-export"
tags: ["bridge"]
---

# Register EHI Export request

`POST /bridge/fhir/ehi-export`

<Note>
This endpoint is idempotent. If a request with the same `org_connection_id` has already been registered, it will return the existing request.
</Note>

This endpoint will register an bulk medical record export request with the Fasten Connect API for the provided `org_connection_id` (Patient id)

This functionality is similar in design to the HL7 [EHI Export](https://build.fhir.org/ig/argonautproject/ehi-api/ehi-export.html) specification.
However it is designed to be a unified API for all EHRs, as many EHRs do not support the HL7 EHI Export specification.

<Warning>
This endpoint requires an API public id & private key for authentication. Do not expose these keys in the browser.
</Warning>

This task will run asynchronously and may take some time to complete. 
You can check the status of the task using the [Get Request Status](/api-reference/ehi_export/get) endpoint.

On completion a webhook will be sent to your `webhook_url` with metadata about the task, and a `download_link` to download the results.

## Request body

- object
  - `org_connection_id` string, uuid — Patient Connection Id
  - `fixtures` object — Optional testing fixtures for TEFCA API-mode exports.
    - `tefca_ccda` 'myra-jones.xml' | 'lennie-connell.xml' | 'myra-jones-v2.xml' | 'myra-jones-v7.xml' | 'bernice-maxwell.xml' — Force a specific synthetic CCDA response for TEFCA testing.

## Response `200`

successful operation

- object
  - `success` boolean
  - `data` EhiExportRequestStatus
    - `task_id` string, string — Task Id
    - `status` 'pending' | 'success' | 'failed'

---

[API](https://skmtc.net/fastenhealth/apis/fasten-connect.md) · [All operations](https://skmtc.net/fastenhealth/apis/fasten-connect/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/fastenhealth/fasten-connect/revisions/e8a1d9b54053/schema)