Retrieve an allergy

GET/healthcare/{connection_id}/allergy/{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 Allergy

Returns

Response fieldTypeRequiredDescription
idstringNoUnique identifier for the allergy/intolerance
created_atstring (date-time)NoWhen the allergy record was created (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
updated_atstring (date-time)NoWhen the allergy record was last updated (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
patient_idstringNoThe patient who has the allergy
encounter_idstringNoThe encounter in which the allergy was recorded
practitioner_idstringNoThe practitioner who recorded or asserted the allergy
namestringNoHuman-readable name of the substance
codesHealthcareCode[]NoCodings for the substance (e.g. RxNorm, SNOMED CT)
codes[].systemstringNoThe code system URI (e.g. http://loinc.org, http://snomed.info/sct)
codes[].codestringNoThe code within the system
codes[].displaystringNoHuman-readable display text for the code
statusenumNoClinical status of the allergy Values: ACTIVE, INACTIVE, RESOLVED, OTHER
typeenumNoCategory of the substance Values: FOOD, MEDICATION, ENVIRONMENT, BIOLOGIC, OTHER
criticalityenumNoPotential severity of future reactions Values: LOW, HIGH, UNABLE_TO_ASSESS, OTHER
reactionsHealthcareCode[]NoCodings for observed reaction manifestations (e.g. hives, anaphylaxis)
reactions[].systemstringNoThe code system URI (e.g. http://loinc.org, http://snomed.info/sct)
reactions[].codestringNoThe code within the system
reactions[].displaystringNoHuman-readable display text for the code
onset_atstring (date-time)NoWhen the allergy was first identified (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
recorded_atstring (date-time)NoWhen the allergy was recorded (ISO-8601 / YYYY-MM-DDTHH:MM:SSZ format)
notesstringNoFree-text notes about the allergy
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: 'GET',
  url: 'https://api.unified.to/healthcare/5de520f96e439b002043d8dc/allergy/5de520f96e439b002043d8d8',
  headers: {
    authorization: 'bearer .....'
  },
  params: {
    fields: '',
    raw: '',
  }
};

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