Validation Results for SmartAppLaunch

Generated Tue May 14 20:31:24 UTC 2024, FHIR version 4.0.1 for hl7.fhir.uv.smart-app-launch#2.2.0 (canonical = http://hl7.org/fhir/smart-app-launch (history)). See Errors Only

Quality Checks
Publisher Version:	IG Publisher Version: v1.6.7
Publication Code:	smart-app-launch . PackageId = hl7.fhir.uv.smart-app-launch, Canonical = http://hl7.org/fhir/smart-app-launch
Realm Check for UV:	Error: realms in canonical and package id are different: uv vs fhir n/a
Publication Request:	Version 2.2.0 has already been published Publication Request is for version v2.2.0 which is already published
Supressed Messages:	41 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.uv.smart-app-launch 2.2.0 R4 http://hl7.org/fhir/smart-app-launch hl7.fhir.uv.extensions 5.1.0 M R5 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0 FHIR Version Mismatch hl7.terminology.r5 5.5.0 M R5 http://terminology.hl7.org http://terminology.hl7.org/5.5.0 FHIR Version Mismatch hl7.terminology 5.5.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/5.5.0 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Latest Release is 5.1.0 Templates: hl7.smart.template#0.0.1 -> hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.1.0
Dependent IGs:	10 guides
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4 (details)
HTA Analysis:	no Non-HL7 references found
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), Organization (13 uses), CommonLanguages (6 uses), OrganizationType (1 uses), ContactEntityType (1 uses), Basic (1 uses), BasicResourceTypes (1 uses), Practitioner (7 uses), PractitionerRole (7 uses), RelatedPerson (7 uses), Task (6 uses), ActivityDefinition (2 uses), TaskStatus (2 uses), TaskIntent (2 uses), RequestPriority (2 uses), Encounter (2 uses), Device (4 uses), ProcedurePerformerRoleCodes (2 uses), CareTeam (2 uses), HealthcareService (2 uses), Location (2 uses), Coverage (2 uses), ClaimResponse (2 uses), Provenance (2 uses), Group (2 uses), CommonTags (1 uses), Endpoint (1 uses), EndpointStatus (1 uses), EndpointConnectionType (1 uses), EndpointPayloadType (1 uses) hl7.fhir.uv.tools#0.2.0: ResourceSortExt (18 uses) hl7.terminology#5.5.0: OrganizationType (8 uses), EndpointConnectionType (8 uses), EndpointPayloadType (8 uses)
Modifier Extensions:	(none)
Previous Version Comparison:
IPA Comparison:	n/a
IPS Comparison:	n/a
Narratives Suppressed	Basic/app-state, Bundle/example1, Bundle/example2, Bundle/example3, Bundle/example4, Task/task-for-ehr-launch, Task/task-for-standalone-launch
Summary:	errors = 0, warn = 0, info = 0, broken links = 0

n/a Show Validation Information

input/resources/Basic-app-state.json Show Validation Information (1)

input/resources/Bundle-example1.json Show Validation Information (5)

input/resources/Bundle-example2.json Show Validation Information (11)

input/resources/Bundle-example3.json Show Validation Information (7)

input/resources/Bundle-example4.json Show Validation Information (7)

input/resources/CapabilityStatement-smart-app-state-server.json Show Validation Information (1)

input/resources/CodeSystem-smart-codes.json Show Validation Information (1)

input/resources/ImplementationGuide-hl7.fhir.uv.smart-app-launch.json Show Validation Information (1)

input/resources/StructureDefinition-patient-access-brand.json Show Validation Information (1)

input/resources/StructureDefinition-smart-app-state-basic.json Show Validation Information (1)

input/resources/StructureDefinition-task-ehr-launch.json Show Validation Information (1)

input/resources/StructureDefinition-task-standalone-launch.json Show Validation Information (1)

input/resources/StructureDefinition-user-access-brands-bundle.json Show Validation Information (1)

input/resources/StructureDefinition-user-access-endpoint.json Show Validation Information (1)

input/resources/Task-task-for-ehr-launch.json Show Validation Information (1)

input/resources/Task-task-for-standalone-launch.json Show Validation Information (1)

input/resources/ValueSet-smart-launch-info.json Show Validation Information (1)

input/resources/ValueSet-smart-launch-types.json Show Validation Information (1)

input/resources/ValueSet-user-access-category.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

Example URI in example.org domain does not need to be validated

• INFORMATION: Basic/app-state: Basic.code.coding[0].system: A definition for CodeSystem 'https://myapp.example.org' could not be found, so the code cannot be validated (1 uses)

Examples are validated in the context of their Brand Bundles

• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/smart-app-launch/StructureDefinition/user-access-brand'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)
• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/smart-app-launch/StructureDefinition/user-access-endpoint'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)

Ignoring info about references to draft code system for Organization type, since we've beek asked to use this draft code system

• INFORMATION: Bundle/example1: Bundle.entry[0].resource/*Organization/examplelabs*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example1: Bundle.entry[1].resource/*Endpoint/examplelabs*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example2: Bundle.entry[0].resource/*Organization/examplehealth*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example2: Bundle.entry[1].resource/*Organization/ehchospital*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example2: Bundle.entry[2].resource/*Organization/ehpmadison*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example2: Bundle.entry[3].resource/*Endpoint/examplehealth-r2*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example2: Bundle.entry[4].resource/*Endpoint/examplehealth-r4*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example3: Bundle.entry[0].resource/*Organization/examplehospital*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example3: Bundle.entry[1].resource/*Endpoint/examplehospital-ehr1*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example3: Bundle.entry[2].resource/*Endpoint/examplehospital-ehr2*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example4: Bundle.entry[0].resource/*Organization/brand1*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example4: Bundle.entry[1].resource/*Organization/brand2*/.type[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/organization-type|2.0.0 (1 uses)
• INFORMATION: Bundle/example4: Bundle.entry[2].resource/*Endpoint/coequal-example*/.payloadType[0]: Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: StructureDefinition/user-access-endpoint: StructureDefinition.differential.element[10].pattern.ofType(CodeableConcept): Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)
• INFORMATION: StructureDefinition/user-access-endpoint: StructureDefinition.differential.element[4].pattern.ofType(Coding): Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-connection-type|2.1.0 (1 uses)
• INFORMATION: StructureDefinition/user-access-endpoint: StructureDefinition.snapshot.element[12].pattern.ofType(Coding): Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-connection-type|2.1.0 (1 uses)
• INFORMATION: StructureDefinition/user-access-endpoint: StructureDefinition.snapshot.element[25].pattern.ofType(CodeableConcept): Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-payload-type|2.0.0 (1 uses)

The 'no narrative' parameter is used for these resources instances because they are infrastructural in nature and used in strictly managed trading systems where all systems share a common data model and additional text is unnecessary.

• WARNING: Basic/app-state: Basic: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example1: Bundle.entry[0].resource/*Organization/examplelabs*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example1: Bundle.entry[1].resource/*Endpoint/examplelabs*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[0].resource/*Organization/examplehealth*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[1].resource/*Organization/ehchospital*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[2].resource/*Organization/ehpmadison*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[3].resource/*Endpoint/examplehealth-r2*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[4].resource/*Endpoint/examplehealth-r4*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[0].resource/*Organization/examplehospital*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[1].resource/*Endpoint/examplehospital-ehr1*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[2].resource/*Endpoint/examplehospital-ehr2*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[0].resource/*Organization/brand1*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[1].resource/*Organization/brand2*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[2].resource/*Endpoint/coequal-example*/: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Task/task-for-ehr-launch: Task: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)
• WARNING: Task/task-for-standalone-launch: Task: Constraint failed: dom-6: 'A resource should have narrative for robust management' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)

These example resources have content that can be inferred, and a standalone examples page providing more detail

• WARNING: Unable to find ImplementationGuide.definition.resource.description for the resource Bundle/example1. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list. (1 uses)
• WARNING: Unable to find ImplementationGuide.definition.resource.description for the resource Bundle/example2. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list. (1 uses)
• WARNING: Unable to find ImplementationGuide.definition.resource.description for the resource Bundle/example3. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list. (1 uses)
• WARNING: Unable to find ImplementationGuide.definition.resource.description for the resource Bundle/example4. Descriptions are strongly encouraged if they cannot be inferred from the resource to allow proper population of the artifact list. (1 uses)

smart-codes is granted an exemption, details at https://confluence.hl7.org/display/TSMG/2024-03-18+TSMG+Agenda+and+Minutes

• INFORMATION: CodeSystem/smart-codes: 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)

Errors sorted by type