Authorized purpose: Views, processes, and analyzes prostate MR images for trained professionals; it is not diagnostic and decisions should not rely solely on its results.
Clinical role
Software that retrieves prostate MR studies from PACS and performs diffusion and perfusion analysis, giving quantitative information to assist completing the prostate structured report; it performs no diagnostic function, and the radiologist can verify and edit each step's output.
Images and patients
MRI · Prostate
Key limitation
Keep in mind: Sequence and protocol availability gates plug-ins, trained-user interpretation is required, and the device is not a diagnostic function.
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: Views, processes, and analyzes prostate MR images for trained professionals; it is not diagnostic and decisions should not rely solely on its results.
Which images or clinical context are in scope?Modality: MRI Anatomy or clinical context: Prostate Input: DICOM prostate MR with T2 plus DWI, T2 plus DCE, or T2+DWI+DCE workflows.
Who uses it?Intended users: Radiologists specialized in prostate imaging, urologists, and oncologists.
What does the software produce?Output: ADC and perfusion maps, automated prostate segmentation, DICOM viewing and analysis, and structured PI-RADS v2.1 reporting with user verification and editing.
What is its most important limitation?Key limitation: Sequence and protocol availability gates plug-ins, trained-user interpretation is required, and the device is not a diagnostic function.
Clinical takeaway. Clinical role: Views, processes, and analyzes prostate MR images for trained professionals; it is not diagnostic and decisions should not rely solely on its results.
Evidence takeaway. Evidence from the reviewed source record: QIBA DWI/DCE digital-reference-object bench testing and clinical testing on named 1.5T and 3T Siemens, GE, and Philips systems; datasets varied by component and no single device-level performance value applies.
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
Views, processes, and analyzes prostate MR images for trained professionals; it is not diagnostic and decisions should not rely solely on its results.
Exact FDA submission
Checked 2026-09-15
Clinical-use display mirrors the exact FDA-supported purpose reconciled in this remediation finding.
Software that retrieves prostate MR studies from PACS and performs diffusion and perfusion analysis, giving quantitative information to assist completing the prostate structured report; it performs no diagnostic function, and the radiologist can verify and edit each step's output.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The sof tware can communicate with any Picture Archiving Communications System (PACS) through the DICOM standard. This communication includes standard Query/Retrieve DICOM operations in order to receive prostate MR image studies in qp -Prostate." … "qp-Prostate is aimed f or dif f usion and perf usion analysis of prostate MR cases, providing quantitative inf ormation usef ul to assist the prof essional in completing the prostate structured report template.". Read from the exact FDA decision document on 2026-11-14.
ADC and perfusion maps, automated prostate segmentation, DICOM viewing and analysis, and structured PI-RADS v2.1 reporting with user verification and editing.
Used within the hospital or medical clinic network, where the platform's high-performance computer is installed, and accessed by web browser from computers on the hospital/center network, for prostate MR image viewing, processing and analysis.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The platf orm runs as a client-server model that requires a high-perf ormance computer installed by QUIBIM inside the hospital or medical clinic network." … "Prostate is accessible through the web browser (Google Chrome or Mozilla Firef ox) of any standard “of f -the-shelf” computer connected to the hospital/center network.". Read from the exact FDA decision document on 2026-11-14.
QIBA DWI/DCE digital-reference-object bench testing and clinical testing on named 1.5T and 3T Siemens, GE, and Philips systems; datasets varied by component and no single device-level performance value applies.
Exact FDA submission
Checked 2026-09-15
Submission-reported technical and clinical testing.
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
QIBA DWI/DCE digital-reference-object bench testing and clinical testing on named 1.5T and 3T Siemens, GE, and Philips systems; datasets varied by component and no single device-level performance value applies.
FDA source
Exact FDA submission
Checked 2026-09-15
Submission-reported technical and clinical testing.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
qp-Prostate regulatory performance study summary
DesignStand-Alone Performance
PopulationPopulation described in the exact-submission ACR model card
Scopeexact submission
Tested versionExact product version not reported; regulatory study summarized for FDA submission K203582
Samplen=157
IndependenceIndependence not established
K203582
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
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 K203582. 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.
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: DICOM prostate MR with T2 plus DWI, T2 plus DCE, or T2+DWI+DCE workflows.
Scope: Exact FDA submission. FDA packet input scope.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Scope: Exact FDA submission. Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
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 qp-Prostate as a client-server platform requiring a high-performance computer installed by QUIBIM inside the hospital or medical clinic network, accessed through a web browser on any standard computer connected to that network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Scope: Exact FDA submission. Packet wording: "The platf orm runs as a client-server model that requires a high-perf ormance computer installed by QUIBIM inside the hospital or medical clinic network." … "Prostate is accessible through the web browser (Google Chrome or Mozilla Firef ox) of any standard “of f -the-shelf” computer connected to the hospital/center network.". 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: ADC and perfusion maps, automated prostate segmentation, DICOM viewing and analysis, and structured PI-RADS v2.1 reporting with user verification and editing.
Scope: Exact FDA submission. FDA packet output scope.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: ADC and perfusion maps, automated prostate segmentation, DICOM viewing and analysis, and structured PI-RADS v2.1 reporting with user verification and editing.
Scope: Exact FDA submission. FDA packet output scope.
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 qp-Prostate as a client-server platform requiring a high-performance computer installed by QUIBIM inside the hospital or medical clinic network, accessed through a web browser on any standard computer connected to that network. Current hosting, data flow, and commercial configuration require vendor confirmation.
Exact FDA submission
Checked 2026-11-14
Packet wording: "The platf orm runs as a client-server model that requires a high-perf ormance computer installed by QUIBIM inside the hospital or medical clinic network." … "Prostate is accessible through the web browser (Google Chrome or Mozilla Firef ox) of any standard “of f -the-shelf” computer connected to the hospital/center network.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The exact-submission ACR model card explicitly references DICOM in the described input, output, or workflow; exact interfaces, versions, and local compatibility require confirmation.
Exact FDA submission
Checked 2026-09-01
Interoperability terms explicitly reported in the exact-submission ACR model card; interface versions and local compatibility still require confirmation.
Quibim's security and privacy statement describes an ISO 27001-certified information security management system and ISO 13485-certified quality management system; QP-Care platform data hosted on Microsoft Azure protected by multi-factor authentication and encryption in transit and at rest; pseudonymization of processed data; regular penetration tests following OSSTMM and OWASP methodologies; staff security training and confidentiality obligations.
Vendor-wide
Checked 2026-10-27
Vendor statement; certificates were not read. Applicant name variants ('QUIBIM S.L.', 'Quibim S.L.') are bridged via the identical distinctive name and QP product naming. Exact-release scope is not established.
ACR AI Central provides an exact-submission model card for QUIBIM Precision Prostate (qp-Prostate); FDA labeling remains controlling for clinical use, limitations, and performance.
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
25Fields reviewed
10Source 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, acr ai central product, fda device recall, literature index, trial registry, fda decision summary packet, 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 K203582 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
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.
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.
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.
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.
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.