The 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)
01 Suppressing common warnings and warnings inherited from core spec
Reference to deprecated ValueSet http://hl7.org/fhir/ValueSet/jurisdiction|5.0.0 (13 uses)
Reference to experimental CodeSystem http://hl7.org/fhir/guide-parameter-code|5.0.0 (16 uses)
The definition for the element 'Device.name.type' binds to the value set 'http://hl7.org/fhir/ValueSet/device-nametype|5.0.0' which is experimental, but this structure is not labeled as experimental (2 uses)
The definition for the element 'Observation.category' binds to the value set 'http://hl7.org/fhir/ValueSet/observation-category|5.0.0' which is experimental, but this structure is not labeled as experimental (1 uses)
The definition for the element 'Observation.referenceRange.type' binds to the value set 'http://hl7.org/fhir/ValueSet/referencerange-meaning|5.0.0' which is experimental, but this structure is not labeled as experimental (1 uses)
02 Supressing warnings related to CardX-CIED specific terminology.
Most code systems defined in HL7 IGs will need to move to THO later during the process. Consider giving this code system a THO URL now (See https://confluence.hl7.org/display/TSMG/Terminology+Play+Book, and/or talk to TSMG) (1 uses)
03 Observations have 1 or more devices generating the information and do not have a performer
Best Practice Recommendation: In general, all observations should have a performer (5 uses)
04 Supressing messages realted to standard terminology
Reference to draft CodeSystem urn:iso:std:iso:11073:10101|2024-12-05 (16 uses)
hl7.fhir.uv.cardx-cied
hl7.fhir.uv.tools.r5