FDA-cleared profile

Workflow Box

Mirada Medical Ltd. · Radiotherapy Planning Imaging · FDA-cleared (510(k))

Authorized purpose: Workflow Box is a software system for routing DICOM-compliant data to and from automated processing components. It supports atlas-based contouring, deformable-image-registration re-contouring, and machine-learning contouring for CT, MR, and RTSTRUCT data; contours may be used in clinical workflows including radiation-therapy treatment planning. Appropriate software must review and edit generated contours, and Workflow Box is not intended to automatically detect lesions.

Clinical role
Radiotherapy contouring, treatment planning, treatment management, image processing, or session support under qualified review and approval.
Images and patients
Radiotherapy Planning Imaging · CT, MR, and RTSTRUCT imaging data for automated contours and radiotherapy planning
Key limitation
Keep in mind: Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.

Overview status: Source-reviewed overview

Report a correction
Clinical details Purpose, workflow fit, evidence, and safety record

Workflow navigation pilot

Workflow role has not yet been reviewed for this navigation pilot.

A tag identifies a documented role; it does not establish compatibility or local acceptance. Methods and sources

  • What does this software do?Authorized purpose: Workflow Box is a software system for routing DICOM-compliant data to and from automated processing components. It supports atlas-based contouring, deformable-image-registration re-contouring, and machine-learning contouring for CT, MR, and RTSTRUCT data; contours may be used in clinical workflows including radiation-therapy treatment planning. Appropriate software must review and edit generated contours, and Workflow Box is not intended to automatically detect lesions.
  • Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: CT, MR, and RTSTRUCT imaging data for automated contours and radiotherapy planning Input: Supported CT or MR images, structures, prescriptions, treatment plans, registrations, and treatment-session data.
  • Who uses it?Intended users: Radiation oncologists, medical physicists, dosimetrists, therapists, and other qualified radiation professionals.
  • What does the software produce?Output: Contours, plans, adapted plans, image-processing results, treatment-management records, or session information requiring professional review.
  • What is its most important limitation?Key limitation: Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.

Clinical takeaway. Clinical role: Workflow Box is a software system for routing DICOM-compliant data to and from automated processing components. It supports atlas-based contouring, deformable-image-registration re-contouring, and machine-learning contouring for CT, MR, and RTSTRUCT data; contours may be used in clinical workflows including radiation-therapy treatment planning. Appropriate software must review and edit generated contours, and Workflow Box is not intended to automatically detect lesions.

Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports that Workflow Box was validated and verified against its user needs and intended use through planned performance, functional and algorithmic testing, which it states demonstrated that the device meets its user needs and requirements; verification and validation were carried out in compliance with CFR 21 Part 820 and in adherence to the DICOM standard. Results are as reported in the FDA submission, not independent validation.

Evidence context

Evidence context not reviewed for this FDA record.

Public-label constraints

Label constraints have not been reviewed for this exact FDA record. Unknown is not all ages or evidence of unsuitability.

Public-label constraints, not patient-level eligibility or a medical recommendation. Training and evaluation populations are separate. Read the original labeling and confirm the exact release and protocol.

Purpose
Workflow Box is a software system for routing DICOM-compliant data to and from automated processing components. It supports atlas-based contouring, deformable-image-registration re-contouring, and machine-learning contouring for CT, MR, and RTSTRUCT data; contours may be used in clinical workflows including radiation-therapy treatment planning. Appropriate software must review and edit generated contours, and Workflow Box is not intended to automatically detect lesions.
  • Exact FDA submission
  • Checked 2026-09-04
Workflow role
Radiotherapy contouring, treatment planning, treatment management, image processing, or session support under qualified review and approval.
  • Exact FDA submission
  • Checked 2026-09-04
Required input
Supported CT or MR images, structures, prescriptions, treatment plans, registrations, and treatment-session data.
  • Exact FDA submission
  • Checked 2026-09-04
Output and clinician action
Contours, plans, adapted plans, image-processing results, treatment-management records, or session information requiring professional review.
  • Exact FDA submission
  • Checked 2026-09-04
Care setting
Radiation-oncology settings within the labeled workflow.
  • Exact FDA submission
  • Checked 2026-09-04
Intended users
Radiation oncologists, medical physicists, dosimetrists, therapists, and other qualified radiation professionals.
  • Exact FDA submission
  • Checked 2026-09-04
Limitations
Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.
  • Exact FDA submission
  • Checked 2026-09-04
Evidence summary
The exact FDA document reports that Workflow Box was validated and verified against its user needs and intended use through planned performance, functional and algorithmic testing, which it states demonstrated that the device meets its user needs and requirements; verification and validation were carried out in compliance with CFR 21 Part 820 and in adherence to the DICOM standard. Results are as reported in the FDA submission, not independent validation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Workflow Box is validated and verified against its user needs and intended use by the successful execution of planned performance, functional and algorithmic testing included in this submission." … "The results of performance, functional and algorithmic testing demonstrate that Workflow Box meets the user needs and requirements of the device". Read from the exact FDA decision document on 2026-11-14.

Evidence

Performance evidence

Metrics are shown only when they are tied to a source, endpoint, population, and tested product version. Candidate literature without exact product and version linkage is not shown as product evidence.

Evidence summary
The exact FDA document reports that Workflow Box was validated and verified against its user needs and intended use through planned performance, functional and algorithmic testing, which it states demonstrated that the device meets its user needs and requirements; verification and validation were carried out in compliance with CFR 21 Part 820 and in adherence to the DICOM standard. Results are as reported in the FDA submission, not independent validation.
  • FDA source
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Workflow Box is validated and verified against its user needs and intended use by the successful execution of planned performance, functional and algorithmic testing included in this submission." … "The results of performance, functional and algorithmic testing demonstrate that Workflow Box meets the user needs and requirements of the device". Read from the exact FDA decision document on 2026-11-14.

Reported sensitivity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Sensitivity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.

Reported specificity
Not applicable
  • Not applicable
  • Not applicable
  • Checked 2026-09-04

Specificity is not promoted as a product-wide endpoint. Compare only an exact endpoint, threshold, population, version, study design, and source if separately verified.

No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.

K181572 FDA decision evidence package for Workflow Box

  • DesignFDA decision evidence and product verification described in the exact submission or PMA decision record.
  • PopulationCT, MR, and RTSTRUCT imaging data for automated contours and radiotherapy planning
  • Scopeexact submission
  • Tested versionWorkflow Box configuration described in K181572
  • IndependenceSponsor or vendor study

K181572

FDA decision material is manufacturer-submitted regulatory evidence. It is not independent clinical validation unless the exact source expressly establishes that distinction; local technical, clinical, privacy, security, and workflow acceptance remains necessary.

Safety and lifecycle

Postmarket record

Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.

Postmarket safety review
The 2026-09-02 openFDA device-recall snapshot contained no record matched to K181572 by exact native submission identifier. This does not exclude product-family, later-version, or adverse-event information.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-04

Exact-identifier review does not prove absence of all product-family safety signals.

Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.

Reimbursement

IT implementation Deployment, interfaces, data handling, and support

System and version relationships

Match the AI release, system build, configuration and region. Source documentation does not establish acceptance of an installed system.

No specific system/version pairing has completed review for this FDA record. A broad DICOM or product-family statement does not establish a named viewer build's support.

Review Merge, Visage, Sectra, AGFA and IntelePACS context

Integration chain: evidence at each hop

Public source context, not tested interoperability. Each hop needs its own release/configuration evidence. Missing or unavailable routes are not documented incompatibility. All local tests are planned, not passed; no installed-system acceptance is recorded.

Acquisition/source → routing → AI processing → returned objects → viewer/worklist/report → support owner

No specific route context has been source-reviewed for this record. Obtain both endpoint builds and documents; this is not a finding of incompatibility.

  1. Acquisition/source

    Source context, not route validation: Supported CT or MR images, structures, prescriptions, treatment plans, registrations, and treatment-session data.

    Scope: Exact FDA submission.

    Confirm scanner/model, protocol, series completeness and both software builds.

    Field checked 2026-09-04 · FDA 510(k) decision material K181572: Workflow Box

  2. Routing

    Source context, not route validation: The exact FDA package describes Workflow Box routing CT, MR and RTSTRUCT data to and from DICOM nodes within a hospital network, interoperating via DICOM objects and networking with other DICOM capable devices such as PACS and Radiation Treatment Planning Systems. Interface versions and local compatibility require confirmation.

    Scope: Exact FDA submission. Packet wording: "Workflow Box data routing and contouring workflows support CT, MR and RTSTRUCT image data and structures. Workflow Box supports the routing of data to and from DICOM nodes within a hospital network." … "The proposed and predicate device are both designed to interoperate via DICOM objects and networking with other DICOM capable devices such as PACS and Radiation Treatment Planning Systems.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.

    Field checked 2026-11-14 · FDA 510(k) decision material K181572: Workflow Box

  3. AI processing

    Source context, not route validation: The exact FDA package describes Workflow Box as a server based application supporting Microsoft Windows 10 (64-bit) and Microsoft Windows Server 2016. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "Server based application supporting Computer platform & Workstation and Server based application supporting Microsoft Windows 10 (64-bit) and operating system Windows Server 2008 R2, SP1 and Windows 7 (64-bit) Microsoft Windows Server 2016." … "Comparison of Technological Characteristics with Predicate Device Characteristic Workflow Box predicate". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

    Confirm processing location, queue ownership, exclusions and exact AI build.

    Field checked 2026-11-14 · FDA 510(k) decision material K181572: Workflow Box

  4. Returned objects

    Source context, not route validation: Contours, plans, adapted plans, image-processing results, treatment-management records, or session information requiring professional review.

    Scope: Exact FDA submission.

    Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.

    Field checked 2026-09-04 · FDA 510(k) decision material K181572: Workflow Box

  5. Viewer/worklist/report

    Unresolved route: Contours, plans, adapted plans, image-processing results, treatment-management records, or session information requiring professional review.

    Scope: Exact FDA submission.

    Confirm the named viewer/worklist/report build, display behavior and report transfer. Output support alone does not establish this endpoint. The displayed source describes output, not validated end-to-end delivery.

    Field checked 2026-09-04 · FDA 510(k) decision material K181572: Workflow Box

  6. Support owner

    Unresolved route: Not established for the exact route.

    Scope: Scope not established.

    Name the local, platform and AI supplier support owners and escalation path.

Planned local route tests

No tests below have been performed or accepted.

  1. Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
  2. Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
  3. Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
  4. Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
  5. Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
  6. Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
  7. Updates and rollback (planned). Define version change control, revalidation triggers, stop-use criteria and a tested rollback route.

Local implementation checklist

Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.

Open the printable evaluation checklist

Deployment
The exact FDA package describes Workflow Box as a server based application supporting Microsoft Windows 10 (64-bit) and Microsoft Windows Server 2016. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Server based application supporting Computer platform & Workstation and Server based application supporting Microsoft Windows 10 (64-bit) and operating system Windows Server 2008 R2, SP1 and Windows 7 (64-bit) Microsoft Windows Server 2016." … "Comparison of Technological Characteristics with Predicate Device Characteristic Workflow Box predicate". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The exact FDA package describes Workflow Box routing CT, MR and RTSTRUCT data to and from DICOM nodes within a hospital network, interoperating via DICOM objects and networking with other DICOM capable devices such as PACS and Radiation Treatment Planning Systems. Interface versions and local compatibility require confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "Workflow Box data routing and contouring workflows support CT, MR and RTSTRUCT image data and structures. Workflow Box supports the routing of data to and from DICOM nodes within a hospital network." … "The proposed and predicate device are both designed to interoperate via DICOM objects and networking with other DICOM capable devices such as PACS and Radiation Treatment Planning Systems.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Training
Only radiation oncologists, medical physicists, dosimetrists, therapists, and other qualified radiation professionals should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
  • Exact FDA submission
  • Checked 2026-09-04
Monitoring
Monitor K181572 by exact hardware, software, model, and algorithm 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 these product-specific limits: Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.
  • Exact FDA submission
  • Checked 2026-09-04

This is buyer-facing monitoring guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.

Release and scope verification

Map installed model, build, options, population, anatomy, inputs, outputs, and enabled functions to K181572 before acceptance.

exact submission · checked 2026-09-04

Later product-family features are not evidence that this cleared or authorized release includes them.

Deployment boundary

The exact public deployment topology remains incomplete; establish hosting responsibility, data flow, availability, upgrade, service, and downtime boundaries locally.

exact submission · checked 2026-09-04

FDA-described topology does not establish current hosting contracts, security controls, uptime, or local qualification.

Interoperability acceptance

The exact public integration contract remains incomplete; establish and test supported input, output, identity, routing, archive, and downtime behavior locally.

exact submission · checked 2026-09-04

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. Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.

exact submission · checked 2026-09-04

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.

exact submission · checked 2026-09-04

No exact-product price or reimbursement determination was promoted.

Lifecycle monitoring

Monitor K181572 by exact hardware, software, model, and algorithm 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 these product-specific limits: Generated contours must be reviewed and edited with appropriate software by trained medical professionals; the exact indication excludes automatic lesion detection.

exact submission · checked 2026-09-04

Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.

Sources & review details FDA identity, research record, source ledger, and history

Regulatory identity

FDA record and catalog context

The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.

FDA submission
K181572
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
Radiotherapy Planning Imaging
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Anatomy
CT, MR, and RTSTRUCT imaging data for automated contours and radiotherapy planning
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-04
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2018-07-10
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
FDA status
FDA-cleared
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31

Research record

What has been checked

This audit distinguishes completed source review from fields that have not yet been researched.

Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
9Source classes checked
0Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains no PubMed or ClinicalTrials.gov candidates; no external evidence was promoted. The current discovery snapshot contains 0 PubMed and 0 ClinicalTrials.gov candidate records; its dated, count-matched human screening remains current. Unlinked candidates remain quarantined. Native FDA recall identifiers produced 0 postmarket candidate records; 0 have been reviewed (0 published, 0 rejected) and 0 remain unreviewed.

Candidate leads were screened against the exact product and tested version. Unlinked records remain quarantined.

Source classes: fda ai list, fda decision summary, fda decision material, fda device recall, literature index, trial registry, pubmed, clinical trials, openfda device recall

Field review details

Recorded state, verification date, notes and sources for fields without a publishable value. Conflicting records stay explicitly unsettled here; no plain settled value is shown for them.

  • Public pricing: Not publicly available - checked 2026-09-04 - Exact FDA submission

    No public list price for the exact cleared or authorized configuration was found. Obtain a written quote separating license or hardware basis, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.

  • Pricing model: Not yet reviewed
  • Setup and integration fees: Not yet reviewed
  • Recurring fees: Not yet reviewed
  • Minimum commitment: Not yet reviewed
  • Contract duration: Not yet reviewed
  • Renewal terms: Not yet reviewed
  • Cancellation terms: Not yet reviewed
  • Support and service terms: Not yet reviewed
  • Trial or pilot terms: Not yet reviewed
  • Reimbursement: Not publicly available - checked 2026-09-04 - Exact FDA submission

    No exact-product reimbursement determination was promoted in this timeboxed review. Verify payer, site-of-service, coding, coverage, and local payment assumptions independently.

  • Data hosting location: Not yet reviewed
  • Data retention: Not yet reviewed
  • Documented data use: Not yet reviewed
  • Hardware requirements: Not yet reviewed
  • Network requirements: Not yet reviewed
  • Identity and access: Not yet reviewed
  • Security: Not publicly available - checked 2026-09-04 - Exact FDA submission

    Public materials reviewed for this exact release do not establish the complete security posture. Request data-flow, identity, audit, encryption, retention, remote-access, vulnerability-management, backup, and incident-response evidence.

  • Installation timeline: Not yet reviewed

5 sources - 3 history items

Source ledger

  1. FDA 510(k) decision material K181572: Workflow Box

    U.S. Food and Drug Administration - Published 2018-07-10 - Accessed 2026-09-04

    Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary

  2. Artificial Intelligence-Enabled Medical Devices

    U.S. Food and Drug Administration - Accessed 2026-08-31

    Scope: regulatoryIdentity, modalityContext

  3. PubMed biomedical literature index

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery

  4. ClinicalTrials.gov study registry

    U.S. National Library of Medicine - Accessed 2026-09-01

    Scope: evidenceDiscovery, studyStatus

  5. openFDA Device Recall API

    U.S. Food and Drug Administration - Accessed 2026-09-02

    Scope: recallDiscovery, nativeSubmissionMatching

Research history

  1. K181572 FDA decision

    Regulatory record

    510(k)

  2. Source-review record updated

    Research record

    fda record reviewed

  3. Reader overview source-reviewed

    Editorial review

    Source-reviewed editorial overlay

Alternatives

Related tools to compare

FDA-cleared K252190

DeepBT Detector-Plus

Aitewan Biomedical Technology, Inc.

Authorized purpose: DeepBT Detector-Plus provides initial gross-tumor-volume contours on T1-weighted contrast-enhanced and optional T2-weighted MR images for radiation-treatment planning in adults with the labeled brain tumors.

Modality
Radiotherapy Planning Imaging
Anatomy
Brain tumors, including metastases, meningiomas, and acoustic neuromas
Decision
2026-04-10
FDA-cleared K250035

Contour ProtégéAI+

MIM Software Inc.

Authorized purpose: Contour ProtégéAI+ automatically creates contours on CT and T2 MR DICOM images as an accessory to MIM software for quantitative analysis, adaptive therapy, transfer, and archive; users must review and edit contours, and the device is not intended to detect or contour lesions.

Modality
Radiotherapy Planning Imaging
Anatomy
CT anatomical regions; prostate, seminal vesicles, and urethra on T2 MR
Decision
2025-02-03
FDA-cleared K221305

AI-Rad Companion Organs RT

Siemens Medical Solutions USA, Inc

Authorized purpose: AI-Rad Companion Organs RT VA40 automatically contours predefined structures from adult DICOM CT for qualified review and DICOM RTSTRUCT transfer; this release added 29 head-and-neck structures and does not detect or contour lesions.

Modality
Radiotherapy Planning Imaging
Anatomy
Multi-region
Decision
2022-10-14
FDA-cleared K212915

MVision AI Segmentation

MVision AI

Authorized purpose: MVision AI Segmentation automatically generates initial contours from CT images for radiotherapy planning; the contours are transferred for professional visualization, review, modification, and approval, and the labeled software is not intended for lesion or tumor detection or real-time adaptive planning.

Modality
Radiotherapy Planning Imaging
Anatomy
Head and neck, brain, breast, lung and abdomen, male pelvis, and female pelvis structures
Decision
2022-05-03

Correct this exact record

Copy this public context and add the field, proposed wording and original source before sending. Nothing here is submitted automatically. Form-specific prefill has not been verified.

Open existing correction destination

Permission to display a submission is not evidence verification. A submission enters editorial review; it does not approve a public change. Form availability, data entry, receipt, review and publication are separate steps. Data entry and receipt remain unverified.

Accepted repository change history

No entry has been added to this scoped change history for this record. This is not proof that the record never changed.

Correction policy and limits · Public repository change history