Clinical research technology and CRO services
A sponsor should be able to see which data and which program produced a result. We write analysis plans, calculate sample size from stated assumptions, and run the methods the software implements: diagnostic accuracy, agreement, and the survival and longitudinal methods that are actually present. A textbook method that is not implemented is not offered as if it were.
Population, endpoint, missing data and multiplicity, before the confirmatory look.
Assumptions written beside the number.
Sensitivity, specificity and intervals where those methods exist.
Methods such as Bland–Altman where the study needs them and the code exists.
Tables and figures tied to the run.
A second qualified person can check the output. That is a service, not an automatic certificate.
The plan is versioned.
On the frozen snapshot.
A statistician accepts or rejects the output.
The report cites that output.
Diagnostic accuracy, agreement, and the survival and longitudinal methods that are actually in the software can be planned. A method that is not implemented is named as unavailable, not offered as if a general statistical language were attached. There is no claim of an arbitrary R runtime. You provide the endpoint definition and the snapshot. You accept the output before a report quotes it.
No. There is no general claim of an arbitrary R runtime.
Software on this page is what the product can record today. CRO work is a professional service under a separate scope. Neither is a certification, a regulator’s approval, or proof that a study is compliant because the software was used. A qualified person still signs consequential decisions.
The conversation is about your study design and what the software can and cannot do today.
Clinical trial management for drugs, devices, and diagnostics. EU and US regulatory packages from one record. CAREPOI CRO, registered with EOF 16 November 2026.
© 2026 CAREPOI · ValidTrials · Helsinki, EU