Pharmacovigilance case management

Every ICSR on time. Every export valid.

IntelliBase tracks your 15- and 90-day clocks, drafts cases from source documents, and stops invalid E2B(R3) files before they leave your team.

For MAHs and CROsWe set up your workspace

Real IntelliBase screens on a demo workspace. Sample data.

Built around the formats your team already usesICH E2B(R3)MedDRACIOMS IPRR · ROR · χ²
The problem

Safety deadlines shouldn’t live in a spreadsheet

Most teams still stitch case intake, deadlines and exports together by hand. That’s where days disappear.

01

Deadlines depend on memory

Someone has to remember to check the tracker. Sooner or later, someone forgets.

02

Cases get retyped from emails

Reporter emails and literature excerpts turn into hours of copy and paste.

03

Bad files fail too late

An invalid E2B(R3) file shows up at the gateway, not at your desk.

How it works

From first email to valid file, in four steps

One workflow replaces the inbox, the tracker and the export checklist.

1

Receive

Paste a reporter email or literature excerpt. IntelliBase drafts the case fields for you to review.

AI-assisted intake
2

Review

Your team checks every suggestion in a guided editor, codes reactions from the MedDRA release your company has loaded and scores causality.

Reviewer QC step
3

Export

Validate and download E2B(R3) XML, or a CIOMS I form. Invalid files are blocked.

Schema validated
4

Monitor

Watch every clock, get alerts, and run signal analysis on your own case data.

Clock and signals
Product

Everything a safety team needs, built in

Each module does one job well and shares one case record.

Compliance clock

The 15-day and 90-day deadlines start when a case is received. Open cases sort into overdue, due soon and on track, and email alerts go out daily.

2
4
21

Guided case editor

Eight sections, MedDRA coding from your own licensed release and Naranjo causality scoring.

ReporterPatientDrugsReactionsCausality+3 more

AI drafts. People decide.

Every suggested field stays flagged until someone accepts it. Nothing is submitted automatically.

Patient age54 yearsAccepted
ReactionHepatitisSuggested
Suspect drugProduct ASuggested

Signal management

Run PRR, ROR and chi² on your own case data. Track each signal from first flag to closure.

Product / event pairs1 signal flagged

Audit log you can’t edit

Every change records who, what and when. Export the log as CSV for an inspection.

  • Reviewer returned case IB-2026-0142
  • Editor updated Reactions section
  • E2B(R3) export validated and downloaded

Product dictionary

Keep each product’s ingredients, strengths and listed terms with their MedDRA codes in one place, with its RSI version and update date. Disable a product to free its plan slot.

  • 2 ingredients · 14 listed terms
  • Version 3, updated this quarter
  • Registered · enabled

Also included

  • CIOMS I and plain-text case export
  • Follow-up cases chained to the original
  • Global search across cases, products and users
  • In-app notifications and email alerts
  • Audit log export as CSV
  • Invite-only users with role control
Teams

A seat for everyone in the safety process

Editor

Enters and edits cases, and prepares exports.

Reviewer

Returns a case with a note, or moves it forward.

Admin

Manages users, the plan and company settings.

Auditor

Reads cases and the audit log. Can’t change anything.

Reviewer and auditor roles depend on your plan.

Security and audit

Controls you can show an inspector

The system enforces these. Your team doesn’t have to remember them.

Invalid exports are blocked

Every E2B(R3) file is validated against the ICH ICSR schema and business rules. If it fails, you see why and nothing is produced.

Isolation in the database

Row-level security is forced on every tenant table. Another company’s data stays out of reach, even if application code has a bug.

An audit log that stays intact

The database role can’t update or delete audit entries. Signal sign-offs also need the signer’s password.

IntelliBase prepares your E2B(R3) files. You submit them through your regulator’s gateway.
Pricing

Plans sized to your team and case volume

Every plan includes the compliance clock, case editor and audit log. Ask us for pricing.

Growth

For teams starting to centralise safety work
10 users · 50 reports / month
  • Case editor and compliance clock
  • Dashboard and audit log
  • E2B(R3) and CIOMS I export
  • Reviewer QC step
Request pricing
Most popular

Scale

For growing teams with a QC process
20 users · 250 reports / month
  • Everything in Growth
  • AI-assisted case intake
Request pricing

Enterprise

For large teams and complex portfolios
Unlimited users and reports
  • Everything in Scale
  • Signal management (PRR, ROR)
Request pricing
FAQ

Questions safety teams ask us

Does IntelliBase submit cases to regulators?

No. IntelliBase produces validated E2B(R3) files and CIOMS I forms. You submit them through your regulator’s gateway.

Can AI submit a case on its own?

No. AI drafts fields from pasted text and suggests terms. A person reviews and accepts each suggestion, and nothing is submitted automatically.

How do we get access?

Request access and tell us about your team. We set up your workspace and send your admin an invite.

How is our data kept separate from other companies?

Row-level security is forced on every tenant table in the database, and the app connects through a restricted database role.

Put your safety deadlines on autopilot

Tell us about your team. We’ll set up your workspace and send your admin an invite.