Generated Tue Oct 27 16:21:29 EDT 2026, FHIR version 4.0.1 for sequoia.fhir.us.sphd#1.18.0 (canonical = https://sequoiaproject.org/fhir/sphd (history)). See Full QA Report & IP
| Quality Checks | |||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publisher Version: | IG Publisher Version: v3.0.1 | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Code: | n/a . PackageId = sequoia.fhir.us.sphd, Canonical = https://sequoiaproject.org/fhir/sphd | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Realm Check for n/a: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Language Info: | This IG has no language information | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Publication Request: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Supressed Messages: | 33 Suppressed Issues | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Dependency Checks: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Related IGs: | n/a | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Dependent IGs: | no references | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Global Profiles: | (none declared) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Terminology Server(s): | https://tx.fhir.org/r4 (details) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| HTA Analysis: | Non-HL7 Igs are exempt from terminology dependency analysis | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| R5 Dependencies: | (none) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Draft Dependencies: |
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Modifier Extensions: | (none) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Previous Version Comparison: | Unable to compare with previous version: Unable to find version history at https://sequoiaproject.org/fhir/sphd (Problem #1 with package-list.json at https://sequoiaproject.org/fhir/sphd: 404 Not Found) | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IPA Comparison: | n/a | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| IPS Comparison: | n/a | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Validation Flags: | On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| Summary: | errors = 0, warn = 44, info = 42, broken links = 0, pinned = 3 (when multiples). | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
| output\searchform.html | warning | The html source is not well formed: Found "</a>" expecting "</img>" at line 34 column 177 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 79 column 10 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 80 column 9 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 109 column 8 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 111 column 12 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 112 column 20 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 113 column 16 HTML_NOT_WELL_FORMED |
| output\searchform.html | warning | The html source is not well formed: Found "</div>" expecting "</body>" at line 115 column 12 HTML_NOT_WELL_FORMED |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/AdministrativeStatus should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/DelegationRoleCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/Domains should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/EndpointConnectionType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/EndpointRoleCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/EndpointType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/EndpointUseCaseCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/HubRoutingStatus should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/HubServiceSubscriptionCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/IASResponseModeCS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/InitiatorOnlyCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/OrganizationNodeTypeCS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/OrganizationType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/PurposeOfUse should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/SequoiaIdentifierCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/SequoiaServiceDeliveryLocationRoleTypeCodingSystem should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource CodeSystem/TransactionCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| ImplementationGuide.dependsOn[2] (l1/c1696) | warning | The ImplementationGuide uses package hl7.terminology#5.5.0 released on 2024-03-09, but the most recent appropriate version is 7.5.0. This reference is getting old and the more recent version should be considered IG_DEPENDENCY_VERSION_WARNING_OLD | -- |
| Resource | information | The resource ImplementationGuide/sequoia.fhir.us.sphd could usefully have an OID assigned (OIDs are easy to assign - see https://build.fhir.org/ig/FHIR/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/AdministrativeStatus should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/DelegationRoleVS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/Domains should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/EndpointConnectionType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/EndpointPayloadTypeCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/EndpointType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/EndpointUseCaseCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/HubRoutingStatus should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/HubServiceSubscriptions should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/IASResponseModeVS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/InitiatorOnly should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/OrganizationNodeTypeVS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/OrganizationType should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/PurposeOfUse should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/RCEPurposeVS should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/SequoiaIdentifierCodes should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/SequoiaServiceDeliveryLocationRoleTypeValueSet should 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/ig-guidance/oids.html) | -- |
| Path | Severity | Message | Validating |
| Resource | warning | The resource ValueSet/Transactions should 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/ig-guidance/oids.html) | -- |
Suppressed Messages (Warnings, hints, broken links)
01. Repeating elements have a pattern that is expected to apply to all the repeats.
02. Deprecated concepts that Sequoia directories still use
03. Reference to draft and experimental code systems acknowledged and appropriate for examples.
04. Inactive codes and wrong display names will be reviewed in future updates.
05. This IG is FHIR R4. Discriminator types will be reviewed when moving to R5+.
06. Organization.identifier' slice for 'CLIA' is inherited from US Core 6.1.0.
07. Pinned versions have been reviewed and are correct.
08. This IG is intended to contain only abstract StructureDefinitions, so Warning is expected.
09. Canonical URL 'https://sequoiaproject.org/fhir/sphd' is confirmed to be correct.
10. This IG intentionally depends on specified versions: FHIR R4 and US Core 6.1.0.
11. OIDs will be considered in the future.
Errors sorted by type
| fsh-generated\resources\ImplementationGuide-sequoia.fhir.us.sphd.json | The ImplementationGuide uses package hl7.terminology#5.5.0 released on 2024-03-09, but the most recent appropriate version is 7.5.0. This reference is getting old and the more recent version should be considered | -- |
| fsh-generated\resources\Endpoint-fhir-endpoint.json | Reference to draft CodeSystem http://terminology.hl7.org/CodeSystem/endpoint-connection-type|2.1.0 from active ValueSet https://sequoiaproject.org/fhir/sphd/ValueSet/EndpointConnectionType|1.18.0 | AuditEvent |
| fsh-generated\resources\StructureDefinition-SequoiaEndpoint.json | The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) | -- |
| fsh-generated\resources\StructureDefinition-SequoiaEndpoint.json | The discriminator type 'pattern' is deprecated in R5+. For future compatibility, you could consider using type=value with a pattern[x] instead (if this is not an inherited slicing) | -- |
| fsh-generated\resources\StructureDefinition-SequoiaEndpoint.json | The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) | -- |
| fsh-generated\resources\ValueSet-AuthorRole.json | Wrong Display Name 'Medical doctor (inactive code)' for http://snomed.info/sct#112247003. Valid display is one of 3 choices: 'Medical doctor' (en), 'General physician' (en) or 'Medical doctor (occupation)' (en) (for the language(s) 'en-US'). Note that the display in the ValueSet does not have to match; this check exists to help check that it's not accidentally the wrong code | -- |