# Reasonable Adjustments - Impairment Categories

**URL:** <https://developer.community.nhs.uk/t/reasonable-adjustments-impairment-categories/778>\
**Category:** Reasonable Adjustment Flag\
**Tags:** fhir\
**Created:** [1 March 2024 10:51 UTC](https://developer.community.nhs.uk/t/reasonable-adjustments-impairment-categories/778 "2024-03-01T10:51:22Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![stuart.ross](https://avatars.discourse-cdn.com/v4/letter/s/0ea827/32.png) [@stuart.ross](https://developer.community.nhs.uk/u/stuart.ross)\
**Post date:** [1 March 2024 10:51 UTC](https://developer.community.nhs.uk/t/reasonable-adjustments-impairment-categories/778/1 "2024-03-01T10:51:22Z")

</div>

Can it be confirmed that suppliers do not need to send a broad impairment category using a value from [FHIR Reference Server Reasonable Adjustments Record Condition Code](https://fhir.nhs.uk/STU3/CodeSystem/RARecord-ConditionCode-1) and can instead send a Snomed code(s) representing the the impairment(s).

Can it be confirmed this is still the source of truth for the national API specification. [RARecord Terminology | FHIR® Reasonable Adjustments API (dev-reasonable-adjust-beta.netlify.app)](https://dev-reasonable-adjust-beta.netlify.app/explore_terminology)

---

<div class="post-metadata">

**Author:** ![clarecooke](https://avatars.discourse-cdn.com/v4/letter/c/f475e1/32.png) [@clarecooke](https://developer.community.nhs.uk/u/clarecooke)\
**Post date:** [5 March 2024 10:18 UTC](https://developer.community.nhs.uk/t/reasonable-adjustments-impairment-categories/778/2 "2024-03-05T10:18:40Z")

</div>

Hi Stuart,  
The FHIR 4 Spec will address your question. We will send you the draft spec of the Read API today and happy to have a quick chat on any initial questions you have on it and to explain timelines for release of the full spec.