- Integration
- Uses some Eclipse 15.6 functions and exports contours and plans to the user's TPS; validate DICOM transfer, structure naming, beam model, machine configuration, dose recalculation, plan integrity, and failure recovery.
Public source Exact FDA submission Checked 2026-09-03
- Deployment and data flow
- Web-based planning software with site-specific integration to CT, network, and treatment-planning infrastructure; current no-cost access goals are product-family context, not a guaranteed commercial term.
Public source Exact FDA submission Checked 2026-09-03
- Security and privacy
- Vendor documentation pending
Vendor confirmation Exact FDA submission Checked 2026-09-03
Public materials reviewed for this batch do not establish the complete security posture for the exact release. Request data-flow, identity, audit, encryption, retention, support-access, vulnerability-management, backup, and incident-response evidence.
- Training and support
- Only qualified radiation oncologists, medical physicists, dosimetrists, and trained radiation-therapy planning staff. should operate or interpret the system. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
FDA source Exact FDA submission Checked 2026-09-03
- Monitoring and change control
- Monitor by exact hardware, software and model version, patient population, anatomy, protocol, operator, input quality, output edits or overrides, failed studies, repeat acquisition or rework, downstream impact, downtime, incidents, recalls, and updates. Track the limits that matter for this product: RPA is not a primary treatment-planning system. Every contour and plan must be imported into the user's TPS for review, editing, and final dose calculation; unsupported disease sites, techniques, machines, or local protocols must not be inferred.
Public source Exact FDA submission Checked 2026-09-03
Release and scope verification
Map the installed model, build, options, population, anatomy, inputs, and outputs to K222728 before acceptance.
exact submission · checked 2026-09-03 Later product-family features are not evidence that this cleared release includes them.
Interoperability acceptance
Uses some Eclipse 15.6 functions and exports contours and plans to the user's TPS; validate DICOM transfer, structure naming, beam model, machine configuration, dose recalculation, plan integrity, and failure recovery.
exact submission · checked 2026-09-03 Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Clinical acceptance
Use a signed local test set for the supported population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. RPA is not a primary treatment-planning system. Every contour and plan must be imported into the user's TPS for review, editing, and final dose calculation; unsupported disease sites, techniques, machines, or local protocols must not be inferred.
exact submission · checked 2026-09-03 Define stop-use, escalation, rollback, and revalidation triggers before production use.
Economic evaluation
Model capital and recurring cost against net staff time after review, throughput, repeat imaging or rework, room time, consumables, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-03 Vendor productivity claims are scenario inputs, not guaranteed local savings.
Lifecycle monitoring
Monitor by exact hardware, software and model version, patient population, anatomy, protocol, operator, input quality, output edits or overrides, failed studies, repeat acquisition or rework, downstream impact, downtime, incidents, recalls, and updates. Track the limits that matter for this product: RPA is not a primary treatment-planning system. Every contour and plan must be imported into the user's TPS for review, editing, and final dose calculation; unsupported disease sites, techniques, machines, or local protocols must not be inferred.
exact submission · checked 2026-09-03 Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.