Fetching Observations for a Patient

Observations are entities that map to multiple different resources for a patient

Get v2 observations for a patient

get
Path parameters
patientIdForObservationstringRequiredPattern: [^\/#\?]+?
Query parameters
observationCodeNamestring[]Optional
observationGroupNamestring[]Optional
draftbooleanOptional
sourceTypestringOptional
sourceIdnumberOptional
observationCodeIdnumber[]Optional
observationGroupIdnumber[]Optional
organizationIdnumberOptional
startDateone ofOptional
string · dateOptional
or
string · date-timeOptional
patientIdstringOptional
isWearablebooleanOptional
personIdnumberOptional
endDateone ofOptional
string · dateOptional
or
string · date-timeOptional
skipnumberOptional
limitnumberOptional
sortstringOptional
Responses
200Success
application/json
get
/patients/{patientIdForObservation}/observations/v2
200Success

FHIR Resources Observations Map to

The FHIR (Fast Healthcare Interoperability Resources) standard defines a set of modular, extensible resources for exchanging healthcare information. Key FHIR resources involved in clinical documentation and analytics include:

Data Type
Corresponding Resource
Purpose/Description

Diagnoses (ICD-10)

Condition, Observation

Identifies patient conditions, chronic diseases, and diagnoses.

Procedures (CPT)

Procedure, Observation

Describes clinical services performed, office visits, surgeries, and other interventions.

Lab Tests (Regular Observations)

Observation

Diagnostic tests such as blood tests, urinalysis, imaging results, and other measurable clinical data.

Vital Signs

Observation

Common physiological measurements including blood pressure, heart rate, respiratory rate, temperature.

Diagnostic Measurements

Observation

Specialized clinical measurements such as imaging-derived results or pulmonary function test values.

Wearable/RPM Data

Observation

Patient-generated health data from wearables or home monitoring devices (e.g., steps, glucose, BP).

Social Determinants of Health (SDOH)

Observation

Quantified SDOH data like smoking status, BMI (39156-5), or nutrition indicators, often stored as observations.

Through these mappings, our single unified construct represents a wide variety of patient data, enabling interoperability and analytics across clinical, administrative, and patient-generated data sources.

While conditions and procedures have dedicated FHIR resources (Condition and Procedure), they may also appear as coded Observations for simplicity or workflow reasons in certain implementations. if needed, please reach out to the team for more information on dedicated Condition and Procedure endpoints

Examples

Get Patient Observations ICD Codes

GET /api/patients/:patientId/observations/v2

This example outlines how one can fetch ICD codes that are part of a patient profile

Headers

Name
Value

organization_code

{{ organization_code }}

api_key

{{ api_key }}

Query Params

Name
Value
Description

sort

desc

asc , desc

limit

1

isWearable

false

startDate

2024-12-16

Date

endDate

2024-12-18

Date

observationCodeName

Type2DiabetesMellitusWithoutComplications

Code for the Data we are fetching

observationGroupName

Diagnoses

Path Variables

Value
Description

patientid

4089-b05f-6cd81c869749

FHIR resource id for the externalid

Response

Get Patient Observations CPT codes

GET /api/patients/:patientId/observations/v2

Fetching Procedure Codes for a Patient

Headers

Name
Value

organization_code

{{ organization_code }}

api_key

{{ api_key }}

Query Params

Name
Value
Description

sort

desc

asc , desc

limit

1

isWearable

false

startDate

2024-12-16

Date

endDate

2024-12-18

Date

observationCodeName

Office/outpatientVisitEstablished

Code for the Data we are fetching

observationGroupName

Procedures

Path Variables

Value
Description

patientid

4089-b05f-6cd81c869749

FHIR resource id for the externalid

Response

Last updated