Ethos Treatment Management, Ethos Treatment Planning, Ethos Radiotherapy System, Halcyon
K192377Varian Medical Systems, Inc. · cleared 2020-02-10 · product code IYE · Radiology
Premarket evidence — what FDA accepted
source quote (p.4)
“Ethos Treatment Management is software designed for radiation therapy medical professionals to support them in managing radiation treatments for patients. Ethos Treatment Planning is software that is designed generate treatment plans, modify treatment plans, and guide users within adaptive treatment sessions.”
source quote (p.6)
“Support for Adaptive Radiotherapy Treatment Planning and Automated Plan Generation”
source quote (p.6)
“Support for Adaptive Radiotherapy Treatment Planning and Automated Plan Generation”
Validation studies (1)
Bench
sample size not stated
standards: FDA Quality System Regulation (21 CFR §820), ISO 13485 quality Management System standard, ISO 14971 Risk Management Standard, FDA's Guidance for Industry and FDA Staff, "Guidance for the Content of Premarket Submissions for Software Contained in Medical Devices.", IEC 60601-1 standards for safety, IEC 60601-1-2 standard for EMC, IEC 62304, IEC 61217, IEC 62274, IEC 62083, IEC 82304-1, IEC 62366-1, IEC 60825-1, IEC 60976, IEC 60601-1, IEC 60601-1-2, IEC 60601-1-3, IEC 60601-1-6, IEC 60601-2-1, IEC 60601-2-68, EN ISO 13485:2016 Edition 3 2016-03, EN ISO 14971:2012 2012-07, ISO 15223-1 Third Edition 2016-11-01
Reported performance (0 observations)
FDA source did not state a quantitative performance metric — non-reporting is itself the signal.
Each value carries its own analysis unit and task — never compare or pool across devices. Source: 510(k) summary PDF.
Predicate network
Postmarket — what happened after clearance
- re_clearance
The FDA AI/ML device list shows a newer 510(k) K232923 (decision 2024-04-30) from Varian Medical Systems Inc. for a matching device line ("Ethos Treatment Management (3.0); Ethos Treatment Planning (2.0)") — a new clearance for the same line is a change event.
first seen 2026-07-08 · k_number:K232923
- recall_reason_pattern
Software/algorithm-related recall in product code IYE (Accuray Incorporated, initiated 2026-06-16): "In certain cases, a collimator may not fully dock, which triggers a system interlock and prevents motion from the operator console. If personnel then enter the treatment room and i" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:99075
- recall_reason_pattern
Software/algorithm-related recall in product code IYE (Accuray Incorporated, initiated 2026-06-16): "In certain cases, a collimator may not fully dock, which triggers a system interlock and prevents motion from the operator console. If personnel then enter the treatment room and i" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:99083
- recall_reason_pattern
Software/algorithm-related recall in product code IYE (Elekta, Inc., initiated 2026-05-21): "Software may fail to load adapted baseline shift plan during treatment delivery when a communication error occurs." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98980
- recall_reason_pattern
Software/algorithm-related recall in product code IYE (Elekta, Inc., initiated 2025-12-10): "Using oncology information system that manages workflow may result in overtreatment if:Plan delivered with Particle Therapy IHE-RO TDW-II interface,With one field per fraction or l" Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:98116
- recall_reason_pattern
Software/algorithm-related recall in product code IYE (ELEKTA SOLUTIONS AB, initiated 2025-09-17): "When appending a care plan that contains one or more wave medication orders, the occurrence and frequency of the appended orders may not match the intended schedule." Recalling firm is another firm in the same product code.
first seen 2026-07-08 · recall res_event_number:97562
- …and 4 more.
Recall and MAUDE counts are product-code-level (reports aren't reliably attributable to one device). Signals are descriptive observables with sources — never a judgment that the device is unsafe or drifting. Snapshot 2026-07-08.
Reimbursement — how devices like this got paid
Not yet tracked — no payment pathway indexed for this clearance (the reimbursement corpus is a growing seed set).