The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: ' Profile on Organization to convey a User Access Brand. For background and context, see User Access Brands Overview. In addition to the core data elements on Organization, two key extensions are used in this profile: http://hl7.org/fhir/StructureDefinition/organization-brand conveys the organization's logo(s) and other top-level branding details. See definitions for details. http://hl7.org/fhir/StructureDefinition/organization-portal conveys the details of a user portal and its associated FHIR endpoints. See definitions for details. Notes: 0..1 MS partOf Conveys that an affiliate Brand response for providing this Brand's user access. The hierarchy of "access provided by" links SHALL NOT exceed a depth of two (i.e., a Brand either includes portal details or links directly to a Brand that provides them). 0..* MS identifier Conveys identifiers that apps can use to link this Brand across publishers or with external data sets. EHRs SHALL support customer-supplied identifiers (system and value). It is RECOMMENDED that each Brand include an identifier where system is urn:ietf:rfc: 3986 (meaning the identifier is a URL) and value is the HTTPS URL for the Brand's primary web presence, omitting any "www." prefix from the domain and omitting any path component. For example, since the main web presence of Boston Children's Hospital is https://www.childrenshospital.org/, a recommended identifier would be: {"system": "urn:ietf:rfc:3986","value": "https://childrenshospital.org"} 'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' JSON FHIR Bundle (type: collection) of Organizations and Endpoints that is hosted at a stable, publicly available, publicly disclosed location. For background and context, see User Access Brands Overview. Bundle Entries include: User Access Endpoint Profile resources. User Access Brand (Organization) resources. Vendors SHALL publish at least a "primary brand" for each endpoint and SHOULD support the publication of a more detailed Brand hierarchy. Brand Bundles SHALL populate Bundle.timestamp to advertise the timestamp of the last change to the contents. In addition, Brand Bundles SHOULD populate Bundle.entry.resource.meta.lastUpdated with a more detailed timestamp if the system tracks updates per Resource. 'CONFORMANCE_STATEMENT_WORD
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: ' Profile on Endpoint associated with a User Access Brand. For background and context, see User Access Brands Overview. In addition to the core data elements on Endpoint, one key extension is used in this profile: http://hl7.org/fhir/StructureDefinition/endpoint-fhir-version conveys is a denormalization to help clients focus on supported endpoints. The valueCode is any version from http://hl7.org/fhir/valueset-FHIR-version.html (e.g., 4.0.1 is expected for FHIR R4 endpoints). Notes: 0..1 name Conveys a fallback or default name describing the endpoint and the organization offering User API access at this endpoint. This value MAY contain technical details like FHIR API Version designations and apps SHOULD preferentially use names from an associated UserAccessBrand rather than displaying this value to users. 1..* MS contact website where developers can configure access to this endpoint, providing at least one "system": "url" contact point where the value is an https:// URL intended for app developers 1..1 MS address FHIR base URL for server supporting user access 'CONFORMANCE_STATEMENT_WORD
en/app-launch.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: ' Apps SHALL ensure that when protocol steps include transmission of sensitive information (authentication secrets, authorization codes, tokens), transmission is ONLY to authenticated servers, over TLS-secured channels. 'CONFORMANCE_STATEMENT_WORD
en/app-state.html
information
The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause: 'Apps SHALL NOT use smart-app-state when the data being persisted could be managed directly using FHIR domain models. For example, an app would never persist clinical diagnoses or observations using smart-app-state. Such usage is prohibited because the standard FHIR API provides safer and more interoperable mechanisms for clinical data sharing.'CONFORMANCE_STATEMENT_WORD
en/backend-services.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Before a SMART client can run against a FHIR server, the client SHALL register with the server by following the registration steps described in client-confidential-asymmetric authentication.'CONFORMANCE_STATEMENT_WORD
en/brands.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Brand Bundle Publisher. Any organization hosting or enabling management of a User Access Brand Bundle. SHALL publish at least a "primary brand" that references each FHIR endpoint in the Brand Bundle SHOULD support the publication of a more detailed Brand hierarchy SHALL populate Bundle.timestamp to advertise the timestamp of the last change to the contents SHOULD populate Bundle.entry.resource.meta.lastUpdated with a more detailed timestamp if the system tracks updates per Resource. SHALL support Cross-Origin Resource Sharing (CORS) for all GET requests to the artifacts described in this guide. SHOULD include a weak ETag header in all Brand Bundle HTTP responses SHALL allow Health Data Providers to manage all data elements marked "Must-Support" in the "User Access Brand" and "User Access Endpoint" profiles SHALL support customer-supplied Organization identifiers (system and value) MAY provide a Data Absent Reason of asked-declined or asked-unknown in a Brand Bundle SHALL NOT use Data Absent Reasons other than asked-declined or asked-unknown in a Brand Bundle 'CONFORMANCE_STATEMENT_WORD
en/client-confidential-asymmetric.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'Before a SMART client can run against a FHIR server, the client SHALL generate or obtain an asymmetric key pair and SHALL register its public key set with that FHIR server’s authorization service (referred to below as the "FHIR authorization server"). SMART does not require a standards-based registration process, but we encourage FHIR service implementers to consider using the OAuth 2.0 Dynamic Client Registration Protocol.'CONFORMANCE_STATEMENT_WORD
en/conformance.html
information
The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause: 'This specification uses the conformance verbs SHALL, SHOULD, and MAY as defined in RFC2119. Unlike RFC 2119, however, this specification allows that different applications may not be able to interoperate because of how they use optional features.'CONFORMANCE_STATEMENT_WORD
en/scopes-and-launch-context.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'Valid suffixes are a subset of the in-order string .cruds. For example, to convey support for creating and updating observations, use scope patient/Observation.cu. To convey support for reading and searching observations, use scope patient/Observation.rs. For backwards compatibility with scopes defined in the SMART App Launch 1.0 specification, servers SHOULD advertise the permission-v1 capability in their .well-known/smart-configuration discovery document, SHOULD return v1 scopes when v1 scopes are requested and granted, and SHOULD process v1 scopes with the following semantics in v2:'CONFORMANCE_STATEMENT_WORD
en/token-introspection.html
information
The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause: 'SMART on FHIR EHRs SHOULD support Token Introspection, which allows a broader ecosystem of resource servers to leverage authorization decisions managed by a single authorization server. Token Introspection is conducted according to RFC 7662: OAuth 2.0 Token Introspection, with the additional considerations presented in the sections below.'CONFORMANCE_STATEMENT_WORD
This element does not match any known slice defined in the profile http://hl7.org/fhir/smart-app-launch/StructureDefinition/user-access-brand|2.2.0 (this may not be a problem, but you should check that it's not intended to match a slice)Show Reasoning
This element does not match any known slice Defined in the profile http://hl7.org/fhir/smart-app-launch/StructureDefinition/user-access-brand|2.2.0 (this may not be a problem, but you should check that it's not intended to match a slice)
Bundle.entry[0].resource/*Organization/examplelabs*/.type[0]: discriminator = true and ($this memberOf 'http://hl7.org/fhir/smart-app-launch/ValueSet/user-access-category')
The resource CapabilityStatement/smart-app-state-server could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource CodeSystem/smart-codes must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
ImplementationGuide/hl7.fhir.uv.smart-app-launch: ImplementationGuide: Validated against fhir.ImplementationGuide
Path
Severity
Message
Validating
ImplementationGuide (l1/c29584)
warning
HL7 Implementation Guides should state their maturity explicitly using the extension http://hl7.org/fhir/StructureDefinition/structuredefinition-fmmIG_HL7_FMM_SHOULD
--
Resource
information
The resource ImplementationGuide/hl7.fhir.uv.smart-app-launch could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-brand to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-portal to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-brand to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-portal to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'MSG_DEPENDS_ON_DEPRECATED_NOTE
The resource StructureDefinition/user-access-brand could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/smart-app-state-basic could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/task-ehr-launch could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/task-standalone-launch could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource StructureDefinition/user-access-brands-bundle could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Pinned the version of http://hl7.org/fhir/StructureDefinition/endpoint-fhir-version to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
Pinned the version of http://hl7.org/fhir/StructureDefinition/endpoint-fhir-version to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)PIN_VERSION
--
Resource
information
The resource StructureDefinition/user-access-endpoint could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/smart-launch-info must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The resource ValueSet/smart-launch-types must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
The code 'laboratory' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'laboratory' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'imaging' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'imaging' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'pharmacy' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'pharmacy' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'health-information-network' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'health-information-network' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
The code 'health-data-aggregator' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'health-data-aggregator' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')VALUESET_INCLUDE_INVALID_CONCEPT_CODE
--
Resource
error
The resource ValueSet/user-access-category must have an OID assigned to cater for possible use with OID based terminology systems e.g. CDA usage (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/fhir-tools-ig/CodeSystem-ig-parameters.html#ig-parameters-auto-oid-root)
Example URI in example.org domain does not need to be validated
WARNING: 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)
Example brand logos are inline data: URIs, which the validator cannot resolve as canonical URLs
WARNING: Bundle/example1: Bundle.entry[0].resource/*Organization/examplelabs*/.extension[0].extension[0].value.ofType(url): No definition could be found for URL value 'data:image/svg+xml;utf8,<svg%20xmlns='http://www.w3.org/2000/svg'%20width='1024'%20height='1024'><path%20d='M0%200h1024v1024H0z'%20style='fill:%23eee'/><text%20x='40'%20y='170'%20style='font-size:150px'>1024x1024</text></svg>' (1 uses)
WARNING: Bundle/example1: Bundle.entry[0].resource/*Organization/examplelabs*/.extension[1].extension[2].value.ofType(url): No definition could be found for URL value 'data:image/svg+xml;utf8,<svg%20xmlns='http://www.w3.org/2000/svg'%20width='1024'%20height='1024'><path%20d='M0%200h1024v1024H0z'%20style='fill:%23666'/><text%20x='40'%20y='170'%20style='font-size:150px'>1024x1024</text></svg>' (1 uses)
WARNING: Bundle/example2: Bundle.entry[1].resource/*Organization/ehchospital*/.extension[0].extension[0].value.ofType(url): No definition could be found for URL value 'data:image/svg+xml;base64,PHN2ZyB0aXRsZT0iU3Rld2FydCBNZW1vcmlhbCBIb3Nw...+IDwvc3ZnPgo=' (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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (0 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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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)
This element does not match any known slice defined in the profile http://hl7.org/fhir/smart-app-launch/StructureDefinition/user-access-brand|2.2.0 (this may not be a problem, but you should check that it's not intended to match a slice)
The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.3.0 is deprecated with the note: 'Use additionalBinding extension or element instead'
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-brand to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-portal to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-brand to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
Pinned the version of http://hl7.org/fhir/StructureDefinition/organization-portal to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
Pinned the version of http://hl7.org/fhir/StructureDefinition/endpoint-fhir-version to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
Pinned the version of http://hl7.org/fhir/StructureDefinition/endpoint-fhir-version to 5.3.0 from choices of 5.2.0 (hl7.fhir.uv.extensions.r4#5.2.0), 5.3.0 (hl7.fhir.uv.extensions.r4#5.3.0)
The code 'laboratory' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'laboratory' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')
The code 'imaging' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'imaging' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')
The code 'pharmacy' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'pharmacy' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')
The code 'health-information-network' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'health-information-network' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')
The code 'health-data-aggregator' is not valid in the system http://terminology.hl7.org/CodeSystem/organization-type (Unknown code 'health-data-aggregator' in the CodeSystem 'http://terminology.hl7.org/CodeSystem/organization-type' version '2.0.1')
hl7.fhir.uv.smart-app-launch
hl7.fhir.uv.tools.r4