capabilities.work

Provision FHIR Data Store and Export Data

A 4-step recipe with Amazon HealthLake. We can help you get access.

Recipe · 4 steps

Provision FHIR Data Store and Export Data

Create a FHIR data store, wait for ACTIVE, then export data and wait for COMPLETED.

  1. Create the FHIR data store. The response returns the AWS-generated data store id, ARN, status, and endpoint.
  2. Describe the data store and inspect its status. While the status is CREATING the step loops back to itself; once the status is ACTIVE the flow proceeds to start the export job.
  3. Begin the FHIR export job against the newly active data store. The response returns the AWS-generated job id and job status.
  4. Describe the export job and inspect its status. While the status is SUBMITTED or IN_PROGRESS the step loops back to itself; once the status is COMPLETED the workflow ends.
What you'll need to have ready
  • DatastoreName: The user generated name for the data store.
  • DatastoreTypeVersion: The FHIR version of the data store. The only supported version is R4.
  • CreateClientToken: Optional token used for ensuring idempotency of data store creation.
  • OutputS3Uri: The S3 location used for the export job output.
  • OutputKmsKeyId: The KMS key ID used to access the output S3 bucket.
  • DataAccessRoleArn: The IAM role ARN used during the initiation of the export job.
  • ExportClientToken: Token used for ensuring idempotency of the export job.
  • ExportJobName: The user generated name for the export job.
For your developer

Arazzo workflow amazon-healthlake:provision-datastore-and-export, 4 operations: CreateFHIRDatastore → DescribeFHIRDatastore → StartFHIRExportJob → DescribeFHIRExportJob. Specs on APIs.io.