## Profile Comparison between http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey vs http://hl7.org/fhir/us/covid19library/StructureDefinition/covid19-underlying-condition-observation-parent

Left: | US Core Observation Survey Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey)
Right: | UnderlyingConditionObservationParent (http://hl7.org/fhir/us/covid19library/StructureDefinition/covid19-underlying-condition-observation-parent)

### Messages

Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey' vs 'http://hl7.org/fhir/us/covid19library/StructureDefinition/covid19-underlying-condition-observation-parent'
Error | StructureDefinition.version | Values for version differ: '5.0.1' vs '1.0.0'
Information | StructureDefinition.name | Values for name differ: 'USCoreObservationSurveyProfile' vs 'UnderlyingConditionObservationParent'
Information | StructureDefinition.date | Values for date differ: '2022-04-20' vs '2022-07-25T13:34:17+00:00'
Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International - Cross-Group Projects' vs 'HL7 International - Clinical Information Modeling Initiative'
Information | StructureDefinition.copyright | Values for copyright differ: 'Used by permission of HL7 International, all rights reserved Creative Commons License' vs 'HL7 International & Logica Health, all rights reserved Creative Commons License'
Warning | StructureDefinition.abstract | Values for abstract differ: 'false' vs 'true'
Warning | Observation | Elements differ in short: 'Survey Observation' vs 'Measurements and simple assertions'
Warning | Observation | Elements differ in definition: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.'
Warning | Observation | Elements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
Warning | Observation.status | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Observation.category | Elements differ in requirements: 'To identify that observation is derived from a questionnaire.' vs 'Used for filtering what observations are retrieved and displayed.'
Warning | Observation.category | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | Observation.category | Element minimum cardinalities differ: '1' vs '0'
Warning | Observation.code | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | Observation.code | Example/preferred bindings differ at Observation.code using binding from USCoreObservationSurveyProfile
Warning | Observation.subject | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | Observation.subject | Element minimum cardinalities differ: '1' vs '0'
Warning | Observation.effective[x] | 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 '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.'
Warning | Observation.effective[x] | 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.'
Warning | Observation.effective[x] | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Observation.performer | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Observation.value[x] | 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.'
Warning | Observation.value[x] | Elements differ in definition for mustSupport: 'true' vs 'false'
Information | Observation.value[x] | Element maximum cardinalities differ: '1' vs '0'
Warning | Observation.dataAbsentReason | 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.'
Warning | Observation.dataAbsentReason | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Observation.hasMember | Elements differ in short: 'Reference to panel or multi-select responses' vs 'Related resource that belongs to the Observation group'
Warning | Observation.hasMember | Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' 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.'
Warning | Observation.hasMember | 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.'
Warning | Observation.hasMember | Elements differ in definition for mustSupport: 'true' vs 'false'
Warning | Observation.derivedFrom | Elements differ in short: 'Related Observations or QuestionnaireResponses that the observation is made from' vs 'Related measurements the observation is made from'
Warning | Observation.derivedFrom | 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.'
Warning | Observation.derivedFrom | Elements differ in definition for mustSupport: 'true' vs 'false'
Error | Observation.derivedFrom | 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/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
Warning | Observation.component | Elements differ in definition for mustSupport: 'false' vs 'true'
Warning | Observation.component.extension | Elements differ in short: 'Additional content defined by implementations' vs 'Extension'
Warning | Observation.component.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'
Warning | Observation.component.extension | Elements differ in definition for mustSupport: 'false' vs 'true'
Information | Observation.component.extension | Element minimum cardinalities differ: '0' vs '1'

### 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 | HL7 International & Logica Health, all rights reserved Creative Commons License | Values Differ
date | 2022-04-20 | 2022-07-25T13:34:17+00:00 | Values Differ
description | To promote interoperability and adoption through common implementation, the US Core Observation Survey Profile sets minimum expectations for the Observation Resource to record, search, and fetch retrieve observations that represent the questions and responses to form/survey and assessment tools. It can be used to represent individual responses, panels of multi-question surveys, and multi-select responses to “check all that apply” questions. It identifies which core elements, extensions, vocabularies and value sets **SHALL** be present in the resource when using this profile. It provides the floor for standards development for specific uses cases. | A general structure for the observations of the presense or absence of underlying conditions. | Values Differ
experimental |  |
fhirVersion | 4.0.1 |
jurisdiction |  |
jurisdiction[0] | urn:iso:std:iso:3166#US |
kind | resource |
name | USCoreObservationSurveyProfile | UnderlyingConditionObservationParent | Values Differ
publisher | HL7 International - Cross-Group Projects | HL7 International - Clinical Information Modeling Initiative | Values Differ
purpose |  |
status | active |
title | US Core Observation Survey Profile |  | Removed the item 'US Core Observation Survey Profile'
type | Observation |
url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey | http://hl7.org/fhir/us/covid19library/StructureDefinition/covid19-underlying-condition-observation-parent | Values Differ
version | 5.0.1 | 1.0.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 | 0..* | Observation | Survey Observation us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present us-core-3: SHALL use UCUM for coded quantity units. | I | 0..* | Observation | This is an abstract profile Measurements and simple assertions | Elements differ in short: 'Survey Observation' vs 'Measurements and simple assertions' Elements differ in definition: '\-' vs 'Measurements and simple assertions made about a patient, device or other subject.' Elements differ in comments: '\-' vs 'Used for simple observations such as device measurements, laboratory atomic results, vital signs, height, weight, smoking status, comments, etc. Other resources are used to provide context for observations such as laboratory reports, etc.'
id | Σ | 0..1 | string | Logical id of this artifact | Σ | 0..1 | string | Logical id of this artifact |
meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | 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 | code | Language of the resource content Binding: CommonLanguages (preferred): A human language.
Additional Bindings | Purpose
AllLanguages | Max Binding
|  | 0..1 | code | 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..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored | ?! | 0..* | Extension | Extensions that cannot be ignored |
identifier | Σ | 0..* | Identifier | Business Identifier for observation | Σ | 0..* | Identifier | Business Identifier for observation |
basedOn | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order | Σ | 0..* | Reference(CarePlan | DeviceRequest | ImmunizationRecommendation | MedicationRequest | NutritionOrder | ServiceRequest) | Fulfills plan, proposal or order |
partOf | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event | Σ | 0..* | Reference(MedicationAdministration | MedicationDispense | MedicationStatement | Procedure | Immunization | ImagingStudy) | Part of referenced event |
status | ?!S Σ | 1..1 | code | registered | preliminary | final | amended + Binding: ObservationStatus (required): Codes providing the status of an observation. | ?!Σ | 1..1 | code | registered | preliminary | final | amended + Binding: ObservationStatus (required): Codes providing the status of an observation. | Elements differ in definition for mustSupport: 'true' vs 'false'
Slices for category | S | 1..* | CodeableConcept | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ObservationCategoryCodes (preferred): Codes for high level observation categories. |  | 0..* | CodeableConcept | Classification of type of observation 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.' Elements differ in definition for mustSupport: 'true' vs 'false' Element minimum cardinalities differ: '1' vs '0'
code | S Σ | 1..1 | CodeableConcept | Type of observation (code / type) Binding: US Core Survey Codes (preferred) | Σ | 1..1 | CodeableConcept | Type of observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations. | Elements differ in definition for mustSupport: 'true' vs 'false' Example/preferred bindings differ at Observation.code using binding from USCoreObservationSurveyProfile
subject | S Σ | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about | Σ | 0..1 | Reference(Patient | Group | Device | Location) | Who and/or what the observation is about | Elements differ in definition for mustSupport: 'true' vs 'false' 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 | Σ | 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 Σ I | 0..1 | dateTime S, Period, Timing, instant | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. | Σ | 0..1 | dateTime, Period, Timing, instant | Clinically relevant time/time-period for observation | 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 '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.' 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.' Elements differ in definition for mustSupport: 'true' vs 'false'
issued | Σ | 0..1 | instant | Date/Time this version was made available | Σ | 0..1 | instant | Date/Time this version was made available |
performer | S Σ | 0..* | Reference(US Core Practitioner Profile S | US Core Organization Profile | US Core Patient Profile | PractitionerRole | US Core CareTeam Profile | US Core RelatedPerson Profile) | Who is responsible for the observation | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation | Elements differ in definition for mustSupport: 'true' vs 'false'
value[x] | S Σ I | 0..1 | Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual result | Σ I | 0..0 |  |  | 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 definition for mustSupport: 'true' vs 'false' Element maximum cardinalities differ: '1' vs '0'
dataAbsentReason | S I | 0..1 | CodeableConcept | Why the result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing. | I | 0..1 | CodeableConcept | Why the result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing. | 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.' Elements differ in definition for mustSupport: 'true' vs 'false'
interpretation |  | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations. |  | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations. |
note |  | 0..* | Annotation | Comments about the observation |  | 0..* | Annotation | Comments about the observation |
bodySite |  | 0..1 | CodeableConcept | Observed body part Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality. |  | 0..1 | CodeableConcept | Observed body part Binding: SNOMEDCTBodyStructures (example): Codes describing anatomical locations. May include laterality. |
method |  | 0..1 | CodeableConcept | How it was done Binding: ObservationMethods (example): Methods for simple observations. |  | 0..1 | CodeableConcept | How it was done Binding: ObservationMethods (example): Methods for simple observations. |
specimen |  | 0..1 | Reference(Specimen) | Specimen used for this observation |  | 0..1 | Reference(Specimen) | Specimen used for this observation |
device |  | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device |  | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device |
referenceRange | I | 0..* | BackboneElement | Provides guide for interpretation | I | 0..* | BackboneElement | Provides guide for interpretation |
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations |  | 0..* | Extension | Additional content defined by implementations |
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
low | I | 0..1 | SimpleQuantity | Low Range, if relevant | I | 0..1 | SimpleQuantity | Low Range, if relevant |
high | I | 0..1 | SimpleQuantity | High Range, if relevant | I | 0..1 | SimpleQuantity | High Range, if relevant |
type |  | 0..1 | CodeableConcept | Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range. |  | 0..1 | CodeableConcept | Reference range qualifier Binding: ObservationReferenceRangeMeaningCodes (preferred): Code for the meaning of a reference range. |
appliesTo |  | 0..* | CodeableConcept | Reference range population Binding: ObservationReferenceRangeAppliesToCodes (example): Codes identifying the population the reference range applies to. |  | 0..* | CodeableConcept | 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 | string | Text based reference range in an observation |  | 0..1 | string | Text based reference range in an observation |
hasMember | S Σ | 0..* | Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile | MolecularSequence) | Reference to panel or multi-select responses | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group | Elements differ in short: 'Reference to panel or multi-select responses' vs 'Related resource that belongs to the Observation group' Elements differ in definition: 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' 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.' 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.' Elements differ in definition for mustSupport: 'true' vs 'false'
derivedFrom | S Σ | 0..* | Reference(US Core Observation Survey Profile S | US Core QuestionnaireResponse Profile S | US Core DocumentReference Profile | ImagingStudy | Media | MolecularSequence) | Related Observations or QuestionnaireResponses that the observation is made from | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | 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/Observation], CanonicalType[http://hl7.org/fhir/StructureDefinition/MolecularSequence]])
component | Σ | 0..* | BackboneElement | Component results | S Σ | 0..* | BackboneElement | Component results | Elements differ in definition for mustSupport: 'false' vs 'true'
id |  | 0..1 | string | Unique id for inter-element referencing |  | 0..1 | string | Unique id for inter-element referencing |
extension |  | 0..* | Extension | Additional content defined by implementations | S | 1..* | Extension | 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' Elements differ in definition for mustSupport: 'false' vs 'true' Element minimum cardinalities differ: '0' vs '1'
modifierExtension | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized | ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized |
code | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations. | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: LOINCCodes (example): Codes identifying names of simple observations. |
value[x] | Σ | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result | Σ | 0..1 | CodeableConcept | Actual component result Slice: Unordered, Closed by type:$this |
dataAbsentReason | I | 0..1 | CodeableConcept | Why the component result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing. | I | 0..1 | CodeableConcept | Why the component result is missing Binding: DataAbsentReason (extensible): Codes specifying why the result (Observation.value[x]) is missing. |
interpretation |  | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations. |  | 0..* | CodeableConcept | High, low, normal, etc. Binding: ObservationInterpretationCodes (extensible): Codes identifying interpretations of observations. |
referenceRange |  | 0..* | See referenceRange (Observation) | Provides guide for interpretation of component result |  | 0..* | See referenceRange (Observation) | Provides guide for interpretation of component result |
Documentation for this format