A Chenvar Healthtech
platform

MedClarivaTM

Pharmacovigilance, held to a physician’s standard.

A pharmacovigilance platform combining structured safety operations, medical review, regulatory workflows, validation and competency development.

Platform
PV Suite · PV Academy · PV Sandbox · PV Tools
Coverage
Intake to inspection readiness — 11 lifecycle stages, 15 modules
Status
Deployment, development and validation declared separately, per product
Medical governance
Physician-founded · safety-physician review built into the workflow
Operator
Chenvar Healthtech Private Limited · Hyderabad, India
01 · The PV lifecycle

How much of your PV operation can it support?

MedClariva is not a case-management tool with extras. It is built around the whole safety lifecycle, and each stage is mapped to the module that carries it — with its build status stated.

  1. Intake
  2. Case processing
  3. Medical review
  4. ICSR
  5. E2B(R3)
  6. Signal
  7. Aggregate
  8. Benefit–risk
  9. RMP
  10. QPPV oversight
  11. Inspection readiness
01Intake01 ICSR / Case Processing · 04 Literature SurveillanceOperational build
02Case processing01 ICSR / Case Processing · 12 Product DictionaryOperational build
03Medical review01 review and QC workflow · safety-physician review on requestOperational build
04ICSR01 ICSR / Case ProcessingOperational build
05E2B(R3)ICSR / E2B(R3) layer — canonical data representationIn development
06Signal02 Signal ManagementOperational build
07Aggregate03 Aggregate ReportingOperational build
08Benefit–risk05 Benefit–RiskOperational build
09RMP06 Risk Management PlansOperational build
10QPPV oversight08 QPPV Dashboard · 07 PSMFOperational build
11Inspection readiness15 Inspection Readiness · 09 CAPA & Deviations · 10 SOP Management · 11 Vendor OversightOperational build
02 · The platform

One platform, four surfaces.

Operations, practice, assessment and utilities — kept distinct so each can be evaluated, deployed and validated on its own terms.

03 · PV Suite

Fifteen modules. One safety record.

The modules are layers of a single system, not fifteen separate products. A case entered once is the same record that a signal, a periodic report, the PSMF and an inspector later rely on.

Case operationsWhere safety information becomes a record
  • 01ICSR / Case Processing
  • 04Literature Surveillance
  • 12Product Dictionary

Structured, coded cases feed signal detection and every periodic report.

Safety scienceWhere records become conclusions
  • 02Signal Management
  • 03Aggregate Reporting
  • 05Benefit–Risk
  • 06Risk Management Plans

Signal and benefit–risk conclusions feed the RMP, the periodic reports and the PSMF.

PV system & qualityWhere the system proves it is in control
  • 07PSMF
  • 08QPPV Dashboard
  • 09CAPA & Deviations
  • 10SOP Management
  • 11Vendor Oversight
  • 15Inspection Readiness

Oversight draws on every record above; Inspection Readiness assembles it for the inspector.

Platform foundationApplied across every module
  • 13Regulatory Intelligence
  • 14Users & Roles

Regulatory rules and role separation govern what each user can see, do and sign.

04 · ICSR and E2B(R3)

From safety information to a governed case.

The ICSR layer is designed as a chain: each step hands a controlled record to the next, so the E2B(R3) representation is derived from governed data rather than assembled at the end.

  1. Safety informationOperational build
  2. Structured caseOperational build
  3. Medical review / QCOperational build
  4. Governed dataOperational build
  5. E2B(R3) representationIn development
  6. Downstream safety operationsOperational build
Current state

The E2B(R3) representation is in development. MedClariva makes no claim of E2B(R3) conformance, gateway submission readiness or acceptance by any authority. That claim will be made only against a declared, validated baseline.

05 · Validation and assurance

Built as a regulated system. Evidenced as one.

A safety system is defensible when every change can be traced to a requirement, a release, a test and a person. These controls are part of the architecture, not a module added before an inspection.

01

Requirements & traceability

Requirements mapped to implementation and verification evidence.

  • A maintained requirements register
  • Every write passes through a controlled procedure that validates, authorises and logs it
  • Regulated data elements governed by a versioned data contract
02

Controlled baselines

Identifiable software releases and controlled configuration states.

  • Identified releases, declared by date
  • A canonical schema baseline under version control
  • Environment-parity checks between staging and production
03

Verification & testing

Documented test execution against defined requirements.

  • Qualification runs recorded per environment
  • Defects root-caused and recorded, not patched silently
  • Evidence retained with the release it verifies
04

Auditability

Controlled records, attribution, timestamps, signatures and history.

  • Append-only audit — not editable, including by administrators
  • Attributable electronic signatures with a stated reason on controlled actions
  • Tenancy enforced by the database, not the application

Deployment status, development status and validation status are independently declared.

ProductDeploymentDevelopmentValidation
PV SuiteSafety operationsPilot accessOperational buildValidation in progress
ICSR / E2B(R3) layerWithin PV SuiteNot releasedIn developmentNot claimed
PV AcademyCompetency assessmentPrivate betaOperational buildNot applicable
PV SandboxSimulated workflowNot releasedIn developmentNot applicable
PV ToolsOpen utilitiesAvailableOperational buildNot claimed
Status as declared on 21 September 2026. “Not claimed” means no validation claim is made for that surface. “Not applicable” marks training surfaces that do not hold regulated safety records.
06 · Who it is for

For organisations that must show control of their safety system.

Built for teams that need structured, traceable and scalable safety operations — and have to demonstrate them to an inspector, a partner or a licensor.

  • Small and mid-sized marketing authorisation holders
  • Pharmaceutical and biotechnology companies building a safety function
  • Indian pharmaceutical companies expanding into regulated international markets
  • Pharmacovigilance service providers and CROs
  • Organisations that need structured, traceable drug-safety infrastructure

PV professionals and learners: see PV Academy and Sandbox.

07 · PV Academy and PV Sandbox

Train on the concepts that underpin structured safety operations.

The competency layer of MedClariva. Academy teaches and assesses; Sandbox gives controlled, simulated experience. Together they produce evidence that a person can do the work.

01→

Learn

Structured learning built on a fictional safety database and a versioned reference-safety corpus.

Private beta
02→

Practice

Simulated end-to-end workflow in the Sandbox, against synthetic data.

Not released
03→

Assess

Case files scored on causality, seriousness, expectedness and submission decisions — judgement, not recall.

Private beta
04

Demonstrate competency

A record of assessed performance that an employer or a sponsor can rely on.

Private beta
08 · Safety-physician services

Technology where it scales. Medical judgement where it matters.

Some decisions in pharmacovigilance are medical. For those, MedClariva provides qualified safety-physician input alongside the platform.

01Safety-physician reviewPhysician sign-off on cases where the medical content decides the outcome.
02Complex case assessmentMedical assessment of confounded, multi-drug or clinically ambiguous cases.
03Causality assessmentStructured causality with the clinical reasoning written down.
04Signal and benefit–risk inputMedical evaluation of validated signals and benefit–risk questions.
05Aggregate-report medical reviewMedical review of PBRER / PSUR, DSUR and PADER content.
06RMP medical inputSafety specification and risk-minimisation input from a clinician.
07PV medical governanceMedical oversight of the safety system itself — procedures, escalation, sign-off.
09 · Medical governance

Physician-founded. Safety-engineered.

MedClariva was founded by Dr Varun Kumar Gone, a consultant physician in internal medicine who designed its clinical architecture himself.

The consequence is practical: the system was designed with a physician’s understanding of clinical safety information — what makes a case serious, what makes a narrative usable, and where a reviewer’s judgement has to be recorded rather than inferred.

Clinical
13+ years in internal medicine and critical care
Qualifications
MD, Internal Medicine · MRCP (UK)
Safety training
Pharmacovigilance and drug-safety training · medical affairs (BCMAS)
Role
Founder · clinical architecture of MedClariva

Full record on ORCID.

10 · Evaluate MedClariva

Request a MedClariva pilot.

Or discuss your PV operation first. Tell us what you run today and what you want the platform to take on.

  1. Reply within two working days — from the founder, not a queue.
  2. Scoping call on your products, markets, case volume and current system.
  3. Written pilot scope — modules, data, duration and what success looks like.
Location
Hyderabad, Telangana, India
Markets / regions
Modules of interest

Do not include patient-identifiable information or case data in this form. Looking to enrol in PV Academy? Use Academy enrolment instead.