> 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-integrated-beneficiary-registry-v1.0.0/ibr/1.-crvs/1.2-process/prs.ibr.03-sp-mis-updates-the-ibr-when-the-enrolment-status-of-a-beneficiary-or-household-changes/example-1-disability-cash-transfer-scheme.md).

# Example 1: Disability Cash Transfer Scheme

This process workflow provides an example of a generic use case PRS.IBR.03 (SP-MIS updates the IBR when the enrolment status of a beneficiary or household changes). The example used is a scheme that provides cash transfer benefits to people with disabilities.  

In this example, a person enrolled in the scheme has died. Their death is recorded in the CRVS, which in turn notifies the SP-MIS. Once informed, the person's status in the SP-MIS is updated to ‘deceased’. Other business rules associated with the death of a beneficiary are also followed. 

The SP-MIS then uses the API to transmit the UIN of the person, the scheme identifier and the new status to the IBR. The IBR responds with a confirmation. 

This ensures that the IBR has the latest status for the beneficiary. It can, in turn, alert other SP-MISs in which the beneficiary is enrolled. 

The process steps below describe this flow in more detail. 

#### Process Flow: SP-MIS Updates the IBR when the Enrolment Status of a Beneficiary Changes

<table><thead><tr><th width="223.5">Sections </th><th>Description</th></tr></thead><tbody><tr><td>Actors and Entities</td><td>Applicant, SP-MIS, 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></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 SP-MIS makes a subscribe request to the CRVS, requesting notifications of death events.</p><p></p><p><strong>Step 2</strong>: The CRVS notifies the SP-MIS of a death event for a specific person, sending their UIN to the SP-MIS.</p><p></p><p>The SP-MIS records a change of status for the beneficiary in the programme. Provision of benefits is stopped.</p><p></p><p>The SP-MIS generates a batch of beneficiaries who have exited from the scheme. </p><p></p><p><strong>Step 3</strong>: The SP-MIS uses the API to update the IBR for a batch of beneficiaries whose status has change.</p><p></p><p>The following information is transmitted to the IBR using the API: UIN, household ID, programme name, programme ID, benefit type, date last benefit received, enrolment status, and date suspended.</p><p></p></td></tr><tr><td>Outputs</td><td>The IBR is updated with the details of beneficiaries who have exited the programme.</td></tr><tr><td>Control Points</td><td>The decision to update the status of a beneficiary lies with the SP-MIS, based on the information received from the CRVS and/or other sources. The SP-MIS takes into account the data provided by the CRVS (for deceased), social registry (for poverty score), IBR (for enrolment status in other programmes) and other sources. It applies its own criteria and guidelines to determine the eligibility of the beneficiary for continued enrolment. This ensures that the exit process is carried out accurately and in accordance with the established protocols and requirements set by the SP-MIS.</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 - Disability Cash Transfer Scheme: PRS.IBR.03

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


---

# 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-integrated-beneficiary-registry-v1.0.0/ibr/1.-crvs/1.2-process/prs.ibr.03-sp-mis-updates-the-ibr-when-the-enrolment-status-of-a-beneficiary-or-household-changes/example-1-disability-cash-transfer-scheme.md?ask=<question>&goal=<endgoal>
```

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