us-core-observation-sexual-orientation vs vital-signs-panel

Logical id of this artifact

0..1

Logical id of this artifact

category

0..*

Classification of type of observation
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 definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'

code

SΣ

1..1

Sexual Orientation
Binding: LOINCCodes (example): Codes identifying names of simple observations.

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

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: 'Sexual Orientation' 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).'
Elements differ in binding.description: 'Codes identifying names of simple observations.' vs 'This identifies the vital sign result type.'

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
us-core-1: Datetime must be at least to day.

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: 'This records the time during which the patient had identified their emotional, romantic, sexual, or affectional attraction to another person.' vs 'Often just a dateTime for Vital Signs.'
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

0..*

Who is responsible for the observation

0..*

Who is responsible for the observation

Slices for value[x]

ΣC

0..1

Actual result
Slice: Unordered, Closed by type:$this

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 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'
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 definition for mustSupport: 'false' vs 'true'
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

Text based reference range in an observation

hasMember

0..*

Reference(Observation | QuestionnaireResponse | MolecularSequence)

Related resource that belongs to the Observation group

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: 'Related resource that belongs to the Observation group' vs 'Used when reporting vital signs panel components'
Elements differ in definition: 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' vs 'Used when reporting vital signs panel components.'
Elements differ in definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'
Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]])

derivedFrom

0..*

Related measurements the observation is made from

0..*

Related measurements the observation is made from

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..*