Version difference

hl7.fhir.uv.smart-app-launch 1.0.0 → 2.2.0

The 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.

← All version differences · Download the evidence pack (markdown — this page as one citable file)

Version gap report — hl7.fhir.uv.smart-app-launch 1.0.0 → 2.2.0

0 newly required0 potentially breaking0 new must-support0 strengthened0 binding changes

Informational only — readiness is judged against the target version and never changes with this report.

Read the element counts as a floor

6 profiles exist only in 2.2.0, and 1 only in 1.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 70 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. No profile in one version matches a profile in the other by canonical URL, so every difference appears as coverage rather than as an element change.

The shape of the change

0 critical0 needs review0 indeterminate0 informational

0 element-level requirement changes, each graded to exactly one tier — so every view below sums to the same total.

Slice the findings

filtershowing 0 of 0

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: 6
Removed from baseline: 1
Element obligations carried by added profiles: 70

PROFILE_ADDED · Task · OBSERVED_ONLY
task-standalone-launch is new in the target version, carrying 13 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/smart-app-launch/StructureDefinition/task-standalone-launch
PROFILE_ADDED · Bundle · OBSERVED_ONLY
user-access-brands-bundle is new in the target version, carrying 19 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/smart-app-launch/StructureDefinition/user-access-brands-bundle
PROFILE_ADDED · Organization · OBSERVED_ONLY
user-access-brand is new in the target version, carrying 12 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/smart-app-launch/StructureDefinition/user-access-brand
PROFILE_ADDED · Task · OBSERVED_ONLY
task-ehr-launch is new in the target version, carrying 13 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/smart-app-launch/StructureDefinition/task-ehr-launch
PROFILE_ADDED · Endpoint · OBSERVED_ONLY
user-access-endpoint is new in the target version, carrying 10 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/smart-app-launch/StructureDefinition/user-access-endpoint
PROFILE_ADDED · Basic · OBSERVED_ONLY
smart-app-state-basic is new in the target version, carrying 3 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/smart-app-launch/StructureDefinition/smart-app-state-basic
PROFILE_REMOVED · Extension · OBSERVED_ONLY
oauth-uris exists in the baseline version and not in the target. Nothing in the target replaces it under a matching canonical URL.
http://fhir-registry.smarthealthit.org/StructureDefinition/oauth-uris

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.smart-app-launch#1.0.0` sha256 `1b73c8ad6037280768af213a887ef2cf6ed9674f062b516d5db08a66fd18e6d6` 1 profiles · 0 value sets · 0 operations · CC0-1.0
Target	`hl7.fhir.uv.smart-app-launch#2.2.0` sha256 `0bb498dd09677684239f24d279b6da711cd814449f2f473c2970fbe881ec9c70` 6 profiles · 3 value sets · 0 operations · CC-BY-4.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.