Create a destination for AWS + HealthLake

For cloud connectivity with Redox, you decide which cloud provider and cloud product(s) to use. Then, you'll need to create a cloud destination in your Redox organization.

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.

This article is for this combination of cloud products:

• Amazon Web Services (AWS)
• HealthLake

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. This destination will be where your data is pushed to.

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 accessKeyId and secretAccessKey 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 response with details for the new auth credential.
5. Review the Create destination endpoint.
6. In your terminal, prepare the /v1/environments/{environmentId}/destinations request.
7. Specify these values in the request.
   • 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
       }
8. You should get a successful response with details for the new destination for AWS.
9. Your new destination will now be able to receive messages. Redox converts any notification bundles or other message bundles into individual FHIR® resource requests, which are stored in the HealthLake datastore.