Exporting files from a HealthLake data store
To export data from your HealthLake data store, use the following operations.
-
Make an export request using the
StartFHIRExportJob
API operation using the HealthLake SDK.-
This operation only supports making a system-wide export request.
-
-
Make an export request using the
export
syntax using the HealthLake FHIR REST API.-
This operation supports making system-wide, Patient, and Group export requests. You can also apply parameters to further filter the data in the export request.
-
Users can enqueue their import or export jobs to their HealthLake data store. These asynchronous import or export jobs will be processed in a FIFO (First In First Out) manner. Users can create, read, update, or delete FHIR resources while an import or export job is in progress.
Both of these operations require a service role. In it, HealthLake must be defined as the service principal, and you must define an Amazon Simple Storage Service (S3) bucket of where you want to export your files. To learn more, see Creating a service role.
Both of these operations only support exporting your files to an Amazon S3 (S3) bucket. All files from your HealthLake data store are exported as newline delimited JSON (.ndjson
) files, where each line consists of a valid FHIR resource.