FHIR sort is a _sort parameter with a comma-separated list of parameter names, optionally negated with a leading dash for descending order. The mechanic looks simple. It becomes not-simple the moment two resources tie on the sort key and...
Latest Posts
Using _count and _offset Without Losing Consistency
FHIR search pagination is a topic where the spec is careful and the servers vary. _count requests a page size, servers may cap it, offset-style pagination via _offset produces inconsistent results when the underlying set changes between...
Modifier Stacking: :not, :in, :missing Without Foot-Guns
FHIR search modifiers turn a plain parameter into a set-operation query. :not inverts, :in filters against a value set, :missing finds resources where the element is absent. Each is useful; each has edge cases; server support is uneven....
Date Search Precision and the Range It Implicitly Covers
FHIR date search has a precision-implies-range rule that trips up callers who have not read the chapter. A search for ?date=2026 matches everything in that year. A search for ?date=2026-07-11 matches everything on that day. The precision...
A 2026 Reference Guide to FHIR Questionnaire Orchestration
A FHIR Questionnaire orchestration layer is the part of a clinical forms stack that turns Questionnaire definitions into rendered, validated, and persisted patient or clinician data. The SDC (Structured Data Capture) IG defines most of the
Reserved Characters in Search Values That Break Silently
FHIR search reserves a small set of characters for structural meaning inside a search value: comma, ampersand, pipe, dollar sign, and a couple of others. Values that carry any of them raw truncate silently at the first delimiter, and the...
The FHIR Searches That Look Correct But Are Wrong
FHIR search is permissive on the way in. The server accepts the parameters, returns a searchset Bundle, and reports no error. That combination hides a category of queries that are syntactically valid, semantically wrong, and produce...
FHIR Patient/$match vs Vendor MPI APIs: A Practical Comparison
A patient-matching call at the integration boundary can take two shapes. The spec-aligned shape is `Patient/$match`, the FHIR operation that returns a Bundle of candidate Patient resources ranked by match score. The vendor shape is a propri
EMPI vs MPI: Which Fits Multi-Payer Networks
A multi-payer network has to pick between an MPI and an EMPI, and the choice has real architectural consequences. The terminology blurs in vendor marketing because every product calls itself both, but the underlying design assumptions diver
Top 5 EMPI Tools for Research Data Warehouses
A research data warehouse runs an EMPI under different constraints than a clinical one. Match decisions need to be defensible to an IRB long after they are made, the cohort has to remain stable across reanalysis cycles, and the same patient
