Adverse Events Workflow
Table of Contents
Background
This document describes the need and scope of adding forms to track adverse events after a dose is administered to a beneficiary within V2.0, explaining the module’s features, specifications, purpose, and functionality. It also provides the descriptive view of the application along with the specification of each element.
While administering the dose to a beneficiary (usually children), there can be instances when the beneficiary shows some symptoms against the dose provided. These adverse events need to be recorded and monitored as it helps to take precautionary measures for further doses as well as in future campaigns for that beneficiary. It is helpful for cases when a beneficiary's situation becomes critical and he/she needs to be referred to a healthcare facility. This is also crucial for resource tracking because in certain campaigns, the beneficiary can be re-administered the dose even after he vomits out the medicine.
Target Audience
This document is intended for the engineering and platform (tech teams), product management, and implementation teams to agree on requirements for the Health Campaign Management (HCM) Platform.
Objectives (of this release)
Recording adverse events.
Enabling actors to record and track the adverse events observed in a beneficiary after administration of the dose.
Monitoring the data to plan and decide for upcoming doses during the campaign.
Assumptions and Validations
Sr. No. | Theme | Assumption |
1 | Triggering adverse events flow. | Adverse events will always be linked to the service delivery. |
Process flow
Specifications
Field | Data type | Data validation | Required (Y/N) | Comments |
Resource administered | Table (Read-only) | This displays the data for resources administered to the beneficiary. | NA |
|
Select the symptoms | Multiple select list | The user must be able to select multiple values from the list. The list must be configurable. | Y |
|
Did you re-administer | Binary (yes/no) |
| Y |
|
Number of times re-administered | Increment/decrement | If user selects yes for re-administer, then this field must be displayed | Y |
|
Design
Find the mock-ups below:
Deliver Intervention
The user needs to provide the delivery details for the resources delivered to the beneficiary. The screen is configurable depending upon the campaign type and the auto-calculated resources and quantity are displayed and populated in the fields. The user can edit the fields if required to change the resource administered.
Adverse Events
When the user clicks ‘Next’ on the deliver intervention screen, it opens a pop-up that asks: “Did you observe any adverse events?” If the user selects ‘No’, the adverse events screen is skipped, and he/she is directly navigated to the next screen in the flow. If the user selects ‘Yes’, it opens the adverse events form to capture the details. On top the summary of delivered resources is displayed in a tabular form. The list of symptoms must be configurable to include more values if required. It is possible that the beneficiary shows multiple symptoms, thus the user must be able to select multiple values from the list.
If the dose is readministered, then the user must select ‘yes’ and provide the number of times it has been readministered.
The “Refer Beneficiary” button navigates the user to the refer beneficiary flow, in case the beneficiary is critical and requires medical assistance. The ‘Next’ button takes the user to the next screen in the flow.
Last updated
