> 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.03-sp-system-queries-the-dr-to-request-information-needed-for-analysis.md).

# PRS.DR.03 SP system queries the DR to request information needed for analysis

This use case example outlines the process by which the SP system can request supplementary data from the DR to enhance the analysis of individuals with disabilities who are beneficiaries of various social protection programmes.

Using the SP systems' search API, the DR can also query the systems for specific details regarding PWDs who are beneficiaries of various programmes. This request may encompass insights into the types of benefits they receive, ensuring that the DR has comprehensive data for conducting analyses. 

Please refer to the sub-page for a detailed description of this use case.

## API Reference

[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)


---

# 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.03-sp-system-queries-the-dr-to-request-information-needed-for-analysis.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.