> 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.01-sp-system-queries-the-dr-to-request-potential-beneficiaries-for-programme-enrolment.md).

# PRS.DR.01 SP-System queries the DR to request potential beneficiaries for programme enrolment

This use case relates to the assess stage of the social protection delivery chain. Its purpose is to provide information that the SP system needs for enrolling potential beneficiaries in social protection programmes. It applies in cases where eligibility for a social protection programme is dependent on the potential beneficiary with a disability. 

This use case applies in cases where the SP system proactively requests a list of potential beneficiaries from the DR who meet specific eligibility criteria to initiate enrolment in a programme. Or it may be reactive where a potential beneficiary requests enrolment in the scheme, prompting the SP system to query the DR to retrieve additional information on the potential beneficiary or their household/family to verify their eligibility. 

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

## API Reference 

* [API.DR.01 ASY Search (Async approach)](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.01-asy-search-async-approach.md)
* [API.DR.01 SYN Search (Sync approach)](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.01-syn-search-sync-approach.md)
* [API.DR.02 Event Subscription](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.02-event-subscription.md)
* [API.DR.04 SYN Status (Sync approach)](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.04-syn-status-sync-approach.md)
* [API.DR.05 SYN Get Disability details](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.05-syn-get-disability-details.md)
* [API.DR.07 SYN Get Disability Support](/standards/dci-standards/wip-disability-registry/disability-registry-and-sp-systems-interface/1.-crvs/api/methods/api.dr.07-syn-get-disability-support.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 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/1.2-process/prs.dr.01-sp-system-queries-the-dr-to-request-potential-beneficiaries-for-programme-enrolment.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.