Adverse event monitoring in health preference surveys
In studies conducted in the context of a drug development programme, adverse events disclosed by patients during the survey may trigger regulatory reporting obligations.
This article explains adverse event monitoring for health preference DCEs, how to set up real-time alerts in SurveyEngine, and how to manage the pharmacovigilance workflow.
Knowledge Base -> Data Quality -> Health
Ben White, 07.07.2026
What triggers adverse event reporting?
When a patient participating in a health preference study discloses a new or worsening symptom that could be related to a treatment under study, this may constitute an adverse event (AE) under the sponsor's pharmacovigilance procedures. In studies conducted in the context of an IND or post-marketing commitment, AE reporting timelines are strictly regulated - serious adverse events may need to be reported to the FDA within 15 days.
The challenge is that health preference surveys are not designed as safety studies and are not conducted under the same frameworks as clinical trials. Patients may disclose AEs incidentally - in an open-ended text field, in response to a question about current symptoms, or as an explanation for a preference choice. The sponsor's medical team needs to review these disclosures and determine whether they trigger reporting obligations.
Why monitoring matters even in preference studies
Even though health preference studies are not designed as safety studies, patient disclosures during the survey can constitute knowledge of an adverse event for the sponsor under ICH E2D and 21 CFR Part 312. 'Spontaneous reports' - unsolicited patient disclosures - are subject to the same reporting timelines as solicited safety reports in some regulatory frameworks.
The safest approach is to assume that any patient disclosure of a new or worsening symptom requires medical review. SurveyEngine's real-time notification system allows the sponsor's pharmacovigilance team to review disclosures as they occur, rather than discovering them at the end of fieldwork.
In practice, the large majority of patient disclosures in preference studies do not trigger formal AE reports. But the review process must be in place and documented.
Setting up AE monitoring in SurveyEngine
Step 1: Define the AE trigger question. Add a specific question to the survey asking whether the patient has experienced any new or worsening symptoms since starting their current treatment. Provide response options (yes/no) and an optional free-text field for description.
Step 2: Configure real-time alerts. In SurveyEngine's notification settings, configure an email or SMS alert to the pharmacovigilance team whenever a patient answers 'yes' to the AE trigger question. The alert should include the anonymised patient study ID and the free-text response.
Step 3: Establish the review workflow. Define who reviews alerts (typically the medical monitor or pharmacovigilance officer), the review timeline (typically within 24 hours), and the criteria for escalating to a formal AE report.
Step 4: Document the monitoring process in the study protocol. The AE monitoring process must be described in the study protocol and, where required, in the ethics application and regulatory submission.
Step 5: Report monitoring outcomes in the study report. Document the number of AE trigger responses received, the number reviewed, and the number that resulted in formal AE reports. This demonstrates due diligence to regulators.
Worked example - post-marketing preference study AE monitoring
A post-marketing patient preference study for a rheumatology treatment includes an AE trigger question. Over 6 weeks of fieldwork with 300 patients, 23 respond 'yes' to the trigger question. Medical review of the 23 free-text responses identifies: 18 as existing documented symptoms not requiring reporting; 3 as new symptoms requiring further information; and 2 as potential serious adverse events requiring expedited reporting within 15 days.
The two expedited AE reports are filed within 10 days of the patient disclosure. The monitoring process, alert system, and review workflow are documented in the final study report submitted to the regulatory authority.
References
Conducting a patient preference study in a regulatory context? Contact SurveyEngine to discuss adverse event monitoring setup.
Or Contact us at support@surveyengine.com — we're glad to help.