Validation Results for USCore

Generated Fri Dec 13 23:02:38 UTC 2024, FHIR version 4.0.1 for hl7.fhir.us.core#8.0.0-ballot (canonical = http://hl7.org/fhir/us/core (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.8.1
Publication Code:	core . PackageId = hl7.fhir.us.core, Canonical = http://hl7.org/fhir/us/core
Realm Check for US:	Snomed: The IG specifies the US edition of SNOMED CT ✓ Profiles: All OK
Publication Request:	Version 8.0.0-ballot has already been published Publication Request is for version v8.0.0-ballot which is already published
Supressed Messages:	49 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.us.core 8.0.0-ballot R4 http://hl7.org/fhir/us/core hl7.terminology.r4 6.1.0 M R4 http://terminology.hl7.org http://terminology.hl7.org/6.1.0 hl7.fhir.uv.smart-app-launch 2.0.0 O R4 http://hl7.org/fhir/smart-app-launch http://hl7.org/fhir/smart-app-launch/STU2 Latest Release is 2.2.0 us.nlm.vsac 0.21.0 M R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac hl7.fhir.uv.sdc 3.0.0 M R4 http://hl7.org/fhir/uv/sdc http://hl7.org/fhir/uv/sdc/STU3 hl7.fhir.r4.examples 4.0.1 O R4 http://hl7.org/fhir http://hl7.org/fhir/R4 Latest Release is 5.0.0 us.cdc.phinvads 0.12.0 M R4 http://fhir.org/packages/us.cdc.phinvads http://fhir.org/packages/us.cdc.phinvads hl7.fhir.uv.extensions.r4 5.1.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0 Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: 0.3.0
Dependent IGs:	76 guides
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4 (details)
HTA Analysis:	All OK
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (17 uses), CompositionAttestationMode (3 uses), Ordinal Value (54 uses), FHIR Defined Concept Properties (1 uses), observation-vitalsigns (83 uses), CommonLanguages (58 uses), CarePlan (38 uses), DeviceRequest (27 uses), ImmunizationRecommendation (31 uses), MedicationRequest (33 uses), NutritionOrder (30 uses), ServiceRequest (38 uses), MedicationAdministration (27 uses), MedicationDispense (28 uses), MedicationStatement (27 uses), Procedure (32 uses), Immunization (28 uses), ImagingStudy (56 uses), ObservationCategoryCodes (48 uses), Encounter (32 uses), PractitionerRole (70 uses), VitalSignsUnits (43 uses), SNOMEDCTBodyStructures (32 uses), ObservationMethods (26 uses), Specimen (30 uses), Device (74 uses), DeviceMetric (26 uses), ObservationReferenceRangeMeaningCodes (26 uses), ObservationReferenceRangeAppliesToCodes (26 uses), QuestionnaireResponse (54 uses), MolecularSequence (55 uses), DocumentReference (32 uses), Media (30 uses), DocumentReferenceStatus (4 uses), CompositionStatus (2 uses), Practitioner (32 uses), Group (37 uses), Organization (42 uses), DocumentRelationshipType (2 uses), EpisodeOfCare (4 uses), AllergyIntolerance (3 uses), AllergyIntoleranceClinicalStatusCodes (2 uses), AllergyIntoleranceVerificationStatusCodes (2 uses), AllergyIntoleranceType (1 uses), AllergyIntoleranceCategory (1 uses), AllergyIntoleranceCriticality (1 uses), RelatedPerson (25 uses), SubstanceCode (1 uses), SNOMEDCTClinicalFindings (7 uses), AllergyIntoleranceSeverity (1 uses), SNOMEDCTRouteCodes (3 uses), LOINCCodes (27 uses), BodyLengthUnits (4 uses), BodyTemperatureUnits (2 uses), BodyWeightUnits (2 uses), CareTeam (11 uses), PlanDefinition (4 uses), Questionnaire (3 uses), Measure (3 uses), ActivityDefinition (4 uses), RequestStatus (3 uses), CarePlanIntent (2 uses), CarePlanCategory (2 uses), Condition (22 uses), Goal (4 uses), CarePlanActivityOutcome (1 uses), Appointment (2 uses), CommunicationRequest (1 uses), Task (1 uses), VisionPrescription (1 uses), RequestGroup (1 uses), CarePlanActivityKind (1 uses), ProcedureCodes(SNOMEDCT) (1 uses), DiagnosticReport (9 uses), CarePlanActivityStatus (1 uses), Location (11 uses), HealthcareService (3 uses), Medication (4 uses), Substance (7 uses), SNOMEDCTMedicationCodes (1 uses), CareTeamStatus (2 uses), CareTeamCategory (1 uses), ConditionClinicalStatusCodes (4 uses), ConditionVerificationStatus (4 uses), ConditionCategoryCodes (3 uses), Condition/DiagnosisSeverity (2 uses), ConditionStage (2 uses), ClinicalImpression (2 uses), ConditionStageType (2 uses), ManifestationAndSymptomCodes (2 uses), CommonTags (4 uses), Coverage (3 uses), FinancialResourceStatusCodes (1 uses), SubscriberRelationshipCodes (2 uses), CoverageClassCodes (3 uses), CoverageCopayTypeCodes (1 uses), ExampleCoverageFinancialExceptionCodes (1 uses), Contract (1 uses), DiagnosticReportStatus (4 uses), DiagnosticServiceSectionCodes (3 uses), EncounterStatus (2 uses), ServiceType (1 uses), ParticipantType (1 uses), EncounterReasonCodes (1 uses), DiagnosisRole (1 uses), Account (1 uses), AdmitSource (1 uses), Diet (1 uses), SpecialCourtesy (1 uses), SpecialArrangements (1 uses), EncounterLocationStatus (1 uses), LocationType (2 uses), GoalLifecycleStatus (2 uses), GoalAchievementStatus (1 uses), GoalCategory (1 uses), GoalPriority (1 uses), GoalStartEvent (1 uses), RiskAssessment (1 uses), ImmunizationStatusCodes (2 uses), ImmunizationStatusReasonCodes (2 uses), ImmunizationOriginCodes (1 uses), CodesForImmunizationSiteOfAdministration (1 uses), ImmunizationRouteCodes (1 uses), ImmunizationFunctionCodes (1 uses), ImmunizationReasonCodes (1 uses), ImmunizationSubpotentReason (1 uses), ImmunizationProgramEligibility (1 uses), ImmunizationFundingSource (1 uses), ImmunizationTargetDiseaseCodes (1 uses), DeviceDefinition (1 uses), UDIEntryType (1 uses), FHIRDeviceStatus (1 uses), FHIRDeviceStatusReason (1 uses), DeviceNameType (1 uses), FHIRDeviceTypes (3 uses), LocationStatus (1 uses), LocationMode (1 uses), Endpoint (3 uses), Medication Status Codes (1 uses), SNOMEDCTFormCodes (1 uses), MedicationDispense Status Codes (1 uses), DetectedIssue (3 uses), MedicationDispense Status Reason Codes (1 uses), MedicationDispense Category Codes (1 uses), MedicationDispense Performer Function Codes (1 uses), UCUMCodes (6 uses), Common UCUM units (6 uses), SNOMEDCTAdditionalDosageInstructions (2 uses), SNOMEDCTMedicationAsNeededReasonCodes (3 uses), SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (2 uses), SNOMEDCTAdministrationMethodCodes (2 uses), DoseAndRateType (2 uses), Provenance (5 uses), medicationrequest Status (2 uses), medicationRequest Status Reason Codes (1 uses), medicationRequest Intent (2 uses), medicationRequest Category Codes (3 uses), RequestPriority (2 uses), ProcedurePerformerRoleCodes (2 uses), medicationRequest Course of Therapy Codes (1 uses), ClaimResponse (2 uses), OrganizationType (1 uses), ContactEntityType (1 uses), EventStatus (2 uses), ProcedureCategoryCodes(SNOMEDCT) (1 uses), ProcedureOutcomeCodes(SNOMEDCT) (1 uses), Composition (1 uses), Condition/Problem/DiagnosisCodes (1 uses), ProcedureFollowUpCodes(SNOMEDCT) (1 uses), ProcedureDeviceActionCodes (1 uses), ProvenanceActivityType (1 uses), SecurityRoleType (3 uses), ProvenanceParticipantType (2 uses), ProvenanceEntityRole (1 uses), regex (1 uses), QuestionnaireResponseStatus (1 uses), QuestionnaireAnswerCodes (1 uses), PatientRelationshipType (2 uses), SpecimenStatus (1 uses), FHIRSpecimenCollectionMethod (1 uses), SpecimenProcessingProcedure (1 uses), SpecimenContainerType (1 uses), NarrativeStatus (1 uses), Value Set Expansion (2 uses), clinical-status (1 uses), patient (14 uses), category (1 uses), date (6 uses), status (1 uses), status (1 uses), abatement-date (1 uses), category (1 uses), clinical-status (1 uses), code (5 uses), encounter (1 uses), _lastUpdated (4 uses), onset-date (1 uses), recorded-date (1 uses), patient (1 uses), patient (1 uses), status (1 uses), type (1 uses), category (1 uses), status (1 uses), category (1 uses), date (1 uses), _id (8 uses), period (1 uses), status (1 uses), type (2 uses), class (1 uses), identifier (1 uses), location (1 uses), status (1 uses), lifecycle-status (1 uses), target-date (1 uses), status (1 uses), address-city (1 uses), address-postalcode (1 uses), address-state (1 uses), address (1 uses), name (1 uses), status (2 uses), type (1 uses), authoredon (1 uses), encounter (1 uses), intent (1 uses), category (1 uses), status (1 uses), address (1 uses), name (1 uses), birthdate (1 uses), death-date (1 uses), family (1 uses), gender (1 uses), given (1 uses), identifier (1 uses), name (1 uses), identifier (1 uses), name (1 uses), practitioner (1 uses), specialty (1 uses), status (1 uses), authored (1 uses), patient (1 uses), questionnaire (1 uses), status (1 uses), name (1 uses), patient (1 uses), authored (1 uses), category (1 uses), status (1 uses), patient (1 uses), RequestIntent (1 uses), ServiceRequestCategoryCodes (2 uses), ServiceRequestOrderDetailsCodes (1 uses), ParticipantRoles (1 uses) hl7.fhir.uv.extensions.r4#5.1.0: ItemWeight (2 uses), PatSexParameterForClinicalUse (3 uses), SDStatusDerivation (424 uses), TypeMustSupport (710 uses) hl7.fhir.uv.sdc#3.0.0: StructuredDataCapture (1 uses), SDCBaseQuestionnaire (15 uses), SDCQuestionnaireResponse (3 uses), ItemMedia (1 uses), ItemAnswerMedia (1 uses) hl7.fhir.uv.tools.r4#0.3.0: ResourceSortExt (433 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 7.0.0 Comparison with version 6.1.0 Comparison with version 5.0.1 Comparison with version 4.0.0 Comparison with version 3.1.1
IPA Comparison:	n/a
IPS Comparison:	n/a
Validation Flags:	On: autoLoad; Off: hintAboutNonMustSupport, anyExtensionsAllowed, checkAggregation, showReferenceMessages, noExperimentalContent, displayWarnings
Narratives Suppressed	Bundle/docref-example-1, Bundle/docref-example-2, DocumentReference/discharge-summary
Summary:	errors = 4, warn = 0, info = 0, broken links = 0

n/a Show Validation Information

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

input/examples/patient-example.json Show Validation Information (2)

input/resources/ValueSet-simple-language.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

=== The following code system and value set are in FHIR Core/THO and not under the direct control of US Core editors ===

• Reference to draft CodeSystem http://hl7.org/fhir/narrative-status|4.0.1 (1 uses)
• Reference to draft ValueSet http://hl7.org/fhir/ValueSet/servicerequest-category|4.0.1 (2 uses)

=== Added this STU NOTE: This profile is technically non-conformant with the base FHIR ver 4.0.1 vitals profile, which defines a required binding that excludes the concept for L/min for Observation.component.value(x). This is a known issue, which means validation errors may occur when validating against this version of the US Core Pulse Oximetry Profile. This issue has been corrected in base FHIR ver 4.3.0 ("Release 4B") which will correct this error when this guide is based a newer version of FHIR. ===

• ERROR: Observation/satO2-fiO2: Observation.component[0].value.ofType(Quantity): The code provided (http://unitsofmeasure.org#L/min) was not found in the value set' Vital Signs Units' (http://hl7.org/fhir/ValueSet/ucum-vitals-common|4.0.1), and a code from this value set is required: The provided code 'http://unitsofmeasure.org#L/min' was not found in the value set 'http://hl7.org/fhir/ValueSet/ucum-vitals-common|4.0.1' (0 uses)
• ERROR: US Core Vital Signs Profile.Observation.component.value[x]: illegal attempt to change the binding on Observation.component.value[x] from required to extensible (0 uses)

=== Based upon FHIR-I's guidance on backporting CodeableReference dataype in R4 implementations, the use of the FHIR R5-based Sex Parameters for Clinical Use Extension is correct. The publication valiidation tool needs to updated to validate it correctly. See this Chat: https://chat.fhir.org/#narrow/channel/179166-implementers/topic/UV.20Extension.20Sex.20Parameter.20for.20clinical.20use.20broken.20for.20R4.3F ===

• ERROR: Patient/example: Patient.extension[5].extension[1]: Extension.extension:supportingInfo.extension: max allowed = 0, but found 3 (from http://hl7.org/fhir/StructureDefinition/patient-sexParameterForClinicalUse|5.1.0) (1 uses)
• ERROR: Patient/example: Patient.extension[5].extension[1]: Extension.extension:supportingInfo.value[x]: minimum required = 1, but only found 0 (from http://hl7.org/fhir/StructureDefinition/patient-sexParameterForClinicalUse|5.1.0) (1 uses)

=== Because the "is-a" filter is currently not defined by CPT; therefore, the publication validator does not recognize it. See this Chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Clarify.20why.20terminology.20server.20is.20yielding.20this.20error The publication and VSAC team is clarifying with CPT whether this filter is allowed.

• ERROR: Encounter/example-1: Encounter.type[0]: Error from http://tx.fhir.org/r4: The filter "concept is-a 1013625" from the value set http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.3.88.12.80.32|20240711 was not understood in the context of http://www.ama-assn.org/go/cpt (1 uses)

=== Examples provided in Bundle (e.g. PractitionerRole_Practitioner_Endpoint_Bundle_Example, Allergyintolerance Provenance Example) (2)===

• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)

=== HL7 Terminology (THO) defines the ServiceDeliveryLocationRoleType and HealthcareServiceLocation value sets that compose this ValueSet. however, no codes are displayed in HL7 Terminology for HealthcareServiceLocation value set which is composed of NHSN Healthcare Facility Patient Care Location (HSLOC) and CMS Place of Service Codes (POS) codes. These codes are available at:ServiceDeliveryLocationRoleType: https://terminology.hl7.org/6.1.0/ValueSet-v3-ServiceDeliveryLocationRoleType.html,HLSOC: https://vsac.nlm.nih.gov/valueset/2.16.840.1.113883.1.11.20275/expansion/Latest,POS: https://www.cms.gov/medicare/coding-billing/place-of-service-codes/code-sets===

• WARNING: ValueSet.where(id = 'us-core-location-type'): Unable to expand included value set 'http://terminology.hl7.org/ValueSet/v3-HealthcareServiceLocation', but no error (and Error from http://tx.fhir.org/r4: Unable to provide support for code system https://www.cms.gov/Medicare/Coding/place-of-service-codes/Place_of_Service_Code_Set) (1 uses)

=== In this example, representing the concept clearly with human-readable annotations {pack-years} is not misleading. It clearly illustrates how to use the Observation with the code, and demonstrates a clinical need outweighing concerns about using annotations. new in ver 7.0.0 ===

• WARNING: Observation/pack-years-example: Observation.value.ofType(Quantity): UCUM Codes that contain human readable annotations like {pack-years} can be misleading (e.g. they are ignored when comparing units). Best Practice is not to depend on annotations in the UCUM code, so this usage should be checked (1 uses)

=== Several examples derived from this profile are provided in this guide (1) ===

• WARNING: StructureDefinition.where(URL = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-vital-signs'): The Implementation Guide contains no examples for this profile (1 uses)

=== The 'no-narrative' parameter is used for these resources instances because they are displayed as inline JSON examples to illustrate transactions and the narrative degrades human readability ===

• WARNING: Bundle/docref-example-1: Bundle.entry[0].resource/*DocumentReference/ccd123*/: 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/docref-example-2: Bundle.entry[0].resource/*DocumentReference/procedure-note123*/: 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/docref-example-2: Bundle.entry[1].resource/*DocumentReference/procedure-note456*/: 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/docref-example-2: Bundle.entry[2].resource/*DocumentReference/discharge*/: 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: DocumentReference/discharge-summary: DocumentReference: 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)

=== The binding applies to the Quantity data type for US Core Vitals Signs Profile. It inherits the structure from Core, and a change request to correct this has been applied to the base FHIR ver 4.3.0 ("Release 4B"). Will need to slice value[x] in future (updated text from 7.0.0) ===

• The element Observation.component.value[x] has a binding, and has multiple types subject to bindings ([dateTime, boolean, string, SampledData, Quantity, Period, Ratio, integer, time, Range, CodeableConcept]). The binding will apply to all the types (1 uses)
• The element Observation.value[x] has a binding, and has multiple types subject to bindings ([dateTime, boolean, string, SampledData, Quantity, Period, Ratio, integer, time, Range, CodeableConcept]). The binding will apply to all the types (1 uses)

=== The code is from the US Core defined NUCC binding and not from base FHIR preferred c80-practice-codes value set (updated text from 7.0.0) ===

• None of the codings provided are in the value set 'Practice Setting Code Value Set' (http://hl7.org/fhir/ValueSet/c80-practice-codes|4.0.1), and a coding is recommended to come from this value set (codes = http://nucc.org/provider-taxonomy#208D00000X) (1 uses)

=== The following code system is not discoverable because they are code systems in THO, but THO doesn't define the codes due to AHA NUBC Patient Discharge Status Codes IP issues, these codes were checked manually (updated text from 7.0.0)===

• WARNING: Encounter/1036: Encounter.hospitalization.dischargeDisposition.coding[0].system: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/nubc-UB92' could not be found, so the code cannot be validated (1 uses)
• WARNING: Encounter/1036: Encounter.hospitalization.dischargeDisposition: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/nubc-UB92' could not be found, so the code cannot be validated; Unable to check whether the code is in the value set 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|3.0.0' because the code system http://terminology.hl7.org/CodeSystem/nubc-UB92 was not found (1 uses)
• WARNING: Encounter/1036: Encounter.hospitalization.dischargeDisposition: Unable to check whether the code is in the value set 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|3.0.0' because the code system http://terminology.hl7.org/CodeSystem/nubc-UB92 was not found (1 uses)

=== There are 2 Bundle examples that use this profile and 1 non-validated inline example that conforms to it as well - when the publisher understands versioned examples, we will create a published example to replace it. ===

• INFORMATION: StructureDefinition.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-provenance'): The Implementation Guide contains no explicitly linked examples for this profile (1 uses)

=== These Examples demonstrate the use of additional Codes or Identifiers not defined in US Core profiles Updated from 7.0.0-ballot ===

• A definition for CodeSystem 'http://example.org/michigan.gov/lara/license-type' could not be found, so the code cannot be validated (1 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure|8.0.0-ballot (1 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization|8.0.0-ballot (2 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|8.0.0-ballot (4 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry|8.0.0-ballot (1 uses)

=== These questionnaires are created using NLM tooling based on LOINC LFORMs. They use standard FHIR Questionnaire Extensions that "extend" the base SDC profile ===

• This element does not match any known slice defined in the profile http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaire|3.0.0 (10 uses)

=== This Search Parameter expression `Goal.target.due as date` is inherited from the FHIR base. Since US Core inherits from the FHIR R4 base, this warning is acknowledged as an issue with the base specification. In R5, this expression has been updated to `(Goal.target.due.ofType(date))`. ===

• WARNING: SearchParameter/us-core-goal-target-date: SearchParameter.expression: The left side is inherently a collection, and so the expression 'Goal.target.due as date' may fail or return false if there is more than one item in the content being evaluated (1 uses)

=== US Core thoroughly documents its Must Support expectations for the must supports, including how they apply to choice of target references. See this chat https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Must.20Support.20Target.20Error.20for.20Reference.20type.20Element ===

• The element Procedure.performer.actor has types/profiles/targets that are marked as must support, but the element itself is not marked as must-support (1 uses)

=== Using the extension US Core Extension Questionnaire URI pointing to a pdf form of the Questionnaire for this example. Regarding the message: "No questionnaire is identified, so no validation can be performed against the base questionnaire" ===

• INFORMATION: QuestionnaireResponse/glascow-coma-score: QuestionnaireResponse: No questionnaire is identified, so no validation can be performed against the base questionnaire (1 uses)

=== Using the standard CapabilityStatementExpectation extension in additional contexts to fully express intended capabilities: see FHIR-12419 (115) (updated text from 7.0.0-ballot) ===

• This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/capabilitystatement-search-parameter-combination|5.1.0 (this may not be a problem, but you should check that it's not intended to match a slice) (142 uses)

==== Since the ValueSet's grammar based definition leads to an infinite set, it cannot be expanded and leads to the following error ===

• ERROR: ValueSet.where(id = 'simple-language'): Error from http://tx.fhir.org/r4: Language valuesets cannot be expanded as they are based on a grammar (1 uses)

==== The US Core Team is aware of this and will budget and move these values to THO in a future publication cycle ===

• 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) (5 uses)

==== The following code systems are not discoverable because they are code systems in THO, but THO doesn't define the codes. They have been checked and the identifiers are correct (updated text from 7.0.0) ===========

• WARNING: Observation/observation-occupation-industry-unknown: Observation.value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found, so the code cannot be validated (1 uses)
• WARNING: Observation/observation-occupation-unknown: Observation.component[0].value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found, so the code cannot be validated (1 uses)
• WARNING: Observation/observation-occupation: Observation.component[0].value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found, so the code cannot be validated (1 uses)
• WARNING: Observation/observation-occupation: Observation.value.ofType(CodeableConcept).coding[0].system: A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found, so the code cannot be validated (1 uses)
• WARNING: ValueSet.where(id = 'us-core-condition-code'): Error from http://tx.fhir.org/r4: Unable to provide support for code system http://terminology.hl7.org/CodeSystem/icd9cm (1 uses)

==== The following content is inherited from the base standard and cannot be changed ====

• The markdown contains content that appears to be an embedded HTML tag starting at 'Th'. This will (or SHOULD) be escaped by the presentation layer. The content should be checked to confirm that this is the desired behaviour (1 uses)
• The string value contains text that looks like embedded HTML tags. If this content is rendered to HTML without appropriate post-processing, it may be a security risk (1 uses)

==== The pattern is set in a repeating slice. The pattern is expected to hold for all repetitions of that slice. (It's fixing the 'system' for the identifier.) ====

• INFORMATION: StructureDefinition/us-core-organization: StructureDefinition.snapshot.element[18].pattern.ofType(Identifier): The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (1 uses)
• INFORMATION: StructureDefinition/us-core-organization: StructureDefinition.snapshot.element[19].pattern.ofType(Identifier): The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (1 uses)
• INFORMATION: StructureDefinition/us-core-organization: StructureDefinition.snapshot.element[20].pattern.ofType(Identifier): The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (1 uses)
• INFORMATION: StructureDefinition/us-core-practitioner: StructureDefinition.snapshot.element[18].pattern.ofType(Identifier): The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (1 uses)

==== The self-link for these searchset bundles is to the $docref operation and not to a FHIR search string====

• No types could be determined from the search string, so the types can't be checked (2 uses)

==== Understood and note that this is rendered by the ig-publisher in the ig ====

• The value set expansion is too large, and only a subset has been displayed (1 uses)

====FHIR R4 http://hl7.org/fhir/ValueSet/formatcodes is in error which is has been corrected in the FHIR R5. The guide is referencing the "HL7 ValueSet of Format Codes for use with Document Sharing" that is used in R5 (updated text from 7.0.0) ===

• INFORMATION: Bundle/docref-example-1: Bundle.entry[0].resource/*DocumentReference/ccd123*/.content[0].format: The Coding provided (http://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodes#urn:hl7-org:sdwg:ccda-structuredBody:2.1) was not found in the value set 'DocumentReference Format Code Set' (http://hl7.org/fhir/ValueSet/formatcodes|4.0.1), and a code is recommended to come from this value set. (error message = The provided code 'http://terminology.hl7.org/CodeSystem/v3-HL7DocumentFormatCodes#urn:hl7-org:sdwg:ccda-structuredBody:2.1: 'ccda-structuredBody:2.1'' was not found in the value set 'http://hl7.org/fhir/ValueSet/formatcodes|4.0.1') (1 uses)

Errors sorted by type

Validation_VAL_Profile_Maximum

Validation_VAL_Profile_Minimum