basedOn"A plan, proposal or order that is fulfilled in whole or in part by this event." - HL7 CIMI, EvaluationResultTopic.basedOn"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." - HL7 FHIR, Observation.basedOn"The order, proposal or plan that is fulfilled in whole or in part by this QuestionnaireResponse. For example, a ServiceRequest seeking an intake assessment or a decision support recommendation to assess for post-partum depression." - HL7 FHIR, QuestionnaireResponse.basedOn
bodySiteIdentifies the anatomical site or system that is the focus of the Observation."Contains the body site(s) where the measurement being reported was obtained. This field should not be used for a specimen source or specimen collection site. This information is of particular importance if the clinical meaning of a value is modified either directly by the site (for example, is the temperature central or peripheral?) or if the site of one measurement impacts the value of another measurement (for example, is the finger SpO2 probe on the same arm as the NIBP cuff?). In most cases these observations are performed directly upon the patient and do not involve a specimen." - HL7 Version 2.8, OBX-20."Indicates the site on the subject's body where the observation was made (i.e. the target site)." - HL7 FHIR, Observation.bodySite.
categoryThis optional property is used to classify the observation into coarse-grained groups such as vital signs, laboratory, etc. This property is included for compatibility to FHIR, although in the FHIM, such a categorization is usually handled through generalization (sub-type) relationships."A code that classifies the general type of observation being made." Possible values are: Activity; Exam; Imaging; Laboratory; Procedure; Social History; Survey; Therapy; Vital Signs. - HL7 FHIR, Observation.category
componentObservationPointer to a set of observations that occurred during the same time or as part of the primary observation."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." - HL7 FHIR, Observation.component
dataAbsentReason"If the result value is missing, a code explaining the reason the result cannot be provided." - HL7 CIMI, RecordedContext.exceptionValue"Provides a reason why the expected value in [value] is missing" - HL7 FHIR, Observation.dataAbsentReason.
dateTimeThe date (and optionally, time) that the Observation took place. Note that this is the clinically-relevant time, for example, the clinically relevant time of a result of a lab test on a blood sample is the time the blood was drawn, not when the test was run. Note that in FHIR this can be either a point in time or a period (i.e., a TimeInterval). In the FHIM, this is currently modeled as only a point in time. Note also that when used by the Condition sub-type of Observation, this is the date that the Condition was first detected or asserted."This field is required in two circumstances. The first is when the observations reported beneath one report header have different dates/times. This could occur in the case of queries, timed test sequences, or clearance studies where one measurement within a battery may have a different time than another measurement.... The observation date-time is the physiologically relevant date-time or the closest approximation to that date-time. In the case of tests performed on specimens, the relevant date-time is the specimen's collection date-time. In the case of observations taken directly on the patient (e.g., X-ray images, history and physical), the observation date-time is the date-time that the observation was performed." - HL7 Version 2.8, OBX-14."Contains the date/time when the corresponding problem was initially identified by the caregiver." - HL7 Version 2.8, PRB-7"Estimated or actual date the condition/problem/diagnosis was first detected/suspected." - HL7 FHIR, Condition resource."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." - HL7 FHIR, Observation.effective[x]"Date of vitals measure." - PCORnet Common Data Model, Vital.Measure_Date"Time of vitals measure." - PCORnet Common Data Model, Vital.Measure_Time
dateTimeIssued"The date and time this observation was made available to providers, typically after the results have been reviewed and verified." - HL7 FHIR, Observation.issued"The date and time this observation was made available to providers, typically after the results have been reviewed and verified." - HL7 CIMI, RecordedContext.RecordedContext
deltaFlag"Flag indicating whether there was a significant change from previous results." - HL7 CIMI, RecordedContext.deltaFlag
derivedFromPointer to another ObservationStatement from which this Observation was derived. This property is currently marked as derived as it can potentially be realized through the RelatedClinicalInformation structure inherited from ClinicalStatement."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." - HL7 CIMI, EvaluationResultTopic.derivedFrom"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." - HL7 FHIR, Observation.derivedFrom
description"An optional description of the finding in human narrative form." - HL7 CIMI, FindingTopic.description
deviceInstance"Identifies the Equipment Instance (e.g., Analyzer, Analyzer module, group of Analyzers, etc.) responsible for the production of the observation...." - HL7 Version 2.8, OBX-18."The device used to evaluate the characteristic such as the type of blood pressure cuff used on a patient." - HL7 CIMI, EvaluationResultTopic.device"The device used to generate the observation data." - HL7 FHIR, Observation.device
evaluationProcedure"The evaluation procedure that is the source of the evaluation result." - HL7 CIMI, EvaluationResultTopic.evaluationProcedure
exceptionValueIndicates the reason why a test was unable to be performed. It may indicate that the quantity of specimen was insufficient, that the specimen was contaminated, that the specimen is inappropriate for the kind of test ordered, etc.Note that when the reason that a test could not be performed is due to some aspect of the specimen, the specimen appropriateness and/or speciment condition should be used instead of this property."As best practice in the future, a combination of SPM-21 and SPM-24 should be used to provide the most detailed coded information about the specimen reject reason and the specific specimen condition, if applicable. Use of SPM-21 is the ideal way to communicate when a test order is canceled due to specimen rejection as it codifies the reason for cancellation. Because disposition of a specimen is a CLIA requirement this reason needs to be retained and displayed in the patient record and incorporated into any type of report regardless of the medium of that report (paper, displayed on screen). The IG has identified HL70490 table as the value set for SPM-21, though the content needs improvement. The SNOMED finding hierarchy also has some appropriate terms, but is not complete. Future work on these vocabularies will expand the content. Use of SPM-24 can be very useful for communicating specimen condition information that does not meet the laboratory’s standard for acceptability (HL70493). The SNOMED finding hierarchy also has some appropriate terms, but is not complete. Future work on these vocabularies will expand the content. If a laboratory system cannot use SPM-21 and SPM-24, then this information shall be communicated using OBX-5 and NTE segment(s)""Contains the value observed by the observation producer.... It is not a required field because some systems will report only the Interpretation Codes.... This field may repeat for multipart, single answer results." - HL7 Version 2.8, OBX-5."If the result value is missing, a code explaining the reason the result cannot be provided." - HL7 CIMI, RecordedContext.exceptionValue
hasMember"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." - HL7 FHIR, Observation.hasMember
interpretationEventPointer to a clinical judgement or assessment concerning the significance of the value or result of the Clinical Observation. For chemistry tests, provides an indication (often automated) of the result, based upon "normal" values as indicated by the reference range. Examples include High, Low, Critically High, Critically Low, etc. For antibiotic sensitivity tests, provides an indication of the susceptibility of the identified organism to the test antibiotic. Possible values include: Intermediate, Moderately Susceptible, Resistant, Susceptible. In addition, Not Tested may occasionally be used when an antibiotic that would commonly be tested was not for some reason."One or more codes specifying a categorical assessment of the observation value, such as "Normal", "Abnormal", "Positive", "Negative", "Resistant", "Susceptible", etc...." - HL7 Version 2.8, OBX-8"A clinical judgment concerning the significance or impact of the finding with respect to its subject (e.g., the patient)." - HL7 CIMI, FindingTopic.interpretation"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." - HL7 FHIR, Observation.interpretation
methodProvides additional detail about the means or technique used to ascertain the Observation. The method used may affect how the observation value is interpreted."The method or procedure by which an observation was obtained when the sending system wishes to distinguish among one measurement obtained by different methods and the distinction is not implicit in the test ID. Chemistry laboratories do not usually distinguish between two different methods used to measure a given serum constituent (e.g., serum potassium) as part of the test name...." - HL7 Version 2.8, OBX-17."The means by which a measurement, evaluation, or assessment was made." - HL7 CIMI, EvaluationResultTopic.method"Indicates the mechanism used to perform the observation." - HL7 FHIR, Observation.method.Note that for laboratory observations, the aerobic condition of the culture is included in this concept. Note also that this property can repeat.
multimedia"Audio, visual, or other binary content produced during the evaluation, such as an X-ray." - HL7 CIMI, FindingTopic.multimedia
observed"Information about who observed the characteristic, when did they make the observation, etc..." - HL7 CIMI, RecordedContext.observed"Who was responsible for asserting the observed value as true." - HL7 FHIR, Observation.performer
observedCharacteristicIndicates what was observed. This property may be re-defined in sub-classes to explictly describe a particular kind of observation (e.g., Heart Rate)."Describes what was observed. Sometimes this is called the observation "name"." - HL7 FHIR, Observation.code
partOfPointer to a ClinicalStatement about an event of which this Observation is a component or step. This property is currently marked as derived as it can potentially be realized through the RelatedClinicalInformation structure inherited from ClinicalStatement."A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure. Do not use this attribute to link this observation to the encounter where it originates. Use the 'encounter' attribute of ClinicalStatement instead." - HL7 CIMI, EvaluationResultTopic.partOf"A larger event of which this particular Observation is a component or step. For example, an observation as part of a procedure." - HL7 FHIR, Observation.partOf
referenceRangePointer to a set of normal or recommended ranges that can be used to compare against the value of the actual observation or test results."When the observation quantifies the amount of a toxic substance, then the upper limit of the range identifies the toxic limit. If the observation quantifies a drug, the lower limits identify the lower therapeutic bounds and the upper limits represent the upper therapeutic bounds above which toxic side effects are common." - HL7 Version 2.8, OBX-7"Contains the nature of the abnormal test. Refer to HL7 Table 0080 - Nature of abnormal testing for valid values. As many of the codes as apply may be included, separated by repeat delimiters." - HL7 Version 2.8, OBX.10"The range for the measurement." - HL7 CIMI, EvaluationResultTopic.referenceRange"Guidance on how to interpret the value by comparison to a normal or recommended range." - HL7 FHIR, Observation.referenceRange
reliability"An estimate of the degree to which quality issues have impacted on the value reported." - HL7 FHIR, Observation.reliability.
resultStatusIndicates the state of the result value, for example whether it is preliminary or final, etc. Note that this status differs from the record status inherited from Clinical Information, in that the record status indicates whether the record is active, obsoleted, etc. While there is some overlap between the two statuses (e.g., they both can represent entered-in-error), this property is meant to convey more clinical information regarding the reliability of the information (e.g., preliminary versus final), whereas the record status tends to focus on the lifecycle of the record (e.g., new versus active)."Contains the observation result status.... This field reflects the current completion status of the results for one Observation Identifier...." - HL7 Version 2.8, OBX-11"The last recorded state of the finding, indicating whether the finding is preliminary, amended, final, to be attained, etc." - HL7 CIMI, FindingContext.status"The status of the result value." - HL7 FHIR, Observation.status. Note that the possible values for status in FHIR are: Registered, Preliminary, Final, Amended, Corrected, Cancelled, Entered in Error, Unknown.
specimenPointer to the specimen about which the observation took place."The specimen that was used when this observation was made." - HL7 FHIR, Observation.specimen
valueContains the value of the Clinical Observation. This property is modeled as an Any datatype in the generic Observation; specific subtypes are expected to re-define this property to the appropriate datatype."Contains the value observed by the observation producer.... It is not a required field because some systems will report only the Interpretation Codes.... This field may repeat for multipart, single answer results." - HL7 Version 2.8, OBX-5"Contains the units of measurement for the value in OBX-5, Observation Value." - HL7 Version 2.8, OBX-6"The value of the finding, typically a quantity for measurements and a concept code for qualitative evaluations and assertions. In general, any data type can be the value of a finding." - HL7 CIMI, RecordedContext.resultValue"The information determined as a result of making the observation, if the information has a simple value." - HL7 FHIR, Observation.value[x]
FHIM::Common::ClinicalStatement