Observation (FHIR Observation)

fhir technical technical fhirclinicalinteroperabilityhealthcare
Source: HL7 System: http://hl7.org/fhir Code: Observation Reviewed: 20/02/2026 License: CC-BY-4.0

Observation (FHIR Observation)

One-sentence definition: The FHIR Observation resource represents a measurement, assessment, or finding about a patient — the primary resource for lab results, vital signs, clinical assessments, and survey responses in FHIR-based health data exchange.

Full Definition

The Observation resource is one of the most frequently used FHIR resources. It captures the outcome of a measurement or assessment: a serum glucose level, a blood pressure reading, a depression screening score, a smoking status. Almost any quantifiable or codeable clinical finding that is not itself a condition or diagnosis fits the Observation model.

Every Observation has a code that identifies what was measured (typically a LOINC code), a value that records the result (a quantity, a string, a coded concept, or others), a status (preliminary, final, amended, etc.), and a subject who the observation is about. Observations are also linked to effectiveDateTime or effectivePeriod — when the measurement was taken — and optionally to an encounter and a performer.

The US Core IG defines a family of Observation profiles that constrain the base resource for specific clinical categories: vital signs (with child profiles for blood pressure, heart rate, body weight, and others), laboratory results, smoking status, SDOH assessments, and more. Each profile specifies required LOINC codes, Must Support elements, and binding strengths for coded values.

Context and Usage

Where This Term Appears

  • Laboratory interfaces: Lab results arrive as Observation resources (or are transformed into them from HL7 v2 ORU messages)
  • Vital signs pipelines: Blood pressure, heart rate, oxygen saturation, body weight — all modeled as Observation resources with LOINC codes
  • Quality measures and CDS: Quality measure logic queries Observation resources to identify patients with specific findings
  • US Core conformance: US Core Observation profiles are required elements of ONC certification

Common Usage Examples

In conversation: “The lab result comes back as an Observation with LOINC 2345-7 in the code and a valueQuantity of 95 mg/dL.”

In documentation: “Vital signs must be represented as US Core Vital Signs Observations, with Observation.category set to vital-signs and Observation.code populated with the appropriate LOINC code.”

Relationship to Other Terms

  • FHIR — the standard that defines Observation as a core resource
  • Resource — Observation is one of FHIR’s most-used resource types
  • LOINC — the coding system used in Observation.code to identify what was measured
  • Profile — US Core Observation profiles constrain the base resource for specific clinical categories

Common Misconceptions

Misconception: Observation Is Only for Lab Results

  • Incorrect belief: The Observation resource is a lab result container — vital signs and clinical assessments should use different resources.
  • Reality: Observation is a general-purpose measurement resource covering lab results, vital signs, social history (smoking status, housing situation), clinical assessments (PHQ-9 scores), imaging findings, and more. The category element differentiates these uses.
  • Why it matters: Teams building vital signs monitoring, survey tools, or SDOH screening workflows all need to produce Observation resources — not just teams building lab integrations.

Misconception: Any Clinical Finding Should Be an Observation

  • Incorrect belief: Anything a clinician observes about a patient should be modeled as an Observation resource.
  • Reality: FHIR has distinct resources for different types of clinical information. A diagnosis is a Condition; a medication a patient is taking is a MedicationStatement or MedicationRequest; an allergy is an AllergyIntolerance. Observation is specifically for measurements, assessments, and findings that have a quantifiable or codeable value.
  • Why it matters: Modeling diagnoses or allergies as Observations rather than using the appropriate FHIR resource breaks downstream queries that search specific resource types.

Why Observation Matters

Observation is the primary vehicle for clinical measurement data in FHIR. Lab results, vital signs, and clinical assessments that flow through FHIR-based integrations are Observation resources. Quality measures, clinical decision support rules, and population health analytics all query Observations to identify patients with specific findings. Getting Observation coding right — using the correct LOINC code, the right category, and the right value representation — determines whether downstream systems can correctly interpret the data.

For Observation profile details, US Core vital signs profiles, and how to code specific measurement types, see the canonical reference → FHIR Profiling

Cross-References

  • FHIR — the standard that defines Observation as a core resource
  • Resource — Observation is one of FHIR’s most-used resource types
  • LOINC — the coding system used in Observation.code to identify what was measured
  • Profile — US Core Observation profiles constrain the base resource for specific clinical categories

Last reviewed: February 20, 2026 Definition authority: HL7 International Content status: Canonical reference