Provision FHIR Data Store and Import Data
A 4-step recipe with Amazon HealthLake. We can help you get access.
Recipe · 4 steps
Provision FHIR Data Store and Import Data
with Amazon HealthLake
Create a FHIR data store, wait for ACTIVE, then import data and wait for COMPLETED.
- Create the FHIR data store. The response returns the AWS-generated data store id, ARN, status, and endpoint.
- 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 import job.
- Begin the FHIR import job against the newly active data store. The response returns the AWS-generated job id and job status.
- Describe the import 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.
- InputS3Uri: The S3 location of the FHIR data to be imported.
- OutputS3Uri: The S3 location used for the import job output.
- OutputKmsKeyId: The KMS key ID used to access the output S3 bucket.
- DataAccessRoleArn: The IAM role ARN that gives AWS HealthLake access to your input data.
- ImportClientToken: Token used for ensuring idempotency of the import job.
- ImportJobName: The user generated name for the import job.
For your developer
Arazzo workflow amazon-healthlake:provision-datastore-and-import, 4 operations: CreateFHIRDatastore → DescribeFHIRDatastore → StartFHIRImportJob → DescribeFHIRImportJob. Specs on APIs.io.