Server-side APIEndpointsPatients

Vitals

Every recorded set of vitals for a patient, newest first, with units.

A patient's vital readings at this clinic, newest first.

API-key only, gated on devapi_patients_vitals. Responses carry Cache-Control: no-store.

A list, not a page

A vitals series is read whole to be plotted, so this returns a bare JSON array rather than the paged envelope. Bound it with limit; there are no page or size parameters.

Parameters

Path parameters

patientIdintegerrequiredExample: 4821

The Medos patient id, from GET /v1/patients.

Query parameters

limitintegermin: 1max: 500Default: 100

How many readings to return, newest first.

Headers

x-api-keystringrequiredExample: mk_…

Your Developer API key. Server-side only.

X-Acting-User-IdstringExample: MDU_A1B2C3D4E5F6

The staff member the call is attributed to, as an MDU_… id. Omit it to attribute the call to the workspace admin.

Responses

  • Units travel beside their values and are not normalised. Clinics record in the units they use, and converting here would invent precision the record does not have. Read weight together with weightUnit.
  • bpSystolic / bpDiastolic are the parsed pair. Read those rather than any free-text blood-pressure value.
  • Several measurements arrive as strings (heartRate, temperature, weight, …) because Medos stores them as entered.

A patient with no readings is 200 with []. To add a reading, see Record vitals.

Test request