Transform healthcare with cutting-edge FHIR data solutions, empowering seamless integration and innovation for your medical applications.
Editorial illustration in origami-folded style depicting four merge cases showing disjoint, same-field conflict, semantic-equal, and array-union resolutions
Json Diff Desk

When a Diff Should Be a Merge Conflict

A diff that changes different fields on the same resource can be merged. A diff that changes the same field on the same resource cannot — that is a merge conflict, and pretending it is not produces silent data corruption. FHIR-aware merge...
Editorial illustration in origami-folded style depicting a PR review flow with formatter, semantic diff, and reviewer checklist
Json Diff Desk

Reviewing FHIR Diffs in a Pull Request

FHIR fixtures and IG examples live in pull requests. Reviewing a PR that touches Bundle.json is not the same as reviewing a code change — the reviewer needs to see the semantic change, not the character-level noise. Most default PR diff...
Editorial illustration in origami-folded style depicting a JSON diff transforming into a JSON Patch with test, remove, add, replace ops
Json Diff Desk

PATCH Generation From a JSON Diff

Once you have a diff between two versions of a resource, generating a PATCH to transform one into the other is a small step. Done well, the resulting PATCH is minimal, safe, and applyable by any FHIR server that supports JSON Patch. Done...
Editorial illustration in origami-folded style depicting structural vs semantic FHIR diff modes side-by-side
Json Diff Desk

Structural Diff vs Semantic Diff for FHIR JSON

Two FHIR diffs of the same pair of resources can produce very different output. A structural diff finds every byte-level change. A semantic diff finds every clinically meaningful change. The two are related and different, and knowing which...