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 →Tag: .NET 10
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 →A2A and MCP Across Clouds: Connecting a .NET Agent Framework Agent to an Agent on Bedrock AgentCore
MCP connects an agent to its tools; A2A connects an agent to another agent. This article wires a .NET Microsoft Agent Framework coordinator on Azure to a Python agent and MCP tool server laid out for Amazon Bedrock AgentCore Runtime, and reports what broke: A2A 0.3 versus 1.0 version skew, identity across the cloud boundary, and task lifecycle handling.
Read more →One Abstraction, Two Clouds: Microsoft.Extensions.AI over Azure OpenAI and Amazon Bedrock
Microsoft.Extensions.AI gives .NET services one interface over Azure OpenAI and Amazon Bedrock. This article builds a two-provider ASP.NET Core service with per-provider telemetry, caching, token metering, tool calling and failover, and is clear about where the abstraction stops: model identity, errors, content safety and model behaviour remain provider-specific.
Read more →.NET 10 on AWS Lambda: Managed Runtime, Native AOT and SnapStart
One .NET 10 function built three ways from one source tree and run in the AWS Lambda base images under the Runtime Interface Emulator: what each build costs at start-up, what breaks under Native AOT, what SnapStart asks of your code, and how to choose.
Read more →