Authorized purpose: Transpara version 1.5 is a concurrent screening full-field digital mammography aid that presents suspicious-region marks and scores for physician review and cannot be used as the sole basis for interpretation.
Clinical role
Breast image acquisition, reconstruction, density assessment, or computer-aided interpretation support.
Images and patients
Mammography/DBT · Breast
Key limitation
Keep in mind: Patient management decisions should not be made solely on the basis of analysis by Transpara. Transpara is an adjunct tool and not intended to replace a physicians' own review of a mammogram.
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: Transpara version 1.5 is a concurrent screening full-field digital mammography aid that presents suspicious-region marks and scores for physician review and cannot be used as the sole basis for interpretation.
Which images or clinical context are in scope?Modality: Mammography/DBT Anatomy or clinical context: Breast Input: Transpara is configured as a DICOM node and receives its input images from another DICOM node, such as a mammography device or a PACS archive.
Who uses it?Intended users: Physicians qualified to read screening mammograms.
What does the software produce?Output: Output of the device includes marks placed on suspicious soft tissue lesions and suspicious calcifications; region-based scores, displayed upon the physician's query, indicating the likelihood that cancer is present in specific regions; and an overall score indicating the likelihood that cancer is present on the mammogram.
What is its most important limitation?Key limitation: Patient management decisions should not be made solely on the basis of analysis by Transpara. Transpara is an adjunct tool and not intended to replace a physicians' own review of a mammogram.
Clinical takeaway. Clinical role: Transpara version 1.5 is a concurrent screening full-field digital mammography aid that presents suspicious-region marks and scores for physician review and cannot be used as the sole basis for interpretation.
Evidence takeaway. Evidence from the reviewed source record: K192287 reports multicenter, multivendor validation and references predicate reader evidence for version 1.5; it is not a sole-reading device.
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
Transpara version 1.5 is a concurrent screening full-field digital mammography aid that presents suspicious-region marks and scores for physician review and cannot be used as the sole basis for interpretation.
Exact FDA submission
Checked 2026-09-19
Clinical-use display mirrors the exact FDA-supported purpose reconciled from the decision-summary packet.
Output of the device includes marks placed on suspicious soft tissue lesions and suspicious calcifications; region-based scores, displayed upon the physician's query, indicating the likelihood that cancer is present in specific regions; and an overall score indicating the likelihood that cancer is present on the mammogram.
Exact FDA submission
Checked 2026-09-19
The exact indications support marks and region/overall scores; reconstructed images, density measures, and categories are not stated.
Patient management decisions should not be made solely on the basis of analysis by Transpara. Transpara is an adjunct tool and not intended to replace a physicians' own review of a mammogram.
Exact FDA submission
Checked 2026-09-19
This uses the packet's explicit non-sole-basis and adjunct warnings rather than the dossier's generalized image/view/population limitations.
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
K192287 reports multicenter, multivendor validation and references predicate reader evidence for version 1.5; it is not a sole-reading device.
Sensitivity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
Reported specificity
Not applicable
Not applicable
Not applicable
Checked 2026-09-03
Specificity is not the primary endpoint for this acquisition, reconstruction, segmentation, guidance, or quantitative function. Use the task-specific evidence below.
No contextualized exact-version metric has completed evidence review. Regulatory-document values, when available, are shown above with their limitations.
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 K192287 by exact submission identifier. This does not exclude product-family or later safety information.
Public source
Exact FDA submission
Checked 2026-09-03
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, procedural, or surgical service line and verify payer, site-of-service, and coding 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: Transpara is configured as a DICOM node and receives its input images from another DICOM node, such as a mammography device or a PACS archive.
Scope: Exact FDA submission. The exact packet specifies DICOM-node input from a mammography device or PACS archive and does not support DBT input for this submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Source context, not route validation: Validate supported acquisition systems, image type and processing, DICOM transfer, hanging protocols, display requirements, result presentation, and archive retention.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Source context, not route validation: Output of the device includes marks placed on suspicious soft tissue lesions and suspicious calcifications; region-based scores, displayed upon the physician's query, indicating the likelihood that cancer is present in specific regions; and an overall score indicating the likelihood that cancer is present on the mammogram.
Scope: Exact FDA submission. The exact indications support marks and region/overall scores; reconstructed images, density measures, and categories are not stated.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Unresolved route: Output of the device includes marks placed on suspicious soft tissue lesions and suspicious calcifications; region-based scores, displayed upon the physician's query, indicating the likelihood that cancer is present in specific regions; and an overall score indicating the likelihood that cancer is present on the mammogram.
Scope: Exact FDA submission. The exact indications support marks and region/overall scores; reconstructed images, density measures, and categories are not stated.
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.
Validate supported acquisition systems, image type and processing, DICOM transfer, hanging protocols, display requirements, result presentation, and archive retention.
ScreenPoint Medical's security reporting page states its security program is aligned with ISO/IEC 27001 and describes a vulnerability reporting channel for Transpara. It states alignment, not certification; no controls are listed. Vendor-wide.
Vendor-wide
Checked 2026-10-25
Vendor statement, not an attestation; exact-release scope is not established.
Only qualified breast-imaging technologists and interpreting physicians. should operate or interpret the product. Local onboarding should cover the exact release, supported population, limitations, failure examples, escalation, downtime, and competency documentation.
Monitor by exact hardware, software and model 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: Results are adjunctive and cannot serve as the sole basis for interpretation, diagnosis, or management; image type, vendor, view, and population limits apply.
Validate supported acquisition systems, image type and processing, DICOM transfer, hanging protocols, display requirements, result presentation, and archive retention.
exact submission · checked 2026-09-03
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. Results are adjunctive and cannot serve as the sole basis for interpretation, diagnosis, or management; image type, vendor, view, and population limits apply.
exact submission · checked 2026-09-03
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-03
Vendor productivity claims are scenario inputs, not guaranteed local savings.
Monitor by exact hardware, software and model 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: Results are adjunctive and cannot serve as the sole basis for interpretation, diagnosis, or management; image type, vendor, view, and population limits apply.
exact submission · checked 2026-09-03
Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
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.
The exact K192287 packet is for screening mammograms from compatible FFDM systems; it does not support the dossier's DBT extension. Controlled directory display reconciled from exact FDA wording: Full-field digital mammography (FFDM). -> Mammography/DBT.
This audit distinguishes completed source review from fields that have not yet been researched.
Exact FDA record reviewedStatus
2026-09-20Last searched
27Fields reviewed
14Source classes checked
18Screened PubMed leads
6Screened trial leads
0Unreviewed FDA recall leads
The refreshed discovery snapshot contains 18 PubMed and 6 ClinicalTrials.gov candidate records. 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 18 PubMed and 6 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, vendor documentation, fda decision material, vendor product page, reimbursement policy, fda device recall, fda decision summary packet, 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-03 - Exact FDA submission
No public list price for the exact cleared configuration was found. Obtain a written quote separating hardware or license basis, enabled features, implementation, interfaces, infrastructure, training, service, upgrades, renewal, consumables, and exit costs.
Authorized purpose: Flags calcifications, masses, asymmetries and architectural distortions on compatible FFDM or DBT screening examinations; management must not be based solely on MammoScreen output.
Authorized purpose: Tags screening cases as suspicious or blank to aid worklist prioritization; radiologists must review every examination and it does not mark original images.
Authorized purpose: Lunit INSIGHT MMG v1.1.10 aids physicians in detection, localization and characterization of suspicious breast-cancer areas on female screening mammograms from compatible FFDM systems, viewed after the physician's initial read as an adjunct to complete clinical interpretation.
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.