This is the STU 2 - Ballot version of the Central Cancer Registry Reporting FHIR IG.
changes
changes.html
RelatedIgs
(None Found)
This IG has never been published
This appears to be the first publication, so first must be true
Publication Request is for 'hl7.fhir.us.central-cancer-registry-reporting' but package is hl7.fhir.us.dapl
Publication Request is for v'2.0.0-ballot' but package version is v0.1.0
Proposed path for this publication does not start with the canonical URL (http://hl7.org/fhir/us/central-cancer-registry-reporting/2026Jan vs http://hl7.org/fhir/us/dapl)
Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
This release is not labelled as a milestone or technical correction, so should have a patch version (0.1.0)
This IG is not yet published at all, so there must be "first" : true in the publication request
No publication request category found (needed for first publication - consult FHIR product director for a value
No publication request title found (needed for first publication)
No publication request introduction found (needed for first publication)
No publication request ci-build found (needed for first publication)
Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/us/dapl (Problem #1 with package-list.json at http://hl7.org/fhir/us/dapl: Not Found)
IPA Comparison:
n/a
IPS Comparison:
n/a
Validation Flags:
On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Unable to find ImplementationGuide.definition.resource.description for the resource Bundle/dapl-deidentified-bundle. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list.
error
There is no jira specification file defined with the expected name of FHIR-us-dapl in the xml folder of the https://github.com/HL7/Jira-Spec-Artifacts project. This must exist before ballot or publication.
The link 'reportingguidance.html' for "Reporting Guidance" cannot be resolvedHTML_LINK_CHECK_FAILED
spec.html
information
The 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
1
warning
The HTML fragment 'ip-statements.xhtml' is not included anywhere in the produced implementation guide
2
warning
An HTML fragment from the set [cross-version-analysis.xhtml, cross-version-analysis-inline.xhtml] is not included anywhere in the produced implementation guide
3
warning
An HTML fragment from the set [dependency-table.xhtml, dependency-table-short.xhtml, dependency-table-nontech.xhtml] is not included anywhere in the produced implementation guide
4
warning
The HTML fragment 'globals-table.xhtml' is not included anywhere in the produced implementation guide
5
warning
The HTML fragment 'expansion-params.xhtml' is not included anywhere in the produced implementation guide
A definition for CodeSystem 'http://www.nubc.org/patient-discharge' could not be found, so the code cannot be validated (from https://tx.fhir.org/r4) UNKNOWN_CODESYSTEM
Extension.extension:detailed: max allowed = 0, but found 1 (from http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-ethnicity-extension|0.1.0)Validation_VAL_Profile_Maximum
Extension.extension:detailed: max allowed = 0, but found 1 (from http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-ethnicity-extension|0.1.0)Validation_VAL_Profile_Maximum
Extension.extension:detailed: max allowed = 0, but found 1 (from http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-ethnicity-extension|0.1.0)Validation_VAL_Profile_Maximum
US FHIR Usage rules require that all profiles on AllergyIntolerance derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core AllergyIntolerance ProfileUS_CORE_DERIVATION
Element Patient.address.postalCode: derived min (0) cannot be less than the base min (1) in http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-deidentified-patient|0.1.0
The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.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'MSG_DEPENDS_ON_DEPRECATED_NOTE
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient ProfileUS_CORE_DERIVATION
US FHIR Usage rules require that all profiles on Coverage derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Coverage ProfileUS_CORE_DERIVATION
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#7.0.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
US FHIR Usage rules require that all profiles on Encounter derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Encounter ProfileUS_CORE_DERIVATION
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#7.0.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0'TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient ProfileUS_CORE_DERIVATION
US FHIR Usage rules require that all profiles on RelatedPerson derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core RelatedPerson ProfileUS_CORE_DERIVATION
US FHIR Usage rules require that all profiles on Immunization derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Immunization ProfileUS_CORE_DERIVATION
US FHIR Usage rules require that all profiles on MedicationRequest derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core MedicationRequest ProfileUS_CORE_DERIVATION
US FHIR Usage rules require that all profiles on Procedure derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Procedure ProfileUS_CORE_DERIVATION
Best Practice Recommendation which is not required by UDS+
Best Practice Recommendation: In general, all observations should have a performer (3 uses)
Messages from the Base Specification
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.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 (0 uses)
Resources in DAPL are de-identified and text is not allowed, hence the resources should not have text.
Constraint failed: dom-6: 'A resource should have narrative for robust management (text.`div`.exists())' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (38 uses)
The Terminology Server does not have the CodeSystem loaded
The definition for the Code System with URI 'urn:oid:2.16.840.1.113883.6.238' doesn't provide any codes so the code cannot be validated (0 uses)
This element does not match any known slice defined in the profile http://hl7.org/fhir/us/dapl/StructureDefinition/dapl-income-observation|0.1.0 (this may not be a problem, but you should check that it's not intended to match a slice)
This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|8.0.1 (this may not be a problem, but you should check that it's not intended to match a slice)
The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.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'
Pinned the version of http://terminology.hl7.org/CodeSystem/v3-AdministrativeGender to 4.0.0 from choices of 3.0.0 (hl7.terminology#5.5.0), 4.0.0 (hl7.terminology.r4#7.1.0)
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0092'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#7.0.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0092' to 'http://terminology.hl7.org/ValueSet/v2-0092|3.0.0'
There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v2-0116'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.0.0 (from hl7.terminology.r4#7.0.0), 3.0.0 (from hl7.terminology.r4#7.1.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v2-0116' to 'http://terminology.hl7.org/ValueSet/v2-0116|3.0.0'
US FHIR Usage rules require that all profiles on AllergyIntolerance derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core AllergyIntolerance Profile
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient Profile
US FHIR Usage rules require that all profiles on Coverage derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Coverage Profile
US FHIR Usage rules require that all profiles on Encounter derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Encounter Profile
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient Profile
US FHIR Usage rules require that all profiles on RelatedPerson derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core RelatedPerson Profile
US FHIR Usage rules require that all profiles on Immunization derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Immunization Profile
US FHIR Usage rules require that all profiles on MedicationRequest derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core MedicationRequest Profile
US FHIR Usage rules require that all profiles on Procedure derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Procedure Profile