> 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-social-registry-v1.0.0/social-registry/1.-crvs/1.2-process/prs.sr.03-social-registry-updates-attributes-for-a-batch-of-beneficiaries-in-sp-mis.md).

# PRS.SR.03: Social registry updates attributes for a batch of beneficiaries in SP-MIS

This use case relates to the assess stage of the social protection delivery chain. Its purpose is to update information in the SP-MIS for a batch of beneficiaries when that information changes in the social registry. 

This use case applies when information in the social registry has been updated for beneficiaries already enrolled in one or more social protection schemes. The social registry must notify one or more SP-MISs of these changes. 

In this use case attributes like poverty score, household size, address or phone number may have changed. Additionally, some beneficiaries may have been reported as deceased.

The social registry needs to update the relevant attributes for these beneficiaries in any SP-MIS in which they are enrolled. 

Please refer to the sub-page for descriptions that illustrate this generic use case using examples from common social protection schemes. 

## API Reference 

* [Search API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_search)
* [Notification API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_notify)
* [Transaction Status API](https://api.spdci.org/release/html/social_api_v1.0.0.html#tag/Sync/operation/post_reg_sync_txnstatus)


---

# 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-social-registry-v1.0.0/social-registry/1.-crvs/1.2-process/prs.sr.03-social-registry-updates-attributes-for-a-batch-of-beneficiaries-in-sp-mis.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.