Generated Narrative: StructureDefinition eu-ai-observation Name Flags Card. Type Description & Constraints Observation 0..* Observation Measurements and simple assertions #xD; Slices for extension 2..* Extension Extension Slice: Unordered, Open by value:url #xD; extension:caseIndication S 1..1 CodeableConcept Case-Specific Indication URL: http://example.org/fhir/eu-ai-transparency/StructureDefinition/case-specific-indication Binding: EU AI Case-Specific Indication ValueSet (extensible) #xD; extension:automatedDecision S 1..1 boolean Automated Decision-Making Flag URL: http://example.org/fhir/eu-ai-transparency/StructureDefinition/automated-decision-flag #xD; status 1..1 code Workflow state: preliminary (unseen) | final (checked) | entered-in-error (overridden) #xD; code S 1..1 CodeableConcept Type of observation (code / type) #xD; subject S 1..1 Reference(Patient | Group | Device | Location | Organization | Procedure | Practitioner | Medication | Substance | BiologicallyDerivedProduct | NutritionProduct) Who and/or what the observation is about #xD; effective[x] S 1..1 dateTime Time the AI generated this result #xD; Slices for interpretation 1..* CodeableConcept High, low, normal, etc Slice: Unordered, Open by value:coding #xD; interpretation:aiGeneratedFlag S 1..1 CodeableConcept Mandatory flag indicating AI origin #xD; coding 1..* Coding Code defined by a terminology system Required Pattern: At least the following #xD; system 1..1 uri Identity of the terminology system Fixed Value: http://example.org/fhir/eu-ai-transparency/CodeSystem/EUAIActCodeSystem #xD; code 1..1 code Symbol in syntax defined by the system Fixed Value: ai-generated #xD; device S 1..1 Reference(EU AI System Device) Link to the AI Device that generated this result #xD; Documentation for this format
An Observation profile representing a clinical output generated by an AI system, including AI-related transparency metadata and links to the relevant patient, encounter, and AI system.
Measurements and simple assertions made about a patient, device or other subject.
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.
If the resource is contained in another resource, it SHALL NOT contain nested Resources
If the resource is contained in another resource, it SHALL be referred to from elsewhere in the resource or SHALL refer to the containing resource
contained.where((('#'+id in (%resource.descendants().reference | %resource.descendants().ofType(canonical) | %resource.descendants().ofType(uri) | %resource.descendants().ofType(url))) or descendants().where(reference = '#').exists() or descendants().where(ofType(canonical) = '#').exists() or descendants().where(ofType(canonical) = '#').exists()).not()).trace('unmatched', id).empty()
If a resource is contained in another resource, it SHALL NOT have a meta.versionId or a meta.lastUpdated
contained.meta.versionId.empty() and contained.meta.lastUpdated.empty()
If a resource is contained in another resource, it SHALL NOT have a security label
When a resource has no narrative, only systems that fully understand the data can display the resource to a human safely. Including a human readable representation in the resource makes for a much more robust eco-system and cheaper handling of resources by intermediary systems. Some ecosystems restrict distribution of resources to only those systems that do fully understand the resources, and as a consequence implementers may believe that the narrative is superfluous. However experience shows that such eco-systems often open up to new participants over time.
A resource should have narrative for robust management
dataAbsentReason SHALL only be present if Observation.value[x] is not present
dataAbsentReason.empty() or value.empty()
If Observation.component.code is the same as Observation.code, then Observation.value SHALL NOT be present (the Observation.component.value[x] holds the value).
value.empty() or component.code.where(coding.intersect(%resource.code.coding).exists()).empty()
bodyStructure SHALL only be present if Observation.bodySite is not present
bodySite.exists() implies bodyStructure.empty()
Entity, Role, or Act,Observation[classCode=OBS, moodCode=EVN]
The logical id of the resource, as used in the URL for the resource. Once assigned, this value never changes.
Within the context of the FHIR RESTful interactions, the resource has an id except for cases like the create and conditional update. Otherwise, the use of the resouce id depends on the given use case.
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.
All FHIR elements must have a @value or children
hasValue() or (children().count() > id.count())
A set of rules under which this content was created
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.
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 its narrative along with other profiles, value sets, etc.
This element is labeled as a modifier because the implicit rules may provide additional knowledge about the resource that modifies its meaning or interpretation
The base language in which the resource is written.
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 summary of the resource, for human interpretation
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.
Contained resources do not have a 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.
These resources do not have an independent existence apart from the resource that contains them - they cannot be identified independently, nor can they have their own independent transaction scope. This is allowed to be a Parameters resource if and only if it is referenced by a resource that provides context/meaning.
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.
Must have either extensions or value[x], not both
The clinical reason why the AI was used for this specific patient.
Indicates whether the AI-generated output was used as part of a solely automated decision-making process within the meaning of GDPR Article 22.
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 managable, 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).
There can be no stigma associated with the use of extensions by any application, project, or standard - regardless of the institution or jurisdiction that uses or defines the extensions. The use of extensions is what allows the FHIR specification to retain a core level of simplicity for everyone.
Modifier extensions allow for extensions that *cannot* be safely ignored to be clearly distinguished from the vast majority of extensions which can be safely ignored. This promotes interoperability by eliminating the need for implementers to prohibit the presence of extensions. For further information, see the [definition of modifier extensions](http://hl7.org/fhir/R5/extensibility.html#modifierExtension).
Modifier extensions are expected to modify the meaning or interpretation of the resource that contains them
A unique identifier assigned to this observation.
Allows observations to be distinguished and referenced.
OBX-21 For OBX segments from systems without OBX-21 support a combination of ORC/OBR and OBX must be negotiated between trading partners to uniquely identify the OBX segment. Depending on how V2 has been implemented each of these may be an option: 1) OBR-3 + OBX-3 + OBX-4 or 2) OBR-3 + OBR-4 + OBX-3 + OBX-4 or 3) some other way to uniquely ID the OBR/ORC + OBX-3 + OBX-4.
The reference to a FHIR ObservationDefinition resource that provides the definition that is adhered to in whole or in part by this Observation instance.
ObservationDefinition can be referenced by its canonical url using instantiatesCanonical, or by a name or an identifier using the appropriate sub-elements of instantiatesReference.
A plan, proposal or order that is fulfilled in whole or in part by this event. For example, a MedicationRequest may require a patient to have laboratory test performed before it is dispensed.
Allows tracing of authorization for the event and tracking whether proposals/recommendations were acted upon.
Identifies the observation(s) that triggered the performance of this observation.
Unique id for the element within a resource (for internal references). This may be any string value that does not contain spaces.
Additional content defined by implementations
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 managable, 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.
Extensions that cannot be ignored even if unrecognized
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 managable, 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).
Modifier extensions are expected to modify the meaning or interpretation of the element that contains them
Reference to the triggering observation.
The type of trigger. Reflex | Repeat | Re-run.
Reason that the observation was triggered
Provides the reason why this observation was performed as a result of the observation(s) referenced.
A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure.
To link an Observation to an Encounter use `encounter`. See the [Notes](http://hl7.org/fhir/R5/observation.html#obsgrouping) below for guidance on referencing another Observation.
Workflow state: preliminary (unseen) | final (checked) | entered-in-error (overridden)
This element is labeled as a modifier because the status contains codes that mark the resource as not currently valid.
Need to track the status of individual results. Some results are finalized before the whole report is finalized.
This element is labeled as a modifier because it is a status element that contains status entered-in-error which means that the resource should not be treated as valid
Codes providing the status of an observation.
status Amended & Final are differentiated by whether it is the subject of a ControlAct event with a type of "revise"
A code that classifies the general type of observation being made.
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.
Used for filtering what observations are retrieved and displayed.
Codes for high level observation categories.
.outboundRelationship[typeCode="COMP].target[classCode="LIST", moodCode="EVN"].code
Describes what was observed. Sometimes this is called the observation "name".
*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.
Knowing what kind of observation is being made is essential to understanding the observation.
Codes identifying names of simple observations.
< 363787002 |Observable entity| OR < 386053000 |Evaluation procedure|
Who and/or what the observation is about
The patient, or group of patients, location, device, organization, procedure or practitioner this observation is about and into whose or what 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.
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. The subject of an Observation may in some cases be a procedure. This supports the regulatory inspection use case where observations are captured during inspections of a procedure that is being performed (independent of any particular patient or whether patient related at all).
Observations have no value if you don't know who or what they're about.
What the observation is about, when it is not about the subject of record
The actual focus of an observation when it is not the patient of record representing something or someone associated with the patient such as a spouse, parent, fetus, or donor. For example, fetus observations in a mother's record. The focus of an observation could also be an existing condition, an intervention, the subject's diet, another observation of the subject, or a body structure such as tumor or implanted device. An example use case would be using the Observation resource to capture whether the mother is trained to change her child's tracheostomy tube. In this example, the child is the patient of record and the mother is the focus.
Typically, an observation is made about the subject - a patient, or group of patients, location, or device - and the distinction between the subject and what is directly measured for an observation is specified in the observation code itself ( e.g., "Blood Glucose") and does not need to be represented separately using this element. Use `specimen` if a reference to a specimen is required. If a code is required instead of a resource use either `bodysite` for bodysites or the standard extension [http://hl7.org/fhir/StructureDefinition/observation-focusCode](http://hl7.org/fhir/extensions/StructureDefinition-observation-focusCode.html).
Healthcare event during which this observation is made
The healthcare event (e.g. a patient and healthcare provider interaction) during which this observation is made.
This will typically be the encounter the event occurred within, but some events may be initiated prior to or after the official completion of an encounter but still be tied to the context of the encounter (e.g. pre-admission laboratory tests).
For some observations it may be important to know the link between an observation and a particular encounter.
inboundRelationship[typeCode=COMP].source[classCode=ENC, moodCode=EVN]
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.
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/R5/datatypes.html#timing) datatype which allow the measurement to be tied to regular life events.
Knowing when an observation was deemed true is important to its relevance as well as determining trends.
OBX-14, and/or OBX-19 after v2.4 (depends on who observation made)
Date/Time this version was made available
The date and time this version of the observation was made available to providers, typically after the results have been reviewed and verified.
For Observations that don't require review and verification, it may be the same as the [`lastUpdated` ](http://hl7.org/fhir/R5/resource-definitions.html#Meta.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.
OBR-22 (or MSH-7), or perhaps OBX-19 (depends on who observation made)
Who was responsible for asserting the observed value as "true".
May give a degree of confidence in the observation and also indicates where follow-up questions should be directed.
OBX-15 / (Practitioner) OBX-16, PRT-5:PRT-4='RO' / (Device) OBX-18 , PRT-10:PRT-4='EQUIP' / (Organization) OBX-23, PRT-8:PRT-4='PO'
The information determined as a result of making the observation, if the information has a simple value.
- An observation may have: 1. a single value here 1. both a value and a set of related or component values 1. only a set of related or component values. - If a value is present, the datatype for this element should be determined by the `code`. - *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 `code` defines a coded value. - *Attachment* is used if the observation result value is a binary file such as an image. If the observation result value is derived from the binary file (for example 'X' detected and here is the the proof in this image), the binary file may be directly represented using *DocumentReference* and referenced by `derivedFrom`. - The usage of valueReference is restricted to the MolecularSequence resource when used as a definitional resource, not as a patient-specific finding. . - For additional guidance, see the [Notes section](http://hl7.org/fhir/R5/observation.html#notes) below.
An observation exists to have a value, though it might not if it is in error, or if it represents a group of observations.
Provides a reason why the expected value in the element Observation.value[x] is missing.
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.
For many results it is necessary to handle exceptional values in measurements.
Codes specifying why the result (`Observation.value[x]`) is missing.
A categorical assessment of an observation value. For example, high, low, normal.
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.
For some results, particularly numeric results, an interpretation is necessary to fully understand the significance of a result.
Codes identifying interpretations of observations.
Extensions are always sliced by (at least) url
A reference to a code defined by a terminology system.
Codes may be defined very casually in enumerations, or code lists, up to very formal definitions such as SNOMED CT - see the HL7 v3 Core Principles for more information. Ordering of codings is undefined and SHALL NOT be used to infer meaning. Generally, at most only one of the coding values will be labeled as UserSelected = true.
Allows for alternative encodings within a code system, and translations to other code systems.
fhir:CodeableConcept.coding rdfs:subPropertyOf dt:CD.coding
Plain text representation of the concept
A human language representation of the concept as seen/selected/uttered by the user who entered the data and/or which represents the intended meaning of the user.
Very often the text is the same as a displayName of one of the codings.
The codes from the terminologies do not always capture the correct meaning with all the nuances of the human using them, or sometimes there is no appropriate code at all. In these cases, the text is used to capture the full meaning of the source.
C*E.9. But note many systems use C*E.2 for this
fhir:CodeableConcept.text rdfs:subPropertyOf dt:CD.originalText
Comments about the observation or the results.
May include general statements about the observation, or statements about significant, unexpected or unreliable results values, or information about its source when relevant to its interpretation.
Need to be able to provide free text additional information.
NTE-3 (partner NTE to OBX, or sometimes another (child?) OBX)
Indicates the site on the subject's body where the observation was made (i.e. the target site).
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.
Indicates the body structure on the subject's body where the observation was made (i.e. the target site).
Only used if not implicit in code found in Observation.code or bodySite is used. In many systems, this may be represented as a related observation instead of an inline component.
Indicates the mechanism used to perform the observation.
Only used if not implicit in code for Observation.code.
In some cases, method can impact results and is thus used for determining whether results can be compared or determining significance of results.
The specimen that was used when this observation was made.
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).
If Observation.specimen is a reference to Group, the group can only have specimens
(reference.resolve().exists() and reference.resolve() is Group) implies reference.resolve().member.entity.resolve().all($this is Specimen)
Link to the AI Device that generated this result
A reference to the device that generates the measurements or the device settings for the device.
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.
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.
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.
Knowing what values are considered "normal" can help evaluate the significance of a particular result. Need to be able to provide multiple reference ranges for different contexts.
Must have at least a low or a high or text
low.exists() or high.exists() or text.exists()
outboundRelationship[typeCode=REFV]/target[classCode=OBS, moodCode=EVN]
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).
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).
The value of the normal value of the reference range.
Codes identifying the normal value of the observation.
Codes to indicate the what part of the targeted reference population it applies to. For example, the normal or therapeutic range.
This SHOULD be populated if there is more than one range. If this element is not present then the normal range is assumed.
Need to be able to say what kind of reference range this is - normal, recommended, therapeutic, etc., - for proper interpretation.
Code for the meaning of a reference range.
< 260245000 |Findings values| OR < 365860008 |General clinical state finding| OR < 250171008 |Clinical history or observation findings| OR < 415229000 |Racial group| OR < 365400002 |Finding of puberty stage| OR < 443938003 |Procedure carried out on subject|
Codes to indicate the target population this reference range applies to. For example, a reference range may be based on the normal population or a particular sex or race. Multiple `appliesTo` are interpreted as an "AND" of the target populations. For example, to represent a target population of African American females, both a code of female and a code for African American would be used.
This SHOULD be populated if there is more than one range. If this element is not present then the normal population is assumed.
Need to be able to identify the target population for proper interpretation.
Codes identifying the population the reference range applies to.
The age at which this reference range is applicable. This is a neonatal age (e.g. number of weeks at term) if the meaning says so.
Text based reference range in an observation
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".
Related resource that belongs to the Observation group
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.
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/R5/observation.html#obsgrouping) below. Note that a system may calculate results from [QuestionnaireResponse](http://hl7.org/fhir/R5/questionnaireresponse.html) into a final score and represent the score as an Observation.
Relationships established by OBX-4 usage
Related resource from which the observation is made
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.
All the reference choices that are listed in this element can represent clinical observations and other measurements that may be the source for a derived value. The most common reference will be another Observation. For a discussion on the ways Observations can assembled in groups together, see [Notes](http://hl7.org/fhir/R5/observation.html#obsgrouping) below.
Some observations have multiple component observations. These component observations are expressed as separate code value pairs that share the same attributes. Examples include systolic and diastolic component observations for blood pressure measurement and multiple component observations for genetics observations.
For a discussion on the ways Observations can be assembled in groups together see [Notes](http://hl7.org/fhir/R5/observation.html#notes) below.
Component observations share the same attributes in the Observation resource as the primary observation and are always treated a part of a single observation (they are not separable). However, the reference range for the primary observation value is not inherited by the component values and is required when appropriate for each component observation.
Type of component observation (code / type)
Describes what was observed. Sometimes this is called the observation "code".
*All* code-value and component.code-component.value pairs need to be taken into account to correctly understand the meaning of the observation.
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 the `code`. - *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 `code` defines a coded value. - *Attachment* is used if the observation result value is a binary file such as an image. If the observation result value is derived from the binary file (for example 'X' detected and here is the the proof in this image), the binary file may be directly represented using *DocumentReference* and referenced by `derivedFrom`. - If a value is present, the datatype for this element should be determined by the `code`. - *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 `code` defines a coded value. - *Attachment* is used if the observation result value is a binary file such as an image. If the observation result value is derived from the binary file (for example 'X' detected and here is the the proof in this image), the binary file may be directly represented using *DocumentReference* and referenced by `derivedFrom`. - The usage of valueReference is restricted to the MolecularSequence resource when used as a definitional resource, not as a patient-specific finding. . - For additional guidance, see the [Notes section](http://hl7.org/fhir/R5/observation.html#notes) below.
363714003 |Interprets| < 441742003 |Evaluation finding|
Provides a reason why the expected value in the element Observation.component.value[x] is missing.
"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.
Provides guide for interpretation of component result
Guidance on how to interpret the value by comparison to a normal or recommended range.