Safety and monitoring

Safety clocks. Risk indicators. An audit workspace that is independent.

Adverse events, SUSARs, and device effects that name the reporting rules of each authority on the study. Monitoring visit reports, deviations, and a risk indicator scan.

Safety workspace

Adverse event workflow

Term, seriousness criteria, expectedness, causality, outcome, and narrative, with versions and follow-ups. Coding is typed by a licensed coder. Every change is audited.

Reporting rules

Each serious case names the rules that apply to the study's authorities, such as CTIS 7-day, IND 15-day, or MDR Article 87. People prepare and send the reports.

E2B(R3)-shaped draft

A case file shaped like E2B(R3) XML can be downloaded for review. It is not a validated E2B transmission and nothing is sent to an authority gateway.

Medical review

A medical reviewer signs the case review. Safety reconciliation lists cases that need attention.

Unblinding

Emergency unblinding is one participant, one person, and one reason, with a signature. Randomization codes are kept in their own records.

Not included

There is no DMC workspace and no endpoint adjudication workflow.

Monitoring

Risk indicators

A scan computes risk indicators from the study data and stores the findings. Quality tolerance limits are not set or enforced by the system.

Visit reports

Monitoring visit reports with findings and actions, signed by the monitor. Follow-up letters are written by a person.

Protocol deviations

Deviations are tracked items with a status and an owner on the study.

Findings and CAPA

Findings are tracked items with an owner and a due date. CAPA effectiveness checks are not a separate workflow.

Audit-trail review

A person reviews the audit trail for a period and signs the review. The review is stored with its scope and outcome.

Bring us the protocol.

We read the study, configure ValidTrials, and the sites work in one record. The first conversation is about your protocol, not a software tour.

Further reading