Authorized purpose: INT Contour uses a machine-learning approach to provide initial segmentation and contouring of treatment targets and organs at risk for radiation-treatment planning; qualified dosimetrists, physicists, and radiation oncologists must review and edit results when necessary.
Clinical role
Radiotherapy contouring, treatment planning, adaptation, or treatment-session support under professional review.
Images and patients
Radiotherapy Planning Imaging · Head and neck, thorax, abdomen, and male pelvis
Key limitation
Keep in mind: Initial segmentations are not a replacement for thorough review by qualified professionals and require editing when necessary.
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: INT Contour uses a machine-learning approach to provide initial segmentation and contouring of treatment targets and organs at risk for radiation-treatment planning; qualified dosimetrists, physicists, and radiation oncologists must review and edit results when necessary.
Which images or clinical context are in scope?Modality: Radiotherapy Planning Imaging Anatomy or clinical context: Head and neck, thorax, abdomen, and male pelvis 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, adapted plans, dose or evaluation results, or session information requiring review and approval.
What is its most important limitation?Key limitation: Initial segmentations are not a replacement for thorough review by qualified professionals and require editing when necessary.
Clinical takeaway. Clinical role: INT Contour uses a machine-learning approach to provide initial segmentation and contouring of treatment targets and organs at risk for radiation-treatment planning; qualified dosimetrists, physicists, and radiation oncologists must review and edit results when necessary.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports non-clinical verification and validation, including model performance. Testing data from multiple sources covered head and neck, thorax, abdomen, and male pelvis, from patients aged 18 – 76, with ground truth by at least two trained personnel. Dice and 95% Hausdorff Distance (HD95) were calculated per organ and compared with the predicate/reference device; all organs passed the acceptance criteria. No case counts or metric values are given. 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
INT Contour uses a machine-learning approach to provide initial segmentation and contouring of treatment targets and organs at risk for radiation-treatment planning; qualified dosimetrists, physicists, and radiation oncologists must review and edit results when necessary.
The exact FDA document reports non-clinical verification and validation, including model performance. Testing data from multiple sources covered head and neck, thorax, abdomen, and male pelvis, from patients aged 18 – 76, with ground truth by at least two trained personnel. Dice and 95% Hausdorff Distance (HD95) were calculated per organ and compared with the predicate/reference device; all organs passed the acceptance criteria. No case counts or metric values are given. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical verification and validation test results, including model performance and software usability, established that the device meets its design requirements and intended use" … "Testing data was acquired from multiple sources than the training data that covers head and neck, thorax, abdomen, and male pelvis regions.". 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-clinical verification and validation, including model performance. Testing data from multiple sources covered head and neck, thorax, abdomen, and male pelvis, from patients aged 18 – 76, with ground truth by at least two trained personnel. Dice and 95% Hausdorff Distance (HD95) were calculated per organ and compared with the predicate/reference device; all organs passed the acceptance criteria. No case counts or metric values are given. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Non-clinical verification and validation test results, including model performance and software usability, established that the device meets its design requirements and intended use" … "Testing data was acquired from multiple sources than the training data that covers head and neck, thorax, abdomen, and male pelvis regions.". Read from the exact FDA decision document on 2026-11-14.
Sensitivity is not promoted as a product-wide endpoint for this device or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-04
Specificity is not promoted as a product-wide endpoint for this device or software function. Compare only an exact endpoint, threshold, population, version, and source if later verified.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
K212274 FDA evidence package for INT Contour
DesignFDA 510(k) substantial-equivalence decision evidence and product verification described in the exact submission.
PopulationHead and neck, thorax, abdomen, and male pelvis
Scopeexact submission
Tested versionINT Contour configuration described in K212274
IndependenceSponsor or vendor study
K212274
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 K212274 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.
No separate named-product payment identified in reviewed public material
Centers for Medicare & Medicaid Services · United States
This is not a product-specific reimbursement determination. Build a local total-cost and value model and verify payer, site-of-service, coding, and coverage assumptions independently.
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 processing DICOM-compliant image data and storing segmentation results in DICOM RTSTRUCT format, which can be sent to desired destinations via the DICOM protocol. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "The results of the automatic segmentation will be stored in the DICOM Radiotherapy Structure Set (RTSTRUCT) format, which can be sent to desired destinations via the DICOM protocol." … "DICOM Standard The software processes DICOM Same Compliance compliant image data, including RTSTRUCT". 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 software deployed within a hospital's private network on a workstation with an advanced GPU, running as a service accessed through a web-based interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "INTContour software is intended to be deployed within a hospital’s private network on a workstation with an advanced graphics processing unit (GPU) and runs as a service." … "A web- based interface is used to access the service and manage the transfer of data, automatic segmentation, and visualization.". 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, adapted plans, dose or evaluation results, or session information 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, adapted plans, dose or evaluation results, or session information 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 software deployed within a hospital's private network on a workstation with an advanced GPU, running as a service accessed through a web-based interface. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "INTContour software is intended to be deployed within a hospital’s private network on a workstation with an advanced graphics processing unit (GPU) and runs as a service." … "A web- based interface is used to access the service and manage the transfer of data, automatic segmentation, and visualization.". 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 processing DICOM-compliant image data and storing segmentation results in DICOM RTSTRUCT format, which can be sent to desired destinations via the DICOM protocol. Interface versions and local compatibility require confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The results of the automatic segmentation will be stored in the DICOM Radiotherapy Structure Set (RTSTRUCT) format, which can be sent to desired destinations via the DICOM protocol." … "DICOM Standard The software processes DICOM Same Compliance compliant image data, including RTSTRUCT". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
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.
Monitor K212274 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: Initial segmentations are not a replacement for thorough review by qualified professionals and require editing when necessary.
Exact FDA submission
Checked 2026-09-04
Monitoring guidance is buyer-facing implementation guidance derived from the exact cleared scope; it is not a claim that the FDA package provides a live monitoring service.
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 deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
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.
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. Initial segmentations are not a replacement for thorough review by qualified professionals and require editing when necessary.
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 the reviewed public material; productivity or value claims require local evidence.
Monitor K212274 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: Initial segmentations are not a replacement for thorough review by qualified professionals and require editing when necessary.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. radiotherapy planning or image-processing software limits remain submission-specific.
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.
Human reviewedStatus
2026-09-20Last searched
27Fields reviewed
12Source 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, 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 hardware or license 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
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.
Authorized purpose: AccuContour 4.0 uses deep-learning contours to support segmentation of organs at risk on CT images for radiation-treatment planning, evaluation, and adaptation; qualified professionals review and may edit the contours.
Modality
Radiotherapy Planning Imaging
Anatomy
Head and neck, thorax, abdomen, and pelvis organs at risk
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
Authorized purpose: DeepContour uses deep-learning CT processing to generate editable organ contours and RTSTRUCT objects for selected adult radiation-treatment planning workflows, with quantitative statistics, registration, and three-dimensional visualization; it does not contour tumors.
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
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.