Multi-Region Active-Active on Azure for a .NET API: What Happens to the Write You Acknowledged

Routing two Azure regions is configuration. Deciding what happens to two writes to one record is design. Four write strategies compared on one simulated outage, what Cosmos DB does with a conflict, idempotent retries across regions, readiness probes for Front Door, and the global tier in Terraform.

Read more →

Azure OpenAI Structured Outputs for Clinical Coding: Free Text to FHIR Condition and Observation, with a Human Review Step

A model proposes coded findings from a clinical note inside a strict JSON Schema whose enums are an approved code subset; code checks every proposal against the note; a clinician accepts or rejects; and only accepted items become FHIR Condition, Observation and Provenance resources. C# on .NET 10 and Python.

Read more →

FHIR Validation in CI: Profiles, Terminology and IPS Checks That Fail the Build

A build gate for FHIR conformance: the HL7 validator behind a Python wrapper and the Firely .NET SDK check resources against the IPS profiles in GitHub Actions, with deliberately broken test data that proves the gate refuses what it should, and a clear account of what it cannot see without a terminology server.

Read more →

FHIR Subscriptions and Events on Azure: Keeping Downstream Systems in Step

Azure Health Data Services announces FHIR changes through Event Grid, at least once and in no guaranteed order. An Azure Function on .NET 10 that keeps a downstream projection correct through duplicates, reordering, corrections and deletions with one version-guarded write.

Read more →

Migrating from Azure API for FHIR to Azure Health Data Services: Export, Import, Identity and a Cut-Over Runbook

Azure API for FHIR retires on 30 September 2026. What changes on the Azure Health Data Services FHIR service, a Python script for $export and $import, a C# tool that compares source and target before cut-over, and a runbook with a rollback point.

Read more →

A FHIR Facade over an openEHR Repository on Azure: ASP.NET Core, Entra ID and SMART Scopes

An ASP.NET Core minimal API that serves openEHR blood pressure readings from EHRbase as FHIR Observations and enforces SMART scopes from Microsoft Entra ID tokens. Built on .NET 10, run against a live EHRbase repository, with a Python test client and the Azure Container Apps placement.

Read more →