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…
Federated healthcare networks have a harder MPI problem than single-tenant systems do. The data sits across organizational boundaries, the governance…
The $expand operation is the one that clinical workflows depend on, and the one that often gets sluggish under real…
A FHIR form builder demo always looks clean. Real workflows are the place where the differences show up. The seven…
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…