Validation Results for CentralCancerRegistryReporting

Generated Tue Sep 01 18:50:39 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.central-cancer-registry-reporting#2.0.0-ballot (canonical = http://hl7.org/fhir/us/central-cancer-registry-reporting (history)). See Full QA Report & IP

Quality Checks
Publisher Version:IG Publisher Version: v2.3.3
Publication Code:central-cancer-registry-reporting . PackageId = hl7.fhir.us.central-cancer-registry-reporting, Canonical = http://hl7.org/fhir/us/central-cancer-registry-reporting
Realm Check for US:

Snomed: The IG specifies the US edition of SNOMED CT

Profiles: All OK

Language Info:This IG has no language information
Publication Request:
RelatedIgs(None Found)
  • Version 2.0.0-ballot has already been published
  • Publication Request is for version v2.0.0-ballot which is already published
Supressed Messages:56 Suppressed Issues
Dependency Checks:
PackageVersionFHIRCanonicalWeb BaseComment
.. hl7.fhir.us.central-cancer-registry-reporting2.0.0-ballotR4http://hl7.org/fhir/us/central-cancer-registry-reporting
... hl7.terminology.r47.3.0 MR4http://terminology.hl7.orghttp://terminology.hl7.org/7.3.0
.... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0
..... hl7.terminology.r47.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.1.0Latest Release is 7.3.0
...... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0Latest Release is 5.3.0
... hl7.fhir.uv.extensions.r45.3.0 MR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.3.0 (as above)
... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1Latest Release is 9.0.0
.... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0Latest Release is 5.3.0
.... hl7.fhir.uv.bulkdata2.0.0 OR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2Latest Release is 3.0.0
.... hl7.fhir.uv.smart-app-launch2.1.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.1Latest Release is 2.2.0
..... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.3.0
.... us.nlm.vsac0.11.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
.... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3Latest Release is 4.0.0
..... hl7.fhir.r4.examples4.0.1 OR4http://hl7.org/fhirhttp://hl7.org/fhir/R4Latest Release is 5.0.0
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads
.... ihe.formatcode.fhir1.1.0 OR4https://profiles.ihe.net/fhir/ihe.formatcode.fhirhttps://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0Latest Release is 1.5.0
.... hl7.terminology.r47.0.1 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1 (as above). Latest Release is 9.0.0
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads (as above)
.... us.nlm.vsac0.24.0 MR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsac
.... hl7.fhir.uv.crmi1.0.0 OR4http://hl7.org/fhir/uv/crmihttp://hl7.org/fhir/uv/crmi/STU1Latest Release is 2.0.0
..... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0Latest Release is 7.3.0
...... hl7.fhir.uv.extensions.r41.0.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/1.0.0 (as above). Latest Release is 5.3.0
..... hl7.fhir.uv.extensions.r45.1.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0Latest Release is 5.3.0
.... hl7.fhir.uv.cql2.0.0 MR4http://hl7.org/fhir/uv/cqlhttp://hl7.org/fhir/uv/cql/STU2
..... hl7.terminology.r46.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0Latest Release is 7.3.0
...... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.fhir-clinical-document1.0.1 OR4http://hl7.org/fhir/uv/fhir-clinical-documenthttp://hl7.org/fhir/uv/fhir-clinical-document/STU1.0.1Latest Release is 1.1.0
..... hl7.terminology.r47.0.1 OR4http://terminology.hl7.orghttp://terminology.hl7.org/7.0.1 (as above). Latest Release is 7.3.0
..... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
... hl7.fhir.uv.subscriptions-backport.r41.1.0 MR4http://hl7.org/fhir/uv/subscriptions-backporthttp://hl7.org/fhir/uv/subscriptions-backport/STU1.1FHIR Version Mismatch
.... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.3.0
... hl7.fhir.us.mcode4.0.0 MR4http://hl7.org/fhir/us/mcodehttp://hl7.org/fhir/us/mcode/STU4
.... hl7.terminology.r46.2.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.2.0Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.uv.genomics-reporting2.0.0 OR4http://hl7.org/fhir/uv/genomics-reportinghttp://hl7.org/fhir/uv/genomics-reporting/STU2Latest Release is 3.0.0
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1 (as above). Latest Release is 9.0.0
... hl7.fhir.us.cancer-reporting2.0.0 MR4http://hl7.org/fhir/us/cancer-reportinghttp://hl7.org/fhir/us/cancer-reporting/STU2
.... hl7.terminology.r46.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/6.5.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.uv.extensions.r45.2.0 OR4http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.2.0 (as above). Latest Release is 5.3.0
.... hl7.fhir.us.core6.1.0 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU6.1 (as above). Latest Release is 9.0.0
... hl7.fhir.us.odh1.3.0 MR4http://hl7.org/fhir/us/odhhttp://hl7.org/fhir/us/odh/STU1.3
.... hl7.terminology.r45.0.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.0.0 (as above). Latest Release is 7.3.0
.... hl7.fhir.us.core5.0.1 OR4http://hl7.org/fhir/us/corehttp://hl7.org/fhir/us/core/STU5.0.1Latest Release is 9.0.0
..... hl7.terminology.r43.1.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/3.1.0Latest Release is 7.3.0
..... hl7.fhir.uv.bulkdata2.0.0 OR4http://hl7.org/fhir/uv/bulkdatahttp://hl7.org/fhir/uv/bulkdata/STU2 (as above). Latest Release is 3.0.0
..... hl7.fhir.uv.smart-app-launch2.0.0 OR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2Latest Release is 2.2.0
..... us.nlm.vsac0.7.0 OR4http://fhir.org/packages/us.nlm.vsachttp://fhir.org/packages/us.nlm.vsacLatest Release is 0.24.0
..... hl7.fhir.uv.sdc3.0.0 OR4http://hl7.org/fhir/uv/sdchttp://hl7.org/fhir/uv/sdc/STU3 (as above). Latest Release is 4.0.0
.... us.cdc.phinvads0.12.0 MR4http://fhir.org/packages/us.cdc.phinvadshttp://fhir.org/packages/us.cdc.phinvads (as above)
... hl7.fhir.uv.smart-app-launch2.2.0 MR4http://hl7.org/fhir/smart-app-launchhttp://hl7.org/fhir/smart-app-launch/STU2.2
.... hl7.fhir.uv.extensions5.1.0-snapshot1 OR5http://hl7.org/fhir/extensionshttp://hl7.org/fhir/extensions/5.1.0-snapshot1FHIR Version Mismatch. Latest Release is 5.3.0
..... hl7.terminology.r55.3.0 OR5http://terminology.hl7.orghttp://terminology.hl7.org/5.3.0FHIR Version Mismatch. Latest Release is 7.3.0
.... hl7.terminology5.5.0 OR4http://terminology.hl7.orghttp://terminology.hl7.org/5.5.0 (as above). Latest Release is 7.3.0
... hl7.fhir.uv.tools.r41.1.2 MR4http://hl7.org/fhir/toolshttp://hl7.org/fhir/tools/1.1.2Internal Dependency
Templates: hl7.fhir.template#1.0.0 -> hl7.base.template#1.0.0 -> fhir.base.template#1.0.0
Related IGs:n/a
Dependent IGs:no references
Global Profiles:(none declared)
Terminology Server(s):https://tx-nordics.fhir.org/fhir/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:1 issue
R5 Dependencies:(none)
Draft Dependencies:
Modifier Extensions:(none)
Previous Version Comparison:
IPA Comparison: n/a
IPS Comparison: n/a
Validation Flags: On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Summary: errors = 0, warn = 4, info = 22, broken links = 0, pinned = 31 (when multiples).
FilenameErrorsWarningsHints
Build Errors012
/scratch/repo/input/central-cancer-registry-reporting010
/scratch/repo/input/examples/ccrr-encounter2-based-content-bundle-example010
/scratch/repo/input/examples/ccrr-med-admin-docetaxel-example010

n/a Show Validation Information

warningThe jira specification file appears to be out of date with the versions, artifacts and pages currently defined in the IG. A proposed revised file to be reviewed and, if appropriate, submitted as a pull request against the XML folder in https://github.com/HL7/JIRA-Spec-Artifacts. To see the differences, perform a file compare on 'template/jira-current.xml' (a normalized view of what is in Github) and 'template/jira-new.xml' (reflects current IG content)
CapabilityStatement-central-cancer-registry-reporting-ehr​.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Data Sources (with built-in Data Submitter functionality) SHALL meet the general security requirements documented in FHIR Security guidance.' CONFORMANCE_STATEMENT_WORD
spec.htmlinformationThe html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' SHALL indicates requirements that must be met to be conformant with the specification. ยง ' CONFORMANCE_STATEMENT_WORD

input/central-cancer-registry-reporting.xml Show Validation Information (1)

PathSeverityMessageValidating
ImplementationGuide​.dependsOn[2] (l1​/c2847)warningThe ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD--

input/examples/ccrr-encounter2-based-content-bundle-example.json Show Validation Information (15)

PathSeverityMessageValidating
Bundle​.entry[3]​.resource​.medication​.ofType(CodeableConcept)​.coding[0]​.system (l304​/c10)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONCancer-Related Medication Administration Profile

input/examples/ccrr-med-admin-docetaxel-example.json Show Validation Information (1)

PathSeverityMessageValidating
MedicationAdministration​.medication​.ofType(CodeableConcept)​.coding[0]​.system (l18​/c4)warningA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026 (from https://tx.fhir.org/r4, see log, or see the servers logic) UNKNOWN_CODESYSTEM_VERSIONCancer-Related Medication Administration Profile

Suppressed Messages (Warnings, hints, broken links)

Best Practice Recommendations

Cancer Specific Value Sets that tooling is unable to expand because they are too large, it is a limitation of the publisher.

Code System Validation

Expansion Parameters Related Error This will be fixed in a later version of the IG Publisher (see: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0

Message due to subscription IG , The Subscriptions backport IG was mistakenly released as FHIR 4.0.0 instead of 4.0.1. See https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Subscriptions.20backport.20issue

Message related to CCRR Specification Bundle slicing validated to be false positive

Messages Due to Inherited Slicing

Messages due to dependencies on other specifications

Messages due to pinning of canonicals in snapshot elements from otehr IG dependencies

Messages due to specific versions of the US Core IG, we are currently using US Core 6.1.0 as it is the currently approved SVAP version for HTI-1

Messages for ODH Sliciing validated to be false positive

Messages related to CCRR Content Bundle Slicing validated to be false positive

Messages related to CCRR Reporting Bundle Slicing validated to be false positive

Messages related to creating Ids for Specification statements

Errors sorted by type


Details_for__matching_against_Profile_

input/examples/Central-Cancer-Registry-Reporting-specification-bundle-example.jsonThis element does not match any known slice defined in the profile http://hl7.org/fhir/us/central-cancer-registry-reporting/StructureDefinition/ccrr-specification-bundle|2.0.0-ballot (this may not be a problem, but you should check that it's not intended to match a slice)US Public Health ValueSet

IG_DEPENDENCY_VERSION_WARNING_OLD

input/central-cancer-registry-reporting.xmlThe ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be considered--

MSG_DEPENDS_ON_DEPRECATED_NOTE

input/resources/bundle-ccrr-content-bundle.xmlThe extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'StructureDefinition
input/resources/central-cancer-registry-reporting-patient.xmlThe extension http://hl7.org/fhir/StructureDefinition/regex|5.3.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex'StructureDefinition

MSG_DRAFT

input/examples/cancer-stage-group-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Distant Metastases Category Profile
input/examples/ccrr-content-bundle-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0US Core Practitioner Profile
input/examples/ccrr-content-bundle-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Primary Tumor Category Profile
input/examples/ccrr-content-bundle-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Regional Nodes Category Profile
input/examples/ccrr-content-bundle-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Distant Metastases Category Profile
input/examples/ccrr-content-bundle-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|0.5.0US Core Condition Problems and Health Concerns Profile
input/examples/problem-diabetes.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/condition-category|0.5.0US Core Condition Problems and Health Concerns Profile
input/examples/tnm-clinical-distant-metastases-category-cm0-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Distant Metastases Category Profile
input/examples/tnm-clinical-primary-tumor-category-ct2-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Primary Tumor Category Profile
input/examples/tnm-clinical-regional-nodes-category-cn0-example.jsonReference to draft CodeSystem http://terminology.hl7.org/CodeSystem/observation-category|0.1.0TNM Regional Nodes Category Profile

PIN_VERSION

input/resources/ccrr-composition.xmlPinned the version of http://terminology.hl7.org/ValueSet/v3-ActCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#3.1.0), 3.0.0 (hl7.terminology.r4#6.2.0)--
input/resources/central-cancer-registry-reporting-encounter.xmlPinned the version of http://terminology.hl7.org/ValueSet/v3-ActEncounterCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#3.1.0), 3.0.0 (hl7.terminology.r4#6.2.0)--
input/resources/central-cancer-registry-reporting-encounter.xmlPinned the version of http://terminology.hl7.org/ValueSet/v3-ActEncounterCode to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#3.1.0), 3.0.0 (hl7.terminology.r4#6.2.0)--
input/resources/central-cancer-registry-reporting-encounter.xmlPinned the version of http://terminology.hl7.org/ValueSet/v3-ActPriority to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#3.1.0), 3.0.0 (hl7.terminology.r4#6.2.0)--
input/resources/central-cancer-registry-reporting-encounter.xmlPinned the version of http://terminology.hl7.org/ValueSet/v2-0092 to 3.0.0 from choices of 2.0.0 (hl7.terminology.r4#3.1.0), 3.0.0 (hl7.terminology.r4#7.3.0)--

UNKNOWN_CODESYSTEM_VERSION

input/examples/ccrr-encounter2-based-content-bundle-example.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026Cancer-Related Medication Administration Profile
input/examples/ccrr-med-admin-docetaxel-example.jsonA definition for CodeSystem 'http://www.nlm.nih.gov/research/umls/rxnorm' version '09022025' could not be found, so the code cannot be validated. Valid versions: 03022026Cancer-Related Medication Administration Profile

VALUESET_INC_TOO_MANY_CODES

input/resources/valueset-cancer-core-reportability-codes.jsonThe value set include has too many concepts to validate (4,920, more than the limit of 1,000), so each individual code has not been checked--
input/resources/valueset-cancer-core-reportability-codes.jsonThe value set include has too many concepts to validate (2,986, more than the limit of 1,000), so each individual code has not been checked--