Definition
Adverse-event intake
Adverse-event intake is the operational path from a patient mentioning a safety signal to a named person receiving a transcribed, time-stamped report inside the program's reporting window. It is not diagnosis. It is detection, documentation, and routing so pharmacovigilance and clinical teams can act. Every voice, text, and chat path has to do this the same way, or cases leak.
Definition
What adverse-event intake is
An adverse event is any untoward medical occurrence in a patient who received a product, whether or not it is considered related. Intake is the first operational step: notice the signal in a conversation, capture it in the patient's words, and get it to the person who owns the clock.
Hubs, patient support programs, and study sites run this under protocol-specific windows. If outreach is split across a call center, a text vendor, and a chat widget, each path needs the same detection and the same destination. Otherwise the case that started on Friday night never reaches Monday's safety mailbox.
Rivvi detects adverse events on every call, text, and chat, transcribes them, and routes them to the person you name, inside your reporting window, on every program. Consent, HIPAA, and TCPA handling are already in production. Clinical judgment stays with clinicians.
Adverse-event intake, answered
- Is this the same as pharmacovigilance?
- Pharmacovigilance is the discipline that assesses, understands, and prevents adverse effects. Intake is the front door: the conversation that surfaces the signal and the routing that starts the clock. Rivvi does the intake and the handoff. Your safety team owns the case.
- Does Rivvi decide if an event is related to the product?
- No. Rivvi does not diagnose, code causality, or close a safety case. It captures what the patient said, timestamps it, and routes it. Relatedness and seriousness stay with the named clinician or safety reviewer.
- Which conversations are covered?
- Every voice, text, and web-chat path on the program. Adverse-event routing is not an add-on for one campaign. It is on every conversation so a signal that arrives on a refill check-in is treated the same as one that arrives on a pre-screening call.