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/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The following matrix maps common FAST scenarios to the minimum identity assurance needed for the organizational layer. The matrix is non-normative for STU3 but is intended to harden into SHALL/SHOULD language as adoption matures.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
No conformance term found in the text: B.7.3) resolves to the healthcare organization via the ECR. This is the canonical "side-by-side" pattern in CONFORMANCE_STATEMENT_NOCONFWORD
en/LEI_vLEI_Profiling.html
information
No conformance term found in the text: B.8.4 and CONFORMANCE_STATEMENT_NOCONFWORD
en/LEI_vLEI_Profiling.html
information
No conformance term found in the text: B.8.2, CONFORMANCE_STATEMENT_NOCONFWORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Cardinality guidance. This IG SHOULD treat the LEI as the preferred organizational identifier where one is available, while continuing to permit NPI, Tax ID, and OID identifiers in the same Organization.identifier array. Slicing on system allows multiple identifiers to coexist without ambiguity.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'The FAST Identity work group SHOULD define a single extension on Organization.identifier (slice: LEI) for this purpose. A working name is org-vlei-anchor. The extension should carry, at minimum:'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'For healthcare exchange, the OOBI URL SHOULD resolve to an endpoint that the organization itself controls — typically a path under the organization's primary domain. The recommended pattern is to publish the OOBI under a stable, well-known path:'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Implementers SHOULD ensure that:'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'An organization MAY publish more than one OOBI URL — for example, one on its own domain and one or more provided by witness operators — for resilience and for independent attestation. The oobi extension cardinality is therefore 1..*. Verifiers SHOULD be prepared to try alternate OOBIs if one is unreachable, and MUST require that all reachable OOBIs resolve to materially consistent KERI state for the same AID. Where the relying party's policy specifies a witness threshold, the verifier MUST confirm that threshold has been met before accepting a credential.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'An organization MAY publish more than one OOBI URL — for example, one on its own domain and one or more provided by witness operators — for resilience and for independent attestation. The oobi extension cardinality is therefore 1..*. Verifiers SHOULD be prepared to try alternate OOBIs if one is unreachable, and MUST require that all reachable OOBIs resolve to materially consistent KERI state for the same AID. Where the relying party's policy specifies a witness threshold, the verifier MUST confirm that threshold has been met before accepting a credential.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ''CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Provenance is the natural FHIR carrier for "this assertion was made by X on behalf of Y" and SHOULD be used for transactions where attribution must survive later dispute (matrix row 10).'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'For audit and attribution, Provenance.agent.who SHOULD reference whatever resource represents the delegate, with Provenance.agent.onBehalfOf referencing the Organization and a credential pointer to the ECR.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Human co-signing requirement, where regulated. For actions that require human accountability (e.g., final clinical decisions, executed claims approvals), the agent's ECR SHOULD require co-presentation with a human's OOR or ECR carrying appropriate authority, so that the relying party can enforce policy by inspecting credentials rather than maintaining out-of-band rules.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'For attribution, Provenance.agent SHOULD record: agent.who referencing the agent's resource representation; agent.type (or an extension) distinguishing software / AI agents from human actors; agent.onBehalfOf referencing the Organization; and a pointer to the agent's ECR credential anchor.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'For regulated actions requiring human co-sign, Provenance.agent MAY include both the AI agent and the responsible human, each with their own credential pointers — recording that the action was prepared by the agent and authorized by the human.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Notes. This use case is structurally similar to Org ↔ IT Vendor delegation (a non-human system actor authorized via ECR) but with three healthcare-specific tightening factors: (1) ECR scopes for AI agents SHOULD be narrower and more frequently revisited than for IT vendors, because agent capabilities and risk profiles evolve as models change; (2) provenance is mandatory, not optional — every regulated agent action SHOULD be recorded with full credential attribution, both for accountability and to enable later dispute resolution; and (3) agent ECRs SHOULD encode any oversight or human-co-sign requirements as part of the credential's scope, so that those requirements travel with the credential and are enforceable by any relying party. Agent-to-agent delegation chains MAY be expressed via nested ECRs (analogous to subcontracting in §B.8.3), but SHOULD be kept short for auditability.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_Profiling.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Conformance language. As adoption matures, the matrix in §B.4.1 should be re-expressed as SHALL / SHOULD statements bound to specific use case profiles.'CONFORMANCE_STATEMENT_WORD
en/LEI_vLEI_primer.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'A vLEI credential also carries one or more Out-Of-Band Introduction (OOBI) URLs — these are how a relying party bootstraps verification of the credential's KERI key state. In a healthcare context, an OOBI URL SHOULD point to an endpoint that the organization itself controls (typically under a .well-known path on the organization's primary domain). This serves two purposes at once: it is the verification anchor for the vLEI, and it can simultaneously act as an informational discovery endpoint — for example, advertising the organization's FHIR exchange capabilities, supported networks, endpoint metadata, or trust contacts. The OOBI thus does double duty as a cryptographic verification handle and as a service-discovery touchpoint, which is uniquely useful for healthcare exchange. (The mechanics of this pattern, including how the OOBI URL is conveyed in a FHIR Organization resource, are profiled in §B.5.2.)'CONFORMANCE_STATEMENT_WORD
en/OperationDefinition-IDI-match.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' This extension of the $match operation is further constrained to meet the additional requirements found in this IG. One of the IDI Patient profiles outline in this guide (IDI-Patient, IDI-Patient-L0, IDI-Patient-L1, IDI-Patient-L2) SHALL be used as the input for the match request. An IDI-Match-Bundle will be returned to the requesting entity. This Bundle will contain the full URLs of the sourced information, an Organization resource, and any matched Patient resources. 'CONFORMANCE_STATEMENT_WORD
en/StructureDefinition-idi-match-bundle.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' Bundle requirements for responders to an $IDI-match request. Responders SHALL include only absolute URL FHIR server addresses, and SHALL NOT include URIs for UUIDs or OIDs, in the fullURL returned. This additional constraint on a response to $IDI-match is intended to help recipients understand the source of the response, particularly when a patient match is invoked as part of record location–such that the URL would be needed for additional health data requests performed subsequent to matching. Additionally, the .identifier.assigner element within the returned Bundle SHOULD include an Organization resource that contains at least one appropriate contact point. 'CONFORMANCE_STATEMENT_WORD
The link '../examples.ttl.zip' for "Turtle" cannot be resolvedHTML_LINK_CHECK_FAILED
en/changelog.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'MUST to SHALL'CONFORMANCE_STATEMENT_WORD
en/identity.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'The vLEI and/or LEI SHALL be encoded in an Identifier datatype as follows:'CONFORMANCE_STATEMENT_WORD
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)CODESYSTEM_THO_CHECK
--
CodeSystem.concept[0] (l1/c3658)
warning
HL7 Defined CodeSystems should ensure that every concept has a definitionCODESYSTEM_CONCEPT_NO_DEFINITION
ImplementationGuide/hl7.fhir.us.identity-matching: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide.dependsOn[2] (l1/c2604)
warning
The ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be consideredIG_DEPENDENCY_VERSION_WARNING_OLD
No definition could be found for URL value 'https://examplehealth.org/.well-known/vlei/oobi/EBfdlu8R27Fbx-ehrqwImnK-8Cm79sqbAQ4MmvEAYqao'Type_Specific_Checks_DT_URL_Resolve
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'MSG_DEPENDS_ON_DEPRECATED_NOTE
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users)SD_VALUE_TYPE_REPEAT_HINT
--
StructureDefinition.snapshot (l1/c93259)
warning
The slice 'CLIA' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c93259)
warning
The slice 'NAIC' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient ProfileUS_CORE_DERIVATION
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)SD_PATH_SLICING_DEPRECATED
The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users)SD_VALUE_TYPE_REPEAT_HINT
--
StructureDefinition.snapshot (l1/c75528)
warning
The slice 'CLIA' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
--
StructureDefinition.snapshot (l1/c75528)
warning
The slice 'NAIC' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true
This IG uses US Core 6.1.0 because of TEFCA requirements
The ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 8.0.1. This reference is getting old and the more recent version should be considered (0 uses)
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)
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)
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)
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)
The ImplementationGuide uses package hl7.fhir.us.core#6.1.0 released on 2023-06-30, but the most recent appropriate version is 9.0.0. This reference is getting old and the more recent version should be considered
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing)
US FHIR Usage rules require that all profiles on Patient derive from the core US profile. See https://confluence.hl7.org/display/CGP/US+Core+Variance+Request+Process. Comparison with US Core Patient Profile
hl7.fhir.us.identity-matching
hl7.terminology.r4