Validation Results for RTLS

Generated Thu Mar 30 12:53:34 UTC 2023, FHIR version 5.0.0 for hl7.fhir.uv.rtls#1.0.0-ballot (canonical = http://hl7.org/fhir/uv/rtls (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.3.4
Publication Code:	rtls . PackageId = hl7.fhir.uv.rtls, Canonical = http://hl7.org/fhir/uv/rtls
Realm Check for UV:	n/a
Publication Request:	package-id hl7.fhir.uv.rtls version 1.0.0-ballot path http://hl7.org/fhir/uv/rtls/2023May milestone status ballot sequence STU 1.0 desc STU 1.0 initial ballot descmd STU 1.0 initial ballot first true category administration title Real Time Location Services Implementation Guide introduction This implementation guide defines the use of FHIR resources to exchange information that describes the location of patients, providers, staff, equipment, or other permanent assets within a hospital or other healthcare facility. This data is typically exchanged between a healthcare system (e.g. EHR software) and a Real Time Location System (RTLS) that captures, processes, and stores information about the location of tracking tags. The tracking tags are associated with an assigned subject (i.e. patients, providers, assets) and their location data is recorded as the associated subject moves throughout a healthcare facility. This location data has many applications in the healthcare context, such as workflow automation, staff/asset tracking, and patient monitoring. The communication workflows that this implementation guide enables includes tag location updates, association/disassociation from subjects, co-location notifications, status updates, availability updates, and other auxiliary functions (e.g. button presses) a tag may offer. Note that it only provides a communication model for notifying interested parties that these events occurred, and does not define the situational requirements for which each event is applicable. ci-build https://build.fhir.org/ig/HL7/rtls-ig This IG has never been published
Supressed Messages:	11 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.uv.rtls 1.0.0-ballot R5 http://hl7.org/fhir/uv/rtls hl7.terminology.r5 5.0.0 O R5 http://terminology.hl7.org http://terminology.hl7.org/5.0.0 Latest Release is 5.1.0 hl7.fhir.uv.extensions.r5 1.0.0 M R5 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current
Dependent IGs:	no references
Global Profiles:	(none declared)
HTA Analysis:	no Non-HL7 references found
R5 Dependencies:	(none)
Modifier Extensions:	(none)
Previous Version Comparison:	Unable to compare with previous version: Unable to find version history at http://hl7.org/fhir/uv/rtls (Problem #1 with package-list.json at http://hl7.org/fhir/uv/rtls: Invalid HTTP response 404 from http://hl7.org/fhir/uv/rtls/package-list.json?nocache=1680180716628 (Not Found) (content in c:\temp\fhir-http-3.log))
IPA Comparison:	n/a
Summary:	errors = 1, warn = 0, info = 0, broken links = 0

n/a Show Validation Information

C:\temp\hl7.fhir.uv.rtls#1.0.0-ballot\input\resources\rtlsSubscription.xml Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

Example is created but publisher was failing for some reason

• WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsSubscriptionTopic'): The Implementation Guide contains no examples for this profile (847 uses)

Examples are included in Bundle resource profile example

• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsMessageHeader'): The Implementation Guide contains no explicitly linked examples for this profile (847 uses)
• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/uv/rtls/StructureDefinition/rtlsSubscriptionStatus'): The Implementation Guide contains no explicitly linked examples for this profile (847 uses)

Inherited from base resource

• WARNING: StructureDefinition/rtlsMessageHeader: StructureDefinition.snapshot.element[10]: Rule eld-27: 'Mappings SHOULD be unique by key' Failed (0 uses)
• WARNING: StructureDefinition/rtlsMessageHeader: StructureDefinition.snapshot.element[17]: Rule eld-27: 'Mappings SHOULD be unique by key' Failed (0 uses)
• WARNING: StructureDefinition/rtlsMessageHeader: StructureDefinition.snapshot.element[18]: Rule eld-27: 'Mappings SHOULD be unique by key' Failed (0 uses)
• WARNING: StructureDefinition/rtlsSubscription: StructureDefinition.snapshot.element[13]: Rule eld-27: 'Mappings SHOULD be unique by key' Failed (0 uses)
• WARNING: StructureDefinition/rtlsSubscriptionTopic: StructureDefinition.snapshot.element[35].definition: The markdown contains content that appears to be an embedded HTML tag starting at 'UR'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (847 uses)
• WARNING: StructureDefinition/rtlsSubscriptionTopic: StructureDefinition.snapshot.element[53].definition: The markdown contains content that appears to be an embedded HTML tag starting at 'UR'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (847 uses)
• WARNING: StructureDefinition/rtlsSubscriptionTopic: StructureDefinition.snapshot.element[59].comment: The markdown contains content that appears to be an embedded HTML tag starting at 'UR'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (847 uses)
• WARNING: StructureDefinition/rtlsSubscriptionTopic: StructureDefinition.snapshot.element[68].comment: The markdown contains content that appears to be an embedded HTML tag starting at 'UR'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (847 uses)

Errors sorted by type

Extension_EXT_Type