Server-side APIEndpointsPatients

Medical history

Allergies, chronic conditions and surgical history for one patient.

The patient's standing clinical background at this clinic, as one object.

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

Parameters

Path parameters

patientIdintegerrequiredExample: 4821

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

Query parameters

addressIdintegerExample: 1

Read this location's record. Omit it for the clinic's first record for the patient.

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.

addressId is optional. Medos keeps one medical-history record per location. Pass the location's id to read that record, the same one Replace medical history writes for that addressId. Without it you get the clinic's first record for the patient, which for a single-location clinic is the only one. Any other query parameter is a 400.

Responses

The three lists are always arrays, never null, so you can iterate them without a guard. Nothing recorded and a clinic holding no history for the patient give the same answer, empty arrays. Medos makes no distinction between the two either.

To write it, see Replace medical history.

Test request