> For the complete documentation index, see [llms.txt](https://docs.digit.org/llms.txt). Markdown versions of documentation pages are available by appending `.md` to page URLs; this page is available as [Markdown](https://docs.digit.org/health/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/common-functions/tracking-side-effects-for-beneficiaries.md).

# Tracking Side-Effects for Beneficiaries

A distributor can record the side-effects experienced by a beneficiary after consuming the drug. The list of side-effects can be configured based on the specific campaign being conducted.

## Key Features

* Allows administrators to record side-effects for drugs delivered to the beneficiaries after every dose consumed by the beneficiary.
* The distributor can record the side-effects for both direct delivery where all the doses of the drug is administered directly to the beneficiary, as well as for indirect delivery where the beneficiary is provided with all the remaining doses by the distributor at the same time and is asked to administer the drug on their own.&#x20;

## User Roles

<table><thead><tr><th width="140">User Role</th><th width="229">Scope of Action</th><th>Role Description</th></tr></thead><tbody><tr><td>Distributor</td><td><ul><li>Administer drug to the beneficiaries and observe the effect of drug</li><li>Record side effects observed due to administration</li></ul></td><td>The user goes from house-to-house for drug administration and records any side-effects observed in the beneficiary for previous doses of drugs for indirect delivery as well as for current dose during direct delivery.</td></tr></tbody></table>

## **Steps for Recording Side-Effects During Direct Delivery:**

In Step 4 of recording the [Multi-Round Campaign](https://app.gitbook.com/o/-MEQmzNGXk5ajuZujG7E/s/vycOJBMmAsXuxqjuITDy/~/changes/105/products/health-campaign-management/frontline-workers-app/hcm-app-user-manual/multi-round-campaigns) delivery process, based on the response provided by the distributor for the question "Did you provide drugs for the next doses?" the screens for recording the side-effects in a given cycle will be as follows:

**If you replied 'No' (Recording side-effects when the the distributor does direct delivery for all rounds):**&#x20;

**Step 1**

After you have completed the delivery for first dose, you will see the list of beneficiaries who are eligible for the next round of drug delivery. If the beneficiary experienced any side-effect, click on the "Unable to Deliver?" button, where you will get 3 options. Here, the last option will be "Record Side Effects".

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/UaNnEuOcghr8fagIqSUW/image.png" alt="" width="185"><figcaption></figcaption></figure>

**Step 2**

You will be taken to the next screen where you need to record the side-effect experienced by the beneficiary. Once you have selected the relevant side-effect, click on 'Next'.

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/N1FQKA8OTJ0YHExd2etL/image.png" alt="" width="185"><figcaption></figcaption></figure>

You will see a success screen that says, "Data recorded successfully". &#x20;

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/c8ebiOU939gstyUumhUU/image.png" alt="" width="185"><figcaption></figcaption></figure>

**If you replied 'Yes' (Recording side-effects when the the distributor does indirect delivery for subsequent deliveries):**&#x20;

**Step 1**

If you replied 'Yes' the next time you visit the beneficiary and click on "Record Delivery" against that beneficiary in the household details page, you will see the following screens:

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/sFN29xTGgAlVrT9mvwCb/image.png" alt="" width="185"><figcaption><p>These Questions are specific to our SMC Campaign in Mozambique and can be Customised based on the needs and processes set for a specific campaign.</p></figcaption></figure>

**Step 2**

Once you submit the answers, you can record the side-effects for the beneficiary. If no side-effects were reported, select 'No' to move on to the beneficiary details screen, and the delivery status for all cycles will show as 'Completed'.

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/p0rGzmsM0RnDgYr6e60j/image.png" alt="" width="185"><figcaption></figcaption></figure>

**Step 3**

If you select 'Yes', you can record the side effect. Click on 'Next'.&#x20;

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/MXL3bhoYDBUf6RHT46tH/image.png" alt="" width="185"><figcaption></figcaption></figure>

You will see a success screen that says, "Data recorded successfully'. If you select 'No' for side-effects, you will be taken directly to the "Data Recorded Successfully Screen".&#x20;

<figure><img src="https://content.gitbook.com/content/GYQEda2SOh4goA6Ee2d2/blobs/nalDuFW0ljgKoy5Y8wXG/image.png" alt="" width="185"><figcaption></figcaption></figure>

**Note:** If the Distributor answered 'No' on the "Record Past Delivery" page, the delivery status will changed to 'Visited' on the household details page for that specific beneficiary.


---

# 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.digit.org/health/v1.5/hcm-product-suite/health-products/digit-hcm-app/user-manual/common-functions/tracking-side-effects-for-beneficiaries.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.
