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)
StructureDefinition-profile-mapping.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This extension defines a relationship between a search string and a profile. Any resource that meets a given search string will be expected to conform to the particular profile. If more than one profile is nominated for a search string, resources SHALL conform to all the listed profiles. The last extension can be without a search matches and remaining resources'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'If 'true', means that 'conformance' should behave as though it also had a code of 'SHALL NOT' (as introduced in FHIR R6).'CONFORMANCE_STATEMENT_WORD
artifacts.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' Extension definition for Mapping between API and Profile. CapabilityStatement.rest.resource.profile has two different profile statements: profile - the overall system profile for a resource supportedProfile 0..* - a particular profile that the system supports What is missing from this picture is defining which resources conform to which profile. Sometimes, of course, it's impossible to define this, but quite often, there's an algorithmic relationship that a server or client could use to know that resources with a particular set of values will or should conform to a given profile. This extension defines a relationship between a search string and a profile. Any resource that meets a given search string will be expected to conform to the particular profile. If more than one profile is nominated for a search string, resources SHALL conform to all the listed profiles. The last extension can be without a search matches and remaining resources This extension repeats, and order is important - once a match is found, this profile is the one that applies. Todo: If this extension is useful, it will be moved to the core extensions pack 'CONFORMANCE_STATEMENT_WORD
index.html
information
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'Allows a statement to have a 'conformance' level of SHALL NOT, which was not introduced until R6 'CONFORMANCE_STATEMENT_WORD
parameterized-valuesets.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The expression SHALL be a FHIRPath expression, using a restricted subset of the FHIRPath specification. The following functions SHALL not be used, and servers do not make them available: resolve() elementDefinition() slice() conformsTo() any functions defined for the Type Factory and the General Service API Note that the terminology API is expected to be available 'CONFORMANCE_STATEMENT_WORD
parameterized-valuesets.html
information
Unable to find a conformance word for the language en in the text "<div summary="Additional markdown conformance statement SHALL apply" id="conf-1" class="fhir-conformance"><p>Title</p> <p>This is an additional conformance statement:</p> <ul> <li>Clause 1</li> <li>Clause 2</li> </ul></div>", so conformance statement not extracted.CONFORMANCE_STATEMENT_NOCONFWORD
parameterized-valuesets.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'All parameters that are used in the expansion SHALL be included in the ValueSet.expansion.parameters element of the resulting ValueSet.'CONFORMANCE_STATEMENT_WORD
Constraint failed: eld-24: 'pattern[x] should be used rather than fixed[x] (fixed.exists().not())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-24
Constraint failed: eld-24: 'pattern[x] should be used rather than fixed[x] (fixed.exists().not())' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation)http://hl7.org/fhir/StructureDefinition/ElementDefinition#eld-24
Hyperlink '#CDSHooksResponse.cards.suggestions.actions' at 'div/div/table/tr/td/a' for 'actions' resolves to multiple targets ($/text/div/div[0]/table/tr[16]/td[0]/a[1]/@name, $/snapshot/element/id, $/differential/element/id)TYPE_SPECIFIC_CHECKS_DT_XHTML_MULTIPLE_MATCHES
Extensions and id aren't possible here, so fixed is appropriate
WARNING: StructureDefinition/CDSHooksRequest: StructureDefinition.differential.element[6]: Constraint failed: eld-24: 'pattern[x] should be used rather than fixed[x]' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation) (0 uses)
WARNING: StructureDefinition/CDSHooksRequest: StructureDefinition.snapshot.element[8]: Constraint failed: eld-24: 'pattern[x] should be used rather than fixed[x]' (defined in http://hl7.org/fhir/StructureDefinition/ElementDefinition) (Best Practice Recommendation) (0 uses)
These won't ever be move to THO
CODESYSTEM_THO_CHECK (16 uses)
This isn't a conformance usage
INFORMATION: StructureDefinition-requirements-statementshallnot.html: The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause (0 uses)
Will be cleaned up when moving CDS hooks content to CDSHooks spec
CODESYSTEM_PROPERTY_UNKNOWN_CODE (4 uses)
Will be fixed by a future extensions pack release
MSG_DRAFT (0 uses)
this is ok
MSG_DEPRECATED (114 uses)
SD_CONTEXT_SHOULD_NOT_BE_ELEMENT (3 uses)
The Implementation Guide contains no examples for this extension (48 uses)
The element Extension.extension.value[x] has a binding, and has multiple types subject to bindings ([code, string]). The binding will apply to all the types (1 uses)
The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk (1 uses)
Hyperlink '#CDSHooksResponse.cards.suggestions.actions' at 'div/div/table/tr/td/a' for 'actions' resolves to multiple targets ($/text/div/div[0]/table/tr[16]/td[0]/a[1]/@name, $/snapshot/element/id, $/differential/element/id)