Allergy records — allergyIntoleranceType field
Summary
Allergy records in the public GraphQL API can now distinguish allergies from intolerances via the new allergyIntoleranceType field and AllergyIntoleranceType enum.
New on AllergyRecord:
allergyIntoleranceType(AllergyIntoleranceType) —allergyorintolerance.
New on create / update inputs:
CreateAllergyRecordDataInput.allergyIntoleranceType— optional; defaults toallergywhen omitted.UpdateAllergyRecordDataInput.allergyIntoleranceType— optional; update to change the classification.
Existing clients that omit the field continue to work; create still stores allergy by default.
Integration guidance
- Prefer requesting
allergyIntoleranceTypein allergy record selections so responses include the classification. - Treat the enum as forward-compatible: ignore unknown values if your client is strict about parsing.
See also
- API reference:
AllergyRecord - API reference:
createAllergyRecord - API reference:
updateAllergyRecord - API reference:
AllergyIntoleranceType