Validation Results for USCore

Generated Thu Jan 22 07:25:11 UTC 2026, FHIR version 4.0.1 for hl7.fhir.us.core#9.0.0 (canonical = http://hl7.org/fhir/us/core (history)). See Full QA Report & IP

Quality Checks
Publisher Version:	IG Publisher Version: v2.0.30
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
Language Info:	This IG has no language information
Publication Request:	RelatedIgs (None Found) Publication Request is for v'9.0.0-ballot' but package version is v9.0.0 Publication Request is for version v9.0.0-ballot which is already published
Supressed Messages:	84 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.us.core 9.0.0 R4 http://hl7.org/fhir/us/core hl7.terminology.r4 7.0.1 M R4 http://terminology.hl7.org http://terminology.hl7.org/7.0.1 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 hl7.fhir.uv.smart-app-launch 2.2.0 M R4 http://hl7.org/fhir/smart-app-launch http://hl7.org/fhir/smart-app-launch/STU2.2 hl7.fhir.uv.extensions 5.1.0-snapshot1 O R5 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0-snapshot1 FHIR Version Mismatch. Latest Release is 5.2.0 hl7.terminology.r5 5.3.0 O R5 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 FHIR Version Mismatch. Latest Release is 7.0.1 hl7.terminology 5.5.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.5.0 Latest Release is 7.0.1 hl7.fhir.uv.extensions.r4 1.0.0 O R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/1.0.0 Latest Release is 5.2.0 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.nlm.vsac 0.24.0 M R4 http://fhir.org/packages/us.nlm.vsac http://fhir.org/packages/us.nlm.vsac 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.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.xver-r5.r4 0.0.1-snapshot-2 U R4 http://hl7.org/fhir/5.0 http://hl7.org/fhir/uv/xver-r5.r4/0.0.1-snapshot-2 hl7.terminology.r4 6.5.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/6.5.0 Latest Release is 7.0.1 hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.extensions.r4 5.2.0 M R4 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.2.0 (as above) hl7.fhir.uv.tools.r4 0.9.0 M R4 http://hl7.org/fhir/tools http://hl7.org/fhir/tools/0.9.0 Internal Dependency Templates: hl7.fhir.template#1.0.0 -> hl7.base.template#1.0.0 -> fhir.base.template#1.0.0
Related IGs:	n/a
Dependent IGs:	no references
Global Profiles:	(none declared)
Terminology Server(s):	http://tx.fhir.org/r4, https://tx-nordics.fhir.org/fhir/r4, https://tx.fhir.org/r4 (details)
HTA Analysis:	All OK
R5 Dependencies:	http://hl7.org/fhir/5.0/StructureDefinition/extension-DocumentReference.attester
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: Value Set Expansion (2 uses), clinical-status (1 uses), patient (15 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 (6 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), 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), observation-vitalsigns (83 uses), CommonLanguages (60 uses), CarePlan (39 uses), DeviceRequest (27 uses), ImmunizationRecommendation (31 uses), MedicationRequest (34 uses), NutritionOrder (30 uses), ServiceRequest (42 uses), MedicationAdministration (27 uses), MedicationDispense (28 uses), MedicationStatement (27 uses), Procedure (32 uses), Immunization (28 uses), ImagingStudy (56 uses), ObservationCategoryCodes (41 uses), Encounter (32 uses), PractitionerRole (76 uses), VitalSignsUnits (43 uses), SNOMEDCTBodyStructures (33 uses), ObservationMethods (26 uses), Specimen (31 uses), Device (35 uses), DeviceMetric (26 uses), ObservationReferenceRangeMeaningCodes (26 uses), ObservationReferenceRangeAppliesToCodes (26 uses), QuestionnaireResponse (55 uses), MolecularSequence (55 uses), DocumentReference (33 uses), Media (30 uses), DocumentReferenceStatus (4 uses), CompositionStatus (2 uses), Practitioner (22 uses), Organization (42 uses), DocumentRelationshipType (2 uses), EpisodeOfCare (4 uses), AllergyIntolerance (4 uses), AllergyIntoleranceClinicalStatusCodes (2 uses), AllergyIntoleranceVerificationStatusCodes (2 uses), AllergyIntoleranceType (1 uses), AllergyIntoleranceCategory (1 uses), AllergyIntoleranceCriticality (1 uses), RelatedPerson (16 uses), SubstanceCode (1 uses), SNOMEDCTClinicalFindings (8 uses), AllergyIntoleranceSeverity (1 uses), SNOMEDCTRouteCodes (1 uses), LOINCCodes (27 uses), BodyLengthUnits (4 uses), BodyTemperatureUnits (2 uses), BodyWeightUnits (2 uses), PlanDefinition (6 uses), Questionnaire (4 uses), Measure (4 uses), ActivityDefinition (6 uses), RequestStatus (4 uses), CarePlanIntent (2 uses), CarePlanCategory (2 uses), Group (35 uses), CareTeam (9 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), Condition (22 uses), DiagnosticReport (12 uses), CarePlanActivityStatus (1 uses), Location (12 uses), HealthcareService (4 uses), Medication (4 uses), Substance (7 uses), SNOMEDCTMedicationCodes (1 uses), CareTeamStatus (2 uses), CareTeamCategory (1 uses), ConditionClinicalStatusCodes (3 uses), ConditionVerificationStatus (3 uses), ConditionCategoryCodes (3 uses), Condition/DiagnosisSeverity (2 uses), ConditionStage (2 uses), ClinicalImpression (2 uses), ConditionStageType (2 uses), ManifestationAndSymptomCodes (2 uses), CommonTags (4 uses), Coverage (4 uses), FinancialResourceStatusCodes (1 uses), SubscriberRelationshipCodes (2 uses), CoverageClassCodes (3 uses), CoverageCopayTypeCodes (1 uses), ExampleCoverageFinancialExceptionCodes (1 uses), Contract (1 uses), DeviceDefinition (1 uses), UDIEntryType (1 uses), FHIRDeviceStatus (1 uses), FHIRDeviceStatusReason (1 uses), DeviceNameType (1 uses), FHIRDeviceTypes (3 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), FamilyMemberHistory (3 uses), FamilyHistoryStatus (1 uses), FamilyHistoryAbsentReason (1 uses), ConditionOutcomeCodes (1 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), 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 (4 uses), SNOMEDCTAnatomicalStructureForAdministrationSiteCodes (2 uses), SNOMEDCTAdministrationMethodCodes (2 uses), DoseAndRateType (2 uses), Provenance (6 uses), medicationrequest Status (2 uses), medicationRequest Status Reason Codes (1 uses), medicationRequest Intent (2 uses), medicationRequest Category Codes (3 uses), RequestPriority (3 uses), ProcedurePerformerRoleCodes (2 uses), medicationRequest Course of Therapy Codes (1 uses), ClaimResponse (3 uses), OrganizationType (1 uses), ContactEntityType (1 uses), RequestIntent (2 uses), ServiceRequestCategoryCodes (4 uses), ServiceRequestOrderDetailsCodes (2 uses), ParticipantRoles (2 uses), ProcedureReasonCodes (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), ProvenanceEntityRole (1 uses), QuestionnaireResponseStatus (1 uses), QuestionnaireAnswerCodes (1 uses), PatientRelationshipType (2 uses), SpecimenStatus (1 uses), FHIRSpecimenCollectionMethod (1 uses), SpecimenProcessingProcedure (1 uses), SpecimenContainerType (1 uses) hl7.fhir.uv.extensions.r4#5.2.0: ItemWeight (2 uses), SDStatusDerivation (210 uses), SDStandardsStatusReason (4 uses), TypeMustSupport (784 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.xver-r5.r4#0.0.1-snapshot-2: GuideParameterCode (16 uses), ConceptProperties (1 uses), NarrativeStatus (1 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	Comparison with version 8.0.0 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 = 19, info = 12, broken links = 4, pinned = n/a. Show Message Ids

n/a Show Validation Information

fsh-generated/resources/ImplementationGuide-hl7.fhir.us.core.json Show Validation Information (1)

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

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

0 0 : start
47 47   : 0ms  : Analysing http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1010.6|20250411 for validation purposes
47 0    : 0ms  : Parameters: disp-lang=en-US, default-to-latest
47 0    : 0ms  : Version Rules: system-version:http://snomed.info/sct#http://snomed.info/sct/731000124108
47 0    : 0ms  : Prepare include: "(http://hl7.org/fhir/sid/cvx)(01,02,03,04,05,06,07,08,09,10,100,101,102,103,104,105,106,107,108,109,11,110,111,112,113,114,115,116,118,119,120,121,122,123,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,146,147,148,149,15,150,151,152,153,155,158,16,160,161,162,163,164,165,166,167,168,169,17,170,171,172,173,174,175,176,177,178,179,18,182,183,184,185,186,187,188,189,19,190,191,192,193,194,195,196,197,198,20,200,201,202,203,204,205,206,207,208,21,210,211,212,213,214,215,216,217,218,219,22,220,221,222,223,224,227,228,229,23,230,231,24,25,26,28,300,301,302,303,304,305,306,307,308,309,31,310,311,312,313,314,315,316,317,318,319,32,320,321,322,323,324,326,327,33,35,37,38,39,40,41,42,43,44,45,46,47,48,49,50,500,501,502,503,504,505,506,507,508,509,51,510,511,512,513,514,515,516,517,518,519,52,520,521,53,54,55,56,62,66,69,74,75,77,78,80,81,82,83,84,85,88,89,90,91,92,94)"
47 0    : 0ms  : CodeSystem found: "http://hl7.org/fhir/sid/cvx|20250715 (from fhir.tx.support.r4#0.32.0)"
47 0    : 0ms  : Validate "[http://hl7.org/fhir/sid/cvx#197 ("Influenza, high-dose, quadrivalent, PF"), http://hl7.org/fhir/sid/ndc#49281012188 ("FLUZONE High-Dose Quadrivalent Northern Hemisphere")]"
47 0    : 0ms  : Check "http://hl7.org/fhir/sid/cvx#197"
62 15   : 15ms : CodeSystem found: http://hl7.org/fhir/sid/cvx|20250715 (from fhir.tx.support.r4#0.32.0) for http://hl7.org/fhir/sid/cvx
62 0    : 15ms : check code in (http://hl7.org/fhir/sid/cvx)(01,02,03,04,05,06,07,08,09,10,100,101,102,103,104,105,106,107,108,109,11,110,111,112,113,114,115,116,118,119,120,121,122,123,125,126,127,128,129,130,131,132,133,134,135,136,137,138,139,140,141,142,143,144,146,147,148,149,15,150,151,152,153,155,158,16,160,161,162,163,164,165,166,167,168,169,17,170,171,172,173,174,175,176,177,178,179,18,182,183,184,185,186,187,188,189,19,190,191,192,193,194,195,196,197,198,20,200,201,202,203,204,205,206,207,208,21,210,211,212,213,214,215,216,217,218,219,22,220,221,222,223,224,227,228,229,23,230,231,24,25,26,28,300,301,302,303,304,305,306,307,308,309,31,310,311,312,313,314,315,316,317,318,319,32,320,321,322,323,324,326,327,33,35,37,38,39,40,41,42,43,44,45,46,47,48,49,50,500,501,502,503,504,505,506,507,508,509,51,510,511,512,513,514,515,516,517,518,519,52,520,521,53,54,55,56,62,66,69,74,75,77,78,80,81,82,83,84,85,88,89,90,91,92,94) at CodeableConcept.coding[0]
62 0    : 15ms : Code "197" found in http://hl7.org/fhir/sid/cvx|20250715 (from fhir.tx.support.r4#0.32.0)
62 0    : 15ms : Check "http://hl7.org/fhir/sid/ndc#49281012188"

input/examples/location-hospital.json Show Validation Information (2)

input/examples/observation-occupation.json Show Validation Information (2)

input/examples/observation-occupation-industry-unknown.json Show Validation Information (2)

input/examples/observation-occupation-unknown.json Show Validation Information (2)

input/resources/StructureDefinition-us-core-encounter.json Show Validation Information (1)

input/resources/StructureDefinition-us-core-provenance.json Show Validation Information (1)

input/resources/ValueSet-us-core-clinical-result-observation-category.json Show Validation Information (1)

input/resources/ValueSet-us-core-documentreference-type.json Show Validation Information (1)

input/resources/ValueSet-us-core-screening-assessment-observation-category.json Show Validation Information (1)

input/resources/ValueSet-us-core-screening-assessment-observation-maximum-category.json Show Validation Information (1)

input/resources/ValueSet-us-core-simple-observation-category.json Show Validation Information (1)

input/resources/valueset-us-core-condition-code.json Show Validation Information (1)

input/resources/valueset-us-core-problem-or-health-concern.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

04. === 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)

05. === 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)

06. === 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)

07. === 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)

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

• 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)

09. === 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.) ===

• The repeating element has a pattern. The pattern will apply to all the repeats (this has not been clear to all users) (5 uses)

10. === 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)

11. === 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)

15. === 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)

17. === 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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (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 (text.`div`.exists())' (defined in http://hl7.org/fhir/StructureDefinition/DomainResource) (Best Practice Recommendation) (1 uses)

18. === 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|5.0.0 (4 uses)
• Reference to draft CodeSystem urn:iso:std:iso:11073:10101|2024-12-05 from fhir.tx.support.r4#0.32.0 (1 uses)
• Reference to draft ValueSet http://hl7.org/fhir/ValueSet/servicerequest-category|4.0.1 (3 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.1.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 3.1.0 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse' to 'http://terminology.hl7.org/ValueSet/v3-PurposeOfUse|3.1.0' (0 uses)

19. === 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) ===

• A definition for CodeSystem 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found, so the code cannot be validated (4 uses)
• The definition for the Code System with URI 'urn:oid:2.16.840.1.113883.6.238' doesn't provide any codes so the code cannot be validated (15 uses)

21. === 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)===

• A definition for CodeSystem 'https://www.nubc.org/CodeSystem/PatDischargeStatus' could not be found, so the code cannot be validated (1 uses)

22. ===FHIR R4 http://hl7.org/fhir/ValueSet/formatcodes is in error which 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)

23. === The US Core Team is aware of this and is actively moving its value sets to VSAC and code systems to THO in each publication cycle. See the change log for details. ===

• INFORMATION: CodeSystem/careplan-category: 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)
• INFORMATION: CodeSystem/condition-category: 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)
• INFORMATION: CodeSystem/us-core-category: 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)
• INFORMATION: CodeSystem/us-core-documentreference-category: 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)

24. === These values are indeed large, and the ig-publisher informs the reader that the expansion is incomplete. ===

• INFORMATION: ValueSet.where(id = 'us-core-diagnosticreport-report-and-note-codes'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'us-core-documentreference-type'): The value set expansion is too large, and only a subset has been displayed (1 uses)
• INFORMATION: ValueSet.where(id = 'us-core-laboratory-test-codes'): The value set expansion is too large, and only a subset has been displayed (1 uses)

26. === 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.2.0 (this may not be a problem, but you should check that it's not intended to match a slice) (140 uses)

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

• A definition for CodeSystem 'http://example.org/fhir/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|9.0.0-ballot (0 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization|9.0.0-ballot (0 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner|9.0.0-ballot (0 uses)
• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-pulse-oximetry|9.0.0-ballot (0 uses)

28. === 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. ===

• 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)

29. === US Core thoroughly documents its Must Support expectations for the must supports on the Must Support page, including how they apply to the choice of target references in the Must Support - Resource References section. (Also, 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)

30. === Two Bundle examples use this profile and one 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)

31. === 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)

33. === To comply with Executive Order 14168, the following changes were made: 1)Removed USCDI mapping, guidance, and examples for the US Core Observation Sexual Orientation Profile 2) Removed the US Core Birth Sex Extension, guidance, and examples from the US Core Patient Profile 3) Deprecated the US Core Gender Identity and US Core Sex Extensions and removed them from the US Core Profile, USCDI mapping, guidance, and examples. Although the profiles and extensions will remain in this version of US Core to allow for backward compatibility - no examples will be supplied. ===

• WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-birthsex'): The Implementation Guide contains no examples for this extension (1 uses)
• WARNING: StructureDefinition.where(url = 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sexual-orientation'): The Implementation Guide contains no examples for this profile (1 uses)

34. === US Core provides IG-specific guidance on interpreting Must Support for slices at `~/must-support.html#must-support---slices`. Where we state: "...the slicer's Must Support property only defines the element level Must Support/Additional USCDI property. In other words, the slicer's Must Support/Additional USCDI is not inherited by the slices, and each slice must be explicitly tagged with the Must Support/Additional USCDI property to define that slice's conformance strength. If no Must Support/Additional USCDI property is defined for the slice, this lengthy chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Slices.20not.20inheriting.20preferred.20bindings.20from.20root/with/514257770 and the resulting tracker FHIR-50391. ===

• The slice 'CLIA' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'NAIC' on path 'Organization.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'NCSBNID' on path 'Practitioner.identifier' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'screening-assessment' on path 'Condition.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'screening-assessment' on path 'Observation.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'us-core' on path 'Observation.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'us-core-pmo-category' on path 'ServiceRequest.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)
• The slice 'uscore' on path 'DocumentReference.category' is not marked as 'must-support' which is not consistent with the element that defines the slicing, where 'must-support' is true (1 uses)

35. === These messages have been acknowledged for this release. After reviewing the implications for conformant systems and downstream publications, we will consider updating and/or adopting the recommended replacement in a future release. ===

• The concept 'urn:hl7-org:sdwg:ccda-structuredBody:1.1' is deprecated and its use should be reviewed (2 uses)
• The concept 'urn:hl7-org:sdwg:ccda-structuredBody:2.1' is deprecated and its use should be reviewed (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-maxValueSet|5.2.0 is deprecated (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/elementdefinition-minValueSet|5.2.0 is deprecated (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/ordinalValue|5.2.0 is deprecated with the note: 'Replaced by [[[http://hl7.org/fhir/StructureDefinition/itemWeight]]]' (1 uses)
• The extension http://hl7.org/fhir/StructureDefinition/regex|5.2.0 is deprecated with the note: 'This was deprecated in favor of using a constraint on the element using FHIRPath, since constraints allow for the provision of a human readable message associated with the regex' (1 uses)

36. === These Extension StructureDefinitions were examined, and there are no substantive changes between versions and thus no reason to specify a version ===

• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate' to 'http://hl7.org/fhir/StructureDefinition/condition-assertedDate|5.2.0' (2 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/ordinalValue'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/ordinalValue' to 'http://hl7.org/fhir/StructureDefinition/ordinalValue|5.2.0' (1 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo' to 'http://hl7.org/fhir/StructureDefinition/workflow-supportingInfo|5.2.0' (2 uses)

37. === The following Extensions are in SDC, a dependent IG, or the FHIR R4 specification and not under the direct control of US Core editors ===

• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/display'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/display' to 'http://hl7.org/fhir/StructureDefinition/display|5.2.0' (1 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-completionMode|5.2.0' (1 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.2.0', found versions: 1.0.0 (from hl7.fhir.uv.extensions.r4#1.0.0), 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.1.0 (from hl7.fhir.uv.extensions.r4#5.1.0), 5.2.0 (from hl7.fhir.uv.extensions.r4#5.2.0). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature' to 'http://hl7.org/fhir/StructureDefinition/questionnaireresponse-signature|5.2.0' (2 uses)

38. === As explained in the section "US Core ValueSet and CodeSystem versions" US Core does not "pin" the version of the terminology to a specific version of US Core. Instead US Core value set packages containing value sets expanded with the updated code system versions will be made available.

• There are multiple different potential matches for the url 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1247.71'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '20250702', found versions: 20241214 (from us.nlm.vsac#0.24.0), 20250702 (from us.nlm.vsac#0.24.0). Suggested fix: change the canonical reference from 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1247.71' to 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1247.71|20250702' (2 uses)
• There are multiple different potential matches for the url 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '20250610', found versions: 20241008 (from us.nlm.vsac#0.24.0), 20250610 (from us.nlm.vsac#0.24.0). Suggested fix: change the canonical reference from 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13' to 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.13|20250610' (2 uses)
• There are multiple different potential matches for the url 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.24'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '20250529', found versions: 20241105 (from us.nlm.vsac#0.24.0), 20250529 (from us.nlm.vsac#0.24.0). Suggested fix: change the canonical reference from 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.24' to 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113762.1.4.1267.24|20250529' (1 uses)
• There are multiple different potential matches for the url 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.19579'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '20250724', found versions: 20240606 (from us.nlm.vsac#0.24.0), 20250724 (from us.nlm.vsac#0.24.0). Suggested fix: change the canonical reference from 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.19579' to 'http://cts.nlm.nih.gov/fhir/ValueSet/2.16.840.1.113883.1.11.19579|20250724' (2 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/narrative-status'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.0.0 (from hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/narrative-status' to 'http://hl7.org/fhir/narrative-status|5.0.0' (1 uses)
• There are multiple different potential matches for the url 'http://hl7.org/fhir/observation-status'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 4.0.1 (from hl7.fhir.r4.core#4.0.1), 5.0.0 (from hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2). Suggested fix: change the canonical reference from 'http://hl7.org/fhir/observation-status' to 'http://hl7.org/fhir/observation-status|5.0.0' (1 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/condition-category'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '2.0.0', found versions: 0.5.0 (from hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2), 1.0.0 (from hl7.terminology#5.5.0), 1.0.1 (from hl7.terminology.r4#6.5.0), 2.0.0 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/condition-category' to 'http://terminology.hl7.org/CodeSystem/condition-category|2.0.0' (0 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/observation-category'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '2.0.0', found versions: 0.1.0 (from hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2), 1.0.0 (from hl7.terminology#5.5.0), 1.0.1 (from hl7.terminology.r4#6.5.0), 2.0.0 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/observation-category' to 'http://terminology.hl7.org/CodeSystem/observation-category|2.0.0' (0 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/CodeSystem/v3-NullFlavor'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '3.0.0', found versions: 2.1.0 (from hl7.fhir.uv.xver-r5.r4#0.0.1-snapshot-2), 3.0.0 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/CodeSystem/v3-NullFlavor' to 'http://terminology.hl7.org/CodeSystem/v3-NullFlavor|3.0.0' (0 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/provenance-agent-type'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '1.0.1', found versions: 1.0.0 (from hl7.terminology#5.5.0), 1.0.1 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/provenance-agent-type' to 'http://terminology.hl7.org/ValueSet/provenance-agent-type|1.0.1' (0 uses)
• There are multiple different potential matches for the url 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition'. It might be a good idea to fix to the correct version to reduce the likelihood of a wrong version being selected by an implementation/implementer, or use the [IG Parameter `pin-canonicals`](https://hl7.org/fhir/tools/CodeSystem-ig-parameters.html). Using version '5.0.0', found versions: 3.0.0 (from hl7.terminology#5.5.0), 5.0.0 (from hl7.terminology.r4#7.0.0). Suggested fix: change the canonical reference from 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition' to 'http://terminology.hl7.org/ValueSet/v3-USEncounterDischargeDisposition|5.0.0' (0 uses)

40 === Similar to the base FHIR specification, the Guide states in the introductory paragraph of the Conformance section's General Requirements page, "The conformance verbs - SHALL, SHOULD, MAY - used in this guide are defined in FHIR Conformance Rules, and these conventions are strictly adhered to throughout the guide. ===

• The html source contains the word 'SHALL NOT' but it is not in a text phrase marked as a conformance clause:% (104 uses)
• The html source contains the word 'SHALL' but it is not in a text phrase marked as a conformance clause:% (75 uses)
• The html source contains the word 'SHOULD' but it is not in a text phrase marked as a conformance clause:% (25 uses)

43 === The error is due to an issue with the terminology server, not the implementation guide. For details, see the Zulip chat at: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/whither.20ICD9cm.20in.20THO.207.2E0.2E0.3F/with/559122224 ===

• ERROR: ValueSet.where(id = 'us-core-condition-code'): Error from https://tx.fhir.org/r4: The code system definition for http://hl7.org/fhir/sid/icd-9-cm is a fragment, so this expansion is not permitted unless the expansion parameter "incomplete-ok" has a value of "true" (1 uses)

44 === Although it may not be published before this ballot version is published, this link will resolve when US Core 8.0.1 is published. ===

• ERROR: changes-between-versions.html#/html/body/div/div/div/div/div/ul/li/a at Line 1141, column 8: The link 'comparison-v8.0.1/index.html' for "Comparison with version 8.0.1" cannot be resolved (0 uses)

45 === This error will be present until the publication team can address it. See this Zulip chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Publisher.20v2.2E0.2E24.20-.20error.20in.20local.20build/with/547712458 ===

• ERROR: ImplementationGuide/hl7.fhir.us.core: ImplementationGuide.definition.extension[96].url: No definition could be found for URL value 'http://hl7.org/fhir/tools/StructureDefinition/expansion-parameters' (0 uses)

46 === The additional binding purpose code for this value set is "Preferred"; therefore, it does not show up in all the provided examples.===

• 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) specified in an additional binding, and a coding is recommended to come from this value set (codes = http://nucc.org/provider-taxonomy#208D00000X) (1 uses)

47 === This NDC codes has been checked and is a valid Unit of Use NDC codes as described on the CDC's IIS website: https://www2a.cdc.gov/vaccines/iis/iisstandards/ndc_tableaccess.asp. There are issues with the NDC directory used for validation, because it is incomplete. For details and the variance approval from the product director, see this Zulip chat: https://chat.fhir.org/#narrow/channel/179252-IG-creation/topic/Immunization.20NDC.20Code.20error/with/562172015 ===

• ERROR: Immunization/imm-1: Immunization.vaccineCode.coding[1].code: Unknown code '49281012188' in the CodeSystem 'http://hl7.org/fhir/sid/ndc' version '' (1 uses)
• INFORMATION: Immunization/imm-1: Immunization.vaccineCode.coding[1].code: Code "49281012188" not found in NDC (1 uses)

49 === This guide uses a custom liquid script to generat the the CapabilityStatement narrative. To facilate rendering of displays and relative links to human readable content, the Capability statemnent uses the Display Name and Narrative Link extensions on the canonicals types - 'supportedProfiles', 'operation.definition', and 'implementationGuide' elements. As a result, the relative links in the Narrative Link extensions will generate "No definition could be found" warnings wherever they are used. For example: "No definition could be found for URL value 'StructureDefinition-us-core-allergyintolerance.html'" The warning have been checked and are valid links internal to to guide or to other guides.

• A definition could not be found for Canonical URL% (4 uses)
• No definition could be found for URL value% (120 uses)

Errors sorted by type

Details_for__matching_against_Profile_

TYPE_SPECIFIC_CHECKS_DT_CANONICAL_MULTIPLE_POSSIBLE_VERSIONS

Type_Specific_Checks_DT_URL_Resolve

Unknown_Code_in_Version