Skip to main content

​
Overview

The Observation Clinical Result resource represents clinical observations and measurements about a patient, including findings from diagnostic imaging, clinical procedures, and other non-laboratory tests. This resource captures results from various clinical assessments such as radiology findings, procedure observations, and examination results. For example, it records observations like the size of a polyp noted during a colonoscopy or findings from an imaging study. At its minimum, Observation contains a code identifying what was observed, a status, a reference to the patient, and the observed value or result, but may also contain data about the performer, timing, and interpretation of the observation. the observation. Each Observation Must Have:
  • a status
  • a category code
  • a LOINC code, if available, which tells you what is being measured
  • a patient
Each Observation Must Support:
  • a time indicating when the measurement was taken
  • a result value
  • a reason why the data is absent
This resource conforms to USCDI v3 profile for Observation Clinical Result - refer to StructureDefinition US Core Observation Clinical Result. Observation Clinical Result response will be provided in JSON (refers to Capability Statement) format as per FHIR standard R4 version.

​
Must support elements, mandatory and optional search parameters

Observation Clinical Result must support these elements:
  • status
  • category
    • category:us-core
  • code
  • subject
  • effective[x]
  • value[x]
  • dataAbsentReason
The following search parameters and search parameter combinations SHALL be supported: The syntax used to describe the interactions is described here. SHALL support searching using the combination of the patient and category search parameters: GET [base url]/Observation?patient={Type/}[id]&category={system|}[code] SHALL support searching using the combination of the patient and code search parameters:
  • including optional support for OR search on code GET [base url]/Observation?patient={Type/}[id]&code={system|}[code]
SHALL support searching using the combination of the patient and category and date search parameters:
  • including support for these date comparators: gt,lt,ge,le
  • including optional support for AND search on date (e.g.date=[date]&date=[date]]&…) GET [base url]/Observation?patient={Type/}[id]&category={system|}[code]&date=[date]
The following search parameters and search parameter combinations SHOULD be supported: SHOULD support searching using the combination of the patient and code and date search parameters:
  • including support for these date comparators: gt,lt,ge,le
  • including optional support for OR search on code (e.g.code={system|}[code],{system|}[code],…)
  • including optional support for AND search on date (e.g.date=[date]&date=[date]]&…) GET [base url]/Observation?patient={Type/}[id]&code={system|}[code]&date=[date]
SHOULD support searching using the combination of the patient and category and status search parameters:
  • including support for OR search on status GET [base url]/Observation?patient={Type/}[id]&category={system|}[code]&status={system|}[code]
The response to any search operation is always a list of resources in a Bundle or an Operation Outcome.

​
Observation Clinical Result By patient and category search parameters

Get Observation Clinical Result by combination of the patient and category search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define observation category code [code] - category of observation (e.g., laboratory, vital-signs) HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Observation Clinical Result By patient and code search parameters

Get Observation Clinical Result by combination of the patient and code search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define observation code (e.g., LOINC) [code] - code identifying what was observed HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Observation Clinical Result By patient, category and date search parameters

Get Observation Clinical Result by combination of the patient, category and date search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define observation category code [code] - category of observation [date] - effective date of observation HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Observation Clinical Result By patient, code and date search parameters

Get Observation Clinical Result by combination of the patient, code and date search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define observation code [code] - code identifying what was observed [date] - effective date of observation HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE:

​
Observation Clinical Result By patient, category and status search parameters

Get Observation Clinical Result by combination of the patient, category and status search parameters. METHOD GET
PARAMS [base url] - FHIR base url [reference] - reference to the Patient {system|} - terminology system used to define observation category/status code [code] - category of observation and status code HEADERS The Authorization token SHALL be obtained during the Authentication and Authorization process. Go to Authentication and Authorization for further details. RESPONSES EXAMPLE: