Version difference
hl7.fhir.us.davinci-dtr 2.0.1 → 2.2.0
← All version differences · Download the evidence pack (markdown — this page as one citable file)
Version gap report — hl7.fhir.us.davinci-dtr 2.0.1 → 2.2.0
Informational only — readiness is judged against the target version and never changes with this report.
Read the element counts as a floor
11 profiles exist only in 2.2.0. Those have no counterpart to compare against, so they contribute no element-level rows to the counts above — the element comparison covers the 14 profiles present in both versions. Both numbers are below; neither is a total on its own.
The 144 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.
The shape of the change
284 element-level requirement changes, each graded to exactly one tier — so every view below sums to the same total.
Most breaking changes
where the migration work concentrates
- 6 of 103
- 5 of 10
- 3 of 38
Most sharply changed
share of a profile's changes that break · profiles with at least 5 changes
- 50% of 10
- 40% of 5
- 25% of 8
Slice the findings
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: 14
- Added in target: 11
- Removed from baseline: 0
- Element obligations carried by added profiles: 144
- PROFILE_ADDED · Questionnaire · OBSERVED_ONLYdtr-base-questionnaire is new in the target version, carrying 81 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/us/davinci-dtr/StructureDefinition/dtr-base-questionnaire
- PROFILE_ADDED · Extension · OBSERVED_ONLYestimated-completion-time is new in the target version, carrying 8 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/us/davinci-dtr/StructureDefinition/estimated-completion-time
- PROFILE_ADDED · Extension · OBSERVED_ONLYqr-coverage is new in the target version, carrying 2 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/us/davinci-dtr/StructureDefinition/qr-coverage
- PROFILE_ADDED · Extension · OBSERVED_ONLYquestionnaireAudience is new in the target version, carrying 2 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/us/davinci-dtr/StructureDefinition/questionnaireAudience
- PROFILE_ADDED · Parameters · OBSERVED_ONLYdtr-next-question-output-parameters is new in the target version, carrying 4 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/us/davinci-dtr/StructureDefinition/dtr-next-question-output-parameters
- PROFILE_ADDED · QuestionnaireResponse · OBSERVED_ONLYdtr-questionnaireresponse-adapt is new in the target version, carrying 33 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/us/davinci-dtr/StructureDefinition/dtr-questionnaireresponse-adapt
- PROFILE_ADDED · Extension · OBSERVED_ONLYcontainedReference is new in the target version, carrying 2 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/us/davinci-dtr/StructureDefinition/containedReference
- PROFILE_ADDED · Parameters · OBSERVED_ONLYdtr-next-question-input-parameters is new in the target version, carrying 4 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/us/davinci-dtr/StructureDefinition/dtr-next-question-input-parameters
- PROFILE_ADDED · Extension · OBSERVED_ONLYalternativeExpression is new in the target version, carrying 2 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/us/davinci-dtr/StructureDefinition/alternativeExpression
- PROFILE_ADDED · Extension · OBSERVED_ONLYrequest-specific is new in the target version, carrying 2 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/us/davinci-dtr/StructureDefinition/request-specific
- PROFILE_ADDED · List · OBSERVED_ONLYdtr-supported-Payers is new in the target version, carrying 4 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/us/davinci-dtr/StructureDefinition/dtr-supported-Payers
What is shown, and what is left out
Every count in the explorer is complete — computed over all 284 element changes. The example rows a node expands to draw on a bounded, deterministic sample of 40, 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.us.davinci-dtr#2.0.1sha256 a2840c31da3277d7b78c74baf65bcbeee97ddfe4f956810bffd79d9cfe5c64f014 profiles · 5 value sets · 2 operations · CC0-1.0 |
|---|---|
| Target | hl7.fhir.us.davinci-dtr#2.2.0sha256 027894027a86e3a250252ac61476f82ca509a2ed04dbd4bad0816d2e24f204ea25 profiles · 8 value sets · 4 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.
Where rules we track mention this guide
Context only, quoted from our mandate register. None of it changes the comparison above, which depends on the two packages and nothing else.
- CMS-0057-F (by 2027-01-01) — register records a recommended version of
2.2.0Documentation templates & rulescompliance 2027-01-01CMS Interoperability & Prior Authorization Final Rule (CMS-0057-F) · in our library - CMS-0062-P (proposed — no adopted date)Named alongside CRD and PAS in the proposed prior-authorization workflow. Not adopted; no version named.PROPOSED 2026-04-14, comments closed 2026-06-15 — not final as of 2026-07-26, no adopted compliance dateFederal Register: Interoperability Standards and Prior Authorization for Drugs (proposed rule) · CMS: 2026 Interoperability Standards and Prior Authorization for Drugs Proposed Rule (CMS-0062-P)
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.
- Clinical Decision Support WG (owner)Owns DTR — the one Da Vinci burden-reduction guide not under Financial Management; its published footer attributes this committee.HL7 committee page · DTR footer attributionreviewed 2026-07-26 · next expected: DTR's next published release attributing a different committee in its footer.