Measurements and assertions about a patient — vital signs, lab results, clinical findings. This page documents the Observation resource as served by the mock.health synthetic FHIR R4 sandbox — 8 search parameters, US Core 6.1 profiling, and the elements accepted on write.
GET https://api.mock.health/fhir/Observation — searchGET https://api.mock.health/fhir/Observation/{id} — read by logical idPOST https://api.mock.health/fhir/Observation — create (Pro)PUT https://api.mock.health/fhir/Observation/{id} — update (Pro)patient (reference) — required — Patient the observation is aboutcode (token) — Observation code (LOINC)date (date) — Clinically relevant date/timeencounter (reference) — Encounter for the observationidentifier (token) — External identifiercategory (token) — vital-signs | laboratory | survey | examstatus (token) — final | preliminary | amendedvalue-quantity (quantity) — Numeric value with optional comparator and unitFields accepted when creating or updating a Observation. Required elements are base FHIR cardinality; the rest are US Core must-support.
status (code) — required — registered | preliminary | final | amended | correctedcode (CodeableConcept) — required — Observation type code (LOINC)subject (Reference(Patient)) — US Core MS — patient the observation is aboutcategory (CodeableConcept[]) — US Core MS — vital-signs | laboratory | survey | exameffectiveDateTime (dateTime) — US Core MS — clinically relevant timevalueQuantity (Quantity) — US Core MS — numeric result with unit (UCUM)Numeric lab observations include referenceRange and interpretation codes. Use category to distinguish vital signs from lab results.
Base definition: HL7 FHIR R4 Observation. Category: Diagnostics.
DiagnosticReport · ImagingStudy · Media · ServiceRequest · Specimen
API reference · Quickstart · USCDI compliance · SMART on FHIR