This sample demonstrates how Azure Health Data Services and Microsoft Entra ID can be used to pass the Inferno test suite for ONC §170.315(g)(10) Standardized API for patient and population services criterion, which include:
- Health Level 7 (HL7®) Version 4.0.1 Fast Healthcare Interoperability Resources Specification (FHIR®)
- United States Core Data for Interoperability (USCDI)
- HL7® FHIR® Bulk Data Access (Flat FHIR®) (V1.0.1:STU 1)
- FHIR® US Core Implementation Guide STU V3.1.1
- HL7® SMART Application Launch Framework Implementation Guide Release 1.0.0
- OpenID Connect Core 1.0 incorporating errata set 1
While Azure Health Data Services is the core of this sample, some custom behavior is required to fully meet the §170.315(g)(10) Standardized API for patient and population services criteria requirements, mostly around SMART on FHIR authentication. This sample is therefore not using only the FHIR Server but other Azure Services with sample code to pass the Inferno tests. You can use this sample as a starting point and reference for building your applications and solutions.
Deployment of this sample requires the creation of supporting Azure services, custom code deployed to Azure Function Apps, and setup in Microsoft Entra ID. For detailed deployment instructions, check out the deployment document here.
This sample is targeted at application developers who are already using Azure Health Data Services or Azure API for FHIR.
You will need an Azure Subscription with Owner privileges and Microsoft Entra ID Global Administrator privileges.
The below components are deployed with this sample. At a high level:
- Routing and SMART Conformance is handled with Azure API Management API Gateway.
- Authorization as defined by the SMART on FHIR and Bulk Data Access Implementation Guide are handled by Microsoft Entra ID with custom code to enable some specific requirements..
- Bulk Data Export is handled mostly by FHIR Service with some custom code to enable users to access the files they've exported per the Bulk Data Implementation Guide.
- While FHIR Service supports
$exportoperations, Azure does not support accessing the files using the same access token used for FHIR Service. - All FHIR data operations are handled by FHIR Service in Azure Health Data Services. Azure API for FHIR would also fit here
For more details of how the pieces work together, check out the technical guide.
If you are having issues with the sample, please look at the troubleshooting document.
If you have questions about this sample, please submit a Github issue. This sample is custom code you must adapt to your own environment and is not supported outside of Github issues. This sample is targeted towards developers with intermediate Azure experience.