Validation Results for SmartAppLaunch

Generated Thu Sep 14 13:39:59 UTC 2023, FHIR version 4.0.1 for hl7.fhir.uv.smart-app-launch#2.2.0-preview (canonical = http://hl7.org/fhir/smart-app-launch (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.4.5
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:	Publication Request is for v'2.1.0' but package version is v2.2.0-preview Publication Request is for version v2.1.0 which is already published
Supressed Messages:	44 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.uv.smart-app-launch 2.2.0-preview R4 http://hl7.org/fhir/smart-app-launch hl7.terminology.r4 5.3.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 hl7.fhir.uv.extensions.r4 1.0.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Templates: hl7.smart.template#0.0.1 -> hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: current
Dependent IGs:	5 guides
Global Profiles:	(none declared)
HTA Analysis:	no Non-HL7 references found
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (15 uses), fhir-type (56 uses), bindingName (48 uses), isCommonBinding (10 uses), Endpoint (1 uses), bestpractice (7 uses), bestpractice-explanation (7 uses), maxValueSet (6 uses), CommonLanguages (6 uses), EndpointStatus (1 uses), EndpointConnectionType (1 uses), Organization (14 uses), EndpointPayloadType (1 uses), CommonTags (1 uses), standards-status (1 uses), hierarchy (1 uses), ContactEntityType (1 uses), translatable (2 uses), Task (6 uses), ActivityDefinition (2 uses), TaskStatus (2 uses), TaskIntent (2 uses), RequestPriority (2 uses), Encounter (2 uses), Device (4 uses), Practitioner (7 uses), PractitionerRole (7 uses), RelatedPerson (7 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), explicit-type-name (6 uses), expectation (1 uses), Basic (1 uses), BasicResourceTypes (1 uses) hl7.fhir.uv.tools#1.0.0-candidate: ResourceSortExt (54 uses) hl7.terminology.r4#5.3.0: EndpointConnectionType (19 uses), EndpointPayloadType (19 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 2.1.0
IPA Comparison:	n/a
Narratives Suppressed	Organization/examplelabs, Organization/ehchospital, Endpoint/example, Bundle/example1, Organization/examplehealth, Organization/examplehospital1-ehr1, Organization/examplehospital2-ehr2, Bundle/example3, Organization/cust-hosted-examplehealth, Bundle/example5, Endpoint/examplelabs, Organization/examplehospital3-ehr1, Bundle/example2, Organization/example, Endpoint/examplehealth-r2, Endpoint/ehr1-examplehealth, Endpoint/brand1-opt2, Organization/ehpmadison, Organization/brand1-opt2, Endpoint/examplehealth-r4, Endpoint/examplehospital1-ehr1, Organization/brand2-opt2, Organization/examplehospital3-ehr2, Endpoint/brand2-opt2, Bundle/example4, Endpoint/examplehospital2-ehr2, Bundle/example6, Task/task-for-ehr-launch, Task/task-for-standalone-launch, Basic/app-state
Summary:	errors = 9, warn = 28, info = 0, broken links = 3

n/a Show Validation Information

input/examples/Organization-brand1-opt2.json Show Validation Information (1)

input/examples/Organization-brand2-opt2.json Show Validation Information (1)

input/examples/Organization-cust-hosted-ehr1-examplehealth.json Show Validation Information (1)

input/examples/Organization-example.json Show Validation Information (1)

input/examples/Organization-examplehealth.json Show Validation Information (1)

input/examples/Organization-examplehospital1-ehr1.json Show Validation Information (1)

input/examples/Organization-examplehospital2-ehr2.json Show Validation Information (1)

input/examples/Organization-examplelabs.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

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

• Code System URI 'https://myapp.example.org' is unknown so the code cannot be validated (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: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example1: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example1: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[2].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[3].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example2: Bundle.entry[4].resource/*Organization/examplehealth*/: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example3: Bundle.entry[2].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example4: Bundle.entry[2].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example5: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example5: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example5: Bundle.entry[2].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example5: Bundle.entry[3].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example6: Bundle.entry[0].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Bundle/example6: Bundle.entry[1].resource: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/brand1-opt2: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/brand2-opt2: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/ehr1-examplehealth: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/example: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/examplehealth-r2: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/examplehealth-r4: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/examplehospital1-ehr1: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/examplehospital2-ehr2: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Endpoint/examplelabs: Endpoint: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/brand1-opt2: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/brand2-opt2: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/cust-hosted-examplehealth: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/ehchospital: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/ehpmadison: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/example: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplehealth: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplehospital1-ehr1: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplehospital2-ehr2: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplehospital3-ehr1: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplehospital3-ehr2: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Organization/examplelabs: Organization: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Task/task-for-ehr-launch: Task: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)
• WARNING: Task/task-for-standalone-launch: Task: Rule dom-6: 'A resource should have narrative for robust management' Failed (Best Practice Recommendation) (1 uses)

Errors sorted by type

Reference_REF_Aggregation