Version differences

What changed between two versions of an IG

9 version pairs across 8 implementation guides. Each report is computed from the two published packages and carries the SHA-256 digest of both, so anyone who fetches the same two archives gets the same answer.

What these reports are, and are not

They answer one question: given version A and version B of an implementation guide, what actually differs? Element cardinality and must-support expectations, target profiles and bindings, invariants, operation parameters, and the profiles that exist on only one side.

They are not a compliance assessment and they carry no deadline. Where a regulation names an implementation guide, the report for that guide cites the rule with its own dates and links — as a footnote, not as a finding. What a rule requires is a claim about a rule; what changed between two versions is a claim about two files, and only the second is what this measures.

Nothing here is limited to a fixed regulatory list. Any two published versions of any guide in the catalog can be compared the same way.

US Core

hl7.fhir.us.core

3.1.1 → 6.1.0· pinned intermediate targetThree major releases apart, and the profile set nearly doubles: 29 profiles exist in both versions, 30 only in 6.1.0, and 1 only in 3.1.1.

162 element changes · 29 profiles in both · +30/−1 coverage · 5 operation changes 6.1.0 → 9.0.0The second leg of the US Core walk: 924 requirement changes across the 58 profiles present in both versions, with only 12 profiles added and 1 removed.

924 element changes · 58 profiles in both · +12/−1 coverage

Da Vinci PAS

hl7.fhir.us.davinci-pas

2.0.1 → 2.2.1The largest requirement delta in the set — 1,007 changes across 70 profiles present in both versions, including 191 new must-support expectations.

1,007 element changes · 70 profiles in both · +11/−1 coverage · 1 operation changes

Da Vinci DTR

hl7.fhir.us.davinci-dtr

2.0.1 → 2.2.0The only pair that moves on both planes at once: two OperationDefinitions added and ten operation-level changes, beside 284 element changes.

284 element changes · 14 profiles in both · +11/−0 coverage · 10 operation changes

Da Vinci CRD

hl7.fhir.us.davinci-crd

2.0.1 → 2.2.1The widest coverage expansion here: 31 profiles exist only in 2.2.1, carrying 400 mandatory or must-support elements between them.

320 element changes · 17 profiles in both · +31/−1 coverage

CARIN Blue Button

hl7.fhir.us.carin-bb

2.0.0 → 2.2.0The densest per-profile delta: 573 requirement changes over just 11 profiles present in both versions, most of them binding and target-profile changes.

573 element changes · 11 profiles in both · +5/−0 coverage

Da Vinci PDex

hl7.fhir.us.davinci-pdex

2.0.0 → 2.1.0The quietest element-level pair at this scale — 48 requirement changes across 25 shared profiles — while still adding 12 profiles outright.

48 element changes · 25 profiles in both · +12/−1 coverage · 1 operation changes

SMART App Launch

hl7.fhir.uv.smart-app-launch

1.0.0 → 2.2.0The publisher's canonical host moved from fhir-registry.smarthealthit.org to hl7.org, so the single 1.0.0 profile matches none of the six in 2.2.0 and the whole difference is coverage, not element-level change.

0 element changes · 0 profiles in both · +6/−1 coverage

FHIR Bulk Data Access

hl7.fhir.uv.bulkdata

1.0.0 → 3.0.0Ships no StructureDefinitions in 1.0.0, so the whole requirement surface is OperationDefinition parameters — 23 parameter changes and no element rows at all.

0 element changes · 0 profiles in both · +4/−0 coverage · 23 operation changes