Create a destination for AWS + HealthLake

To populate your Amazon Web Services (AWS) repository with healthcare data from an EHR system via Redox (and then to analyze and normalize that data in FHIR® format with AWS HealthLake), you must configure a specific Redox cloud destination. A Redox destination represents where a message is delivered (e.g., like the address in the “To” line of an email header). Learn more about connecting Redox to your cloud repository.

You’ll need to perform some steps in your cloud product(s) and some in Redox. You can perform Redox setup in our dashboard or with the Redox Platform API.

• Establish a connection with your preferred EHR system. Learn how to request a connection.
• Complete your AWS and AWS HealthLake configuration before creating your Redox destination. Save any downloads with secret values, since you’ll need to enter some of these details into the Redox dashboard.
• Grant access to Redox from AWS (and any other cloud product) to authorize Redox to push data to your cloud repository.

1. Navigate to the AWS dashboard and log in.
2. Create an IAM user.
3. Generate an access key and secret pair.
4. Create a new HealthLake datastore, or open an existing one.

Next, create a cloud destination in your Redox organization. When the EHR system sends healthcare data to Redox, we push it on to your configured AWS + HealthLake cloud destination.

1. For the select destination step, follow the instructions for creating a cloud destination.
2. From the Product type field, select HealthLake.
3. For the configure destination step, populate these fields. Then click the Next button.
   1. FHIR® URL: Enter the AWS FHIR® endpoint where data should be sent.
4. For the auth credential step, either a drop-down list of existing auth credentials displays or a new auth credential form opens. Learn how to create an auth credential for AWS Sigv4.

   Existing or new auth credential

   Your existing auth credentials will only display if they’re supported for the cloud product type you selected. If you don’t have any supported auth credentials for the cloud type in the current Redox environment, you’ll have to create a new auth credential.

5. For the verify step, follow the instructions for verifying a destination.

1. Review the Create auth credential endpoint.
2. In your terminal, prepare the /v1/authcredentials request.
3. Specify these values in the request.
   • Locate the accessKey and secretKey values in the AWS dashboard.

     Example: Create auth credential for AWS + HealthLake

     json

     Copy

     1
     curl 'https://api.redoxengine.com/platform/v1/authcredentials' \
     2
     --request POST \
     3
     --header 'Authorization: Bearer $API_TOKEN' \
     4
     --header 'accept: application/json' \
     5
     --header 'content-type: application/json' \
     6
     --data '{
     7
         "organization": "<Redox_organization_id>",
     8
         "name": "<human_readable_name_for_auth_credential>",
     9
         "environmentId": "<Redox_environment_ID>",
     10
         "authStrategy": "AwsSigV4",
     11
         "accessKey": "<access_key_from_AWS>",
     12
         "secretKey": "<secret_key_from_AWS>",
     13
         "serviceName": "healthlake",
     14
         "awsRegion": "<aws_region_of_healthlake_datastore>"
     15
       }
4. You should get a successful 200 response and a payload populated with the details of the new auth credential.
5. Review the Create destination endpoint.
6. In your terminal, prepare the /v1/environments/{environmentId}/destinations request with these values:
   • Set authCredential to the auth credential ID from the response you received in step #4.
   • Populate cloudProviderSettings with the settings below.
     • Locate the FHIR® base URL in the AWS dashboard.

       Example: Values for AWS + HealthLake cloudProviderSettings

       json

       Copy

       1
       {
       2
         "cloudProviderSettings": {
       3
           "typeId": "aws",
       4
           "productId": "healthlake", 
       5
           "settings": {
       6
             "fhirBaseUrl": "<URL_of_healthlake_datastore>",
       7
            }
       8
         }
       9
       }
7. You should get a successful 200 response with a payload populated with the details of the new AWS cloud destination. Specifically, the verified status of the destination should be set to true.
8. Your new destination will now be able to receive messages. Redox converts any notification bundles or other message bundles into individual FHIR® resource requests. This ensures compatibility with HealthLake's ingestion requirements. Then, the FHIR® data is stored in the HealthLake datastore.