> 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/1.2-process/prs.dr.02-sp-system-queries-the-dr-to-confirm-disability-status-of-potential-beneficiaries.md).

# PRS.DR.02: SP-System queries the DR to confirm disability status of potential beneficiaries

This use case relates to the enroll stage of the [social protection delivery chain](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/1.2-process.md). Its purpose is for the DR to verify the disability status of a potential beneficiary before enrolment into social protection programmes. In this case, the SP system needs to query the DR to verify their current disability status.   

The request to share the disability status will be initiated by the SP system (possibly alongside requests to other registries) to verify eligibility. This could be a request for an individual member, or a bulk request for a batch of potential beneficiaries. 

For data minimisation purposes, the use case can only request confirmation of whether or not a person is disabled. The DR will return a 'yes' or 'no' response. If the SP system needs to verify other criteria for the programme, then additional requests can be made to obtain details on the disability. 

Please refer to the sub-pages for descriptions that illustrate this generic use case using examples from common social protection schemes. 

## API Reference 

* [API.DR.06 SYN Get Disability Status](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.06-syn-get-disability-status.md)


---

# 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 dynamically by asking a question.

Perform an HTTP GET request on the current page URL with the `ask` query parameter, and the optional `goal` query parameter:

```
GET https://standards.spdci.org/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/1.2-process/prs.dr.02-sp-system-queries-the-dr-to-confirm-disability-status-of-potential-beneficiaries.md?ask=<question>&goal=<endgoal>
```

`ask` is the immediate question: it should be specific, self-contained, and written in natural language.
`goal` is optional and describes the broader end goal you are ultimately trying to accomplish on behalf of the user. GitBook uses it to tailor the answer towards what is most useful for that goal.

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.