head-occipital-frontal-circumference-percentile vs SDOHCC-ObservationGenderIdentity

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

Extension
Slice: Unordered, Open by value:url

Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'

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)

?!SΣ

1..1

final | corrected | entered-in-error | unknown
Binding: SDOHCC ValueSet Observation Status (required)

Elements differ in short: 'registered | preliminary | final | amended +' vs 'final | corrected | entered-in-error | unknown'
Elements differ in definition: 'The status of the result value.' vs 'The status of the observation value.'
Elements differ in requirements: 'Need to track the status of individual results. Some results are finalized before the whole report is finalized.' vs 'Further constrained to values that are relevant for personal characteristic observations.'

Slices for category

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.

1..*

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

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

code

SΣ

1..1

Head Occipital Frontal circumference Percentile
Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

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

SΣ

1..1

Reference(US Core Patient Profile)

Type of observation (code / type)
Binding: LOINCCodes (preferred)
Required Pattern: {"coding":[{"system":"http://loinc.org","code":"76691-5"}]}

Elements differ in short: 'Head Occipital Frontal circumference Percentile' vs 'Type of observation (code / type)'
Elements differ in definition: 'Coded Responses from C-CDA Vital Sign Results.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
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 '*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. NOTE: In LOINC, System Patient is used in the modeling of codes referenced by the Personal Characteristics profiles (e.g., 72826-1 Race OMB.1997, 69490-1 Ethnicity OMB.1997, 76691-5 Gender identity, 76690-7 Sexual orientation, 90778-2 Personal pronouns – Reported, and 99502-7 Recorded sex or gender). If the draft profiles are adopted, new LOINC codes without System Patient would be needed since these profiles can also be used to capture characteristics of a provider (using an extension) or a related person (using focus).'
Elements differ in requirements: '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).' vs 'Knowing what kind of observation is being made is essential to understanding the observation.'

subject

SΣ

1..1

Who and/or what the observation is about

SΣC

0..1

Reference(US Core Patient Profile)

Who and/or what the observation is about

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

focus

0..*

Reference(Resource)

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

ΣC

0..1

Reference(RelatedPerson)

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

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

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

1..1

dateTime S, Period

Often just a dateTime for Vital Signs

0..1

dateTime, Period

Clinically relevant time/time-period for observation

Elements differ in short: 'Often just a dateTime for Vital Signs' vs 'Clinically relevant time/time-period for observation'
Elements differ in definition: 'Often just a dateTime for Vital Signs.' vs '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. 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.' 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. NOTE: dateTime is Must Support, but currently tooling does not support this.'
Elements differ in definition for mustSupport: 'true' vs 'false'
Element minimum cardinalities differ: '1' vs '0'

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

SΣC

0..*

Who is responsible for the observation

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

Slices for value[x]

SΣC

0..1

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

Vital Signs Value
Slice: Unordered, Open by type:$this
Binding: VitalSignsUnits (extensible): Common UCUM units for recording Vital Signs.

SΣC

1..1

Actual result
Binding: Gender Identity (preferred): Codes for self-identified gender, plus unknown and other

Elements differ in short: 'Vital Signs Value' vs 'Actual result'
Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations. This is a value set is for testing purposes only and will ultimately need to be aligned with vetted value sets being developed by the Gender Harmony Project where terms like “male-to-female transsexual” and “female-to-male transsexual” will not be included. See https://build.fhir.org/ig/HL7/fhir-gender-harmony/branches/main/terminology.html#appendix-1--proposed-value-sets'
Element minimum cardinalities differ: '0' vs '1'
Elements differ in binding.description: 'Common UCUM units for recording Vital Signs.' vs 'Codes for self-identified gender, plus unknown and other'

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

Extension
Slice: Unordered, Open by value:url

Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. To make the use of extensions safe and manageable, there is a strict set of governance applied to the definition and use of extensions. Though any implementer can define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs 'An Extension'

coding

0..*

Coding

Code defined by a terminology system

SΣ

0..*

Coding

Code defined by a terminology system

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

text

0..1

Plain text representation of the concept

0..1

Plain text representation of the concept

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

interpretation

0..*

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

0..0

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

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.

1..1

How it was done
Binding: SDOHCC ValueSet Observation Method (extensible): Methods for personal characteristic observations.

Elements differ in definition for mustSupport: 'false' vs 'true'
Element minimum cardinalities differ: '0' vs '1'
Elements differ in binding.description: 'Methods for simple observations.' vs 'Methods for personal characteristic observations.'

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

Reference(Device | DeviceMetric)

(Measurement) Device

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(QuestionnaireResponse | MolecularSequence | Vital Signs Profile)

Used when reporting vital signs panel components

0..*

Reference(Observation | QuestionnaireResponse | MolecularSequence)

Related resource that belongs to the Observation group

Elements differ in short: 'Used when reporting vital signs panel components' vs 'Related resource that belongs to the Observation group'
Elements differ in definition: 'Used when reporting vital signs panel components.' vs '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.'
Type Mismatch: Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence], CanonicalType[http://hl7.org/fhir/StructureDefinition/vitalsigns]]) vs Reference([CanonicalType[http://hl7.org/fhir/StructureDefinition/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/QuestionnaireResponse], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])

derivedFrom

0..*

Related measurements the observation is made from

SΣC

0..*

Reference(DocumentReference | QuestionnaireResponse | Observation)

Related measurements the observation is made from

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

component

SΣC

0..*

BackboneElement

Component observations

0..*

BackboneElement

Component results

Elements differ in short: 'Component observations' vs 'Component results'
Elements differ in definition: 'Used when reporting component observation such as systolic and diastolic blood pressure.' vs '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 definition for mustSupport: 'true' vs 'false'

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

SΣ

1..1

Type of component observation (code / type)
Binding: US Core Vital Signs ValueSet (extensible): The vital sign codes from the base FHIR and US Core Vital Signs.

1..1

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

Elements differ in definition for mustSupport: 'true' vs 'false'
Elements differ in binding.description: 'The vital sign codes from the base FHIR and US Core Vital Signs.' vs 'Codes identifying names of simple observations.'

value[x]

SΣC

0..1

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

Vital Sign Component Value
Binding: VitalSignsUnits (extensible): Common UCUM units for recording Vital Signs.

0..1

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

Actual component result

Elements differ in short: 'Vital Sign Component Value' vs 'Actual component result'
Elements differ in definition: 'Vital Signs value are typically recorded using the Quantity data type. For supporting observations such as cuff size could use other datatypes such as CodeableConcept.' vs 'The information determined as a result of making the observation, if the information has a simple value.'
Elements differ in requirements: '9. SHALL contain exactly one [1..1] value with @xsi:type="PQ" (CONF:7305).' vs 'An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.'
Elements differ in definition for mustSupport: 'true' vs 'false'

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

interpretation

0..*

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

0..*