TrialTriage, a Semiautonomous Prescreening Workflow for Resolving Ambiguity in Phase I Oncology Trial Eligibility: Development and Proof-of-Concept Study Using Synthetic Cases
Enrollment in phase I oncology trials remains low largely because potentially eligible patients are not identified and evaluated quickly enough. Current clinical trial matching systems can identify candidate patients from the electronic health record, but cases with missing or uncertain eligibility data are often routed for offline manual review. This delay impedes clarification and prolongs the final eligibility determination. This study evaluated TrialTriage, a semiautonomous system built on the n8n platform a…
TrialTriage achieved perfect concordance with ground truth on 90 synthetic phase I oncology cases and reclassified ambiguous cases to definitive eligibility after capturing investigator email replies, processing cases in seconds compared to slower manual review.
Some ambiguous cases remained unresolved when investigator replies lacked actionable information, and cases with no reply after 48 hours still required deferral to offline manual review.
Evaluation used only synthetic cases with label definitions aligned to the same protocol rules used to design the rule engine, so results reflect implementation fidelity not real-world clinical performance.
Evidence
- Peer-reviewedJMIR Formative Research2026-08-05
How should this claim be treated?
Truvace Impact Record TRV-2026-0666, v1: “TrialTriage, a Semiautonomous Prescreening Workflow for Resolving Ambiguity in Phase I Oncology Trial Eligibility: Development and Proof-of-Concept Study Using Synthetic Cases.” Truvace, 2026-08-06. /record/TRV-2026-0666 (accessed at citation time). sha256 244046a80329f834…
Calibration history
Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.
Certified into the record
How to verify without trusting this page
Fetch the canonical text of any version from /api/record/TRV-2026-0666 and hash it yourself — for example shasum -a 256 on the saved canonical field. The result must equal content_hash, and each version’s text ends with prev:followed by the prior version’s hash (version 1 chains to 64 zeros). If a single character of any version had been altered since certification, the chain would not reproduce.
ace