503 Error during FHIR Data Export for Multi-Patient Test in Azure FHIR Health Service

Question

we are encountering while trying to pass the Inferno multi-patient (bulk service) test for FHIR Data export. We are using the Azure FHIR Health Service and the Bulk Service app as the client application, but we are consistently receiving a 503 error during the export of group patient data.

 

Here are the key details of our setup:

• FHIR Health Service: We have assigned the appropriate Smart User and Export roles to the Bulk Service app within the FHIR Health Service.
• Azure Function App: We are utilizing an Azure Function App as part of our implementation for this process.
• Error: Despite assigning the correct roles, the 503 error persists when attempting the export.
• Client App Setup: We are using a Key Vault where we have stored the client secret entry for the algorithm ES384, which Azure does not support. To work around this, we are using a storage account.
• Permissions: The Storage Blob Data Contributor role has been assigned to the storage account to ensure proper permissions. Additionally, the Smart User and Exporter roles are assigned in the FHIR Health Service.

 

References:

• We followed the instructions in the Inferno Test App Registration Guide for the backend service client application configuration.
• Additionally, we used the FHIR Health Service Deployment Guide for our FHIR Health Service deployment.

 

Despite following these steps, we are still receiving the 503 error when attempting the multi-patient export.

I am reaching out regarding an issue we are encountering while trying to pass the Inferno multi-patient (bulk service) test for FHIR Data export. We are using the Azure FHIR Health Service and the Bulk Service app as the client application, but we are consistently receiving a 503 error during the export of group patient data.

 

Here are the key details of our setup:

• FHIR Health Service: We have assigned the appropriate Smart User and Export roles to the Bulk Service app within the FHIR Health Service.
• Azure Function App: We are utilizing an Azure Function App as part of our implementation for this process.
• Error: Despite assigning the correct roles, the 503 error persists when attempting the export.
• Client App Setup: We are using a Key Vault where we have stored the client secret entry for the algorithm ES384, which Azure does not support. To work around this, we are using a storage account.
• Permissions: The Storage Blob Data Contributor role has been assigned to the storage account to ensure proper permissions. Additionally, the Smart User and Exporter roles are assigned in the FHIR Health Service.

 

References:

• We followed the instructions in the Inferno Test App Registration Guide for the backend service client application configuration.
• Additionally, we used the FHIR Health Service Deployment Guide for our FHIR Health Service deployment.

 

Despite following these steps, we are still receiving the 503 error when attempting the multi-patient export.