- Integration
- DICOM-RT compliant browser-based workflow with treatment-planning-system scripts used to transmit DICOM files and plan parameters; exact supported TPS versions and scripting permissions require local verification.
Public source Exact FDA submission Checked 2026-09-03
- Deployment and data flow
- FDA summaries describe a Windows-server and web-browser architecture, including cloud Windows servers and client machines. The current vendor FAQ describes enterprise identity integration; confirm tenancy, data residency, availability, backups, and interface ownership.
Public source Exact FDA submission Checked 2026-09-03
- Security and privacy
- The current vendor FAQ states that Oncospace can use an organization's Active Directory or Azure policies for user authentication and invites deployment-specific security review. This is product-family information, not an attestation for a particular installation.
Vendor supplied Product family Checked 2026-09-03
Request the current security package and contract controls for the proposed deployment.
- Training and support
- Only trained and qualified radiation-therapy professionals should operate the software and review, correct, and approve its outputs. Local onboarding must include release-specific limitations, failure examples, escalation, and competency documentation.
Public source Exact FDA submission Checked 2026-09-03
- Monitoring and change control
- Monitor prediction and plan-review performance by software and model version, disease site, protocol, target and OAR geometry, structure-name mapping, objective acceptance, optimization iterations, plan quality, overrides, transfer failures, and update. Revalidate when models, protocols, TPS versions, interfaces, or clinical policies change.
Public source Exact FDA submission Checked 2026-09-03
Release and scope verification
This release updated prostate and head-and-neck models and added thoracic, abdominal, and gynecological regions while keeping algorithms locked before clinical use. Procurement should map the installed build, modules, models, anatomies, inputs, and outputs to K242748 before acceptance.
exact submission · checked 2026-09-03 Later product-family features are not evidence that an earlier cleared release includes them.
Interoperability acceptance
DICOM-RT compliant browser-based workflow with treatment-planning-system scripts used to transmit DICOM files and plan parameters; exact supported TPS versions and scripting permissions require local verification.
exact submission · checked 2026-09-03 Test representative imports, exports, identifiers, orientation, geometry, structure names, units, failure handling, and round trips in the local environment.
Clinical acceptance
Use a signed local test set spanning supported anatomies, scanners, protocols, unusual or postsurgical anatomy, and small or complex structures. Measure edit burden, rejection, downstream plan effects, and reviewer agreement rather than relying only on average overlap metrics.
product family · checked 2026-09-03 Define stop-use, escalation, rollback, and revalidation triggers before production use.
Economic evaluation
Model total annual and per-plan cost against hands-on and elapsed time after review, correction, failed transfers, rework, support, upgrades, downtime, and any effect on plan quality or throughput.
product family · checked 2026-09-03 Vendor time-saving results are scenario inputs, not guaranteed local savings.
Lifecycle monitoring
Monitor prediction and plan-review performance by software and model version, disease site, protocol, target and OAR geometry, structure-name mapping, objective acceptance, optimization iterations, plan quality, overrides, transfer failures, and update. Revalidate when models, protocols, TPS versions, interfaces, or clinical policies change.
product family · checked 2026-09-03 Trend failures and edits by exact software version, model, anatomy, scanner, protocol, and site.