Practical FHIR notes on SDC form builders and terminology server implementations for healthcare integration teams.
A 50 kb Bundle is trivial to pretty-print in memory. A 500 MB export Bundle is not. The formatter that loads the whole payload as a JavaScript object, walks it, and re-serializes will eat memory equal to several times the payload size, and...
A pretty-printer should never touch reference strings. Sounds obvious. In practice, formatters that normalize URL casing, resolve relative paths, or reformat urn:uuid: values silently break Bundle semantics. Reference integrity depends on...
API-first healthcare platforms have a particular set of expectations for a FHIR MPI tool. The match operation has to behave like any other service: clean REST, predictable latency, no surprises in the auth model. Older MPIs that grew up ins
Line-length choice sounds like a bike-shed argument. It becomes a real problem the first time a reviewer opens a Bundle diff in a two-panel code review tool and every fourth line scrolls horizontally. Reviewers who scroll do not review....
Bundles that live in version control — fixtures, examples, IG source, integration test data — deserve the same formatting discipline as source code. The formatter's job is not just readability. It is producing diffs that reviewers can...
Pretty-printing a Bundle should change the whitespace and nothing else. That is the rule. Formatters that helpfully reorder keys, entries, or arrays are not helpful — they turn a formatting operation into a semantic change, and every...
The compact FHIR Bundle that arrived on the wire is optimized for bytes. That is the right shape for transport. It is the wrong shape for every human who has to read it. Every incident where a developer opens a Bundle in a text editor and...
A FHIR master patient index is the layer that decides whether two patient records are the same person. It runs underneath registration, scheduling, billing, and almost every clinical workflow that touches a record. The wrong call merges two
Healthcare platforms hit the managed vs self-hosted FHIR terminology service question earlier than they expect. The first ValueSet lands fine on whichever choice the founding engineer made. The first multi-tenant customer, the first complia
FHIR-native decision support has a specific relationship with the terminology layer. Every CQL expression that walks a SNOMED hierarchy, every quality measure that checks ValueSet membership, every CDS Hooks call that needs subsumption: all