FDA-cleared profile

ProstatID

ScanMed, LLC · MRI · FDA-cleared (510(k))

Authorized purpose: Concurrent CADe/CADx reading aid for qualified physicians interpreting prostate MRI in adult males undergoing screening or clinical MRI, including high-risk screening or diagnostic imaging, to identify prostate abnormalities and regions suspicious for cancer and assess their likelihood of malignancy.

Clinical role
Concurrent reading aid for detection, assessment, and characterization of prostate abnormalities; outputs supplement full MR interpretation and must not be the sole basis for patient management.
Images and patients
MRI · Prostate
Key limitation
Keep in mind: The algorithm does not analyze DCE images; outputs must be interpreted with all available MR data consistent with clinical recommendations, including DCE when available, and in the PI-RADS v2 context. It is not a replacement for physician interpretation or a sole basis for management.

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: Concurrent CADe/CADx reading aid for qualified physicians interpreting prostate MRI in adult males undergoing screening or clinical MRI, including high-risk screening or diagnostic imaging, to identify prostate abnormalities and regions suspicious for cancer and assess their likelihood of malignancy.
  • Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Prostate Input: DICOM axial prostate MRI using T2W, DWI, and ADC data; DCE is not analyzed. The packet lists compatible Philips 1.5T/3.0T, GE 1.5T/3.0T, and Siemens 3.0T systems and surface or endorectal coils.
  • Who uses it?Intended users: Physicians qualified to read and interpret prostate MRI in the context of ACR recommendations and PI-RADS v2.
  • What does the software produce?Output: Colorized 2D T2 overlays, post-processed T2W images linked in 3D through DICOM viewing, regional likelihood-of-suspicion scores on a 0-1 scale, a suggested likelihood or PI-RADS exam score, a 3D lesion rendering, a PDF report, prostate volume, and lesion location and extent.
  • What is its most important limitation?Key limitation: The algorithm does not analyze DCE images; outputs must be interpreted with all available MR data consistent with clinical recommendations, including DCE when available, and in the PI-RADS v2 context. It is not a replacement for physician interpretation or a sole basis for management.

Clinical takeaway. Clinical role: Concurrent CADe/CADx reading aid for qualified physicians interpreting prostate MRI in adult males undergoing screening or clinical MRI, including high-risk screening or diagnostic imaging, to identify prostate abnormalities and regions suspicious for cancer and assess their likelihood of malignancy.

Evidence takeaway. Evidence from the reviewed source record: Standalone testing used 150 retrospective cases, 220 biopsy locations (90 cancerous and 130 non-cancerous), and 150 cases including 44 normal cases; lesion-level ROC AUC was 0.710. Standalone FROC sensitivity was 80% at one false positive per patient and 98% at three false positives per patient. The reader study used 150 cases and nine physicians, with 130 complete-follow-up cases; the wAFROC figure of merit was 0.387 without CAD versus 0.430 with CAD (delta 0.043, p=0.034). AUC, FROC sensitivity at stated operating points, and wAFROC are distinct endpoints.

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
Concurrent CADe/CADx reading aid for qualified physicians interpreting prostate MRI in adult males undergoing screening or clinical MRI, including high-risk screening or diagnostic imaging, to identify prostate abnormalities and regions suspicious for cancer and assess their likelihood of malignancy.
  • Exact FDA submission
  • Checked 2026-09-09
Workflow role
Concurrent reading aid for detection, assessment, and characterization of prostate abnormalities; outputs supplement full MR interpretation and must not be the sole basis for patient management.
  • Exact FDA submission
  • Checked 2026-09-09
Required input
DICOM axial prostate MRI using T2W, DWI, and ADC data; DCE is not analyzed. The packet lists compatible Philips 1.5T/3.0T, GE 1.5T/3.0T, and Siemens 3.0T systems and surface or endorectal coils.
  • Exact FDA submission
  • Checked 2026-09-09
Output and clinician action
Colorized 2D T2 overlays, post-processed T2W images linked in 3D through DICOM viewing, regional likelihood-of-suspicion scores on a 0-1 scale, a suggested likelihood or PI-RADS exam score, a 3D lesion rendering, a PDF report, prostate volume, and lesion location and extent.
  • Exact FDA submission
  • Checked 2026-09-09
Care setting
Healthcare facility or hospital prostate MRI workflow for adult males undergoing screening or clinical imaging, including high-risk or family-history populations.
  • Exact FDA submission
  • Checked 2026-09-09
Intended users
Physicians qualified to read and interpret prostate MRI in the context of ACR recommendations and PI-RADS v2.
  • Exact FDA submission
  • Checked 2026-09-09
Limitations
The algorithm does not analyze DCE images; outputs must be interpreted with all available MR data consistent with clinical recommendations, including DCE when available, and in the PI-RADS v2 context. It is not a replacement for physician interpretation or a sole basis for management.
  • Exact FDA submission
  • Checked 2026-09-09
Evidence summary
Standalone testing used 150 retrospective cases, 220 biopsy locations (90 cancerous and 130 non-cancerous), and 150 cases including 44 normal cases; lesion-level ROC AUC was 0.710. Standalone FROC sensitivity was 80% at one false positive per patient and 98% at three false positives per patient. The reader study used 150 cases and nine physicians, with 130 complete-follow-up cases; the wAFROC figure of merit was 0.387 without CAD versus 0.430 with CAD (delta 0.043, p=0.034). AUC, FROC sensitivity at stated operating points, and wAFROC are distinct endpoints.
  • Exact FDA submission
  • Checked 2026-09-09

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
Standalone testing used 150 retrospective cases, 220 biopsy locations (90 cancerous and 130 non-cancerous), and 150 cases including 44 normal cases; lesion-level ROC AUC was 0.710. Standalone FROC sensitivity was 80% at one false positive per patient and 98% at three false positives per patient. The reader study used 150 cases and nine physicians, with 130 complete-follow-up cases; the wAFROC figure of merit was 0.387 without CAD versus 0.430 with CAD (delta 0.043, p=0.034). AUC, FROC sensitivity at stated operating points, and wAFROC are distinct endpoints.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Reported sensitivity
Standalone lesion-detection sensitivity: 80% at 1 false positive per patient and 98% at 3 false positives per patient; this is an FROC operating-point endpoint.
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09

The FDA packet supports sensitivity only at the stated false-positive rates, not a single global device sensitivity.

Reported specificity
Research pending
  • Needs research
  • Exact FDA submission
  • Checked 2026-08-31

This field has not been curated yet.

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

ProstatID regulatory performance study summary

  • DesignStand-alone performance and reader study (ACR AI Central category)
  • PopulationAdult
  • Scopeexact submission
  • Tested versionExact product version not reported; regulatory study summarized for FDA submission K212783
  • Samplen=150
  • IndependenceIndependence not established

K212783

ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.

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 exact-identifier FDA recall query returned no native recall record for K212783. This limited result does not establish absence of recalls or other safety information and does not cover later versions, family records, MAUDE reports, corrections, or field notices.
  • Public source
  • Exact FDA submission
  • Checked 2026-09-09
Pricing & contracts Public price, contract terms, and reimbursement

Price not public here; enter your quote

Not verified: Pricing information is recorded but not verified against a resolving source.

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: DICOM axial prostate MRI using T2W, DWI, and ADC data; DCE is not analyzed. The packet lists compatible Philips 1.5T/3.0T, GE 1.5T/3.0T, and Siemens 3.0T systems and surface or endorectal coils.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K212783: ProstatID

  2. Routing

    Source context, not route validation: The software is not installed on the MRI system, PACS, or workstation; the packet describes cloud-based SaaS on dedicated servers, DICOM input and output to common workstations, PACS, and RIS, and a stated VPN connection requirement. Exact current interfaces and versions are not established.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K212783: ProstatID

  3. AI processing

    Source context, not route validation: The exact FDA package describes ProstatID as running on cloud-based servers configured as Software as a Service (SaaS), not installed on the user's MRI system, PACS or workstation, with a secure VPN connection required between client and SaaS server. Current hosting, data flow, and commercial configuration require vendor confirmation.

    Scope: Exact FDA submission. Packet wording: "The software is not installed on the user’s MRI system, PACS system, workstation, or any device other than the cloud-based servers configured as a Software as a Service (SaaS) model." … "ProstatID is offered as a virtual or SaaS application and runs on dedicated servers. Implementation requires secure VPN connection between client and SaaS server.". 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 K212783: ProstatID

  4. Returned objects

    Source context, not route validation: Colorized 2D T2 overlays, post-processed T2W images linked in 3D through DICOM viewing, regional likelihood-of-suspicion scores on a 0-1 scale, a suggested likelihood or PI-RADS exam score, a 3D lesion rendering, a PDF report, prostate volume, and lesion location and extent.

    Scope: Exact FDA submission.

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

    Field checked 2026-09-09 · FDA K212783: ProstatID

  5. Viewer/worklist/report

    Unresolved route: Colorized 2D T2 overlays, post-processed T2W images linked in 3D through DICOM viewing, regional likelihood-of-suspicion scores on a 0-1 scale, a suggested likelihood or PI-RADS exam score, a 3D lesion rendering, a PDF report, prostate volume, and lesion location and extent.

    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-09 · FDA K212783: ProstatID

  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 ProstatID as running on cloud-based servers configured as Software as a Service (SaaS), not installed on the user's MRI system, PACS or workstation, with a secure VPN connection required between client and SaaS server. Current hosting, data flow, and commercial configuration require vendor confirmation.
  • Exact FDA submission
  • Checked 2026-11-14

Packet wording: "The software is not installed on the user’s MRI system, PACS system, workstation, or any device other than the cloud-based servers configured as a Software as a Service (SaaS) model." … "ProstatID is offered as a virtual or SaaS application and runs on dedicated servers. Implementation requires secure VPN connection between client and SaaS server.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.

Integration
The software is not installed on the MRI system, PACS, or workstation; the packet describes cloud-based SaaS on dedicated servers, DICOM input and output to common workstations, PACS, and RIS, and a stated VPN connection requirement. Exact current interfaces and versions are not established.
  • Exact FDA submission
  • Checked 2026-09-09

Input or output interoperability

DICOM is explicitly referenced in the described input, output, or workflow.

exact submission · checked 2026-09-01

The model card does not establish every supported DICOM object, transfer method, or local interface.

Supported acquisition environment

Scanner manufacturers: GE;Philips;Siemens

exact submission · checked 2026-09-01

Confirm currently supported software versions, protocols, and site-specific acquisition configurations.

ACR exact-submission catalog context

ACR AI Central provides an exact-submission model card for ProstatID; FDA labeling remains controlling for clinical use, limitations, and performance.

exact submission · checked 2026-09-09
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
K212783
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Modality
MRI
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Anatomy
Prostate
  • FDA source
  • Exact FDA submission
  • Checked 2026-09-09
Clearance type
510(k)
  • FDA source
  • Exact FDA submission
  • Checked 2026-08-31
Decision date
2022-07-08
  • 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
24Fields reviewed
9Source classes checked
1Screened PubMed leads
0Screened trial leads
0Unreviewed FDA recall leads

The refreshed discovery snapshot contains 1 PubMed and 0 ClinicalTrials.gov candidate record. Discovery metadata alone does not establish exact tested-product, version, population, and endpoint applicability, so all candidates remain quarantined and none was promoted. The current discovery snapshot contains 1 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, acr ai central product, 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 verified - checked 2026-09-09 - Exact FDA submission

    No public price or quote for the exact K212783 configuration was established in this review.

  • 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-09 - Exact FDA submission

    No exact-product payer policy, coding instruction, or payment determination was established; eligibility must be evaluated by payer, site of service, and use case.

  • 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 verified - checked 2026-09-09 - Exact FDA submission

    Exact-release security controls, data retention, hosting boundaries, and scoped assurance documentation require vendor confirmation.

  • Installation timeline: Not yet reviewed
  • Training: Not verified - checked 2026-09-09 - Exact FDA submission

    Current training prerequisites, competency checks, and support commitments for the exact configuration require vendor confirmation.

  • Monitoring: Not verified - checked 2026-09-09 - Exact FDA submission

    Current drift, quality, uptime, alert, escalation, and incident-response commitments for the exact configuration require vendor confirmation.

7 sources - 3 history items

Source ledger

  1. FDA K212783: ProstatID

    U.S. Food and Drug Administration - Published 2022-07-08 - Accessed 2026-09-09

    Scope: identity, clinicalUse, modality, anatomy, workflow, evidence, implementation, deployment

  2. Artificial Intelligence-Enabled Medical Devices

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

    Scope: regulatoryIdentity, modalityContext

  3. ProstatID model card (K212783)

    American College of Radiology - Published 2026-08-17 - Accessed 2026-09-01

    Scope: intendedUsers, careSetting, output, limitations, evidenceSummary, integration, anatomy, evidenceStudies, implementationCapabilities

  4. PubMed biomedical literature index

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

    Scope: evidenceDiscovery

  5. ClinicalTrials.gov study registry

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

    Scope: evidenceDiscovery, studyStatus

  6. openFDA Device Recall API

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

    Scope: recallDiscovery, nativeSubmissionMatching

  7. openFDA exact recall query for K212783

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

    Scope: postmarketSafety

Research history

  1. K212783 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 K242683

QP-Prostate® CAD

Quibim S.L.

Authorized purpose: QP-Prostate CAD detects and marks suspected prostate lesions for clinically significant prostate cancer on bi-parametric T2-weighted and diffusion-weighted prostate MRI, returning moderate/high suspicion overlays in DICOM to third-party workstations/PACS for concurrent physician review; patient management must not rely on it alone.

Modality
MRI
Anatomy
Prostate
Decision
2025-03-18
FDA-cleared K241770

Prostate MR AI (VA10A)

Siemens Healthcare GmbH

Authorized purpose: Prostate MR AI (VA10A) is a plug-in CADe/CADx aid for radiologists interpreting prostate MRI in adult men aged 40 years or older with suspected prostate cancer and no prior treatment, using PI-RADS-oriented review; it is not the sole basis for diagnosis or management.

Modality
MRI
Anatomy
Prostate
Decision
2025-03-05
FDA-cleared K233196

Medihub Prostate

JLK Inc.

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.

Modality
MRI
Anatomy
Prostate
Decision
2024-06-21

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