Microsoft Azure API for FHIR
summary
Microsoft outlines two deployable FHIR options: managed service vs open source (FHIR Server for Azure on GitHub). It demonstrates HL7v2→FHIR conversion using the FHIR Converter and a Visual Studio Code extension, templates pushed to Azure Container Registry, and managed identity so the service pulls them. New capabilities include custom search parameters with an async reindex job, validate operation, chained searches, Liquid templates, private endpoint and customer‑managed keys. Exports support group-level anonymization; an example run writes 937 patients and 64 observations as anonymized export to NDJSON (crypto‑hashed IDs, redacted postcodes) and is consumable in Azure Databricks.
AI-written summary · about
chapters (12)
- 0:00Introduction and speaker intro
- 3:07Azure API for FHIR overview
- 5:14New features in managed service
- 8:01Deploying secure FHIR environment
- 11:32Converting and validating data
- 17:59Uploading conversion templates
- 21:36Enhancing data with search parameters
- 25:54Exporting and anonymizing data
- 30:32Analyzing exported data with Databricks
- 34:26Open source FHIR server deployment
- 36:50Key takeaways and resources
- 38:16Q&A session
related talks
22mOpen source and managed ecosystems for FHIR in Azure
22mOpen source and managed ecosystems FHIR in Azure
43mGoogle Cloud FHIR APIs
35mWhat’s new in Terraform for Azure?
34mUnlocking the Latest Innovations in Terraform on Azure
32mCloud Foundry on Azure, Beyond BOSH and CPI
20mGetting Started with Event Stream Processing via Apache Flink on Microsoft Azure
42mOpenshift on Azure deep dive
