Merakee BI Analytics Ltd.

Dedicated pharmacovigilance consulting — safety systems, analytics, dashboards, data migration and extraction, and AI development for drug safety teams.

This page needs JavaScript to display in full. Everything you need to reach us is here:

Email info@merakeebi.com

Phone +1 647 854 1079

Office 600 Matheson Blvd W, Unit 5, Mississauga, ON L5R 4C1, Canada

Home · Analytics · Dashboards · Safety Consulting · Data Migration · Data Extraction · AI Development · Contact

AI DEVELOPMENT

Agentic AI for drug safety, documented for validation.

Most PV teams don’t need another AI platform. They need someone who knows both the safety database and the model — and can put the two together with the evidence trail an inspection calls for. That’s what we build.

WHERE THE HUMAN STAYS
Intake & duplicate check
automated
Coding & narrative draft
automated, cited
Medical judgment
always human — never automated
Submission & audit trail
every step logged
Film in productionThe minute-long version of this page is being made. It will play here.
WHERE AUTOMATION STOPS

A minute on what we automate — and where we deliberately stop.

The same argument this page makes, in sixty seconds: the work that should be automated, the judgment that should not, and the evidence that has to exist either way.

WHY NOW
up to ⅔
of internal PV resources can go to case processing alone
73%
of 250 pharma executives surveyed were planning, piloting or deploying agentic AI
48.7%
less coding time in a peer-reviewed evaluation of AI-assisted MedDRA coding
Industry figures, not Merakee client results. Case processing: Schmider et al., Clin Pharmacol Ther 2019;105:954–61, citing the Navitas PVNET Benchmark Survey 2016 — an upper bound on internal resource use, not an average. Agentic AI: MIT Technology Review Insights, Transforming Commercial Pharma with Agentic AI, October 2025 — custom research commissioned by Globant; 250 executives across nine countries, fielded May–July 2025. MedDRA coding: Yan et al., Ther Innov Regul Sci 2026;60:1059–67 — 2,712 adverse-event terms from a single Phase II oncology trial; the paper reports a 48.7% reduction in average coding time with 95.8% term coverage, at about 70% precision against a manual gold standard. One system on one dataset, not an industry benchmark.
TWO WAYS IN

Decide what to build, or build what you have decided.

Some teams arrive with a shortlist and need it built. Others need to work out what is worth building at all. Both are engagements we take.

BEFORE YOU BUILD
Digital transformation
AI strategy and roadmap
Where AI actually pays, and where it does notData governance and securityUse cases with a business case attachedTarget architecture
System assessment and selection
Bespoke build
ONCE YOU KNOW
Applied solutions
Aggregate and periodic reportsNarrative draftingLiterature screeningMedical assessment supportMedical information handlingLocal health-authority formatsWorkflow automationReal-world data and evidence
ACROSS THE CASE LIFECYCLE

Every one of these proposes. A person disposes.

Automation here is drafting, matching and routing — the parts of a case that are mechanical once the rules are written down. Each output arrives with its rationale and its source record, and waits for someone to accept it.

01Intake
Getting the case in, cleanly and once.
Safety mailbox triageAdverse event recognitionDuplicate detectionStructured intake formsFree-text and scanned formsMedical information intakeEDC reconciliationLiterature intakeHealth-authority and partner sourcesRedaction of personal dataSource document attachment
02Case processing
Drafting and pre-populating, never deciding.
Prioritisation and assignmentCase field pre-populationSeriousness proposalListedness against the reference documentCausality proposalFollow-up query draftingNarrative draftingIn-line and batch quality checksSubmission preparationWorkflow routing
03Compliance and reporting
Evidence that assembles itself.
Aggregate report authoringCompliance and CAPA trackingWorkflow oversightSubmission timeliness monitoringAudit and inspection packsReconciliation reporting
THE ONE WE WILL NOT BUILD
Medical judgment stays with your physicians.

Seriousness, expectedness and causality are assessments a person signs. A model can assemble the evidence for them, show its reasoning and flag what looks unusual — and that is where it stops. We have removed an automated flag from a client’s system for exactly this reason, and we would do it again.

VALIDATED BY DESIGN

The AI is the easy part. The evidence is the job.

We came to AI through computer system validation, not the other way around. Every model we deploy arrives with the same documentation trail we’d hand an auditor for an Argus upgrade — because sooner or later, someone will ask for it.

Talk through your validation approach
GxP validation evidence
IQ/OQ/PQ, traceability matrix, and executed test scripts for every model we put into your environment.
Explainable by default
Every output carries its rationale and source record. Black-box classifications are not fit for regulatory use.
Human in the loop
AI drafts, your reviewers decide. Causality and seriousness assessments stay with qualified people.
Aligned to the frameworks
CIOMS WG XIV, GVP Module IX, ICH E2B(R3), and EU AI Act expectations built into the design, not bolted on after.
HOW A BUILD RUNS

The same controls as any other change.

AI in a safety process is still a change to a regulated workflow. It is specified, tested and evidenced the way anything else touching case data would be.

Step 01
Find the task
A specific, repetitive step — not a department.
Step 02
Define the boundary
What it may decide, and what a human keeps.
Step 03
Build it
Against your data, on infrastructure you control.
Step 04
Test it against known cases
Measured on work whose answer is already known.
Step 05
Evidence and hand over
Specification, test records and the decision log.
WHERE IT RUNS

On infrastructure you control.

Safety data does not leave your environment to be processed by someone else’s service.

WHERE IT RUNSYour cloud tenantOn-premisePrivate networkNo case data to third-party services
WHAT IT TOUCHESSafety databaseDocuments and attachmentsLiterature sourcesReporting layers
WHAT COMES WITH ITSpecificationTest recordsDecision logChange control

Curious what AI could actually take off your plate?

We will walk your workflows with you and say plainly which ones are worth automating — and which are not.

Book an AI readiness review
Merakee BI — Dedicated PV Consulting

Dedicated PV consulting for safety systems, analytics, dashboards, migration and AI development.

CONTACT
600 Matheson Blvd W Unit 5, Mississauga, ON L5R 4C1, Canada
© 2020–2026 Merakee BI Analytics Ltd.
Mississauga, Ontario, Canada
AI DEVELOPMENT

Agentic AI for drug safety, documented for validation.

Most PV teams don’t need another AI platform. They need someone who knows both the safety database and the model — and can put the two together with the evidence trail an inspection calls for. That’s what we build.

WHERE THE HUMAN STAYS
Intake & duplicate check
automated
Coding & narrative draft
automated, cited
Medical judgment
always human — never automated
Submission & audit trail
every step logged
Film in productionThe minute-long version of this page is being made. It will play here.
WHERE AUTOMATION STOPS

A minute on what we automate — and where we deliberately stop.

The same argument this page makes, in sixty seconds: the work that should be automated, the judgment that should not, and the evidence that has to exist either way.

WHY NOW
up to ⅔
of internal PV resources can go to case processing alone
73%
of 250 pharma executives surveyed were planning, piloting or deploying agentic AI
48.7%
less coding time in a peer-reviewed evaluation of AI-assisted MedDRA coding
Industry figures, not Merakee client results. Case processing: Schmider et al., Clin Pharmacol Ther 2019;105:954–61, citing the Navitas PVNET Benchmark Survey 2016 — an upper bound on internal resource use, not an average. Agentic AI: MIT Technology Review Insights, Transforming Commercial Pharma with Agentic AI, October 2025 — custom research commissioned by Globant; 250 executives across nine countries, fielded May–July 2025. MedDRA coding: Yan et al., Ther Innov Regul Sci 2026;60:1059–67 — 2,712 adverse-event terms from a single Phase II oncology trial; the paper reports a 48.7% reduction in average coding time with 95.8% term coverage, at about 70% precision against a manual gold standard. One system on one dataset, not an industry benchmark.
TWO WAYS IN

Decide what to build, or build what you have decided.

Some teams arrive with a shortlist and need it built. Others need to work out what is worth building at all. Both are engagements we take.

BEFORE YOU BUILD
Digital transformation
AI strategy and roadmap
Where AI actually pays, and where it does notData governance and securityUse cases with a business case attachedTarget architecture
System assessment and selection
Bespoke build
ONCE YOU KNOW
Applied solutions
Aggregate and periodic reportsNarrative draftingLiterature screeningMedical assessment supportMedical information handlingLocal health-authority formatsWorkflow automationReal-world data and evidence
ACROSS THE CASE LIFECYCLE

Every one of these proposes. A person disposes.

Automation here is drafting, matching and routing — the parts of a case that are mechanical once the rules are written down. Each output arrives with its rationale and its source record, and waits for someone to accept it.

01Intake
Getting the case in, cleanly and once.
Safety mailbox triageAdverse event recognitionDuplicate detectionStructured intake formsFree-text and scanned formsMedical information intakeEDC reconciliationLiterature intakeHealth-authority and partner sourcesRedaction of personal dataSource document attachment
02Case processing
Drafting and pre-populating, never deciding.
Prioritisation and assignmentCase field pre-populationSeriousness proposalListedness against the reference documentCausality proposalFollow-up query draftingNarrative draftingIn-line and batch quality checksSubmission preparationWorkflow routing
03Compliance and reporting
Evidence that assembles itself.
Aggregate report authoringCompliance and CAPA trackingWorkflow oversightSubmission timeliness monitoringAudit and inspection packsReconciliation reporting
THE ONE WE WILL NOT BUILD
Medical judgment stays with your physicians.

Seriousness, expectedness and causality are assessments a person signs. A model can assemble the evidence for them, show its reasoning and flag what looks unusual — and that is where it stops. We have removed an automated flag from a client’s system for exactly this reason, and we would do it again.

VALIDATED BY DESIGN

The AI is the easy part. The evidence is the job.

We came to AI through computer system validation, not the other way around. Every model we deploy arrives with the same documentation trail we’d hand an auditor for an Argus upgrade — because sooner or later, someone will ask for it.

Talk through your validation approach
GxP validation evidence
IQ/OQ/PQ, traceability matrix, and executed test scripts for every model we put into your environment.
Explainable by default
Every output carries its rationale and source record. Black-box classifications are not fit for regulatory use.
Human in the loop
AI drafts, your reviewers decide. Causality and seriousness assessments stay with qualified people.
Aligned to the frameworks
CIOMS WG XIV, GVP Module IX, ICH E2B(R3), and EU AI Act expectations built into the design, not bolted on after.
HOW A BUILD RUNS

The same controls as any other change.

AI in a safety process is still a change to a regulated workflow. It is specified, tested and evidenced the way anything else touching case data would be.

Step 01
Find the task
A specific, repetitive step — not a department.
Step 02
Define the boundary
What it may decide, and what a human keeps.
Step 03
Build it
Against your data, on infrastructure you control.
Step 04
Test it against known cases
Measured on work whose answer is already known.
Step 05
Evidence and hand over
Specification, test records and the decision log.
WHERE IT RUNS

On infrastructure you control.

Safety data does not leave your environment to be processed by someone else’s service.

WHERE IT RUNSYour cloud tenantOn-premisePrivate networkNo case data to third-party services
WHAT IT TOUCHESSafety databaseDocuments and attachmentsLiterature sourcesReporting layers
WHAT COMES WITH ITSpecificationTest recordsDecision logChange control

Curious what AI could actually take off your plate?

We will walk your workflows with you and say plainly which ones are worth automating — and which are not.

Book an AI readiness review
Merakee BI — Dedicated PV Consulting

Dedicated PV consulting for safety systems, analytics, dashboards, migration and AI development.

CONTACT
600 Matheson Blvd W Unit 5, Mississauga, ON L5R 4C1, Canada
© 2020–2026 Merakee BI Analytics Ltd.
Mississauga, Ontario, Canada