List all procedures

Updated:

GET/healthcare/{connection_id}/procedure

Returns a list of HealthcareProcedures. Narrow the results with the query parameters before paging, then page through them with `limit` and `offset` (the default and maximum page size depend on the integration). Use `fields` to return only the fields you need and reduce the response size. When the integration supports a total count, it is returned in the `X-Total-Count` response header. Use each item's `id` to retrieve, update, or delete it where those operations are supported.

Parameters

limitnumber default=100
offsetnumber default=0
updated_gtedate-time
Return only results whose updated date is equal or greater to this value (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
sort enum
order enum
querystring
Query string to search. eg. email address or name
patient_idstring
The patient ID to filter by
fieldsstring array
Fields to return
rawstring
Raw parameters to include in the 3rd-party request. Encoded as a URL component. eg. raw parameters: foo=bar&zoo=bar -> raw=foo%3Dbar%26zoo%3Dbar
connection_idstring required
ID of the connection

Returns

idstring
Unique identifier for the procedure
created_atdate-time
When the procedure record was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
When the procedure record was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
patient_idstring
The patient the procedure was performed on
encounter_idstring
The encounter in which the procedure was performed
practitioner_idsstring array
The practitioners who performed the procedure
location_idstring
Where the procedure was performed
condition_idsstring array
Conditions that justified the procedure
namestring
Human-readable name of the procedure
codes array
Codings for the procedure (e.g. CPT, SNOMED CT)
status enum
Valid values:
"PREPARATION"
"IN_PROGRESS"
"NOT_DONE"
"ON_HOLD"
"STOPPED"
Status of the procedure
reasons array
Codings for the reason the procedure was performed
body_sites array
Codings for the anatomical locations of the procedure
start_atdate-time
When the procedure was performed (or started) (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
end_atdate-time
When the procedure ended (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
notesstring
Free-text notes about the procedure
metadata array
Custom field values

Errors

Errors return the HTTP status code and a JSON body with statusCode, error (the short label) and message (a human-readable detail).

{
  "statusCode": 429,
  "error": "Too Many Requests",
  "message": "Too many requests to unified.to API; max requests per minute: N"
}
StatusErrorMeaning
400Bad RequestThe request was malformed or failed validation.
401UnauthorizedThe connection is likely broken; re-authorize it.
403ForbiddenThe connection is missing permissions or scopes.
404Not FoundThe requested resource does not exist.
429Too Many RequestsRate limit exceeded (see the two sources below).
500Internal Server ErrorAn unexpected error occurred.
501Not ImplementedNot supported by this integration.

Errors from the underlying integration pass through: the integration's status comes back as ours (429, 401, 403, 404 or 5xx), usually with its message. When the integration's error body is unclear, Unified extracts what it can and returns a clearer message.

429 Too Many Requests

A 429 has two possible sources:

  • The integration's own rate limit, passed through.
  • Unified's workspace limit: a rolling 60 seconds, set by plan, with the message Too many requests to unified.to API; max requests per minute: N.
const options = {
  method: 'GET',
  url: 'https://api.unified.to/healthcare/5de520f96e439b002043d8dc/procedure',
  headers: {
    authorization: 'bearer .....'
  },
  params: {
    limit: 50,
    offset: 0,
    updated_gte: '2026-10-24T20:38:16.397Z',
    sort: 'updated_at',
    order: 'asc',
    query: '',
    patient_id: '',
    fields: '',
    raw: '',
  }
};

const results = await axios.request(options);
Are we missing anything? Let us know
Was this page helpful?