# Example 1:  Analysis of Disability Coverage of Social Protection Schemes

This process workflow provides an example of a generic use case for [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). The example used is when data in the IBR is used to analyse coverage across multiple schemes, but some data required is missing

In this example the analysis focuses on the extent to which people with disabilities are enrolled in the different social protection schemes that are included in the IBR. However, the IBR may include only a flag to specify if a person's disability type, disability status, or disability.

Sensitive information held in the DR is deliberately excluded when the DR shares data with the IBR to minimise the transmission of sensitive personal data. 

To do so, the IBR uses an API to transmit the UIN of the person with the disability to request further information on their disability.

The process steps below describe this flow in more detail. 

#### Process Flow: IBR Queries the Social Registry to Request Information Needed for Analysis

<table><thead><tr><th width="223.5">Sections </th><th>Description</th></tr></thead><tbody><tr><td>Actors and Entities</td><td>DR,  IBR</td></tr><tr><td>Prerequisites</td><td><ul><li>Refer to the <a data-mention href="/pages/iXkpFvYe8BQ5wRGhbMBq">/pages/iXkpFvYe8BQ5wRGhbMBq</a>for prerequisites.</li><li>Appropriate consent has been provided to share this personal information.</li></ul></td></tr><tr><td>Process Inputs</td><td>The applicant's UIN is available.</td></tr><tr><td>Process Flow Steps</td><td><p><strong>Step 1</strong>: The IBR makes a batch search request to the disability registry.  It uses the UIN of beneficiaries, for which the attribute is_disabled has the value 'Disabled'.  For matching beneficiaries it requests their disability_identifier, disability_type, functional_limitation_type and functional_severity.</p><p></p><p>The requested information is transmitted to the IBR using the API.</p><p></p></td></tr><tr><td>Outputs</td><td>The IBR is updated with further details of beneficiaries with disabilities.</td></tr><tr><td>Control Points</td><td>N/A</td></tr><tr><td>Exception Handling</td><td>Refer to <a data-mention href="/pages/kEyarvXSVpnS9WEl90DQ">/pages/kEyarvXSVpnS9WEl90DQ</a>for alternate flows.</td></tr></tbody></table>

### Diagram 1 - Analysis of Disability Coverage of Social Protection Schemes: PRS.DR.03

<figure><img src="/files/GsHvBHBbOzHlx4hO6BD3" alt=""><figcaption></figcaption></figure>


---

# Agent Instructions: 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:

```
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/example-1-analysis-of-disability-coverage-of-social-protection-schemes.md?ask=<question>
```

The question should be specific, self-contained, and written in natural language.
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.