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 →

Querying Clinical Data: AQL vs. FHIR Search vs. SQL on FHIR

Five ordinary clinical questions put to three query languages: FHIR search, openEHR AQL and SQL on FHIR. The comparison shows what each was built for, where approximate cohort queries go wrong, and how view definitions turn FHIR resources into tables. Includes a tested SQL on FHIR pipeline in Python and C# clients for FHIR search and AQL.

Read more →

Mapping openEHR Medication Orders to FHIR: AQL In, Transaction Bundle Out

A medication order has no status field in openEHR: its state lives in separate ACTION entries. This article builds a table-driven mapper, in Python and C#, that reads AQL result sets of medication orders and writes an idempotent FHIR transaction Bundle of MedicationRequest resources, with a report of every row rejected or degraded.

Read more →

FHIR and openEHR: When to Use Which, and How They Coexist

HL7 FHIR was designed to exchange clinical data and openEHR to keep it for a lifetime. This article compares the two on the dimensions that affect architecture, shows the same blood pressure in each, and sets out a coexistence design for Azure with a tested mapping in Python and C# that reports what the FHIR resource could not carry.

Read more →

Hosting Remote MCP Servers Securely on AWS and Azure: Token Validation, Gateways and Network Placement

A remote MCP server is an API that a language model can drive. This article covers the three things that decide whether it is safe: what the MCP authorization specification requires of the server, where to host it on AWS and Azure and who validates the token in each case, and where the endpoint belongs on the network. Includes a tested Python resource server and an ASP.NET Core version for Entra ID.

Read more →