Authorized purpose: Quantib Prostate versions 1.0 and 2.0 provide processing, visualization, editing, registration, mathematical or statistical analysis, semi-automatic segmentation, volume computation, and PI-RADS workflow support for prostate MRI. The software provides information that may assist trained medical professionals in interpreting prostate MR studies, and diagnosis must not be made solely from its analysis.
Clinical role
Multiparametric-MRI viewing, registration, prostate and sub-region segmentation, lesion review, PI-RADS workflow, and report generation.
Images and patients
MRI · Prostate; prostate and prostatic sub-regions
Key limitation
Keep in mind: Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
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: Quantib Prostate versions 1.0 and 2.0 provide processing, visualization, editing, registration, mathematical or statistical analysis, semi-automatic segmentation, volume computation, and PI-RADS workflow support for prostate MRI. The software provides information that may assist trained medical professionals in interpreting prostate MR studies, and diagnosis must not be made solely from its analysis.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Prostate; prostate and prostatic sub-regions Input: Prostate multiparametric MRI datasets and user-confirmed or edited segmentation and ROI inputs.
Who uses it?Intended users: Trained medical professionals interpreting prostate MR studies.
What does the software produce?Output: Registered and combined MR views, prostate and sub-region segmentations, volume computations, PI-RADS properties, PDF reports, DICOM RT Structure Sets, and DICOM segmentation objects.
What is its most important limitation?Key limitation: Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
Clinical takeaway. Clinical role: Quantib Prostate versions 1.0 and 2.0 provide processing, visualization, editing, registration, mathematical or statistical analysis, semi-automatic segmentation, volume computation, and PI-RADS workflow support for prostate MRI. The software provides information that may assist trained medical professionals in interpreting prostate MR studies, and diagnosis must not be made solely from its analysis.
Evidence takeaway. Evidence from the reviewed source record: The exact FDA document reports bench testing of the standalone performance of the prostate sub-region segmentation algorithm, comparing automatic segmentation with a ground truth by Dice overlap and Mean Surface Distance and against inter-observer measurements, without numeric results. In a qualitative clinical test, radiologists scored sub-region segmentations and ROI initial localizations on a 5-point Likert scale and judged them high quality. The prostate segmentation algorithm is unchanged. 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
Quantib Prostate versions 1.0 and 2.0 provide processing, visualization, editing, registration, mathematical or statistical analysis, semi-automatic segmentation, volume computation, and PI-RADS workflow support for prostate MRI. The software provides information that may assist trained medical professionals in interpreting prostate MR studies, and diagnosis must not be made solely from its analysis.
Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
The exact FDA document reports bench testing of the standalone performance of the prostate sub-region segmentation algorithm, comparing automatic segmentation with a ground truth by Dice overlap and Mean Surface Distance and against inter-observer measurements, without numeric results. In a qualitative clinical test, radiologists scored sub-region segmentations and ROI initial localizations on a 5-point Likert scale and judged them high quality. The prostate segmentation algorithm is unchanged. Results are as reported in the FDA submission, not independent validation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "Bench testing of the software was done to show that the system is suitable for its intended use and to evaluate the stand-alone performance of the sub-region segmentation algorithm." … "This was done by comparing the automatic sub-region segmentation to a ground truth and calculating the Dice overlap and Mean Surface Distance.". 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 bench testing of the standalone performance of the prostate sub-region segmentation algorithm, comparing automatic segmentation with a ground truth by Dice overlap and Mean Surface Distance and against inter-observer measurements, without numeric results. In a qualitative clinical test, radiologists scored sub-region segmentations and ROI initial localizations on a 5-point Likert scale and judged them high quality. The prostate segmentation algorithm is unchanged. Results are as reported in the FDA submission, not independent validation.
FDA source
Exact FDA submission
Checked 2026-11-14
Packet wording: "Bench testing of the software was done to show that the system is suitable for its intended use and to evaluate the stand-alone performance of the sub-region segmentation algorithm." … "This was done by comparing the automatic sub-region segmentation to a ground truth and calculating the Dice overlap and Mean Surface Distance.". Read from the exact FDA decision document on 2026-11-14.
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.
K221106 FDA evidence package for Quantib Prostate
DesignSpecial 510(k) bench and qualitative clinical performance testing for prostate sub-region segmentation and PI-RADS sector-map ROI initialization.
PopulationProstate; prostate and prostatic sub-regions
Scopeexact submission
Tested versionQuantib Prostate version 2.0 described in K221106
IndependenceSponsor or vendor study
K221106
Bench testing used Dice overlap and mean surface distance; the clinical test used a five-point Likert scale with radiologist review, but the public summary does not expose sample counts or numeric scores.
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 K221106 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.
No separate named-product Medicare payment was identified in the reviewed CMS coverage material. Evaluate the product within the applicable imaging or clinical service line and verify payer, site-of-service, coding, and coverage assumptions independently.
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: Prostate multiparametric MRI datasets and user-confirmed or edited segmentation and ROI inputs.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The FDA package describes multiparametric MRI input, manual editing and confirmation of prostate segmentation and ROI location, PDF report output, DICOM RT Structure Set output, and DICOM segmentation storage output.
Scope: Exact FDA submission. This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: The FDA summary states that deployment and compatibility with the environment and other devices are equivalent to the previously cleared predicate; current site topology, interfaces, hosting, security, availability, and service remain unverified.
Scope: Exact FDA submission. This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
Confirm processing location, queue ownership, exclusions and exact AI build.
Unresolved route: Registered and combined MR views, prostate and sub-region segmentations, volume computations, PI-RADS properties, PDF reports, DICOM RT Structure Sets, and DICOM segmentation objects.
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 FDA summary states that deployment and compatibility with the environment and other devices are equivalent to the previously cleared predicate; current site topology, interfaces, hosting, security, availability, and service remain unverified.
Exact FDA submission
Checked 2026-09-04
This is the release-level boundary described in the exact FDA package; current hosting, contracts, security, availability, upgrade path, and site configuration remain separate evidence.
The FDA package describes multiparametric MRI input, manual editing and confirmation of prostate segmentation and ROI location, PDF report output, DICOM RT Structure Set output, and DICOM segmentation storage output.
Exact FDA submission
Checked 2026-09-04
This is the interface boundary described in the exact FDA package; current local compatibility, routing, identity, archive, and downtime behavior still require acceptance testing.
Only trained medical professionals interpreting prostate mr studies should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor K221106 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: Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
Exact FDA submission
Checked 2026-09-04
This is buyer-facing monitoring guidance derived from the exact cleared or authorized scope; it is not a claim that the FDA package provides a live monitoring service.
The FDA summary states that deployment and compatibility with the environment and other devices are equivalent to the previously cleared predicate; current site topology, interfaces, hosting, security, availability, and service remain unverified.
exact submission · checked 2026-09-04
FDA-described deployment boundaries do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes multiparametric MRI input, manual editing and confirmation of prostate segmentation and ROI location, PDF report output, DICOM RT Structure Set output, and DICOM segmentation storage output.
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. Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
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 K221106 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: Outer segmentation and ROI location require inspection, editing, and confirmation; diagnosis must not be made solely from Quantib Prostate analysis and individual sub-region volumes are not provided.
exact submission · checked 2026-09-04
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes. prostate MRI image-post-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-04Last searched
26Fields reviewed
12Source classes checked
4Screened PubMed leads
1Screened trial leads
0Unreviewed FDA recall leads
Four PubMed records and one trial record were screened. Three publications and the trial use or discuss Quantib Prostate, but none identifies the tested software as version 2.0 from K221106; the review article is not exact-product performance evidence, so all five records are quarantined. The current discovery snapshot contains 4 PubMed and 1 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, acr ai central product, fda decision material, fda pma record, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, 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 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: Assist trained radiologists and urologists in reviewing and analyzing prostate MR studies through semi-automatic prostate outlining, multiparametric visualization, and related measurements and reporting; patient-management decisions must not rely on the software alone.
Authorized purpose: Adjunctive review of MR prostate images and biopsy findings for prostate segmentation, lesion evaluation, quantification, documentation, and pre-planning biopsy or soft-tissue-ablation procedures.
Authorized purpose: PROView is an aiding tool for the clinicians to review multi-parametric prostate MR images following PI-RADS guidelines. It displays acquired and reformatted data for visualization and provides tools for assessment of the prostate gland volume and findings analysis in patients with known or suspected prostate lesions. Measurements and associated scoring are included in a report for communication to referring physicians.
Authorized purpose: Quantib Prostate is image post-processing software for processing, visualizing, and editing prostate MRI images. It supports registered multiparametric-MRI viewing, optional combined-image visualization, semi-automatic anatomical segmentation, volume computation, manual editing, and a structured PI-RADS workflow to assist trained medical professionals interpreting prostate MR studies; diagnosis should not be made solely from its analysis.
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.