us-core-observation-sdoh-assessment vs vital-signs-panel

Logical id of this artifact

0..1

Logical id of this artifact

Meta

Metadata about the resource

implicitRules

?!Σ

0..1

uri

A set of rules under which this content was created

?!Σ

0..1

uri

A set of rules under which this content was created

language

0..1

Language of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional Bindings

Purpose

AllLanguages

Max Binding

0..1

Language of the resource content
Binding: CommonLanguages (preferred): A human language.

Additional Bindings

Purpose

AllLanguages

Max Binding

text

0..1

Narrative

Text summary of the resource, for human interpretation

0..1

Narrative

Text summary of the resource, for human interpretation

contained

0..*

Resource

Contained, inline Resources

0..*

Resource

Contained, inline Resources

extension

0..*

Additional content defined by implementations

0..*

Additional content defined by implementations

modifierExtension

0..*

Extensions that cannot be ignored

0..*

Extensions that cannot be ignored

identifier

0..*

Identifier

Business Identifier for observation

0..*

Identifier

Business Identifier for observation

basedOn

0..*

Fulfills plan, proposal or order

0..*

Fulfills plan, proposal or order

partOf

0..*

Part of referenced event

0..*

Part of referenced event

status

?!SΣ

1..1

registered | preliminary | final | amended +
Binding: ObservationStatus (required): Codes providing the status of an observation.

?!SΣ

1..1

registered | preliminary | final | amended +
Binding: ObservationStatus (required)

Slices for category

1..*

Classification of type of observation
Slice: Unordered, Open by pattern:$this
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

1..*

Classification of type of observation
Slice: Unordered, Open by value:coding.code, value:coding.system
Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories.

Elements differ in requirements: 'To identify that observation is derived from a questionnaire.' vs 'Used for filtering what observations are retrieved and displayed.'

code

SΣ

1..1

Type of observation (code / type)
Binding: US Core Common SDOH Assessments (preferred)

SΣ

1..1

Vital signs, weight, height, head circumference, oxygen saturation, and BMI panel
Binding: VitalSigns (extensible): This identifies the vital sign result type.

Required Pattern: {"coding":[{"system":"http://loinc.org","code":"85353-1"}]}

Elements differ in short: 'Type of observation (code / type)' vs 'Vital signs, weight, height, head circumference, oxygen saturation, and BMI panel'
Elements differ in definition: 'Describes what was observed. Sometimes this is called the observation "name".' vs 'Vital Signs Panel.'
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.' vs 'additional codes that translate or map to this code are allowed. For example a more granular LOINC code or code that is used locally in a system.'
Elements differ in requirements: 'Knowing what kind of observation is being made is essential to understanding the observation.' vs '5. SHALL contain exactly one [1..1] code, where the @code SHOULD be selected from ValueSet HITSP Vital Sign Result Type 2.16.840.1.113883.3.88.12.80.62 DYNAMIC (CONF:7301).'

0..1

Unique id for inter-element referencing

0..1

Unique id for inter-element referencing

Slices for extension

0..*

Additional content defined by implementations
Slice: Unordered, Open by value:url

0..*

Additional content defined by implementations
Slice: Unordered, Open by value:url

coding

0..*

Coding

Code defined by a terminology system

0..*

Coding

Code defined by a terminology system
Slice: Unordered, Open by value:code, value:system

text

0..1

Plain text representation of the concept

0..1

Reference(US Core Patient Profile)

Plain text representation of the concept

subject

SΣ

1..1

Who and/or what the observation is about

SΣ

1..1

Reference(US Core Patient Profile)

Who and/or what the observation is about

focus

0..*

Reference(Resource)

What the observation is about, when it is not about the subject of record

0..*

Reference(Resource)

What the observation is about, when it is not about the subject of record

encounter

0..1

Reference(Encounter)

Healthcare event during which this observation is made

0..1

Reference(Encounter)

Healthcare event during which this observation is made

effective[x]

SΣC

0..1

dateTime S, Period, Timing, instant

Clinically relevant time/time-period for observation

SΣC

1..1

dateTime, Period

Often just a dateTime for Vital Signs

Elements differ in short: 'Clinically relevant time/time-period for observation' vs 'Often just a dateTime for Vital Signs'
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".' vs 'Often just a dateTime for Vital Signs.'
Elements differ in comments: 'At least a date should be present unless this observation is a historical report.' vs '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.'
Element minimum cardinalities differ: '0' vs '1'

issued

0..1

instant

Date/Time this version was made available

0..1

instant

Date/Time this version was made available

performer

SΣ

0..*

Who is responsible for the observation

0..*

Who is responsible for the observation

Elements differ in definition for mustSupport: 'true' vs 'false'

value[x]

SΣC

0..1

Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period

Actual result

SΣC

0..0

Elements differ in short: 'Actual result' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Signs value are recorded using the Quantity data type. For supporting observations such as Cuff size could use other datatypes such as CodeableConcept.'
Elements differ in comments: 'An observation may have a value if it represents an individual survey question and answer pair. An observation should not have a value if it represents a multi-question survey or multi-select “check all that apply” question. 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.' vs '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.'
Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).'
Element maximum cardinalities differ: '1' vs '0'

dataAbsentReason

0..1

Why the result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

0..0

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.' vs '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.'
Element maximum cardinalities differ: '1' vs '0'

interpretation

0..*

High, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.

0..*

High, low, normal, etc.
Binding: Defined Limits value set (extensible)

note

0..*

Annotation

Comments about the observation

0..*

Annotation

Comments about the observation

bodySite

0..1

Observed body part
Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality.

0..0

Element maximum cardinalities differ: '1' vs '0'

method

0..1

How it was done
Binding: ObservationMethods (example): Methods for simple observations.

0..0

Element maximum cardinalities differ: '1' vs '0'

specimen

0..1

Reference(Specimen)

Specimen used for this observation

0..0

Element maximum cardinalities differ: '1' vs '0'

device

0..1

Reference(Device | DeviceMetric)

(Measurement) Device

0..0

Element maximum cardinalities differ: '1' vs '0'

referenceRange

0..*

BackboneElement

Provides guide for interpretation

0..0

Element maximum cardinalities differ: '2147483647' vs '0'

0..1

Unique id for inter-element referencing

0..1

Unique id for inter-element referencing

extension

0..*

Additional content defined by implementations

0..*

Additional content defined by implementations

modifierExtension

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

low

0..1

Low Range, if relevant

0..1

Low Range, if relevant

high

0..1

High Range, if relevant

0..1

High Range, if relevant

type

0..1

Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

0..1

Reference range qualifier
Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range.

appliesTo

0..*

Reference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.

0..*

Reference range population
Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to.

age

0..1

Range

Applicable age range, if relevant

0..1

Range

Applicable age range, if relevant

text

0..1

Text based reference range in an observation

0..1

Reference(US Core Observation SDOH Assessment Profile S)

Text based reference range in an observation

hasMember

SΣ

0..*

Individual Observations that belong to an SDOH multi-question sruvey or multi-select question.

SΣ

1..*

Reference(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)

Used when reporting vital signs panel components
Slice: Unordered, Closed by profile:resolve()

Elements differ in short: 'Individual Observations that belong to an SDOH multi-question sruvey or multi-select question.' vs 'Used when reporting vital signs panel components'
Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' vs 'Used when reporting vital signs panel components.'
Elements differ in comments: 'This grouping element is used to represent surveys that group several questions together or individual questions with “check all that apply” responses. For example in the simplest case a flat multi-question survey where the "panel" observation is the survey instrument itself and instead of an `Observation.value` the `hasMember` element references other Observation that represent the individual questions answer pairs. In a survey that has a heirarchical grouping of questions, the observation "panels" can be nested. Because surveys can be arbitrarily complex structurally, not all survey structures can be represented using this Observation grouping pattern.' vs 'When using this element, an observation will typically have either a value or a set of related resources, although both may be present in some cases. For a discussion on the ways Observations can assembled in groups together, see [Notes] below. Note that a system may calculate results from [QuestionnaireResponse] into a final score and represent the score as an Observation.'
Element minimum cardinalities differ: '0' vs '1'
Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-sdoh-assessment]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])

derivedFrom

SΣ

0..*

Related Observations or QuestionnaireResponses that the observation is made from

0..*

Related measurements the observation is made from

Elements differ in short: 'Related Observations or QuestionnaireResponses that the observation is made from' vs 'Related measurements the observation is made from'
Elements differ in definition: 'Observations or QuestionnaireResponses from which this observation value is derived.' vs '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' vs 'false'
Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-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]]) vs 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/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])

component

0..*

BackboneElement

Component results

SΣC

0..0

Elements differ in short: 'Component results' vs 'Used when reporting systolic and diastolic blood pressure.'
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 include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.' vs 'Used when reporting systolic and diastolic blood pressure.'
Elements differ in definition for mustSupport: 'false' vs 'true'
Element maximum cardinalities differ: '2147483647' vs '0'

0..1

Unique id for inter-element referencing

0..1

Unique id for inter-element referencing

extension

0..*

Additional content defined by implementations

0..*

Additional content defined by implementations

modifierExtension

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

?!Σ

0..*

Extensions that cannot be ignored even if unrecognized

code

1..1

Type of component observation (code / type)
Binding: LOINCCodes (example): Codes identifying names of simple observations.

SΣ

1..1

Type of component observation (code / type)
Binding: VitalSigns (extensible): This identifies the vital sign result type.

Elements differ in definition for mustSupport: 'false' vs 'true'
Elements differ in binding.description: 'Codes identifying names of simple observations.' vs 'This identifies the vital sign result type.'

value[x]

0..1

Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period

Actual component result

SΣC

0..1

Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period

Vital Sign Value recorded with UCUM
Binding: VitalSignsUnits (required): Common UCUM units for recording Vital Signs.

Elements differ in short: 'Actual component result' vs 'Vital Sign Value recorded with UCUM'
Elements differ in definition: 'The information determined as a result of making the observation, if the information has a simple value.' vs 'Vital Sign Value recorded with UCUM.'
Elements differ in requirements: 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.' vs '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).'
Elements differ in definition for mustSupport: 'false' vs 'true'

dataAbsentReason

0..1

Why the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

0..1

Why the component result is missing
Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing.

Elements differ in definition for mustSupport: 'false' vs 'true'

interpretation

0..*

High, low, normal, etc.
Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations.

0..*