A little FHIRPath sandbox
Somebody asked for a way to try FHIRPath expressions against a payload without setting up an engine, so I put…
Somebody asked for a way to try FHIRPath expressions against a payload without setting up an engine, so I put…
Duplicate patient records are the slow-growing pain that every healthcare data team eventually has to address. Every duplicate is a…
Ontoserver and Snowstorm are the two terminology servers that come up most often when a team needs serious SNOMED CT…
Most healthcare teams have a stack of legacy web forms collecting clinical data somewhere in production. The forms work, more…
Mid-size hospitals sit in the awkward middle of the MPI procurement question. They are too large to muddle through with…
Value set authoring is the slower-moving cousin of terminology server selection. The runtime gets the attention; the authoring tools that…
Form rendering libraries are the unglamorous middle layer of FHIR app development. They take a Questionnaire resource the team authored…
A failing FHIRPath expression rarely fails loud. It returns an empty collection, or a boolean that flips wrong, or a…
FHIR Questionnaires use FHIRPath in two related places: calculated expressions on items, and enable-when logic that shows or hides items…
Extensions are how FHIR carries what the base spec did not model, and navigating them is one of the most…
A FHIRPath expression that passes on the demo resource in the spec often fails on the payload that actually arrives…