The eRx Service is currently in beta.
Allergen Search
Allergen search allows you to search for allergens by name. Searching for allergens is an essential part of protecting patients from allergic and adverse reactions. In this guide, we'll cover the basic functionality of allergen search as well as a recommended approach to using allergen search with the rest of the eRx service.
Access Policy
To search for allergens, your user needs to have the following access policy:
{
"rule": [
{
"action": "eRx:SearchAllergen",
"resource": "eRx:Allergen",
},
],
}
Code Examples
Here is an example of how to search for allergens:
import Oystehr from '@oystehr/sdk';
const oystehr = new Oystehr({
accessToken: "<your_access_token>",
});
const { allergens } = await oystehr.erx.searchAllergens({ name: 'lisinopril' });
Example 200 response body:
[
{
"id": 2501,
"name": "Lisinopril",
"type": "ScreenableIngredient",
"category": "CommonAllergens"
},
{
"id": 1508214,
"name": "FD&C Blue #2 Al Lake/HCTZ/Lisinopril",
"type": "ScreenableIngredient",
"category": "UncommonAllergens"
},
{
"id": 47964,
"name": "THSC Lisinopril Oral Tablet",
"type": "RoutedDoseFormDrugs",
"category": "OtherBrandDrugs"
}
]
Using Allergen Search with the eRx Service
To receive allergy alerts, you'll need to have explicitly synced that allergy for a given patient. So, the expected workflow for adding a new patient allergy looks like this:
- Search for an allergen
- From the search results, choose the identifier of the correct allergen
- Create an AllergyIntolerance (opens in a new tab) FHIR resource for this patient. For a code sample of how to create this resource, see the patient sync documentation.
- Sync the patient
Once these steps are completed, the eRx service will be aware of the patient's allergy. The ePrescribing interface will flag allergy interactions and you'll be able to check for interactions explicitly using the interactions endpoints in the eRx Service (opens in a new tab).