// the find
microsoft/azure-health-data-services-toolkit
Customization model for Azure Health Data Services.
A proxy-pattern SDK from Microsoft for layering custom logic — request/response transforms, custom operations, authorization — in front of Azure Health Data Services' FHIR service. It's for teams already running production FHIR on Azure who need behavior the managed service doesn't expose yet, not a general-purpose FHIR toolkit.
The Filter/Channel/Binding pipeline model is a genuinely useful abstraction: it separates request/response transforms from side-effects to external systems (Blob, Event Hub, Service Bus) from the eventual proxy target, so you're not writing one monolithic middleware per custom operation. It ships as real versioned NuGet packages rather than a sample you fork and copy-paste, and it's compute-agnostic — the same code runs on Azure Functions, App Service, or AKS. The sample catalog is unusually thorough for a Microsoft repo, with a separate runnable project per channel type and caching backend, plus a CAPL (custom policy language) doc for consent-based authorization rules, which is a real pain point in FHIR deployments.
76 stars after several years of existence says this hasn't seen much adoption or battle-testing outside Microsoft's own FHIR customers. The samples skip authorization entirely and the docs assume you're fronting everything with Azure API Management — fine if you already run APIM, an extra piece of infrastructure to stand up if you don't. It's tied tightly to Azure Health Data Services specifically, so none of this transfers if you're running FHIR server OSS elsewhere or on another cloud. The disclaimer is blunt that this isn't a managed service and you bear all compliance risk for the health data flowing through it — reasonable legally, but worth internalizing before treating it as a drop-in solution rather than a framework you still have to own.