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)
Intentional, per TSMG (FHIR-59379): CodeSystem/temporary is a stopgap for the ph code until it is added to the existing THO code system http://terminology.hl7.org/CodeSystem/location-physical-type, so this code system is deliberately not being given a THO URL of its own. Discussed with TSMG at the September 2026 WGM, Monday Q4: https://confluence.hl7.org/spaces/VOC/pages/474742994/Sept+2026+-+HL7+WGM+-+Monday+Q4+Minutes
%Most code systems defined in HL7 IGs will need to move to THO later% (1 uses)
Intentional, per TSMG (FHIR-59379): CodeSystem/temporary is marked experimental on purpose, to signal that the ph code used by the Location example will change when it is added to HL7 Terminology (THO). Discussed with TSMG at the September 2026 WGM, Monday Q4: https://confluence.hl7.org/spaces/VOC/pages/474742994/Sept+2026+-+HL7+WGM+-+Monday+Q4+Minutes
%Reference to experimental CodeSystem http://hl7.org/fhir/uv/smart-scheduling-links/CodeSystem/temporary% (1 uses)
Not actionable in this IG: the maxValueSet extension is inherited unchanged from the FHIR R4 core definition of DomainResource.language, which appears as HealthcareService.language in the generated snapshot. No profile in this IG declares a maxValueSet binding of its own, and the replacement recommended by the deprecation note (ElementDefinition.binding.additional) does not exist in R4, so there is no change this IG can make.
hl7.fhir.uv.smart-scheduling-links
hl7.fhir.uv.tools.r4