Validation Results for USCore

Generated Tue Dec 19 21:29:30 UTC 2023, FHIR version 4.0.1 for hl7.fhir.us.core#7.0.0-ballot (canonical = http://hl7.org/fhir/us/core (history)). See Full QA Report

Quality Checks
Publisher Version:	IG Publisher Version: v1.5.8
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:	package-id hl7.fhir.us.core version 7.0.0-ballot path http://hl7.org/fhir/us/core/2024Jan Pub-Mode working release status ballot sequence STU7 desc The January 2024 Ballot Version adds United States Core Data for Interoperability (USCDI) V4 updates that the Office of the National Coordinator (ONC) published in July 2023. It also addresses over 50 trackers submitted by implementers since the publication of US Core ver 6.1.0. For a detailed list of the changes for this version, see the Change Notes (http://hl7.org/fhir/us/core/2024Jan/changes.html). descmd The January 2024 Ballot Version adds United States Core Data for Interoperability (USCDI) V4 updates that the Office of the National Coordinator (ONC) published in July 2023. It also addresses over 50 trackers submitted by implementers since the publication of US Core ver 6.1.0. For a detailed list of the changes for this version, see the Change Notes. changes changes.html Proposed path for this publication should usually be the canonical with the version or sequence appended and then some kind of label (typically '-snapshot')
Supressed Messages:	125 Suppressed Issues
Dependency Checks:	Package Version FHIR Canonical Web Base Comment hl7.fhir.us.core 7.0.0-ballot R4 http://hl7.org/fhir/us/core hl7.terminology.r4 5.3.0 O R4 http://terminology.hl7.org http://terminology.hl7.org/5.3.0 Latest Release is 5.4.0 hl7.fhir.uv.bulkdata 2.0.0 M R4 http://hl7.org/fhir/uv/bulkdata http://hl7.org/fhir/uv/bulkdata/STU2 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.1.0 us.nlm.vsac 0.17.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 ihe.formatcode.fhir 1.1.0 M R4 https://profiles.ihe.net/fhir/ihe.formatcode.fhir https://profiles.ihe.net/fhir/ihe.formatcode.fhir/1.1.0 hl7.fhir.uv.extensions 5.1.0-ballot1 V R5 http://hl7.org/fhir/extensions http://hl7.org/fhir/extensions/5.1.0-ballot FHIR Version Mismatch 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 5.4.0 Templates: hl7.fhir.template#current -> hl7.base.template#current -> fhir.base.template#current. Tools: current
Dependent IGs:	no references
Global Profiles:	(none declared)
HTA Analysis:	4 issues
R5 Dependencies:	(none)
Draft Dependencies:	hl7.fhir.r4.core#4.0.1: GuideParameterCode (17 uses), Ordinal Value (54 uses), FHIR Defined Concept Properties (1 uses), observation-vitalsigns (91 uses), CommonLanguages (55 uses), CarePlan (37 uses), DeviceRequest (26 uses), ImmunizationRecommendation (30 uses), MedicationRequest (32 uses), NutritionOrder (29 uses), ServiceRequest (37 uses), MedicationAdministration (26 uses), MedicationDispense (27 uses), MedicationStatement (26 uses), Procedure (31 uses), Immunization (27 uses), ImagingStudy (54 uses), ObservationCategoryCodes (46 uses), Encounter (30 uses), Practitioner (55 uses), PractitionerRole (60 uses), Organization (65 uses), CareTeam (33 uses), RelatedPerson (47 uses), VitalSignsUnits (47 uses), SNOMEDCTBodyStructures (31 uses), ObservationMethods (25 uses), Specimen (29 uses), Device (68 uses), DeviceMetric (25 uses), ObservationReferenceRangeMeaningCodes (25 uses), ObservationReferenceRangeAppliesToCodes (25 uses), QuestionnaireResponse (52 uses), MolecularSequence (53 uses), DocumentReference (29 uses), Media (29 uses), AllergyIntolerance (3 uses), AllergyIntoleranceClinicalStatusCodes (2 uses), AllergyIntoleranceVerificationStatusCodes (2 uses), AllergyIntoleranceType (1 uses), AllergyIntoleranceCategory (1 uses), AllergyIntoleranceCriticality (1 uses), SubstanceCode (1 uses), SNOMEDCTClinicalFindings (7 uses), AllergyIntoleranceSeverity (1 uses), SNOMEDCTRouteCodes (3 uses), BodyLengthUnits (4 uses), BodyTemperatureUnits (2 uses), BodyWeightUnits (2 uses), LOINCCodes (21 uses), PlanDefinition (4 uses), Questionnaire (3 uses), Measure (3 uses), ActivityDefinition (4 uses), RequestStatus (3 uses), CarePlanIntent (2 uses), CarePlanCategory (2 uses), Group (35 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), 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), DocumentReferenceStatus (2 uses), CompositionStatus (1 uses), DocumentRelationshipType (1 uses), EncounterStatus (2 uses), ServiceType (1 uses), EpisodeOfCare (3 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 (1 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), 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.bulkdata#2.0.0: BulkDataAccessIG (1 uses) hl7.fhir.uv.extensions#5.1.0-ballot1: TargetElement (1 uses), SDStatusDerivation (426 uses), TypeMustSupport (471 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#1.0.0-candidate: ResourceSortExt (426 uses) hl7.terminology.r5#5.3.0: ObservationCategoryCodes (162 uses), EndpointConnectionType (2 uses), UsageContextType (1 uses), AllergyIntoleranceClinicalStatusCodes (3 uses), AllergyIntoleranceVerificationStatus (3 uses), ProvenanceParticipantType (6 uses), ConditionVerificationStatus (5 uses), ConditionCategoryCodes (8 uses), SubscriberRelationshipCodes (1 uses), CoverageClassCodes (6 uses), OrganizationType (4 uses), ObservationReferenceRangeMeaningCodes (17 uses)
Modifier Extensions:	(none)
Previous Version Comparison:	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
Narratives Suppressed	Bundle/docref-example-1, Bundle/docref-example-2, DocumentReference/discharge-summary, Patient/example-targeted-provenance, Provenance/example-targeted-provenance
Summary:	errors = 5, warn = 0, info = 0, broken links = 0

n/a Show Validation Information

C:\temp\hl7.fhir.us.core#7.0.0-ballot\input\examples\observation-satO2-fiO2.json Show Validation Information (2)

C:\temp\hl7.fhir.us.core#7.0.0-ballot\input\examples\procedure-rehab.json Show Validation Information (2)

C:\temp\hl7.fhir.us.core#7.0.0-ballot\input\examples\servicerequest-rehab.json Show Validation Information (2)

C:\temp\hl7.fhir.us.core#7.0.0-ballot\input\resources\StructureDefinition-us-core-vital-signs.json Show Validation Information (1)

C:\temp\hl7.fhir.us.core#7.0.0-ballot\input\resources\ValueSet-simple-language.json Show Validation Information (1)

Suppressed Messages (Warnings, hints, broken links)

=== 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 and it means validation errors may occur when validating against this version of the US Core Pulse Oximetry Profile. A change request to relax the binding in the FHIR Vitals profile to has been made and approved 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: StructureDefinition/us-core-vital-signs: StructureDefinition: illegal attempt to change the binding on Observation.component.value[x] from required to extensible (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)

=== Code from extensibly bound to NUCC for US Core and not from base FHIR preferred c80-practice-codes valueset (1)===

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

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

=== 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 for transaction 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)
• WARNING: Patient/example-targeted-provenance: Patient: 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: Provenance/example-targeted-provenance: Provenance: 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 US Core Observation Profile are based on US Vendor and Community input and decided that the `Observation.performer` element is optional for Many Observation profiles. ===

• WARNING: Observation/at-home-in-vitro-test: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/blood-pressure: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/bmi: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/bp-data-absent: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/capillary-refill-time-nail-bed: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-erythrocytes: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-hematocrit: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-hemoglobin: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-leukocytes: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-mch: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-mchc: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-mcv: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/cbc-platelets: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-femur-l-armass-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-femur-l-t-score-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-femur-l-z-score-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-hip-l-armass-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-hip-l-t-score-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/dxa-hip-l-z-score-bmd: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/ekg-impression: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/ekg-lead: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/head-circumference: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/heart-rate-rhythm: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/heart-rate: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/height: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/jugular-vein-distension: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/length: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/observation-occupation-industry-unknown: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/observation-occupation-unknown: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/observation-occupation: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/ofc-percentile: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/oxygen-saturation: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/p-r-interval-ekg-lead: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/pediatric-bmi-example: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/pediatric-wt-example: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/pregnancy-intent: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/pregnancy-status: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/pulse-intensity-palpation: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/q-t-interval-ekg-lead: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/qrs-dur-ekg-lead: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/respiratory-rate: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/satO2-fiO2: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-bun: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-calcium: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-chloride: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-co2: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-creatinine: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-glucose: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-potassium: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-sodium: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/serum-total-bilirubin: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/sexual-orientation-example: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/some-day-smoker: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/temperature: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/urobilinogen: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/weight: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/xray-chest-findings: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)
• WARNING: Observation/xray-chest-impression: Observation: Best Practice Recommendation: In general, all observations should have a performer (1 uses)

=== The following comment is understood and acknowledged. In some cases it inherits binding from core and A change request to correct this has been applied to the base FHIR ver 4.3.0 (“Release 4B”) to clarify the binding applies to the Quantity data type. Will need to slice value[x] in future ===

• INFORMATION: StructureDefinition/us-core-vital-signs: StructureDefinition.differential.element[14].binding: 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 (2 uses)

=== These Examples demonstrate use of additional Codes or Identifiers not defined in US Core profiles (7)===

• This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization|7.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|7.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-provenance|7.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-pulse-oximetry|7.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 (16 uses)

=== These warnings are due to using the actual base Type for the _id or _tag SearchParameter expression instead of using "Resource". Reviewed with publishing in Nov 2021 and OK with suppressing these Warnings (source: https://chat.fhir.org/#narrow/stream/179252-IG-creation/topic/Bad.20derived.20searchparameters) (8) ===

• WARNING: SearchParameter/us-core-documentreference-id: SearchParameter: The expression 'DocumentReference.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-encounter-id: SearchParameter: The expression 'Encounter.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-patient-id: SearchParameter: The expression 'Patient.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-practitioner-id: SearchParameter: The expression 'Practitioner.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-questionnaireresponse-id: SearchParameter: The expression 'QuestionnaireResponse.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-relatedperson-id: SearchParameter: The expression 'RelatedPerson.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-servicerequest-id: SearchParameter: The expression 'ServiceRequest.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)
• WARNING: SearchParameter/us-core-specimen-id: SearchParameter: The expression 'Specimen.id' is not compatible with the expression 'Resource.id' in the derivedFrom SearchParameter http://hl7.org/fhir/SearchParameter/Resource-id, and this likely indicates that the derivation relationship is not valid (1 uses)

=== This Examples conform to US Core Average Blood Pressure Profile. It defines additional slices (translations) to the FHIR BP profile for the code and component codes and will not match FHIR BP profile and vice versa ===

• INFORMATION: Observation/average-blood-pressure: Observation.code.coding[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure|7.0.0-ballot (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
• INFORMATION: Observation/average-blood-pressure: Observation.component[0].code.coding[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/bp|4.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
• INFORMATION: Observation/average-blood-pressure: Observation.component[0].code.coding[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure|7.0.0-ballot (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
• INFORMATION: Observation/average-blood-pressure: Observation.component[1].code.coding[0]: This element does not match any known slice defined in the profile http://hl7.org/fhir/StructureDefinition/bp|4.0.1 (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)
• INFORMATION: Observation/average-blood-pressure: Observation.component[1].code.coding[1]: This element does not match any known slice defined in the profile http://hl7.org/fhir/us/core/StructureDefinition/us-core-average-blood-pressure|7.0.0-ballot (this may not be a problem, but you should check that it's not intended to match a slice) (1 uses)

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

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

=== This is a yet to be resolved ICD10PCS issue with publishing/terminology server. see: https://terminology.hl7.org/CodeSystem-icd10PCS.html the code has been verified as a valid ICD10-PCS code (2) ===

• INFORMATION: Procedure/rehab: Procedure.code.coding[1]: The definition for the Code System with URI 'http://www.cms.gov/Medicare/Coding/ICD10' doesnt provide any codes so the code cannot be validated (0 uses)
• INFORMATION: ServiceRequest/rehab: ServiceRequest.code.coding[1]: The definition for the Code System with URI 'http://www.cms.gov/Medicare/Coding/ICD10' doesnt provide any codes so the code cannot be validated (0 uses)
• WARNING: Procedure/rehab: Procedure.code: Code System URI 'http://www.cms.gov/Medicare/Coding/ICD10' could not be found so the code cannot be validated (0 uses)
• WARNING: ServiceRequest/rehab: ServiceRequest.code: Code System URI 'http://www.cms.gov/Medicare/Coding/ICD10' could not be found so the code cannot be validated (0 uses)

=== US Core Goal Description Binding is extensible which allow for text only and guidance to use free text for Goal.description is given in the US Core Goal Implementation Guidance (1). There are 2 Goal examples, Goal/goal-sdoh-2 uses a code this one does not. ===

• No code provided, and a code should be provided from the value set 'US Core Goal Codes' (http://hl7.org/fhir/us/core/ValueSet/us-core-goal-description|7.0.0-ballot) (1 uses)

=== Using standard extension capabilitystatement-expectation for CapabilityStatement in additional contexts to fully express intended capabilities: see FHIR-12419 (115) ===

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

=== VSAC issues - The tooling infrastructure currently is unable to access these codes. They have been checked and the concepts are correct (5) ===

• The definition for the Code System with URI 'urn:oid:2.16.840.1.113883.6.238' doesnt provide any codes so the code cannot be validated (17 uses)

=== these ValueSets are in FHIR Core/THO and not under the direct control of US Core editors ===

• Reference to draft item http://hl7.org/fhir/narrative-status|4.0.1 (1 uses)
• Reference to draft item http://terminology.hl7.org/CodeSystem/condition-category|0.5.0 (2 uses)
• Reference to draft item http://terminology.hl7.org/CodeSystem/observation-category|0.1.0 (43 uses)
• Reference to draft item http://terminology.hl7.org/CodeSystem/provenance-participant-type|0.1.0 (3 uses)

==== The following code system 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 (5) ===========

• The definition for the Code System with URI 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' doesnt provide any codes so the code cannot be validated (4 uses)
• WARNING: Observation/observation-occupation-industry-unknown: Observation.value.ofType(CodeableConcept): Code System URI '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): Code System URI '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): Code System URI '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): Code System URI 'http://terminology.hl7.org/CodeSystem/PHOccupationalDataForHealthODH' could not be found so the code cannot be validated (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 bundle is to the $docref operation and not a search ====

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

==== This is a known issues with the terminology service - there is no timeline for their resolution ===

• 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 (0 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 IHE format code package and the value set uses the corrected FHIR R5 codes. ===

• INFORMATION: Bundle/66c8856b-ba11-4876-8aa8-467aad8c11a2: Bundle.entry[2].resource/*Endpoint/71*/.payloadType[0].coding[0]: The code 'urn:hl7-org:sdwg:ccda-structuredBody:1.1' is valid but is deprecated (1 uses)
• INFORMATION: Bundle/docref-example-1: Bundle.entry[0].resource/*DocumentReference/ccd123*/.content[0].format: The Coding provided (http://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode#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://ihe.net/fhir/ihe.formatcode.fhir/CodeSystem/formatcode#urn:hl7-org:sdwg:ccda-structuredBody:2.1: 'For documents following C-CDA 2.1 constraints using a structured body.'' was not found in the value set 'http://hl7.org/fhir/ValueSet/formatcodes|4.0.1') (1 uses)
• INFORMATION: Bundle/docref-example-1: Bundle.entry[0].resource/*DocumentReference/ccd123*/.content[0].format: The code 'urn:hl7-org:sdwg:ccda-structuredBody:2.1' is valid but is deprecated (1 uses)
• INFORMATION: DocumentReference/episode-summary: DocumentReference.content[0].format: The code 'urn:hl7-org:sdwg:ccda-structuredBody:2.1' is valid but is deprecated (1 uses)
• INFORMATION: Organization/saint-luke-w-endpoint: Organization.contained[0]/*Endpoint/75*/.payloadType[0].coding[0]: The code 'urn:hl7-org:sdwg:ccda-structuredBody:1.1' is valid but is deprecated (1 uses)

Error from server: Unable to provide support for code system http://www.nubc.org/patient-discharge

• Code System URI 'http://www.nubc.org/patient-discharge' could not be found so the code cannot be validated (2 uses)
• WARNING: Encounter/1036: Encounter.hospitalization.dischargeDisposition: Code System URI 'http://www.nubc.org/patient-discharge' could not be found so the code cannot be validated; Unable to check whether the code is in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-discharge-disposition|7.0.0-ballot (1 uses)
• WARNING: Encounter/1036: Encounter.hospitalization.dischargeDisposition: Unable to check whether the code is in the value set http://hl7.org/fhir/us/core/ValueSet/us-core-discharge-disposition|7.0.0-ballot (1 uses)
• WARNING: ValueSet.where(id = 'us-core-discharge-disposition'): Error from http://tx.fhir.org/r4: Unable to provide support for code system http://www.nubc.org/patient-discharge (1 uses)

Errors sorted by type

Terminology_TX_NoValid_12