> 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.02-sp-mis-updates-attributes-for-a-batch-of-beneficiaries-in-the-social-registry.md).

# PRS.SR.02: SP-MIS updates attributes for a batch of beneficiaries in the social registry

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

This use case applies when a scheme determines that information on a beneficiary has changed and updates this in the SP-MIS. The updated information may be the beneficiaries address or contact information. 

In this case the information on the social registry is now out of date. To avoid this, the SP-MIS uses the API to send a batch of data with information on which beneficiary attributes have changed. This ensures that the social registry receives the updated information. It can now determine if the record it holds should be updated. It may then, in turn, notify other systems and registries of the change. 

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