Update a patient

PUT/healthcare/{connection_id}/patient/{id}

Parameters

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
idstring required
ID of the Patient

Payload

idstring
Unique identifier for the patient
created_atdate-time
When the patient record was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atdate-time
When the patient record was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestring
Full name of the patient
first_namestring
Given name of the patient
last_namestring
Family name of the patient
gender enum
Valid values:
"MALE"
"FEMALE"
"OTHER"
"UNKNOWN"
Administrative gender of the patient
birthdatestring
Date of birth (YYYY-MM-DD)
is_deceasedboolean
Whether the patient is deceased
deceased_atdate-time
When the patient died (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
emails array
Email addresses of the patient
telephones array
Phone numbers of the patient
addressobject
Home address of the patient
languagestring
Preferred language code of the patient
identifiers array
Business identifiers (e.g. MRN)
practitioner_idsstring array
The patient's primary care practitioners
is_activeboolean
Whether the patient record is in active use
metadata array

Returns

Response fieldTypeRequiredDescription
idstringNoUnique identifier for the patient
created_atstring (date-time)NoWhen the patient record was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)NoWhen the patient record was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
namestringNoFull name of the patient
first_namestringNoGiven name of the patient
last_namestringNoFamily name of the patient
genderenumNoAdministrative gender of the patient Values: MALE, FEMALE, OTHER, UNKNOWN
birthdatestringNoDate of birth (YYYY-MM-DD)
is_deceasedbooleanNoWhether the patient is deceased
deceased_atstring (date-time)NoWhen the patient died (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
emailsHealthcareEmail[]NoEmail addresses of the patient
emails[].emailstringYes
emails[].typeenumNoValues: WORK, HOME, OTHER
telephonesHealthcareTelephone[]NoPhone numbers of the patient
telephones[].telephonestringYes
telephones[].typeenumNoValues: WORK, HOME, MOBILE, FAX, OTHER
addressobjectNoHome address of the patient
address.address1stringNo
address.address2stringNo
address.citystringNo
address.regionstringNo
address.postal_codestringNo
address.countrystringNo
languagestringNoPreferred language code of the patient
identifiersHealthcareIdentifier[]NoBusiness identifiers (e.g. MRN)
identifiers[].valuestringYesThe identifier value
identifiers[].typeenumNoThe kind of identifier Values: MRN, NPI, SSN, DRIVERS_LICENSE, PASSPORT, INSURANCE, OTHER
identifiers[].systemstringNoThe namespace/system URI that issued the identifier
practitioner_idsstring[]NoThe patient's primary care practitioners
is_activebooleanNoWhether the patient record is in active use
metadataHealthcareMetadata[]No
metadata[].idstringNo
metadata[].valueobjectNo
metadata[].namespacestringNo
metadata[].formatenumNoValues: TEXT, NUMBER, DATE, BOOLEAN, ARRAY, OBJECT
metadata[].extra_dataobjectNo
metadata[].slugstringNo

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: 'PUT',
  url: 'https://api.unified.to/healthcare/5de520f96e439b002043d8dc/patient/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  data: undefined,
  params: {
    fields: '',
    raw: '',
  }
};

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