Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response vs http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment

Messages

Metadata

Name	Value		Comments
abstract	false	true	Values Differ
baseDefinition	http://hl7.org/fhir/StructureDefinition/Observation
copyright	Used by permission of HL7 International, all rights reserved Creative Commons License		Removed the item 'Used by permission of HL7 International, all rights reserved Creative Commons License'
date	2021-11-12	2021-12-07T14:30:02+00:00	Values Differ
description	Profile for observations that represent question and answer pairs from from surveys/questionnaires such as Social Determinants of Health (SDOH) screening instruments.	Profile for Social Determinants of Health (SDOH) observations that involve assessment (e.g., by a provider, payer, etc.) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). The Cross-Group Projects work group granted an exception to US Core on 06/10/2021 - Jira ticket 32892.	Values Differ
experimental
fhirVersion	4.0.1
jurisdiction
jurisdiction[0]	urn:iso:std:iso:3166#US
kind	resource
name	USCoreObservationScreeningResponse	SDOHCCObservationAssessment	Values Differ
publisher	HL7 International - Cross-Group Projects	HL7 International - Patient Care WG	Values Differ
purpose
status	active	draft	Values Differ
title	US Core Screening Response Observation Profile	SDOHCC Observation Assessment	Values Differ
type	Observation
url	http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response	http://hl7.org/fhir/us/sdoh-clinicalcare/StructureDefinition/SDOHCC-ObservationAssessment	Values Differ
version	4.1.0	1.1.0	Values Differ

Structure

Name	L Flags	L Card.	L Type	L Description & Constraints	R Flags	R Card.	L Type	L Description & Constraints	Comments
Observation	I				I				Elements differ in short: "questionnaire observations" "SDOH assessment observation" Elements differ in definition: "For Observations derived from surveys/questionnaires." "For SDOH observations derived from assessment of the individual." Elements differ in comments: "Used for simple observations such as education status, food insecurity observations, etc. This profile allows the representation of SDOH observations based on SDOH screening questionnaire responses (which can also be represented using SDC QuestionnaireResponse)." "For representation of SDOH observations that involve assessment (e.g., by a provider or payer) as opposed to being derived only from screening surveys (as is the case for the SDOHCC Screening Response Observation). Many of the SDOHCC profiles reference one another. One flow supported by this IG is that QuestionnaireResponses result in Observations that can be used as evidence for Conditions that can lead to Goals, ServiceRequests and Procedures. However, alternatives paths are also possible."
id	Σ				Σ
meta	Σ				Σ
implicitRules	?!Σ				?!Σ
language
text
contained
extension			Extension				Extension
modifierExtension	?!				?!
identifier	Σ				Σ
basedOn	Σ				Σ
partOf	Σ				Σ
status	?!SΣ				?!SΣ
Slices for category	S								Elements differ in requirements: "To identify that observation is derived from a questionnaire." "Used for filtering what observations are retrieved and displayed." Elements differ in definition for mustSupport: "true" "false"
code	SΣ				SΣ				Elements differ in comments: "*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation." "*All* code-value and, if present, component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation. As the Gravity Project continues to refine content for the SDOH categories (e.g., food, housing, transportation, etc.), this value set binding strength may change and may be refined to codes (including LOINC and SNOMED) that pertain to SDOH categories." Example/preferred bindings differ at Observation.code using binding from USCoreObservationScreeningResponse
subject	SΣ				SΣ				Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Group], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient]])
focus	Σ				Σ
encounter	Σ				Σ
effective[x]	SΣI				Σ				Elements differ in definition: "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time"." "The time or time-period the observed value is asserted as being true. For biological subjects - e.g. human patients - this is usually called the "physiologically relevant time". This is usually either the time of the procedure or of specimen collection, but very often the source of the date/time is not known, only the date/time itself." Elements differ in comments: "At least a date should be present unless this observation is a historical report." "At least a date should be present unless this observation is a historical report. For recording imprecise or "fuzzy" times (For example, a blood glucose measurement taken "after breakfast") use the [Timing] datatype which allow the measurement to be tied to regular life events." Elements differ in definition for mustSupport: "true" "false"
issued	Σ				Σ
performer	SΣ				SΣ				Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/StructureDefinition/PractitionerRole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-relatedperson]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/RelatedPerson], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitioner], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-practitionerrole], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-organization], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-careteam]])
value[x]	SΣI				SΣI				Elements differ in comments: "An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value." "An observation may have; 1) a single value here, 2) both a value and a set of related or component values, or 3) only a set of related or component values. If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section] below."
dataAbsentReason	SI				I				Elements differ in comments: ""Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For a given LOINC question, if the LOINC answer list includes concepts such as 'unknown' or 'not available', they should be used for Observation.value. Where these concepts are not part of the value set for Observation.value, the Observation.dataAbsentReason can be used if necessary and appropriate." "Null or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "specimen unsatisfactory". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Note that an observation may only be reported if there are values to report. For example differential cell counts values may be reported only when > 0. Because of these options, use-case agreements are required to interpret general observations for null or exceptional values." Elements differ in definition for mustSupport: "true" "false"
interpretation
note
bodySite
method
specimen
device
referenceRange	I				I
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
low	I				I
high	I				I
type
appliesTo
age
text
hasMember	Σ				Σ
derivedFrom	SΣ				Σ				Elements differ in short: "Related questionnaire responses or observations that the observation is made from" "Related measurements the observation is made from" Elements differ in definition: "Questionnaire responses or observations from which this observation value is derived." "The target resource that represents a measurement from which this observation value is derived. For example, a calculated anion gap or a fetal measurement based on an ultrasound image." Elements differ in definition for mustSupport: "true" "false" Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-screening-response], CanonicalType[http://hl7.org/fhir/uv/sdc/StructureDefinition/sdc-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-documentreference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/DocumentReference], CanonicalType[http://hl7.org/fhir/StructureDefinition/ImagingStudy], CanonicalType[http://hl7.org/fhir/StructureDefinition/Media], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
component	SΣ				Σ				Elements differ in definition: "Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples: Individuals may be multiracial. Component is used to capture one or more races." "Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations." Elements differ in comments: "For questions represented in LOINC that specify “check all that apply”, the LOINC question should be used for Observation.code and for Observation.component.code. For “check all that apply” questions, the answers (regardless of whether one or more are selected) should only be represented using Observation.component.value and Observation.value should be empty." "For a discussion on the ways Observations can be assembled in groups together see [Notes] below." Elements differ in definition for mustSupport: "true" "false"
id
extension			Extension				Extension
modifierExtension	?!Σ				?!Σ
code	SΣ				Σ				Elements differ in definition for mustSupport: "true" "false"
value[x]	SΣI				Σ				Elements differ in comments: "see `Observation.value[x]` comments" "Used when observation has a set of component observations. An observation may have both a value (e.g. an Apgar score) and component observations (the observations from which the Apgar score was derived). If a value is present, the datatype for this element should be determined by Observation.code. A CodeableConcept with just a text would be used instead of a string if the field was usually coded, or if the type associated with the Observation.code defines a coded value. For additional guidance, see the [Notes section] below." Elements differ in definition for mustSupport: "true" "false"
dataAbsentReason	SI				I				Elements differ in comments: "see `Observation.dataAbsentReason` comments" ""Null" or exceptional values can be represented two ways in FHIR Observations. One way is to simply include them in the value set and represent the exceptions in the value. For example, measurement values for a serology test could be "detected", "not detected", "inconclusive", or "test not done". The alternate way is to use the value element for actual observations and use the explicit dataAbsentReason element to record exceptional values. For example, the dataAbsentReason code "error" could be used when the measurement was not completed. Because of these options, use-case agreements are required to interpret general observations for exceptional values." Elements differ in definition for mustSupport: "true" "false"
interpretation
referenceRange
Documentation for this format