> For the complete documentation index, see [llms.txt](https://docs.openg2p.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.openg2p.org/products/pbms/_archive/previous-generation/developer-zone/odoo-modules/g2p-program-datashare-rabbitmq.md).

# G2P Program Datashare: RabbitMQ

### Module name

`g2p_program_datashare_rabbitmq`

### Module title

G2P Program Datashare: RabbitMQ

### Technology base

[Odoo](https://www.odoo.com/)

### Functionality

This module extends the core [RabbitMQ DataShare](https://docs.openg2p.org/products/registry/registry/_archive/social-registry/developer-zone/odoo-modules/g2p-registry-datashare-rabbitmq.md) module to support publishing **Beneficiary Registry** data from PBMS (`g2p.program_membership` to external systems via RabbitMQ.

Key enhancements:

* **New Data Source Type**: Introduces a new `data_source` value: `beneficiary_registry`, allowing RabbitMQ configurations specific to PBMS beneficiary data.
* **Program-Specific Configuration**: Introduces a `program_id` field in the RabbitMQ configuration to optionally scope data sharing to a specific program.
* **Automatic Publishing on Change**: Automatically triggers data publishing when a beneficiary is added to a program or when their record is updated.
* **Reuses Core Functionality**: Inherits and utilizes the base module’s RabbitMQ connection and JQ transformation capabilities.

With this module, key beneficiary information—such as program enrollment and participation details—can be streamed in real time to downstream systems for analytics, interoperability, or reporting purposes.

### Source code

[https://github.com/openg2p/openg2p-program](https://github.com/openG2P/openg2p-program)


---

# 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://docs.openg2p.org/products/pbms/_archive/previous-generation/developer-zone/odoo-modules/g2p-program-datashare-rabbitmq.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.
