Example 1 - Disability cash transfer scheme

This process workflow provides an example for 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 for 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 CRVS which in turn notifies SP-MIS. Once informed the status for the person in SP-MIS is updated to be ‘deceased’. Other business rules associated with death of a beneficiary are also followed.

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-MIS in which the beneficiary is enrolled.

The process steps below describe this flow in more detail.

Process Details: SP-MIS updates the IBR when the enrolment status of a beneficiary changes

Sections	Description
Actors and Entities	Applicant, SP-MIS, and IBR.
Prerequisites	Refer to the Assumptionsfor prerequisites
Process Inputs	The applicant's UIN is available
Process Flow Steps	Step 1: SP-MIS makes a subscribe request to the CRVS, requesting for notifications of death events Step 2: CRVS notifies SP-MIS of a death event for a specific person, sending their UIN to SP-MIS SP-MIS records a change of status for the beneficiary in the programme. Provision of benefits is stopped. SP-MIS generates a batch of beneficiaries that have exited from the scheme. Step 3: SP-MIS uses the API to update the IBR for a batch of beneficiaries whose status has change. 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, Date suspended
Outputs	IBR is updated with details of beneficiaries that have exited
Control Points	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 system takes into account the data provided by the CRVS (for deceased), the social registry (for poverty score), IBR (for enrolment status in other programs) 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.
Exception Handling	Refer Exception Handlingfor alternate flows

Sections

Description

Actors and Entities

Applicant, SP-MIS, and IBR.

Prerequisites

Refer to the Assumptionsfor prerequisites

Process Inputs

The applicant's UIN is available

Process Flow Steps

Step 1: SP-MIS makes a subscribe request to the CRVS, requesting for notifications of death events

Step 2: CRVS notifies SP-MIS of a death event for a specific person, sending their UIN to SP-MIS

SP-MIS records a change of status for the beneficiary in the programme. Provision of benefits is stopped.

SP-MIS generates a batch of beneficiaries that have exited from the scheme.

Step 3: SP-MIS uses the API to update the IBR for a batch of beneficiaries whose status has change.

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, Date suspended

Outputs

IBR is updated with details of beneficiaries that have exited

Control Points

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 system takes into account the data provided by the CRVS (for deceased), the social registry (for poverty score), IBR (for enrolment status in other programs) 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.

Exception Handling

Refer Exception Handlingfor alternate flows

Diagram 1 -Disability cash transfer scheme : PRS.IBR.03

Last updated 4 months ago

Sections	Description
Actors and Entities	Applicant, SP-MIS, and IBR.
Prerequisites	Refer to the Assumptionsfor prerequisites
Process Inputs	The applicant's UIN is available
Process Flow Steps	Step 1: SP-MIS makes a subscribe request to the CRVS, requesting for notifications of death events Step 2: CRVS notifies SP-MIS of a death event for a specific person, sending their UIN to SP-MIS SP-MIS records a change of status for the beneficiary in the programme. Provision of benefits is stopped. SP-MIS generates a batch of beneficiaries that have exited from the scheme. Step 3: SP-MIS uses the API to update the IBR for a batch of beneficiaries whose status has change. 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, Date suspended
Outputs	IBR is updated with details of beneficiaries that have exited
Control Points	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 system takes into account the data provided by the CRVS (for deceased), the social registry (for poverty score), IBR (for enrolment status in other programs) 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.
Exception Handling	Refer Exception Handlingfor alternate flows