> 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/example-1-analysis-of-disability-coverage-of-social-protection-schemes.md). # 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
Sections Description
Actors and EntitiesDR, IBR
Prerequisites
Process InputsThe applicant's UIN is available.
Process Flow Steps

Step 1: 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.

The requested information is transmitted to the IBR using the API.

OutputsThe IBR is updated with further details of beneficiaries with disabilities.
Control PointsN/A
Exception HandlingRefer to /pages/kEyarvXSVpnS9WEl90DQfor alternate flows.
### Diagram 1 - Analysis of Disability Coverage of Social Protection Schemes: PRS.DR.03
--- # 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.03-sp-system-queries-the-dr-to-request-information-needed-for-analysis/example-1-analysis-of-disability-coverage-of-social-protection-schemes.md?ask=&goal= ``` `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.