Category: Terminology server

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

Order entry in FHIR uses the ServiceRequest resource, not MedicationRequest (that's for meds). Four patterns cover how EHR vendors implement clinical order workflows in 2026. Pattern 1: Single ServiceRequest per order. Simple lab orders and imaging orders map one-to-one with a single ServiceRequest. code identifies the test, subject is the Patient, requester is the Practitioner, […]