| Left: | US Core Laboratory Result Observation Profile (http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab) |
| Right: | Personal Functioning and Engagement Single Observation (http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-single) |
| Error | StructureDefinition.url | Values for url differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab' vs 'http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-single' |
| Error | StructureDefinition.version | Values for version differ: '7.0.0-ballot' vs '1.9.0' |
| Information | StructureDefinition.name | Values for name differ: 'USCoreLaboratoryResultObservationProfile' vs 'PFESingleObservation' |
| Information | StructureDefinition.title | Values for title differ: 'US Core Laboratory Result Observation Profile' vs 'Personal Functioning and Engagement Single Observation' |
| Information | StructureDefinition.status | Values for status differ: 'active' vs 'draft' |
| Information | StructureDefinition.date | Values for date differ: '2023-10-17' vs '2024-04-16T20:59:30+00:00' |
| Information | StructureDefinition.publisher | Values for publisher differ: 'HL7 International / Cross-Group Projects' vs 'HL7 International / Patient Care' |
| Error | StructureDefinition.baseDefinition | Values for baseDefinition differ: 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result' vs 'http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey' |
| Information | StructureDefinition.short | Values for short differ: 'Measurements and simple assertions' vs 'Survey Observation' |
| Information | StructureDefinition.short | Values for short differ: 'Additional content defined by implementations' vs 'Extension' |
| Information | StructureDefinition.definition | Values for definition differ: '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' |
| Information | StructureDefinition.short | Values for short differ: 'registered | preliminary | final | amended +' vs 'Should have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used.' |
| Information | StructureDefinition.requirements | Values for requirements differ: 'Used for filtering what observations are retrieved and displayed.' vs 'This code should be included in the Value Set associated with the selected PFE category ICF domain for this observation.' |
| Information | Observation.category | Element minimum cardinalities differ: '1' vs '2' |
| Information | StructureDefinition.short | Values for short differ: 'Laboratory Test Name' vs 'For PFE Assessments, should include a LOINC code and text for the question or concept name.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The name of the clinical test or procedure performed on a patient. A LOINC **SHALL** be used if the concept is present in LOINC.' vs 'Describes what was observed. Sometimes this is called the observation 'name'.' |
| Information | StructureDefinition.comment | Values for comment differ: 'The typical patterns for codes are: 1) a LOINC code either as a translation from a 'local' code or as a primary code, or 2) a local code only if no suitable LOINC exists, or 3) both the local and the LOINC translation. Systems SHALL be capable of sending the local code if one exists. When using LOINC , Use either the SHORTNAME or LONG_COMMON_NAME field for the display.' 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.' |
| Information | StructureDefinition.short | Values for short differ: 'Encounter associated with Observation' vs 'Healthcare event during which this observation is made' |
| Warning | Observation.encounter | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' 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'.' |
| Information | StructureDefinition.comment | Values for comment differ: '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](http://hl7.org/fhir/R4/datatypes.html#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.' |
| Information | Observation.effective[x] | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Who is responsible for the observation' vs 'The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization.' |
| Warning | Observation.performer | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | Observation.performer | Element minimum cardinalities differ: '0' vs '1' |
| Information | StructureDefinition.short | Values for short differ: 'Result Value' vs 'Whenever possible should use the CodeableConcept datatype to provide a suitable code to define the concept for the observation data. As for values like an assessment score or roll-up value, the datatype for this element should be determined by Observation.code. However, for values that are ordinal, may use the CodeableConcept datatype along with the Ordinal Value Extension.' |
| Information | StructureDefinition.definition | Values for definition differ: 'The Laboratory result value. If a coded value, the valueCodeableConcept.code **SHOULD** be selected from [SNOMED CT](http://hl7.org/fhir/ValueSet/uslab-obs-codedresults) if the concept exists. If a numeric value, valueQuantity.code **SHALL** be selected from [UCUM](http://unitsofmeasure.org). A FHIR [UCUM Codes value set](http://hl7.org/fhir/STU3/valueset-ucum-units.html) that defines all UCUM codes is in the FHIR specification.' vs 'The information determined as a result of making the observation, if the information has a simple value.' |
| Information | StructureDefinition.comment | Values for comment differ: '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](http://hl7.org/fhir/R4/observation.html#notes) below.' vs '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.' |
| Information | StructureDefinition.comment | Values for comment differ: '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.' 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. 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.' |
| Information | StructureDefinition.short | Values for short differ: 'Result interpretation' vs 'High, low, normal, etc.' |
| Information | StructureDefinition.comment | Values for comment differ: 'Categorical assessment of a laboratory value, often in relation to a test's reference range. Examples include but are not limited to high, low, critical, and normal.' vs 'Historically used for laboratory results (known as 'abnormal flag' ), its use extends to other use cases where coded interpretations are relevant. Often reported as one or more simple compact codes this element is often placed adjacent to the result value in reports and flow sheets to signal the meaning/normalcy status of the result.' |
| Warning | Observation.interpretation | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Warning | Observation.specimen | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Result reference range' vs 'Provides guide for interpretation' |
| Information | StructureDefinition.comment | Values for comment differ: 'Upper and lower limit of test values expected for a designated population of individuals. Reference range values may differ by patient characteristics, laboratory test manufacturer and laboratory test performer.' 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.' |
| Warning | Observation.referenceRange | Elements differ in definition for mustSupport: 'true' vs 'false' |
| Information | StructureDefinition.short | Values for short differ: 'Related resource that belongs to the Observation group' vs 'Reference to panel or multi-select responses' |
| Information | StructureDefinition.definition | Values for definition differ: 'This observation is a group observation (e.g. a battery, a panel of tests, a set of vital sign measurements) that includes the target as a member of the group.' vs 'Aggregate set of Observations that represent question answer pairs for both multi-question surveys and multi-select questions.' |
| Information | StructureDefinition.comment | Values for comment differ: '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](http://hl7.org/fhir/R4/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](questionnaireresponse.html) into a final score and represent the score as an Observation.' vs '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.' |
| Warning | Observation.hasMember | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Information | Observation.hasMember | Element maximum cardinalities differ: '2147483647' vs '0' |
| Information | StructureDefinition.short | Values for short differ: 'Related measurements the observation is made from' vs 'Should point back to the QuestionnaireResponse that this resource is derived from.' |
| Information | StructureDefinition.definition | Values for definition differ: '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.' vs 'Observations or QuestionnaireResponses from which this observation value is derived.' |
| Warning | Observation.derivedFrom | Elements differ in definition for mustSupport: 'false' vs 'true' |
| Error | Observation.derivedFrom | Type Mismatch: 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]]) vs Reference([CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-questionnaireresponse], CanonicalType[http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey]]) |
| Name | Value | Comments | |
|---|---|---|---|
 abstract | false | ||
| baseDefinition | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-clinical-result | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-survey |
|
| copyright | Used by permission of HL7 International, all rights reserved Creative Commons License |
| |
| date | 2023-10-17 | 2024-04-16T20:59:30+00:00 |
|
| description | The US Core Laboratory Result Observation Profile is based upon the US Core Observation Clinical Result Profile and, along with the US Core DiagnosticReport Profile for Laboratory Results Reporting, meets the U.S. Core Data for Interoperability (USCDI) Laboratory requirements. Laboratory results are grouped and summarized using the DiagnosticReport resource, which references Observation resources. Each Observation resource represents an individual laboratory test and result value, a “nested” panel (such as a microbial susceptibility panel) that references other observations, or rarely a laboratory test with component result values. The US Core Laboratory Result Observation Profile sets minimum expectations for the Observation resource to record, search, and fetch laboratory test results associated with a patient to promote interoperability and adoption through common implementation. It identifies which core elements, extensions, vocabularies, and value sets SHALL be present in the resource and constrains the way the elements are used when using this profile. It provides the floor for standards development for specific use cases. | An exchange of post-acute care observation for a patient. This profile is used for exchanging an observation for a single question generally included in a structured resource (e.g., assessment tool, instrument, or screen). |
|
| experimental | false |
| |
| fhirVersion | 4.0.1 | ||
| jurisdiction | |||
 jurisdiction[0] | urn:iso:std:iso:3166#US | ||
| kind | resource | ||
| name | USCoreLaboratoryResultObservationProfile | PFESingleObservation |
|
| publisher | HL7 International / Cross-Group Projects | HL7 International / Patient Care |
|
| purpose | |||
| status | active | draft |
|
| title | US Core Laboratory Result Observation Profile | Personal Functioning and Engagement Single Observation |
|
| type | Observation | ||
| url | http://hl7.org/fhir/us/core/StructureDefinition/us-core-observation-lab | http://hl7.org/fhir/us/pacio-pfe/StructureDefinition/pfe-observation-single |
|
| version | 7.0.0-ballot | 1.9.0 |
|
| Name | L Flags | L Card. | L Type | L Description & Constraints | R Flags | R Card. | R Type | R Description & Constraints | Comments | ||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
 Observation | C | 0..* | USCoreObservationClinicalResultProfile | Measurements and simple assertions obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present us-core-2: If there is no component or hasMember element then either a value[x] or a data absent reason must be present | C | 0..* | USCoreObservationSurveyProfile | Survey Observation obs-6: dataAbsentReason SHALL only be present if Observation.value[x] is not present obs-7: If Observation.code is the same as an Observation.component.code then the value element associated with the code SHALL NOT be present 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. | |||||||||
 id | Σ | 0..1 | id | Logical id of this artifact | Σ | 0..1 | id | 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: ?? (preferred): A human language.
| 0..1 | code | Language of the resource content Binding: ?? (preferred): A human language.
| |||||||||||
| 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 | Extension Slice: Unordered, Open by value:url | |||||||||||
 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: ?? (required): Codes providing the status of an observation. | ?!SΣ | 1..1 | code | Should have the value 'final' when the observation is complete and there are no further actions needed. Otherwise, another value from the value set may appropriately be used. Binding: ?? (required): Codes providing the status of an observation. | |||||||||
| Slices for category | S | 1..* | CodeableConcept | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ?? (preferred): Codes for high level observation categories. | S | 2..* | CodeableConcept | Classification of type of observation Slice: Unordered, Open by pattern:$this Binding: ?? (preferred): Codes for high level observation categories. |
| ||||||||
| code | SΣ | 1..1 | CodeableConcept | Laboratory Test Name Binding: ?? (extensible): Laboratory LOINC Codes | SΣ | 1..1 | CodeableConcept | For PFE Assessments, should include a LOINC code and text for the question or concept name. Binding: ?? (preferred) | |||||||||
| subject | SΣ | 1..1 | Reference(US Core Patient Profile S | Group | Device | US Core Location Profile) | Who and/or what the observation is about | SΣ | 1..1 | Reference(US Core Patient Profile) | Who and/or what the observation is about | |||||||||
| focus | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record | Σ | 0..* | Reference(Resource) | What the observation is about, when it is not about the subject of record | |||||||||
| encounter | SΣ | 0..1 | Reference(US Core Encounter Profile) | Encounter associated with Observation | Σ | 0..1 | Reference(Encounter) | Healthcare event during which this observation is made |
| ||||||||
| effective[x] | SΣC | 0..1 | dateTime S, Period, Timing, instant | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. | SΣC | 1..1 | dateTime S | Clinically relevant time/time-period for observation us-core-1: Datetime must be at least to day. |
| ||||||||
| issued | Σ | 0..1 | instant | Date/Time this version was made available | Σ | 0..1 | instant | Date/Time this version was made available | |||||||||
| performer | Σ | 0..* | Reference(Practitioner | PractitionerRole | Organization | CareTeam | Patient | RelatedPerson) | Who is responsible for the observation | SΣ | 1..* | Reference(US Core Practitioner Profile S | US Core PractitionerRole Profile | US Core Organization Profile) | The person who performed the assessment. The preferred way to specify the performer is to use the PractitionerRole resource to provide both the practitioner and organization. |
| ||||||||
| value[x] | SΣC | 0..1 | Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Result Value us-core-3: SHALL use UCUM for coded quantity units. us-core-4: SHOULD use Snomed CT for coded Results | SΣC | 0..1 | Quantity S, CodeableConcept S, string S, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Whenever possible should use the CodeableConcept datatype to provide a suitable code to define the concept for the observation data. As for values like an assessment score or roll-up value, the datatype for this element should be determined by Observation.code. However, for values that are ordinal, may use the CodeableConcept datatype along with the Ordinal Value Extension. | |||||||||
| dataAbsentReason | SC | 0..1 | CodeableConcept | Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | SC | 0..1 | CodeableConcept | Why the result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | |||||||||
| interpretation | S | 0..* | CodeableConcept | Result interpretation Binding: ?? (extensible): Observation Interpretation Codes | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (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: ?? (example): Codes describing anatomical locations. May include laterality. | 0..1 | CodeableConcept | Observed body part Binding: ?? (example): Codes describing anatomical locations. May include laterality. | |||||||||||
| method | 0..1 | CodeableConcept | How it was done Binding: ?? (example): Methods for simple observations. | 0..1 | CodeableConcept | How it was done Binding: ?? (example): Methods for simple observations. | |||||||||||
| specimen | S | 0..1 | Reference(US Core Specimen Profile) | 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 | SC | 0..* | BackboneElement | Result reference range obs-3: Must have at least a low or a high or text | C | 0..* | BackboneElement | Provides guide for interpretation obs-3: Must have at least a low or a high or text |
| ||||||||
 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 | C | 0..1 | ?? | Low Range, if relevant | C | 0..1 | ?? | Low Range, if relevant | |||||||||
| high | C | 0..1 | ?? | High Range, if relevant | C | 0..1 | ?? | High Range, if relevant | |||||||||
| type | 0..1 | CodeableConcept | Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range. | 0..1 | CodeableConcept | Reference range qualifier Binding: ?? (preferred): Code for the meaning of a reference range. | |||||||||||
| appliesTo | 0..* | CodeableConcept | Reference range population Binding: ?? (example): Codes identifying the population the reference range applies to. | 0..* | CodeableConcept | Reference range population Binding: ?? (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 | Σ | 0..* | Reference(Observation | QuestionnaireResponse | MolecularSequence) | Related resource that belongs to the Observation group | SΣ | 0..0 |
| ||||||||||
| derivedFrom | Σ | 0..* | Reference(DocumentReference | ImagingStudy | Media | QuestionnaireResponse | Observation | MolecularSequence) | Related measurements the observation is made from | SΣ | 0..* | Reference(US Core QuestionnaireResponse Profile S | US Core Observation Survey Profile S) | Should point back to the QuestionnaireResponse that this resource is derived from. |
| ||||||||
 component | Σ | 0..* | BackboneElement | Component results | Σ | 0..* | BackboneElement | Component results | |||||||||
 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 | |||||||||
| code | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (example): Codes identifying names of simple observations. | Σ | 1..1 | CodeableConcept | Type of component observation (code / type) Binding: ?? (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 | Quantity, CodeableConcept, string, boolean, integer, Range, Ratio, SampledData, time, dateTime, Period | Actual component result | |||||||||
| dataAbsentReason | C | 0..1 | CodeableConcept | Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | C | 0..1 | CodeableConcept | Why the component result is missing Binding: ?? (extensible): Codes specifying why the result (Observation.value[x]) is missing. | |||||||||
| interpretation | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (extensible): Codes identifying interpretations of observations. | 0..* | CodeableConcept | High, low, normal, etc. Binding: ?? (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 | |||||||||||||||||