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.
Clinical role
Radiotherapy contouring, treatment planning, image registration, or treatment-session support under professional review.
Images and patients
Radiotherapy Planning Imaging · CT anatomical regions; prostate, seminal vesicles, and urethra on T2 MR
Key limitation
Keep in mind: Generated or modified contours and plans require qualified review, editing when needed, independent checks, and final approval before treatment.
Clinical detailsPurpose, 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: 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.
Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: CT anatomical regions; prostate, seminal vesicles, and urethra on T2 MR Input: Supported CT or MR images, structures, prescriptions, plans, registrations, and treatment-session data.
Who uses it?Intended users: Qualified radiation oncologists, medical physicists, dosimetrists, and radiation therapists.
What does the software produce?Output: Contours, treatment plans, registrations, dose or evaluation results, and planning datasets requiring review and approval.
What is its most important limitation?Key limitation: Generated or modified contours and plans require qualified review, editing when needed, independent checks, and final approval before treatment.
Clinical takeaway. Clinical role: 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.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-inferiority testing of Contour ProtégéAI+ against MIM Maestro (K071964) reference-device atlases on test subjects from a pool of 770 images gathered from 32 institutions, with testing institutions disjoint from training data, measuring Dice and MDA against original ground-truth contours, plus user beta testing of time savings. It states results were equivalent or better than the reference device, though a footnote states equivalence was NOT demonstrated where a contour's minimum sample size was not met. 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
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.
The exact FDA document reports non-inferiority testing of Contour ProtégéAI+ against MIM Maestro (K071964) reference-device atlases on test subjects from a pool of 770 images gathered from 32 institutions, with testing institutions disjoint from training data, measuring Dice and MDA against original ground-truth contours, plus user beta testing of time savings. It states results were equivalent or better than the reference device, though a footnote states equivalence was NOT demonstrated where a contour's minimum sample size was not met. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-inferiority testing was used to compare the Contour ProtégéAI+ subject device to Atlases created from the MIM Maestro (K071964) reference device." … "The Contour ProtégéAI+ subject device was evaluated on the test subjects from a pool of 770 images gathered from 32 institutions.". Read from the exact FDA decision document on 2026-11-14.
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 non-inferiority testing of Contour ProtégéAI+ against MIM Maestro (K071964) reference-device atlases on test subjects from a pool of 770 images gathered from 32 institutions, with testing institutions disjoint from training data, measuring Dice and MDA against original ground-truth contours, plus user beta testing of time savings. It states results were equivalent or better than the reference device, though a footnote states equivalence was NOT demonstrated where a contour's minimum sample size was not met. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-inferiority testing was used to compare the Contour ProtégéAI+ subject device to Atlases created from the MIM Maestro (K071964) reference device." … "The Contour ProtégéAI+ subject device was evaluated on the test subjects from a pool of 770 images gathered from 32 institutions.". Read from the exact FDA decision document on 2026-11-14.
No exact submission-linked sensitivity endpoint with a verified population, threshold, tested version, and source was promoted.
Reported specificity
Not established in reviewed sources
Reviewed sources checked
Exact FDA submission
Checked 2026-09-04
No exact submission-linked specificity endpoint with a verified population, threshold, tested version, and source was promoted.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K250035 FDA evidence package for Contour ProtégéAI+
DesignFDA 510(k) decision evidence package reviewed for exact submission identity and labeled scope
PopulationLabeled population and configuration described in the K250035 FDA decision material
Scopeexact submission
Tested versionContour ProtégéAI+ configuration described in K250035
IndependenceSponsor or vendor study
K250035
Manufacturer evidence submitted for the exact FDA decision. It is not independent clinical validation, and local technical, clinical, privacy, security, and workflow acceptance remains necessary.
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 K250035 by exact native submission identifier. This does not exclude product-family, later, 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.
No separate named-product Medicare payment was identified in the reviewed CMS radiation-oncology material. Evaluate net planning or delivery value within the radiotherapy service line.
IT implementationDeployment, 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.
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.
Acquisition/source
Source context, not route validation: Supported CT or MR images, structures, prescriptions, plans, registrations, and treatment-session data.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact FDA package describes Contour ProtégéAI+ as an accessory to MIM software that processes CT and MR images as supported by ACR/NEMA DICOM 3.0, with uses including transferring contours to radiation therapy treatment planning systems and archiving contours. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "Trained medical professionals use Contour ProtégéAI as a tool to assist in the automated processing of digital medical images of modalities CT and MR, as supported by ACR/NEMA DICOM 3.0." … "Creation of contours using machine-learning algorithms for applications including, but not limited to, quantitative analysis, aiding adaptive therapy, transferring contours to radiation therapy treatment planning systems, and archiving contours for patient follow-up and management.". 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.
Source context, not route validation: The exact FDA package describes Contour ProtégéAI+ operating on Windows, Mac and Linux systems, deployed either on a remote server using the MIMcloud service for data management and transfer or locally on the workstation or server running MIM software. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "operates on Windows, Mac, and Linux computer systems. Contour ProtégéAI+ is deployed on a remote server using the MIMcloud service for data management and transfer; or locally on the workstation or server running MIM software.". 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.
Source context, not route validation: Contours, treatment plans, registrations, dose or evaluation results, and planning datasets requiring review and approval.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Contours, treatment plans, registrations, dose or evaluation results, and planning datasets requiring review and approval.
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.
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.
Patient/study identity (planned). Use approved non-patient test data to verify identifiers, accession and result-to-study linkage at every hop.
Study completeness (planned). Test missing views/series, partial transfer, late arrivals, priors and unsupported acquisition inputs; confirm explicit refusal or fallback.
Ordering and duplicates (planned). Send out-of-order, repeated and corrected studies; verify worklist order, deduplication and no misleading stale results.
Report transfer (planned). Verify output object types, annotations, units, report content, destination and availability of original images.
Access (planned). Verify authorized roles, audit trail, denied access and support ownership at each destination.
Latency and failures (planned). Agree a workload and turnaround target; test queues, timeouts, missing results and fallback reading.
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.
The exact FDA package describes Contour ProtégéAI+ operating on Windows, Mac and Linux systems, deployed either on a remote server using the MIMcloud service for data management and transfer or locally on the workstation or server running MIM software. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "operates on Windows, Mac, and Linux computer systems. Contour ProtégéAI+ is deployed on a remote server using the MIMcloud service for data management and transfer; or locally on the workstation or server running MIM software.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact FDA package describes Contour ProtégéAI+ as an accessory to MIM software that processes CT and MR images as supported by ACR/NEMA DICOM 3.0, with uses including transferring contours to radiation therapy treatment planning systems and archiving contours. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Trained medical professionals use Contour ProtégéAI as a tool to assist in the automated processing of digital medical images of modalities CT and MR, as supported by ACR/NEMA DICOM 3.0." … "Creation of contours using machine-learning algorithms for applications including, but not limited to, quantitative analysis, aiding adaptive therapy, transferring contours to radiation therapy treatment planning systems, and archiving contours for patient follow-up and management.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
MIM Software's security page states SOC 2 Type 2 status, penetration testing and continuous vulnerability scanning of released products, coordinated vulnerability disclosure and a public security advisories page. Vendor-wide.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; exact-release scope is not established.
Only qualified radiation oncologists, medical physicists, dosimetrists, and radiation therapists should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Exact public integration details remain incomplete; establish and test the supported input, output, identity, routing, archive, report, and downtime contract locally.
exact submission · checked 2026-09-04
Test representative identifiers, orientation, geometry, measurements, units, routing, failure handling, and round trips locally.
Use a signed local test set for the exact labeled population and workflow. Include common and difficult cases, exclusions, acquisition variation, failed or low-quality inputs, reviewer overrides, and downstream effects. Generated or modified contours and plans require qualified review, editing when needed, independent checks, and final approval before treatment.
exact submission · checked 2026-09-04
Define stop-use, escalation, rollback, and revalidation triggers before production use.
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-04
No exact-product price was found in reviewed public material; productivity or value claims require local evidence.
Monitor 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.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. No exact native-submission recall record was found in the checked snapshot; this does not exclude other product-family or later signals.
Sources & review detailsFDA 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.
This audit distinguishes completed source review from fields that have not yet been researched.
Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
13Source 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, vendor documentation, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, 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 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
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
Installation timeline: Not yet reviewed
Monitoring: Not publicly available - checked 2026-09-04 - Exact FDA submission
The exact FDA decision and checked recall snapshot do not establish a complete local postmarket monitoring protocol. Track version, population, anatomy, protocol, input quality, edits, failures, repeats, downstream effects, downtime, incidents, recalls, and updates locally.
Authorized purpose: Contour ProtégéAI creates machine-learning contours from CT and MR DICOM images to support quantitative analysis, adaptive therapy, radiotherapy planning, archiving, and follow-up; professionals must visualize, review, and edit contours, and the software is not intended to detect or contour lesions.
Modality
Radiotherapy Planning Imaging
Anatomy
Normal structures in labeled CT locations; prostate, seminal vesicles, and urethra on T2 MR
Authorized purpose: Contour ProtegeAI assists trained medical professionals with automated processing of CT and MR images, creates machine-learning contours for quantitative analysis, adaptive therapy, transfer to radiation-treatment planning systems, and archiving, segments structures across CT locations, and segments the prostate, seminal vesicles, and urethra on T2-weighted MR images.
Modality
Radiotherapy Planning Imaging
Anatomy
CT anatomic locations and the prostate, seminal vesicles, and urethra on T2-weighted MR
Authorized purpose: Contour ProtegeAI assists trained medical professionals with automated processing of CT and MR images, machine-learning contour creation for quantitative analysis, adaptive therapy, transfer to radiation-treatment planning systems, and archiving, segmentation across CT locations, and segmentation of the prostate, seminal vesicles, and urethra on T2-weighted MR images.
Modality
Radiotherapy Planning Imaging
Anatomy
CT anatomic locations and the prostate, seminal vesicles, and urethra on T2-weighted MR
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
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.
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.