ADT and ORM are the two HL7v2 message families that almost every US integration team has to handle. ADT carries admit, discharge, and transfer events; ORM carries clinical orders. They look superficially similar, and the conversion to…
Author: Roland Zhou
Backend engineer from Austin. Covers Subscription and event-driven patterns for FHIR notification pipelines.
Best Patient-Matching Tools for High-Volume EDs in 2026
A high-volume emergency department puts a particular kind of pressure on patient-matching tooling. Patients arrive without a chance to verify demographics calmly, the registration clerk has to capture identity in seconds, the matching engin
Top 6 SDC Form Renderers for Patient-Facing Apps in 2026
Patient-facing SDC form rendering has a different set of constraints than clinician-facing rendering. The user is on a phone half the time, the literacy assumptions are different, and the form has to be tolerant of partial completion, accid
Choosing a FHIR Terminology Server: A Buyer's Guide for US Healthcare
Picking a FHIR terminology server for a US healthcare deployment looks like a checklist exercise on paper, and then it stops looking simple about three weeks into integration. The vendor pages all promise the same set of operations: hosting
CDS Hooks for FHIR: What Actually Works at Point of Care
CDS Hooks is the FHIR-native pattern for clinical decision support in EHR workflow. In 2026, three hook types ship in production; two others are aspirational. Understanding which is which affects integration timelines. Production-ready hooks 1. patient-view. Fires when a clinician opens a patient chart. CDS returns cards with alerts, reminders, and links to more context. […]
FHIR Subscription in R5: SubscriptionTopic Practical Notes
FHIR R5 Subscription replaced R4's per-endpoint criteria-and-hook model with a topic-based model where multiple subscribers reference shared SubscriptionTopic definitions. This scales much better in production; understanding the model matters for anyone building event-driven FHIR integrations. SubscriptionTopic structure A SubscriptionTopic defines: resourceTrigger (what change fires the topic), notificationShape (which fields ride the notification), and canFilterBy (filter […]