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)
Example observation in this IG are supposed to be device generated with often an unknown performer. There will be text in the IG to explain this.
Best Practice Recommendation: In general, all observations should have a performer (5 uses)
Moving code systems and URLs to THO will be discussed in the near future. For now, these warnings can be ignored safely.
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) (3 uses)
Publisher process choice - can safely be ignored
The value set expansion is too large, and only a subset has been displayed (6 uses)
These profiles are only used to define mappings and are not intended to be used for validation. These warnings can be ignored safely.
Observation is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package) (1 uses)
Patient is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package) (1 uses)
Practitioner is labeled as an abstract type, but no concrete descendants were found (check definitions - this is usually an error unless concrete definitions are in some other package) (1 uses)
These warnings are caused by checking a slice with an MDC code against a the BP profile in FHIR core. These messages are expected and can be ignored safely.
This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/bp|4.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (3 uses)
extension labeled as draft on purpose, so that OO can make changes if needed when it moves to the extension pack.
The resource status 'draft' and the standards status 'trial-use' may not be consistent and should be reviewed (1 uses)
extension used in FHIR core R4 that is now deprecated - this warning can be ignored safely
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)
pick 1.0.0 to avoid a warning about the version of the metric-availability code system.
Pinned the version of http://terminology.hl7.org/CodeSystem/metric-availability to 1.0.0 from choices of 1.0.0 (hl7.terminology.r4#7.2.0), 1.0.0-ballot3 (hl7.fhir.uv.pocd#1.0.0-ballot3) (1 uses)
hl7.fhir.uv.pocd
hl7.terminology.r4
