Generated Tue May 09 21:09:38 UTC 2023, FHIR version 4.0.1 for hl7.fhir.us.specialty-rx#2.1.0 (canonical = http://hl7.org/fhir/us/specialty-rx (history)). See Full QA Report
Quality Checks | |||||||||||||||||||||||||
Publisher Version: | IG Publisher Version: v1.3.8 | ||||||||||||||||||||||||
Publication Code: | specialty-rx . PackageId = hl7.fhir.us.specialty-rx, Canonical = http://hl7.org/fhir/us/specialty-rx | ||||||||||||||||||||||||
Realm Check for US: | Snomed: The IG specifies the US edition of SNOMED CT ✓ | ||||||||||||||||||||||||
Publication Request: | No publication request found | ||||||||||||||||||||||||
Supressed Messages: | 7 Suppressed Issues | ||||||||||||||||||||||||
Dependency Checks: |
| ||||||||||||||||||||||||
Dependent IGs: | no references | ||||||||||||||||||||||||
Global Profiles: | (none declared) | ||||||||||||||||||||||||
HTA Analysis: | no Non-HL7 references found | ||||||||||||||||||||||||
R5 Dependencies: | (none) | ||||||||||||||||||||||||
Modifier Extensions: | (none) | ||||||||||||||||||||||||
Previous Version Comparison: | Comparison with version 2.0.0 | ||||||||||||||||||||||||
IPA Comparison: | n/a | ||||||||||||||||||||||||
Summary: | errors = 2, warn = 0, info = 0, broken links = 0 |
Path | Severity | Message |
StructureDefinition.snapshot.element[9].example[0].value.ofType(Identifier) (l1/c43459) | error | if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme) |
Path | Severity | Message |
StructureDefinition.snapshot.element[9].example[0].value.ofType(Identifier) (l1/c43536) | error | if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme) |
Suppressed Messages (Warnings, hints, broken links)
A variance to the US Core Coverage profile was granted by Cross Group Projects WG. See FHIR-40814
Messaging components that are only instantiated within full messages (MessageHeaders, Parameters, Search Bundles) don't have their own examples, but instead are illustrated in full message examples referenced on the profile pages: specialty-rx-bundle-search-result.xml (in examples specialty-rx-query-response-1, -2, -3-w-op-outcome and -unsolicited-1), specialty-rx-messageheader-error.xml (in example specialty-rx-error-1), specialty-rx-messageheader-query.xml (in example specialty-rx-query-1), specialty-rx-messageheader-query-response.xml (in examples specialty-rx-query-response-1 -2 and -3-w-op-outcome), specialty-rx-messageheader-query-response-unsolicited.xml (in example query-response-unsolicited-1), specialty-rx-parameters-query.xml (in example specialty-rx-query-1), specialty-rx-parameters-query-response.xml (in examples specialty-rx-query-response-1, -2 and -3-w-op-outcome), specialty-rx-parameters-query-response-unsolicited.xml (in example query-response-unsolicited-1)
The base R4 Consent StructureDefinition contains an error in the element.example value of Consent.identifier (Consent.identifier element, example.valueIdentifier.system = "urn:ietf:rfc:3986"). Confirmed with CBCP WG that it can be ignored
The fixed value constraint referenced by the warning is in the base R4 Consent and not modified by this IG (StructureDefinition element #35 - policyRule)
This Organization example illustrates a US Core organization resource. Population of NPI matches that in US Core
This example intentionally includes an error in the search string, in order to illustrate an OperationOutcome response
Using standard extension capabilitystatement-expectation for CapabilityStatement in additional contexts to express search parameter capabilities: see FHIR-12419
Errors sorted by type
input/resources/StructureDefinition/specialty-rx-consent.xml | if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme) |
input/resources/StructureDefinition/specialty-rx-consent-requested.xml | if identifier.system is ''urn:ietf:rfc:3986'', then the identifier.value must be a full URI (e.g. start with a scheme) |