> 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.md).

# Process

The process pages describe generic use cases on interoperability between an SP system and a DR. The diagram below illustrates where the use cases are situated in the social protection delivery chain.\
The first use case describes how an SP system can query the DR to access information on a person with a disability, or subscribe to the DR to be notified when a disabled person is registered. The second use case describes how an SP system or a registry can query the DR to verify the disability status of an individual during the programme's eligibility process.

<figure><img src="https://1281514908-files.gitbook.io/~/files/v0/b/gitbook-x-prod.appspot.com/o/spaces%2FHJx5WrasM7PDo3FOhIZK%2Fuploads%2FExVWwzpCg56jrLVeoDj8%2FDR-SPMIS%20Processes%20Walkthrough%2012-09-2024.jpg?alt=media&amp;token=ff2d61bc-53bd-47e3-9150-e1db0d30460a" alt=""><figcaption></figcaption></figure>

| List of Process Workflows for this Interface                                                                                                                                                                                                                                                                        |
| ------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- |
| [PRS.DR.01 SP-System queries the DR to request potential beneficiaries for programme enrolment](/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.02: SP-System queries the DR to confirm disability status of potential beneficiaries](/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.03 SP system queries the DR to request information needed for analysis](/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)                                 |

Please refer to the sub-pages in this section for more details of these use cases, as well as examples from common social protection schemes.


---

# 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.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.
