Claims-to-evidence matrix
Intended use, target population, clinical setting, outputs, endpoints and benefit-risk questions mapped to available and needed evidence.
Clinical Evidence Strategy
We help SaMD teams define what must be demonstrated, evaluate existing evidence, design a proportionate evidence plan and prepare regulatory documentation. We do not operate clinical sites or represent document support as clinical trial conduct.
Selected clients
Healthcare teams we have supported


















Scope and deliverables
Our scope covers regulatory evidence strategy, synthesis and documentation. Site selection, participant recruitment, study conduct, monitoring, biostatistical programming and data management require qualified providers under separate responsibility.
Intended use, target population, clinical setting, outputs, endpoints and benefit-risk questions mapped to available and needed evidence.
Structured inventory of product data, literature, comparator evidence, analytical validation, usability and real-world information with limitations made explicit.
Search protocol, databases, terms, screening criteria, appraisal framework, extraction structure and reproducible update plan.
EU MDR clinical evaluation plan and report support, equivalence assessment inputs, state-of-the-art narrative and linkage to risk and PMS.
Regulatory objectives, population, endpoints, comparator, bias controls, sample-size assumptions and analysis considerations for discussion with clinical and statistical specialists.
Evidence summaries for FDA or EU dossiers, response support, residual-gap rationale and post-market clinical follow-up planning.
Ways to work together
A focused claims, gap and regulatory-question assessment before a study or submission plan is fixed.
Methodical clinical evaluation planning, literature work and report drafting with manufacturer review and approval.
Work alongside the sponsor’s clinicians, statistician, CRO, investigators and regulatory lead with explicit interfaces and ownership.
How it works
Define intended use, claims, population, context, benefit, risk and pathway.
Assess relevance, quality, bias, applicability and gaps across evidence sources.
Specify proportionate methods and qualified delivery roles for unresolved questions.
Build controlled regulatory outputs and connect them to PMS and change triggers.
Regulations, standards and guidance considered
Frequently asked questions
No claim is made that we operate sites, recruit participants or act as a CRO. We support regulatory evidence strategy and documentation and can work with the sponsor’s qualified clinical, statistical, data-management and site partners.
No. The need depends on claims, risk, novelty, available evidence and pathway. Literature, analytical studies, usability evidence or existing clinical data may answer some questions; a prospective study is warranted when material uncertainty remains.
Sometimes, but relevance and quality must be demonstrated. Differences in device, algorithm, data provenance, population, workflow and endpoint can limit applicability. Literature should not be used to bridge product-specific performance without a defensible rationale.
Analytical validation asks whether the software correctly processes inputs and produces accurate outputs. Clinical validation or performance asks whether those outputs achieve the stated purpose in the target population and use context. Both may be necessary.
Only where equivalence can be robustly demonstrated across technical, biological and clinical characteristics and sufficient access to relevant data exists. For many software devices, changes in data, algorithm or workflow make equivalence difficult.
No. Authorities and notified bodies evaluate evidence in context. We document assumptions, limitations and residual uncertainty and recommend early feedback where the evidence threshold is genuinely uncertain.
Start with the product you have