Version difference
hl7.fhir.uv.bulkdata 1.0.0 → 3.0.0
← All version differences · Download the evidence pack (markdown — this page as one citable file)
Version gap report — hl7.fhir.uv.bulkdata 1.0.0 → 3.0.0
Informational only — readiness is judged against the target version and never changes with this report.
Read the element counts as a floor
4 profiles exist only in 3.0.0. Those have no counterpart to compare against, so they contribute no element-level rows to the counts above — the element comparison covers the 0 profiles present in both versions. Both numbers are below; neither is a total on its own.
The 12 mandatory or must-support elements attributed to added profiles are counted from each profile’s effective element list. Where a profile ships no snapshot that list is reconstructed by merging its differential onto its base, so treat the figure as indicative rather than audited. Each row states its own basis.
This guide states its requirements outside profiles
There are no element-level requirement changes here, and that is a fact about where this guide puts its requirements — not an absence of change. 1.0.0 ships no StructureDefinitions at all, so there is nothing to compare element by element; the difference lives in operations and coverage.
The shape of the change
0 element-level requirement changes, each graded to exactly one tier — so every view below sums to the same total.
Slice the findings
Nothing matches the current filters — the totals above are unchanged.
Profile coverage
Profiles present in only one of the two versions. These carry no element-level rows in the catalog above, because there is nothing on the other side to compare them against.
- Compared in both versions: 0
- Added in target: 4
- Removed from baseline: 0
- Element obligations carried by added profiles: 12
- PROFILE_ADDED · Group · OBSERVED_ONLYbulk-cohort-group is new in the target version, carrying 9 mandatory or must-support elements. None of them appear in the element-level change list, because there is no baseline profile to compare against.http://hl7.org/fhir/uv/bulkdata/StructureDefinition/bulk-cohort-group
- PROFILE_ADDED · Extension · OBSERVED_ONLYmembers-refreshed is new in the target version, carrying 1 mandatory or must-support element. None of them appear in the element-level change list, because there is no baseline profile to compare against.http://hl7.org/fhir/uv/bulkdata/StructureDefinition/members-refreshed
- PROFILE_ADDED · Extension · OBSERVED_ONLYmember-filter is new in the target version, carrying 1 mandatory or must-support element. None of them appear in the element-level change list, because there is no baseline profile to compare against.http://hl7.org/fhir/uv/bulkdata/StructureDefinition/member-filter
- PROFILE_ADDED · Extension · OBSERVED_ONLYoperation-not-supported is new in the target version, carrying 1 mandatory or must-support element. None of them appear in the element-level change list, because there is no baseline profile to compare against.http://hl7.org/fhir/uv/bulkdata/StructureDefinition/operation-not-supported
What is shown, and what is left out
Every count in the explorer is complete — computed over all 0 element changes. The example rows a node expands to draw on a bounded, deterministic sample of 0, chosen so every kind of change and the most-affected profiles are each represented. The full set is reproducible from the two packages named below.
Provenance
| Baseline | hl7.fhir.uv.bulkdata#1.0.0sha256 bb023019ae7ba4f8d43a07f275ee33157fa62382dc4f18a99507a8f2b01c74d40 profiles · 0 value sets · 3 operations · CC0-1.0 |
|---|---|
| Target | hl7.fhir.uv.bulkdata#3.0.0sha256 f1c76157b672a9ac9f4cc5875637bfc115dd9c4b75a550eb4d9cb17ca076b2894 profiles · 2 value sets · 3 operations · CC0-1.0 |
| Engines | comparison 1.0.0 · normalization 1.3.0 |
The digests identify the exact archives compared. There is no generation timestamp on purpose: the report is a pure function of those two archives, so regenerating it from the same inputs produces identical bytes.
Who maintains this guide, per our register
Where standards work on this guide actually happens — the room a ballot comment or a question should go to. Quoted from our workgroup register; each claim carries the source it was read from.
- FHIR Infrastructure WG (owner)Owns the two universal-realm guides in our catalog — SMART App Launch and Bulk Data Access; both footers attribute this committee.HL7 committee page · SMART footer attributionreviewed 2026-07-26 · next expected: Either guide's next published release attributing a different committee in its footer.