Bulk Data Access IG: STU1 + Technical Correction

This page is part of the FHIR Bulk Data Access (Flat FHIR) (v1.0.1: STU 1) based on FHIR R4. The current version which supercedes this version is 2.0.0. For a full list of available versions, see the Directory of published versions

Bulk Data

OperationDefinition: export

Formats: Narrative, XML, JSON

BulkDataExport

OPERATION: BulkDataExport

The official URL for this operation definition is: 

http://hl7.org/fhir/uv/bulkdata/OperationDefinition/export

Export data from a FHIR server whether or not it is associated with a patient. This supports use cases like backing up a server or exporting terminology data by restricting the resources returned using the _type parameter. The FHIR server SHALL support invocation of this operation using the FHIR Asynchronous Request Pattern

URL: [base]/$export

Parameters

UseNameCardinalityTypeBindingDocumentation
IN_outputFormat0..1string

The format for the requested bulk data files to be generated as per FHIR Asynchronous Request Pattern. Defaults to application/fhir+ndjson.

IN_since0..1instant

Resources updated after this period will be included in the response.

IN_type0..1string

A string of comma-delimited FHIR resource types. Only resources of the specified resource types(s) SHOULD be included in the response. If this parameter is omitted, the server SHOULD return all supported resources within the scope of the client authorization. Resource references MAY be relative URIs with the format {resource type}/{id}, or absolute URIs with the same structure rooted in the base URI for the server from which the export was performed. References will be resolved looking for a resource with the specified type and id within the file set. Note: Implementations MAY limit the resources returned to specific subsets of FHIR, such as those defined in the Argonaut Implementation Guide.