> For the complete documentation index, see [llms.txt](https://standards.spdci.org/standards/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://standards.spdci.org/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/data-objects/do.dr.04-disabilitydetails.md).

# DO.DR.04 DisabilityDetails

### **DO.DR.04 DisabilityDetails**

This data object contains essential details regarding the nature and extent of a person's impairment/basic functional limitation, intended for use in interoperability scenarios within SP systems. It is there to inform the SP system of the type of accommodation persons may require in accessing social protection schemes, in the absence of specific information on the disability support required, which is not always documented in the DR. It is important to note that this object does not encompass the entirety of the disability information available in the disability registry.

<table><thead><tr><th width="192">Attribute</th><th width="237">Type</th><th width="150">Cardinality</th><th>Description</th></tr></thead><tbody><tr><td>impairment_type</td><td><a data-mention href="/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/code-directory/cd.dr.01-impairmenttype-functional-limitationtype.md">CD.DR.01 ImpairmentType/Functional LimitationType</a></td><td>0...1</td><td>Type of impairment</td></tr><tr><td>impairment_level</td><td><a data-mention href="/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/code-directory/cd.dr.02-impairmentlevel-functional-limitationslevel.md">CD.DR.02 ImpairmentLevel/Functional LimitationsLevel</a></td><td>0...1</td><td>Indicates the  level of impairment</td></tr><tr><td>impairment_cause</td><td><a data-mention href="/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/code-directory/cd.dr.08-impairmentcause-functionallimitationcause.md">CD.DR.08 ImpairmentCause/FunctionalLimitationCause</a></td><td>0...1</td><td>Reason for disability</td></tr><tr><td>age_on_set</td><td><a data-mention href="/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/code-directory/cd.dr.07-disabilityonset.md">CD.DR.07 DisabilityOnSet</a></td><td>0...1</td><td>Age when disability happened</td></tr></tbody></table>

### Example of JSON Data Structure for Disability Details Data Object

```json

{
   "impairment_type": "Physical and movement related functions",
   "impairment_level": "Severe impairment or difficulty",
   "impairment_cause": "Work Accident",
   "age_on_set": "Working age"
}

```

### JSON-LD File on GitHub

{% embed url="<https://github.com/spdci/schemas/blob/main/extensions/dr/v1/DisabilityDetails.jsonld>" fullWidth="false" %}


---

# Agent Instructions
This documentation is published with GitBook. GitBook is the documentation platform designed so that both humans and AI agents can read, navigate, and reason over technical content effectively. Learn more at gitbook.com.

## Querying This Documentation
If you need additional information that is not directly available in this page, you can query the documentation by asking a question.

Perform an HTTP GET request on the following URL with the `ask` and `goal` query parameters:

```
GET https://standards.spdci.org/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/data/data-objects/do.dr.04-disabilitydetails.md?ask=<question>&goal=<user_goal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is what the user is ultimately trying to achieve, the reason they need the answer. Sharing it helps GitBook give you a better, more relevant answer. A goal is most helpful when it describes the outcome the user wants rather than restating the question. For example, with `ask=how do I create an API token`, a goal like `automate deployments from our CI pipeline` lets GitBook tailor the answer to that use case.

The response will contain a direct answer to the question and relevant excerpts and sources from the documentation.

Use this mechanism when the answer is not explicitly present in the current page, you need clarification or additional context, or you want to retrieve related documentation sections.