| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | L Type | L Description & Constraints | Comments |
|---|
  Observation | C | 0..* | Observation | Argonaut Smoking Status Observation Profile
obs-6: SHALL only be present if Observation.value[x] is not present
obs-7: Component code SHALL not be same as observation code
| C | 0..* | Observation | Measurements and simple assertions
| - Elements differ in short: 'Argonaut Smoking Status Observation Profile' vs 'Measurements and simple assertions'
- Elements differ in definition: 'Measurements and simple assertions made about a patient, device or other subject.' vs '\-'
- Elements differ in comments: '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 lab reports, etc.' vs '\-'
|
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | Logical id of this artifact | - Elements differ in comments: 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation. Bundles always have an id, though it is usually a generated UUID.' vs 'The only time that a resource does not have an id is when it is being submitted to the server using a create operation.'
|
| meta | Σ | 0..1 | Meta | Metadata about the resource | Σ | 0..1 | Meta | Metadata about the resource | - Elements differ in definition: 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content may not always be associated with version changes to the resource.' vs 'The metadata about the resource. This is content that is maintained by the infrastructure. Changes to the content might not always be associated with version changes to 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 | - Elements differ in definition: 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content.' vs 'A reference to a set of rules that were followed when the resource was constructed, and which must be understood when processing the content. Often, this is a reference to an implementation guide that defines the special rules along with other profiles etc.'
- Elements differ in comments: 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element as much as possible.' vs 'Asserting this rule set restricts the content to be only understood by a limited set of trading partners. This inherently limits the usefulness of the data in the long term. However, the existing health eco-system is highly fractured, and not yet ready to define, collect, and exchange data in a generally computable sense. Wherever possible, implementers and/or specification writers should avoid using this element. Often, when used, the URL is a reference to an implementation guide that defines these special rules as part of it's narrative along with other profiles, value sets, etc.'
|
| language | | 0..1 | code | Language of the resource content
Binding: todo (required): A human language.
| | 0..1 | code | Language of the resource content
Binding: todo (preferred): A human language.
| - Elements differ in comments: 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).' vs 'Language is provided to support indexing and accessibility (typically, services such as text to speech use the language tag). The html language tag in the narrative applies to the narrative. The language tag on the resource may be used to specify the language of other presentations generated from the data in the resource. Not all the content has to be in the base language. The Resource.language should not be assumed to apply to the narrative automatically. If a language is specified, it should it also be specified on the div element in the html (see rules in HTML5 for information about the relationship between xml:lang and the html lang attribute).'
|
| text | | 0..1 | Narrative | Text summary of the resource, for human interpretation | | 0..1 | Narrative | Text summary of the resource, for human interpretation | - Elements differ in definition: 'A human-readable narrative that contains a summary of the resource, and may be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.' vs 'A human-readable narrative that contains a summary of the resource and can be used to represent the content of the resource to a human. The narrative need not encode all the structured data, but is required to contain sufficient detail to make it "clinically safe" for a human to just read the narrative. Resource definitions may define what content should be represented in the narrative to ensure clinical safety.'
- Elements differ in comments: 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative.' vs 'Contained resources do not have narrative. Resources that are not contained SHOULD have a narrative. In some cases, a resource may only have text with little or no additional discrete data (as long as all minOccurs=1 elements are satisfied). This may be necessary for data from legacy systems where information is captured as a "text blob" or where text is additionally entered raw or narrated and encoded information is added later.'
|
| contained | | 0..* | Resource | Contained, inline Resources
| | 0..* | Resource | Contained, inline Resources
| - Elements differ in comments: 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again.' vs 'This should never be done when the content can be identified properly, as once identification is lost, it is extremely difficult (and context dependent) to restore it again. Contained resources may have profiles and tags In their meta elements, but SHALL NOT have security labels.'
|
 extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs '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.'
|
 modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?! | 0..* | Extension | Extensions that cannot be ignored
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the resource, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the resource and that modifies the understanding of the element that contains it and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| identifier | | 0..* | Identifier | Unique Id for this particular observation
| Σ | 0..* | Identifier | Business Identifier for observation
| - Elements differ in short: 'Unique Id for this particular observation' vs 'Business Identifier for observation'
- Elements differ in definition: 'A unique identifier for the simple observation instance.' vs 'A unique identifier assigned to this observation.'
|
| status | ?!S | 1..1 | code | registered | preliminary | final | amended +
Binding: todo (required) | ?!SΣ | 1..1 | code | (USCDI) registered | preliminary | final | amended +
Binding: todo (required) | - Elements differ in short: 'registered | preliminary | final | amended +' vs '(USCDI) registered | preliminary | final | amended +'
|
| category | | 0..1 | CodeableConcept | Classification of type of observation
Binding: todo (example): Codes for high level observation categories .
| S | 1..* | CodeableConcept | (USCDI) Classification of type of observation
Slice: Unordered, Open by pattern:$this
Binding: todo (preferred): Codes for high level observation categories.
| - Elements differ in short: 'Classification of type of observation' vs '(USCDI) Classification of type of observation'
- Elements differ in definition: 'A code that classifies the general type of observation being made. This is used for searching, sorting and display purposes.' vs 'A code that classifies the general type of observation being made.'
- Elements differ in comments: 'The level of granularity is defined by the category concepts in the value set. More fine-grained filtering can be performed using the metadata and/or terminology hierarchy in Observation.code.' vs 'In addition to the required category valueset, this element allows various categorization schemes based on the owner’s definition of the category and effectively multiple categories can be used at once. The level of granularity is defined by the category concepts in the value set.'
- Elements differ in definition for mustSupport: 'false' vs 'true'
- Element minimum cardinalities differ: '0' vs '1'
- Element maximum cardinalities differ: '1' vs '2147483647'
- Elements differ in binding.description: 'Codes for high level observation categories .' vs 'Codes for high level observation categories.'
|
| code | S | 1..1 | CodeableConcept | Smoking Status: LOINC 72166-2 = Tobacco smoking status NHIS
Binding: todo (example): Codes identifying names of simple observations.
Required Pattern: {"coding":[{"system":"http://loinc.org","code":"72166-2","userSelected":false}]} | SΣ | 1..1 | CodeableConcept | (USCDI) Smoking Status
Binding: todo (extensible) | - Elements differ in short: 'Smoking Status: LOINC 72166-2 = Tobacco smoking status NHIS' vs '(USCDI) Smoking Status'
- Elements differ in definition: 'Smoking Status: Limited to fixed LOINC value 72166-2 = Tobacco smoking status NHIS.' vs 'Describes what was observed. Sometimes this is called the observation "name".'
|
| subject | S | 1..1 | Reference(http://fhir.org/guides/argonaut/StructureDefinition/argo-patient) | Who and/or what this is about | SΣ | 1..1 | Reference(http://hl7.org/fhir/us/core/StructureDefinition/us-core-patient) | (USCDI) Who and/or what the observation is about | - Elements differ in short: 'Who and/or what this is about' vs '(USCDI) Who and/or what the observation is about'
- Elements differ in definition: 'The patient, or group of patients, location, or device whose characteristics (direct or indirect) are described by the observation and into whose record the observation is placed. Comments: Indirect characteristics may be those of a specimen, fetus, donor, other observer (for example a relative or EMT), or any observation made about the subject.' vs 'The patient, or group of patients, location, or device this observation is about and into whose record the observation is placed. If the actual focus of the observation is different from the subject (or a sample of, part, or region of the subject), the `focus` element or the `code` itself specifies the actual focus of the observation.'
- Elements differ in comments: 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated. If the target of the observation is different than the subject, the general extension [observation-focal-subject]. may be used. However, the distinction between the patient's own value for an observation versus that of the fetus, or the donor or blood product unit, etc., are often specified in the observation code.' vs 'One would expect this element to be a cardinality of 1..1. The only circumstance in which the subject can be missing is when the observation is made by a device that does not know the patient. In this case, the observation SHALL be matched to a patient through some context/channel matching technique, and at this point, the observation should be updated.'
|
| 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] | Σ | 0..1 | dateTime, Period | Clinically relevant time/time-period for observation | Σ | 1..1 | dateTime | Clinically relevant time/time-period for observation
Slice: Unordered, Closed by type:$this | - 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 | S | 1..1 | instant | Date/Time this was made available | Σ | 0..1 | instant | Date/Time this version was made available | - Elements differ in short: 'Date/Time this was made available' vs 'Date/Time this version was made available'
- Elements differ in definition: 'The date and time this observation was made available to providers, typically after the results have been reviewed and verified.' vs 'The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.'
- Elements differ in comments: 'Updated when the result is updated.' vs 'For Observations that don’t require review and verification, it may be the same as the [`lastUpdated` ] time of the resource itself. For Observations that do require review and verification for certain updates, it might not be the same as the `lastUpdated` time of the resource itself due to a non-clinically significant update that doesn’t require the new version to be reviewed and verified again.'
- Elements differ in definition for mustSupport: 'true' vs 'false'
- Element minimum cardinalities differ: '1' vs '0'
|
| performer | Σ | 0..* | Reference(Practitioner | Organization | Patient | RelatedPerson) | Who is responsible for the observation
| Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation
| |
| valueCodeableConcept | S | 1..1 | CodeableConcept | Coded Responses from Smoking Status Value Set
Binding: todo (extensible): This value set indicates the current smoking status of a patient
| | | | | |
| dataAbsentReason | C | 0..1 | CodeableConcept | Why the result is missing
Binding: todo (extensible): Codes specifying why the result (Observation.value[x]) is missing.
| C | 0..1 | CodeableConcept | Why the result is missing
Binding: todo (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. 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. Because of these options, use-case agreements are required to interpret general observations for exceptional values.' 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 description: 'Codes specifying why the result (Observation.value[x]) is missing.' vs 'Codes specifying why the result (`Observation.value[x]`) is missing.'
- Elements differ in description: 'Codes specifying why the result (Observation.value[x]) is missing.' vs 'Codes specifying why the result (`Observation.value[x]`) is missing.'
- Unable to resolve left value set http://hl7.org/fhir/ValueSet/observation-valueabsentreason at Observation.dataAbsentReason
|
| interpretation | | 0..1 | CodeableConcept | High, low, normal, etc.
Binding: todo (extensible): Codes identifying interpretations of observations.
| | 0..* | CodeableConcept | High, low, normal, etc.
Binding: todo (extensible): Codes identifying interpretations of observations.
| - Elements differ in definition: 'The assessment made based on the result of the observation. Intended as a simple compact code often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result. Otherwise known as abnormal flag.' vs 'A categorical assessment of an observation value. For example, high, low, normal.'
- Element maximum cardinalities differ: '1' vs '2147483647'
|
| comments | | 0..1 | string | Comments about result | | | | | |
| bodySite | | 0..1 | CodeableConcept | Observed body part
Binding: todo (example): Codes describing anatomical locations. May include laterality.
| | 0..1 | CodeableConcept | Observed body part
Binding: todo (example): Codes describing anatomical locations. May include laterality.
| - Elements differ in comments: 'Only used if not implicit in code found in Observation.code. If the use case requires BodySite to be handled as a separate resource instead of an inline coded element (e.g. to identify and track separately) then use the standard extension[ body-site-instance].' vs 'Only used if not implicit in code found in Observation.code. In many systems, this may be represented as a related observation instead of an inline component.
If the use case requires BodySite to be handled as a separate resource (e.g. to identify and track separately) then use the standard extension[ bodySite].'
|
| method | | 0..1 | CodeableConcept | How it was done
Binding: todo (example): Methods for simple observations.
| | 0..1 | CodeableConcept | How it was done
Binding: todo (example): Methods for simple observations.
| |
| specimen | | 0..1 | Reference(Specimen) | Specimen used for this observation | | 0..1 | Reference(Specimen) | Specimen used for this observation | - Elements differ in comments: 'Observations are not made on specimens themselves; they are made on a subject, but usually by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).' vs 'Should only be used if not implicit in code found in `Observation.code`. Observations are not made on specimens themselves; they are made on a subject, but in many cases by the means of a specimen. Note that although specimens are often involved, they are not always tracked and reported explicitly. Also note that observation resources may be used in contexts that track the specimen explicitly (e.g. Diagnostic Report).'
|
| device | | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device | | 0..1 | Reference(Device | DeviceMetric) | (Measurement) Device | - Elements differ in comments: 'An extension should be used if further typing of the device is needed. Devices used to support obtaining an observation can be represented using either extension or through the Observation.related element.' vs 'Note that this is not meant to represent a device involved in the transmission of the result, e.g., a gateway. Such devices may be documented using the Provenance resource where relevant.'
|
| referenceRange | C | 0..* | BackboneElement | Provides guide for interpretation
obs-3: Must have at least a low or a high or text
| C | 0..* | BackboneElement | Provides guide for interpretation
| - Elements differ in definition: 'Guidance on how to interpret the value by comparison to a normal or recommended range.' vs 'Guidance on how to interpret the value by comparison to a normal or recommended range. Multiple reference ranges are interpreted as an "OR". In other words, to represent two distinct target populations, two `referenceRange` elements would be used.'
- Elements differ in comments: 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g. specific to the patient's age, gender, weight and other factors), but this may not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.' vs 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.'
|
 id | | 0..1 | id | xml:id (or equivalent in JSON) | | 0..1 | string | Unique id for inter-element referencing | - Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
- Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
|
| extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs '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.'
|
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
| - Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
- Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| low | C | 0..1 | Quantity | Low Range, if relevant | C | 0..1 | Quantity | Low Range, if relevant | - Elements differ in definition: 'The value of the low bound of the reference range. The low bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the low bound is omitted, it is assumed to be meaningless (e.g. reference range is <=2.3).' vs 'The value of the low bound of the reference range. The low bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the low bound is omitted, it is assumed to be meaningless (e.g. reference range is <=2.3).'
|
| high | C | 0..1 | Quantity | High Range, if relevant | C | 0..1 | Quantity | High Range, if relevant | - Elements differ in definition: 'The value of the high bound of the reference range. The high bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the high bound is omitted, it is assumed to be meaningless (e.g. reference range is >= 2.3).' vs 'The value of the high bound of the reference range. The high bound of the reference range endpoint is inclusive of the value (e.g. reference range is >=5 - <=9). If the high bound is omitted, it is assumed to be meaningless (e.g. reference range is >= 2.3).'
|
| meaning | | 0..1 | CodeableConcept | Indicates the meaning/use of this range of this range
Binding: todo (example): Code for the meaning of a reference range.
| | | | | |
| 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 | - Elements differ in definition: 'Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" or a list or table of 'normals'.' vs 'Text based reference range in an observation which may be used when a quantitative range is not appropriate for an observation. An example would be a reference value of "Negative" or a list or table of "normals".'
|
| type | | | | | | 0..1 | CodeableConcept | Reference range qualifier
Binding: todo (preferred): Code for the meaning of a reference range.
| |
 appliesTo | | | | | | 0..* | CodeableConcept | Reference range population
Binding: todo (example): Codes identifying the population the reference range applies to.
| |
| related | Σ | 0..* | BackboneElement | Resource related to this observation
| | | | | |
| component | Σ | 0..* | BackboneElement | Component results
| Σ | 0..* | BackboneElement | Component results
| - Elements differ in comments: 'For a discussion on the ways Observations can assembled in groups together see [Notes below].' vs 'For a discussion on the ways Observations can be assembled in groups together see [Notes] below.'
|
| id | | 0..1 | id | xml:id (or equivalent in JSON) | | 0..1 | string | Unique id for inter-element referencing | - Elements differ in short: 'xml:id (or equivalent in JSON)' vs 'Unique id for inter-element referencing'
- Elements differ in definition: 'unique id for the element within a resource (for internal references).' vs 'Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.'
|
| extension | | 0..* | Extension | Additional Content defined by implementations
| | 0..* | Extension | Additional content defined by implementations
| - Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension.' vs '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.'
|
| modifierExtension | ?! | 0..* | Extension | Extensions that cannot be ignored
| ?!Σ | 0..* | Extension | Extensions that cannot be ignored even if unrecognized
| - Elements differ in short: 'Extensions that cannot be ignored' vs 'Extensions that cannot be ignored even if unrecognized'
- Elements differ in definition: 'May be used to represent additional information that is not part of the basic definition of the element, and that modifies the understanding of the element that contains it. Usually modifier elements provide negation or qualification. In order 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 is allowed to define an extension, there is a set of requirements that SHALL be met as part of the definition of the extension. Applications processing a resource are required to check for modifier extensions.' vs 'May be used to represent additional information that is not part of the basic definition of the element and that modifies the understanding of the element in which it is contained and/or the understanding of the containing element's descendants. Usually modifier elements provide negation or qualification. 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. Applications processing a resource are required to check for modifier extensions.
Modifier extensions SHALL NOT change the meaning of any elements on Resource or DomainResource (including cannot change the meaning of modifierExtension itself).'
|
| code | ΣC | 1..1 | CodeableConcept | Type of component observation (code / type)
Binding: todo (example): Codes identifying names of simple observations.
| Σ | 1..1 | CodeableConcept | Type of component observation (code / type)
Binding: todo (example): Codes identifying names of simple observations.
| |
| value[x] | Σ | 0..1 | Quantity, CodeableConcept, string, Range, Ratio, SampledData, Attachment, time, dateTime, Period | Actual component result | Σ | 0..1 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result | - Elements differ in comments: 'Normally, an observation will have either a value or a set of related observations. A few observations (e.g. Apgar score) may have both a value and related observations (for an Apgar score, the observations from which the measure is 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 boolean values use valueCodeableConcept and select codes from <http://hl7.org/fhir/ValueSet/v2-0136> (These "yes/no" concepts can be mapped to the display name "true/false" or other mutually exclusive terms that may be needed"). The element, Observation.value[x], has a variable name depending on the type as follows: valueQuantity, valueCodeableConcept, valueRatio, valueChoice, valuePeriod, valueSampleData, or valueString (The name format is "'value' + the type name" with a capital on the first letter of the type).' vs '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 requirements: 'An observation exists to have a value, though it may not if it is in error, or it represents a group of observations.' 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.'
|
| dataAbsentReason | C | 0..1 | CodeableConcept | Why the component result is missing
Binding: todo (extensible): Codes specifying why the result (Observation.value[x]) is missing.
| C | 0..1 | CodeableConcept | Why the component result is missing
Binding: todo (extensible): Codes specifying why the result (Observation.value[x]) is missing.
| - Elements differ in definition: 'Provides a reason why the expected value in the element Observation.value[x] is missing.' vs 'Provides a reason why the expected value in the element Observation.component.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. 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.' 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 "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 description: 'Codes specifying why the result (Observation.value[x]) is missing.' vs 'Codes specifying why the result (`Observation.value[x]`) is missing.'
- Elements differ in description: 'Codes specifying why the result (Observation.value[x]) is missing.' vs 'Codes specifying why the result (`Observation.value[x]`) is missing.'
- Unable to resolve left value set http://hl7.org/fhir/ValueSet/observation-valueabsentreason at Observation.component.dataAbsentReason
|
 referenceRange | | 0..* | See referenceRange | Provides guide for interpretation of component result
| | 0..* | See referenceRange (Observation) | Provides guide for interpretation of component result
| - Elements differ in comments: 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g. specific to the patient's age, gender, weight and other factors), but this may not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.' vs 'Most observations only have one generic reference range. Systems MAY choose to restrict to only supplying the relevant reference range based on knowledge about the patient (e.g., specific to the patient's age, gender, weight and other factors), but this might not be possible or appropriate. Whenever more than one reference range is supplied, the differences between them SHOULD be provided in the reference range and/or age properties.'
|
| interpretation | | | | | | 0..* | CodeableConcept | High, low, normal, etc.
Binding: todo (extensible): Codes identifying interpretations of observations.
| |
| basedOn | | | | | Σ | 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
| |
| focus | | | | | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record
| |
| value[x] | | | | | SΣC | 1..1 | CodeableConcept S, Quantity, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | (USCDI) Typically Coded Responses from Smoking Status Value Set
Binding: todo (preferred): This value set enumerates codes SNOMED CT codes historically used for the current smoking status of a patient with a maximum required binding to Snomed CT codes.
us-core-3: SHALL use UCUM for coded quantity units. | |
| note | | | | | | 0..* | Annotation | Comments about the observation
| |
| hasMember | | | | | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group
| |
| derivedFrom | | | | | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | Related measurements the observation is made from
| |
Documentation for this format |