The rendered versions of a number of conformance resources (CodeSystem, StructureDefinition, etc. - and presumably eventually all of them) include support for rendering an extension that declares that resource's maturity level. The section includes a hyperlink into the core specification pointing to the page that describes the notion of maturity and the meaning of each of the levels. Pull request https://github.com/HL7/fhir-ig-publisher/pull/72 addressed a problem where many of the places that included the link weren't actually pointing to the core spec, but instead expected to find the page locally within the IG. It also fixed an issue where one of the links was in fact pointing to the core specification, but was pointing to the IG-specific version of the spec (i.e. the version the IG was built against) while still having a hard-coded page. This was a problem because that link didn't exist in DSTU2 (or more specifically it existed at a different location). As well, the rules followed by IGs are actually the 'current' maturity rules, not those that existed in DSTU2 or STU3.
However, the IG publisher generally doesn't like references to http://hl7.org/fhir because in most cases, links should be to a specific version of FHIR. As a result, the most recent fix is likely to generate additional issues. The fix should be re-considered and replaced with something that meets the need:
points to a link that will resolve
points to the release that describes the rules being used
lmckenzi
commented
1 year ago
The rendered versions of a number of conformance resources (CodeSystem, StructureDefinition, etc. - and presumably eventually all of them) include support for rendering an extension that declares that resource's maturity level. The section includes a hyperlink into the core specification pointing to the page that describes the notion of maturity and the meaning of each of the levels. Pull request https://github.com/HL7/fhir-ig-publisher/pull/72 addressed a problem where many of the places that included the link weren't actually pointing to the core spec, but instead expected to find the page locally within the IG. It also fixed an issue where one of the links was in fact pointing to the core specification, but was pointing to the IG-specific version of the spec (i.e. the version the IG was built against) while still having a hard-coded page. This was a problem because that link didn't exist in DSTU2 (or more specifically it existed at a different location). As well, the rules followed by IGs are actually the 'current' maturity rules, not those that existed in DSTU2 or STU3.
However, the IG publisher generally doesn't like references to http://hl7.org/fhir because in most cases, links should be to a specific version of FHIR. As a result, the most recent fix is likely to generate additional issues. The fix should be re-considered and replaced with something that meets the need: