Pharmacovigilance case intake in brief
Case intake is everything between “a report arrived” and “a verified case is in the safety database”: capturing the report, deciding whether it is a valid ICSR, finding duplicates and preparing the data. It is where reporting clocks start, so the job is speed with no loss of accuracy. AI shortens the reading, sorting and typing; safety professionals keep every decision about validity, seriousness and causality.
When Pharmacovigilance Case Intake is appropriate
Intake is the part of drug safety where volume and deadlines collide. Under EMA’s GVP Module VI, a valid case needs an identifiable reporter, one identifiable patient, a suspected product and a suspected reaction. Serious cases go to EudraVigilance within 15 days and non-serious ones within 90, counted from day zero. In the US, 21 CFR 314.80 requires 15-day Alert reports for serious and unexpected experiences, review of information from any source including the scientific literature, and ten years of record retention.
The workflow suits teams with steady report volume, several intake channels and a quality system that can validate a new tool. It is a poor fit when report volume is tiny or when the expectation is that software will replace safety physicians.
When AI Pharmacovigilance Case Intake is appropriate
AI intake makes sense once most of your cost sits in reading and transcribing free text: MICC call notes, emails, scanned forms, partner line listings and articles. If most reports already arrive as structured E2B files from partners, the gain is smaller and a validated import is the better first step. Expect the largest benefit on multilingual inboxes, literature hits and follow-up reports, where a person otherwise rereads the whole case to find what changed.
Intake channels and what each one needs
| Channel | Typical source | What intake must capture | Where AI helps |
|---|
| MICC calls and chats | Patients, pharmacists, physicians asking about a product | Reporter contact, patient descriptor, product, event, call date and time | Spotting safety content in call notes and pre-filling a case draft |
| Safety email inbox | Healthcare professionals, consumers, sales staff | Original message and attachments with receipt timestamp | Sorting adverse events from complaints and enquiries |
| Company website and web forms | Consumers and professionals reporting directly | Structured fields plus free text, submission timestamp | Reading the free-text box and checking the criteria |
| Literature | Weekly database searches, local journals | Search string, article identifier, awareness date | Screening abstracts and full texts for a product, patient and reaction |
| Partners and licensees | Line listings, E2B files, safety data exchange | Partner case ID, agreement reference, receipt date | Mapping partner fields and finding duplicates with your own cases |
| Patient support programmes | Nurses and coordinators in organised programmes | Programme ID and solicited flag | Flagging events in programme notes for the solicited workflow |
Two channel rules from EMA’s GVP Module VI matter here (verified October 2026). Reports notified through medical enquiry or product information services count as spontaneous reports, so MICC staff need adverse event training and a same-day hand-off. Companies should also screen websites and digital media under their management for possible reports, often enough that valid cases still meet the submission time frames counted from the posting date. Reports from patient support programmes are solicited, not spontaneous, and need their own route.
The four minimum criteria and day zero
Per GVP Module VI, a valid ICSR needs (verified October 2026):
- An identifiable reporter, with qualification and country known for at least one reporter. A report from the internet counts as identifiable if, for example, a valid email address shows a real person exists.
- One identifiable patient, described by at least one qualifier such as initials, age, age group, date of birth or gender.
- At least one suspected medicinal product.
- At least one suspected adverse reaction. A bare outcome, such as “the patient was hospitalised”, needs medical judgement before it counts.
Day zero is the first day anyone in the company, including medical representatives and contractors, has information meeting all four criteria, weekends and public holidays included. For literature, the clock starts on awareness of a publication that contains them. An AI checklist can show which criteria are present and quote the sentence for each, but a processor confirms validity.
Reporting clocks intake has to protect
| Jurisdiction | Report type | Deadline | Source |
|---|
| EU | Serious valid ICSR | 15 days from receipt | GVP Module VI |
| EU | Non-serious valid ICSR | 90 days from receipt | GVP Module VI |
| US | Serious and unexpected adverse drug experience (15-day Alert report) | No later than 15 calendar days from initial receipt | 21 CFR 314.80 |
| US | 15-day Alert follow-up | Within 15 calendar days of new information | 21 CFR 314.80 |
| US | Other postmarketing reports | Periodic: quarterly for three years from approval, then annually | 21 CFR 314.80 |
All rows verified October 2026. EMA states that GVP modules affected by the newly adopted ICH E2D(R1) guideline will be revised, and Module VI Rev 2 is still the current text, so recheck these rules when the revision is published. On the format side, FDA accepted E2B(R2) through 30 September 2026; from 1 October 2026, ICSRs sent through ESG NextGen must use E2B(R3).
Where AI helps and where medical review stays
| Step | AI can do | A qualified person decides |
|---|
| Triage | Label each item as possible adverse event, complaint, enquiry or other | Closing any item as not safety-relevant |
| Translation | Translate alongside the original text | Meaning of clinical terms in context |
| Extraction | Pre-fill reporter, patient, product, dose, dates and event text with citations | Accepting every field |
| Coding support | Suggest MedDRA terms for the reported event | Final coding |
| Validity | Show which minimum criteria are present | Whether the case is valid |
| Seriousness and expectedness | Highlight hospitalisation, death or other criteria mentioned in the text | Seriousness, expectedness, causality |
| Follow-up | Draft a request listing missing information | Sending it and judging the reply |
Cost levers for case intake
- Structure at source. MICC scripts and web forms that ask for the four criteria up front avoid follow-up rounds.
- Fewer touches per case. Cited pre-filled fields mean a processor checks rather than types.
- Duplicates before entry. A duplicate caught at intake costs a comparison; one caught after entry costs a nullification and a resubmission.
- Route by complexity. Non-serious consumer reports with complete data take a short path; serious, pregnancy and paediatric cases go to senior staff.
- Literature screening. Weekly searches are expected under GVP Module VI (verified October 2026), and AI screening cuts the number of full texts a person must read.
- Track the right unit. Measure cost per valid case and late submissions together.
SaaS or on-premises case intake
| Question | SaaS intake | On-premises or private cloud intake |
|---|
| Time to start | Fast; vendor runs the stack | Longer; you run infrastructure and models |
| Where health data sits | Vendor environment, under your contract | Your environment |
| Control of model and prompt changes | Vendor release cycle, which your validation must follow | Your change control |
| Validation effort | Vendor package plus your intended-use testing | Your full validation, with more control over scope |
| Best fit | Smaller safety teams, few markets | Strict data residency, many partners, existing validation capability |
Either way, keep the validated safety database as the system of record and treat the intake layer as a feeder that a person reviews.
Designing the operating workflow
- Capture. Every message and file is logged with its receipt time, because that time can become day zero.
- Triage. The agent labels items as potential adverse events, complaints or enquiries; a person reviews anything closed as not relevant.
- Extract. Case fields are pre-filled, each linked to its source sentence, with foreign-language reports translated alongside the original.
- Validate. The four minimum criteria are checked and gaps become follow-up requests.
- Check duplicates. Candidates are listed for a processor to confirm or reject, following the duplicate management addendum to GVP Module VI.
- Hand over. The processor enters the verified case in the safety database, and qualified staff complete the medical assessment.
Data, integration, and evidence
| Intake step | Agent output | Human decision |
|---|
| Triage | Category with the deciding passage | Close or keep each item |
| Extraction | Cited field values | Accept or correct every field |
| Validity | Missing-criteria checklist | Validity and follow-up |
| Duplicates | Ranked candidate cases | Merge, link or keep separate |
For follow-up reports, a diff of the new and previous versions shows processors exactly what changed. On the submission side, the FDA electronic submissions page states that ICSRs sent through ESG NextGen must use E2B(R3) from 1 October 2026 (verified October 2026). That work stays in the safety database.
How VDF.AI supports this use case
VDF AI Agents run on-premises, in a private cloud or air-gapped, so case documents stay in your environment. Agents can combine catalog tools for OCR, translation and table extraction with PII detection and PII redaction for copies that leave the case record.
VDF holds no GxP or regulatory certification of its own. It is software that runs under your quality system, so validation, access control and SOPs remain yours. The GxP AI validation guide covers how teams scope that validation for a non-critical first workload such as intake.
More healthcare workflows are in the healthcare use cases, including literature review support, regulatory knowledge chat for pharma and coding validation.