Error: realms in canonical and package id are different: uv vs fhir
n/a
Language Info:
This IG has no language information
Publication Request:
package-id
hl7.fhir.uv.tools
version
0.4.1
path
http://hl7.org/fhir/tools/0.4.1
Pub-Mode
technical-correction
status
informative
Release-Label
Release 0.2.0
Sequence (Group)
Releases (current: 'Releases', others = n/a)
desc
Technical Correction to fix paths in R4 sub-package
RelatedIgs
(None Found)
Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
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)
Hyperlink '#TestCases.suite.setup' at 'div/div/table/tr/td/a' for 'setup' resolves to multiple targets ($/differential/element/id, $/snapshot/element/id, $/text/div/div/table/tr/td/a/@name)TYPE_SPECIFIC_CHECKS_DT_XHTML_MULTIPLE_MATCHES
Hyperlink '#CDSHooksResponse.cards.suggestions.actions' at 'div/div/table/tr/td/a' for 'actions' resolves to multiple targets ($/differential/element/id, $/snapshot/element/id, $/text/div/div/table/tr/td/a/@name)TYPE_SPECIFIC_CHECKS_DT_XHTML_MULTIPLE_MATCHES
Review the extension type for matchetype-count: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for matchetype-optional: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
Review the extension type for matchetype-sort: extensions should not have a context of Element unless it's really intended that they can be used anywhereSD_CONTEXT_SHOULD_NOT_BE_ELEMENT
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) (1 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) (1 uses)
These won't ever be move to THO
CODESYSTEM_THO_CHECK (15 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 (93 uses)
The Implementation Guide contains no examples for this extension (41 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)
Review the extension type for matchetype-count: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for matchetype-optional: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Review the extension type for matchetype-sort: extensions should not have a context of Element unless it's really intended that they can be used anywhere
Hyperlink '#TestCases.suite.setup' at 'div/div/table/tr/td/a' for 'setup' resolves to multiple targets ($/differential/element/id, $/snapshot/element/id, $/text/div/div/table/tr/td/a/@name)
Hyperlink '#CDSHooksResponse.cards.suggestions.actions' at 'div/div/table/tr/td/a' for 'actions' resolves to multiple targets ($/differential/element/id, $/snapshot/element/id, $/text/div/div/table/tr/td/a/@name)
hl7.fhir.uv.tools
