Starting an import job in HealthLake
After you create a data store and set up permissions for import jobs (Setting up permissions for import jobs), you can start importing files with an import job. You can start an import job by using either the AWS HealthLake console or the AWS HealthLake import API, start-fhir-import-job API.
Importing files with API operations
Prerequisites
When you use the AWS HealthLake API operations, you must first create an AWS Identity and Access Management (IAM) policy and attach it to an IAM role. To learn more about IAM roles and trust policies, see IAM Policies and Permissions. Customers must also use a KMS key for encryption. To learn more about using KMS Keys, see Amazon Key Management Service.
To import files (API), use the following steps.
-
Upload your data into an Amazon S3 bucket.
-
Use the
start-fhir-import-job API
API operation. When you start the job, specify the name of the Amazon S3 bucket that contains the input files, the KMS key you want to use for encryption, and the output data configuration. -
To learn more about a FHIR import job, use the describe-fhir-import-job operation to get the job's ID, ARN, name, start time, end time, and current status. Use list-fhir-import-job to show all import jobs and their statuses.
Starting an import job (console)
To import files with the console, you upload your data into an Amazon S3 bucket,
To import files use the following steps.
-
Upload your data into an Amazon S3 bucket.
-
Open the HealthLake console at https://console.aws.amazon.com//healthlake/home
. -
Go to the data store details page for your data store and choose Import.
-
Specify your Amazon S3 bucket and either create or identify the IAM role and the KMS key you want to use.
-
Choose Import data.