AGENTIC AI 75 · #34
Clinical-trial oversight agents
Medable announced customer adoption of an agent providing intelligence across clinical-development systems.
Last reviewed 2026-11-11
Agentic AI 75 / #34
2026 status: Announced customer adoption · Category: Clinical operations
The 2026 development
Medable announced customer adoption of an agent providing intelligence across clinical-development systems.
The governance gap
Trial oversight touches regulated records. An agent that summarises or flags a trial event needs an audit trail that distinguishes the source record from the agent's interpretation.
Where CAIN-42 fits: Moat 4 — Execution Provenance & Attestation
Core question: Can we prove what actually happened? Hash-chained, signed records binding decision to execution to observable effect.
Record the source document, the extracted fact, the agent's interpretation and the human reviewer as separate layers. A flag is a proposal, not a finding.
How the wiring works
- Ingest the source record with a content digest.
- Extract facts and label them as extracted, not verified.
- Attach the agent's interpretation as a separate layer.
- Require a named reviewer before the flag enters the trial record.
What is real today
PROPOSED A design mapping only. No dedicated implementation exists yet; do not buy this as a finished control.
No clinical-trial connector or regulated validation exists in this repository. Do not treat this page as clinical or regulatory advice.
| Component in this repository | What the module says it is |
|---|---|
cain/compliance.py | CAIN Trust Fabric - Regulatory Compliance & Certification Engine (Phase 4) |
cain/worm_export.py | CAIN Trust Fabric - tamper-evident WORM Causal Evidence Fabric (Phase 4) |
cain/causality/evidence.py | CAIN CAUSALITY — Causal Evidence Independence Graph (Prompt CAUSALITY, Phase 9). |
cain/cain_iso42001_notary.py | CAIN Phase A+++ - Continuous Statutory Compliance Notary (ISO 42001 & EU AI Act). |
Descriptions are the first line of each module's own docstring, read without importing it. A module path is a pointer into this repository, not a hosted endpoint. Its existence is checked by the test suite; its status for this use is the label above.
Check it yourself
- Inspect a signed evidence package
/product-demo - Fire a live decision through the CAIN-42 pipeline
/fabric/try— the same enforcement path every product sits behind.
Commercial package
| Offer | Regulated Workflow Evidence Review |
|---|---|
| Buyer | Clinical sponsors and CROs |
| Price (proposal) | $7,500–$15,000 per engagement |
| Bundle | Runtime Containment & Evidence — Contain first, then prove what happened. |
| Operator stream | Stream 4 of the 10-stream operator playbook |
SOC, incident response, compliance, enterprise IT is the bundle buyer. The entry offer for this bundle is Runtime containment review; signed evidence pack; the range is $2,500–$5,000 per review; $2,000–$10,000 per evidence pack. A price on this page is a proposal, not a validated rate, and no customer is claimed.
Buy this as a product or service
CAIN-A75-034 — Regulated Workflow Evidence Review DELIVERABLE
A bounded engine run on the buyer's sample: findings, a written report, and a SHA-256 artifact manifest. The manifest is unsigned: it is not a signature and not an attestation.
Kind: Evidence Pack · Price (proposal): $7,500–$15,000 per engagement · Lead time: 5 business days.
Open the product page · all 75 products
What this page does not claim
What this page is not. CAIN-42 is not affiliated with, endorsed by, integrated into, or shipped with the organisation named in the 2026 item. The item is public context; the page describes how CAIN-42 would govern that class of capability. No page here claims a customer, a partnership, a certification, a patent, or a production integration. Prices are proposals. Built by a three-person team.