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/requirements.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Provenance can be just about some elements within a Resource. This is a supported use of Provenance, but it is especially important for AI use-cases. The support comes from extensions added to the extension-registry and explained in later versions of FHIR. The Provenance.target SHALL point at a specific element(s) within the targeted resource using the target element extension or target path extension.'CONFORMANCE_STATEMENT_WORD
WARNING: DocumentReference/ModelCard-sample-huggingface-attached: DocumentReference.identifier[0].system: No definition could be found for URL value 'https://github.com/huggingface/huggingface_hub/tree/main/tests/fixtures/cards' (1 uses)
03 some examples refer to the CHAI github
WARNING: DocumentReference/ModelCard-sample-CHAI-attached: DocumentReference.identifier[0].system: No definition could be found for URL value 'https://github.com/coalition-for-health-ai/mc-schema/blob/main/v0.1/examples/' (1 uses)
WARNING: DocumentReference/ModelCard-sample-CHAI-binary: DocumentReference.identifier[0].system: No definition could be found for URL value 'https://github.com/coalition-for-health-ai/mc-schema/blob/main/v0.1/examples/' (1 uses)
WARNING: DocumentReference/ModelCard-sample-CHAI-web: DocumentReference.identifier[0].system: No definition could be found for URL value 'https://github.com/coalition-for-health-ai/mc-schema/blob/main/v0.1/examples/' (1 uses)
06 Example that uses import to binary ising ig-loader that has no way to provide a definition
WARNING: DocumentReference/ModelCard-sample-CHAI-binary: DocumentReference.content[0].attachment.url: No definition could be found for URL value 'Binary/ModelCard-sample-CHAI-binary-xml' (1 uses)
WARNING: DocumentReference/ModelCard-sample-CHAI-binary: DocumentReference.content[1].attachment.url: No definition could be found for URL value 'Binary/ModelCard-sample-CHAI-binary-pdf' (1 uses)
07 This is a pattern profile that can't be actually applied. It is thus purely illustrative
WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-data'): The Implementation Guide contains no examples for this profile (0 uses)
08 These are made up codesystems for examples
WARNING: Observation/f206: Observation.code.coding[0].system: A definition for CodeSystem 'http://example.org/codes/foobar' could not be found, so the code cannot be validated (1 uses)
WARNING: Observation/glasgow: Observation.component[0].value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://example.org/codes' could not be found, so the code cannot be validated (1 uses)
WARNING: Observation/glasgow: Observation.component[1].value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://example.org/codes' could not be found, so the code cannot be validated (1 uses)
WARNING: Observation/glasgow: Observation.component[2].value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://example.org/codes' could not be found, so the code cannot be validated (1 uses)
09 known issue in an examples
INFORMATION: DiagnosticReport/f202: DiagnosticReport.code: None of the codings provided are in the value set 'LOINC Diagnostic Report Codes' (http://hl7.org/fhir/ValueSet/report-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://snomed.info/sct#104177005) (1 uses)
INFORMATION: Observation/glasgow: Observation.component[0].value.ofType(CodeableConcept).coding[1].extension[0]: The extension http://hl7.org/fhir/StructureDefinition/ordinalValue|5.3.0 is deprecated with the note: 'Replaced by [[[http://hl7.org/fhir/StructureDefinition/itemWeight]]]' (1 uses)
WARNING: Bundle/b3c1f2d4-5c8e-4b0a-9f6d-7c8e1f2d4b5c: Bundle.entry[1].resource/*Observation/608c4de1-1ab6-4bfe-b2e4-dca6b19223f0*/: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
WARNING: Observation/glasgow: Observation.referenceRange[0].high: UCUM Codes that contain human readable annotations like {score} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation (1 uses)
WARNING: Observation/glasgow: Observation.referenceRange[1].high: UCUM Codes that contain human readable annotations like {score} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation (1 uses)
WARNING: Observation/glasgow: Observation.referenceRange[1].low: UCUM Codes that contain human readable annotations like {score} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation (1 uses)
WARNING: Observation/glasgow: Observation.referenceRange[2].low: UCUM Codes that contain human readable annotations like {score} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation (1 uses)
WARNING: Observation/glasgow: Observation.value.ofType(Quantity): UCUM Codes that contain human readable annotations like {score} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked, and the Quantity.unit SHOULD contain the annotation (1 uses)
WARNING: Observation/other-model-result: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
10 inherited from FHIR core
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead' (1 uses)
11 Pinning versions when there are multiples
PIN_VERSION (6 uses)
12 These have been reviewed and are okay for our use-case
INFORMATION: StructureDefinition/AI-InputPrompt: StructureDefinition.snapshot.element[17].fixed.ofType(Coding): The repeating element has a fixed. The fixed will apply to all the repeats (this has not been clear to all users) (1 uses)
INFORMATION: StructureDefinition/AI-Provenance: StructureDefinition.snapshot.element[30].fixed.ofType(CodeableConcept): The repeating element has a fixed. The fixed will apply to all the repeats (this has not been clear to all users) (1 uses)
WARNING: StructureDefinition/AI-InputPrompt: StructureDefinition.snapshot.element[17].fixed.ofType(Coding): For the complex type Coding, consider using a pattern rather than a fixed value to avoid over-constraining the instance (1 uses)
WARNING: StructureDefinition/AI-ModelCard: StructureDefinition.snapshot.element[13].fixed.ofType(CodeableConcept): For the complex type CodeableConcept, consider using a pattern rather than a fixed value to avoid over-constraining the instance (1 uses)
WARNING: StructureDefinition/AI-Provenance: StructureDefinition.snapshot.element[30].fixed.ofType(CodeableConcept): For the complex type CodeableConcept, consider using a pattern rather than a fixed value to avoid over-constraining the instance (1 uses)
13 Examples with extra elements beyond minimal slices
INFORMATION: DocumentReference/ModelCard-sample-CHAI-attached: DocumentReference.content[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-ModelCard% (1 uses)
INFORMATION: DocumentReference/ModelCard-sample-CHAI-binary: DocumentReference.content[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-ModelCard% (1 uses)
INFORMATION: DocumentReference/ModelCard-sample-CHAI-web: DocumentReference.content[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-ModelCard% (1 uses)
INFORMATION: Provenance/AI-full-lorem-ipsum: Provenance.reason[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance% (1 uses)
INFORMATION: Provenance/AI-generated-patient-resource: Provenance.reason[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance% (1 uses)
14 We should do this, but after public comments. Some of the codes will go into existing codeSystems in THO and thus not new codeSystems.
INFORMATION: CodeSystem/AIdeviceTypeCS: CodeSystem: 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) (1 uses)
INFORMATION: CodeSystem/AIinputsCS: CodeSystem: 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) (1 uses)
15 We are not using the C-80 codes for DocumentReference.type
Terminology_TX_NoValid_3_CC (10 uses)
16 The AIconfidence extension is intended to be used anywhere
WARNING: StructureDefinition/AIconfidence: StructureDefinition.context[1]: Review the extension type for AIconfidence: extensions should not have a context of Element unless it's really intended that they can be used anywhere (1 uses)
17 the use of requirements formally will happen in future releases, but is not intended for now
INFORMATION: en/requirements.html: The html source contains the word 'MAY' but it is not in a text phrase marked as a conformance clause: 'In general, inputs should be captured using a Input-Prompt DocumentReference linked through the Provenance, but when specific clinical data is involved a FHIR Bundle or other resource MAY also be linked.' (0 uses)
18 examples need to have Provenance.entities that are representing example ANY other stuff
INFORMATION: Provenance/AI-Authored-Element: Provenance.agent[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-Contributed: Provenance.agent[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-Generated-Lab-Results: Provenance.entity[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-PriorAuth-Provenance: Provenance.agent[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-PriorAuth-Provenance: Provenance.entity[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-full-lorem-ipsum: Provenance.agent[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-full-lorem-ipsum: Provenance.entity[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-full-lorem-ipsum: Provenance.entity[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-full-lorem-ipsum: Provenance.entity[2]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
INFORMATION: Provenance/AI-generated-patient-resource: Provenance.agent[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/aitransparency/StructureDefinition/AI-Provenance|1.0.0-current (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
19 the fixed code is intended to make the profile specific
WARNING: StructureDefinition/AI-Device: StructureDefinition.snapshot.element[39].fixed.ofType(CodeableConcept): For the complex type CodeableConcept, consider using a pattern rather than a fixed value to avoid over-constraining the instance (1 uses)