Look up a patient
SIIPS's record of the patient with that document number, and, when history asks for it, the patient's agenda (each appointment with the reference visoft.appointments.cancel takes) and admissions. found:false is an answer, not a failure. The record is cached for five minutes (refresh reads SIIPS again); the agenda is read for every call.
- Scopes: any one of
visoft:appointments:read,visoft:appointments:write - Credentials: an API key, a client-credentials token or a person's access token
- Effect: read-only; safe to retry
- Limits: request body up to 64 KB, response up to 1 MB
- CLI:
arbol visoft patients lookup· MCP tool:visoft_patients_lookup
POST
https://api.getarbol.com/v1/visoft/patients/lookupAuthorization
Request body JSON required
Returns
200
Successful operation.
400
INVALID_INPUT: The request does not match the published schema.
401
UNAUTHORIZED: A valid access token is required.
403
FORBIDDEN: The token does not authorize this operation.
404
CONNECTION_NOT_FOUND: The organization has no such connection.
409
CONNECTION_NOT_CONFIGURED: The organization has no active Visoft connection for this call; an administrator connects Visoft in Account.
413
REQUEST_TOO_LARGE: The request exceeds the allowed size.
415
UNSUPPORTED_MEDIA_TYPE: The request content type is not supported.
422
CREDENTIALS_REJECTED: The organization's connection to this integration couldn't complete the request. Don't retry it automatically; if it keeps happening, contact your Arbol team.
429
RATE_LIMITED: The request rate limit was exceeded. Try again later.
500
INTERNAL_ERROR: The service could not complete the operation.
502
OUTCOME_UNKNOWN: The operation may have been applied; check its result before repeating it.PROVIDER_UNAVAILABLE: The clinical system did not answer or could not complete the request.