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)
en/OperationDefinition-cache-control.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' Manage a terminology client cache on the server. A client that repeatedly validates or expands against the same value sets and code systems can register those resources with the server once, under a server-issued cache-id, and then refer to them by url on subsequent calls instead of re-sending them each time. The protocol is explicit: the client calls this operation with mode=start to create a cache; the server allocates the cache and returns its identifier in the cache-id output parameter. The client then sends that identifier as the X-Cache-Id HTTP header on subsequent $validate-code and $expand requests. Resources are populated into the cache by sending them (as tx-resource, or as the primary valueSet/codeSystem) on those requests, or by front-loading them in the mode=start call. By default a cache is sealed: it holds only the resources front-loaded at mode=start and does not grow. A client that wants the cache to accumulate resources as they are seen (needed for incremental population and batch front-loading) requests an unsealed cache by sending sealed=false at mode=start. The mode=start response always reports, in the sealed output parameter, which kind of cache was created. When finished, the client calls mode=end to release the cache (the server will otherwise time it out). A server releases a cache that has not been used for some time. Because a client's own local caching can absorb its terminology work for long stretches, a client may still depend on a server-side cache it has not touched for a while; mode=check exists for this case. It reports whether the cache is still there, and checking counts as use, so a client that expects to go quiet can keep its cache alive by checking periodically. The response reports the server's idle timeout, so the client can size that interval to the server rather than guessing. Because the server owns the cache-id, it can authoritatively report when a client refers to a cache it does not have (never created, expired, or released): such requests fail with an OperationOutcome whose issue carries the code cache-id-unknown from http://hl7.org/fhir/tools/CodeSystem/tx-issue-type. This is distinct from a value set or code system genuinely not being found, so a client can tell a stale cache from an authoring error. This operation affects server state and SHOULD be invoked with POST; servers MAY also accept GET for convenience. 'CONFORMANCE_STATEMENT_WORD
en/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
en/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
en/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-1a" class="fhir-conformance"><p>Start of rule</p> <p>This is a broken additional conformance statement because only the title has conformance language:</p> <ul> <li>Clause 1</li> <li>Clause 2</li> </ul></div>", so conformance statement not extracted.CONFORMANCE_STATEMENT_NOCONFWORD
es/OperationDefinition-cache-control.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' Manage a terminology client cache on the server. A client that repeatedly validates or expands against the same value sets and code systems can register those resources with the server once, under a server-issued cache-id, and then refer to them by url on subsequent calls instead of re-sending them each time. The protocol is explicit: the client calls this operation with mode=start to create a cache; the server allocates the cache and returns its identifier in the cache-id output parameter. The client then sends that identifier as the X-Cache-Id HTTP header on subsequent $validate-code and $expand requests. Resources are populated into the cache by sending them (as tx-resource, or as the primary valueSet/codeSystem) on those requests, or by front-loading them in the mode=start call. By default a cache is sealed: it holds only the resources front-loaded at mode=start and does not grow. A client that wants the cache to accumulate resources as they are seen (needed for incremental population and batch front-loading) requests an unsealed cache by sending sealed=false at mode=start. The mode=start response always reports, in the sealed output parameter, which kind of cache was created. When finished, the client calls mode=end to release the cache (the server will otherwise time it out). A server releases a cache that has not been used for some time. Because a client's own local caching can absorb its terminology work for long stretches, a client may still depend on a server-side cache it has not touched for a while; mode=check exists for this case. It reports whether the cache is still there, and checking counts as use, so a client that expects to go quiet can keep its cache alive by checking periodically. The response reports the server's idle timeout, so the client can size that interval to the server rather than guessing. Because the server owns the cache-id, it can authoritatively report when a client refers to a cache it does not have (never created, expired, or released): such requests fail with an OperationOutcome whose issue carries the code cache-id-unknown from http://hl7.org/fhir/tools/CodeSystem/tx-issue-type. This is distinct from a value set or code system genuinely not being found, so a client can tell a stale cache from an authoring error. This operation affects server state and SHOULD be invoked with POST; servers MAY also accept GET for convenience. 'CONFORMANCE_STATEMENT_WORD
es/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
es/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
es/parameterized-valuesets.html
information
Unable to find a conformance word for the language es in the text "<div summary="Additional markdown conformance statement SHALL apply" id="conf-1a" class="fhir-conformance"><p>Start of rule</p> <p>This is a broken additional conformance statement because only the title has conformance language:</p> <ul> <li>Clause 1</li> <li>Clause 2</li> </ul></div>", so conformance statement not extracted.CONFORMANCE_STATEMENT_NOCONFWORD
The OID '2.16.840.1.113883.4.642.40.1.42.72' is also used by type-profile-style in /scratch/repo/input/resources/structuredefinition-type-profile-style
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
The OID '2.16.840.1.113883.4.642.40.1.42.73' has already been used by CDSHookOrderDispatchContext in /scratch/repo/input/resources/structuredefinition-CDSHookOrderDispatchContext
The OID '2.16.840.1.113883.4.642.40.1.42.72' has already been used by CDSHookEncounterStartContext in /scratch/repo/input/resources/structuredefinition-CDSHookEncounterStartContext
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 (118 uses)
SD_CONTEXT_SHOULD_NOT_BE_ELEMENT (3 uses)
The Implementation Guide contains no examples for this extension (50 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)
The extension http://hl7.org/fhir/StructureDefinition/codesystem-use-markdown|5.3.0 is deprecated with the note: 'This extension is deprecated as the Terminology Infrastructure work group felt there wasn't a use case for the extension'
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)
hl7.fhir.uv.tools
hl7.terminology.r5