PMS Radar

See reporting exposure before it becomes a deadline problem.

Complaint data in, grounded assessment out. Every decision stays with a named person.

PMS Radar overview
PMS Radar overview · illustrative example data

What you get

Every complaint carries its exposure.

Assessed per jurisdiction, from a confirmed chronology and the stated reporting pathway only.

Regulatory and vigilance exposure, by jurisdiction
Regulatory and vigilance exposure, by jurisdiction · illustrative example data
  • Potentially overduewindow passed
  • Window opendays remaining
  • Awareness unresolvedno clock running
  • Assessment timing reviewassessed after window
  • Submission timing reviewsubmitted after window
  • Not assessablerecord contradicts itself
Exposure states · as the Radar Queue labels them

How it gets there

  1. 01

    Bring the data in

    A complaint export, with its source system kept alongside it.

  2. 02

    Assess the population

    Every record, not only the ones somebody opened.

  3. 03

    Confirm the chronology

    A person confirms the awareness date and the pathway.

  4. 04

    Disposition and sign off

    The decision, and the trail it leaves, are yours.

MDR / vigilance exposure

The clock is arithmetic, not judgment.

Deadlines are calculated by a deterministic engine. RootAí never does this arithmetic and never sets a date itself.

30
calendar days
FDA
5
working days
FDA
15
calendar days
EU MDR
10
calendar days
EU MDR
2
calendar days
EU MDR

A jurisdiction alone never produces a deadline. Unresolved stays unresolved.

Bring a complaint export. See what it says.

Contact Sales