TRV-2026-1372Certified recordPeer-reviewed

Cost-Effectiveness of AI-Powered Decentralized Production for Advanced Therapies in the Hospital-Generated Chimeric Antigen Receptor T-Cell Therapy for Multiple Myeloma From a German Hospital Perspective: Early Health Technology Assessment Study

Background: Although effective, current chimeric antigen receptor T-cell (CAR-T) production methods-centralized, manual, and complex-are cost-intensive, time-consuming, and prone to variability. AIDPATH (AI-Powered Decentralized Production for Advanced Therapies in the Hospital) proposes a decentralized, automated alternative that integrates patient-specific data; optimizes resource use; and potentially improves cell viability, manufacturing efficiency, and patient outcomes. Objective: The aim of this study was…

Health · Good Space — documented gain · certified 2026-10-14 · v1 · article view · machine-readable

Current reading — gain

In a partitioned survival model, the AI-supported AIDPATH platform came out dominant over both cilta-cel and standard of care for triple-class refractory multiple myeloma from the German hospital perspective.

What this doesn’t fix

AIDPATH parameters were estimated rather than observed because the platform is still in development, so the dominance finding is a modeled projection and the authors say further data are needed.

Evidence

Reader signal

How should this claim be treated?

Cite this record

Truvace Impact Record TRV-2026-1372, v1: “Cost-Effectiveness of AI-Powered Decentralized Production for Advanced Therapies in the Hospital-Generated Chimeric Antigen Receptor T-Cell Therapy for Multiple Myeloma From a German Hospital Perspective: Early Health Technology Assessment Study.” Truvace, 2026-10-14. /record/TRV-2026-1372 (accessed at citation time). sha256 f77ac83f77294085…

Calibration history

Every change to this record since certification, in the open. None yet — the reading has held since it entered the record.

  1. Certifiedv1f77ac83f7729…

    Certified into the record

Verify this record
How to verify without trusting this page

Fetch the canonical text of any version from /api/record/TRV-2026-1372 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.