FFDM BAC sensitivity
0.96 proportion
- EndpointStudy-level and breast-level BAC detection sensitivity
- PopulationRetrospective blinded multicenter standalone study of screening FFDM
- Tested versionBAC
FDA-cleared profile
DeepHealth, Inc. · Mammography/DBT · FDA-cleared (510(k))
Authorized purpose: BAC processes screening FFDM and DBT mammograms to detect the presence or absence of breast arterial calcifications at study and breast level and localize detected calcifications for qualified interpreting-physician review.
Overview status: Source-reviewed overview
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
Clinical takeaway. Clinical role: BAC processes screening FFDM and DBT mammograms to detect the presence or absence of breast arterial calcifications at study and breast level and localize detected calcifications for qualified interpreting-physician review.
Evidence takeaway. Evidence from the reviewed source record: The FDA package reports a retrospective blinded multicenter standalone study of 850 FFDM and 925 DBT images from 37 U.S. sites, with modality-specific sensitivity and specificity values recorded in this dossier.
Evidence context not reviewed for this FDA record.
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.
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.
0.96 proportion
0.884 proportion
0.905 proportion
0.906 proportion
K254131
The FDA material reports 850 FFDM images and 925 DBT images from 37 U.S. sites, with 150/700 FFDM and 169/756 DBT positive/negative cases. These are manufacturer-sponsored retrospective performance results, not independent prospective outcome evidence.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
Price not public here; enter your quote
Not publicly available: Reviewed sources do not publish an exact-product procurement price with a stated offer scope.
No separate named-product payment identified in reviewed CMS material
Centers for Medicare & Medicaid Services · United StatesThis is not a product-specific reimbursement determination. Verify payer, site-of-service, coding, and coverage assumptions independently.
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.
Source context, not route validation: Screening full-field digital mammography and digital breast-tomosynthesis studies.
Scope: Exact FDA submission.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-09-04 · FDA 510(k) decision material K254131: BAC
Source context, not route validation: The FDA package describes processing of FFDM and DBT studies and localized outputs; exact DICOM, PACS, worklist, and image-return routing require local testing.
Scope: Exact FDA submission.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-09-04 · FDA 510(k) decision material K254131: BAC
Unresolved route: Not established for the exact route.
Scope: Exact FDA submission. The exact installed deployment, hosting, service, and operational boundary is not established by the reviewed public FDA material.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-04 ·
Source context, not route validation: Study- and breast-level presence or absence of breast arterial calcification with localized image findings for review.
Scope: Exact FDA submission.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-04 · FDA 510(k) decision material K254131: BAC
Unresolved route: Study- and breast-level presence or absence of breast arterial calcification with localized image findings for review.
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-04 · FDA 510(k) decision material K254131: BAC
Unresolved route: Not established for the exact route.
Scope: Scope not established.
Name the local, platform and AI supplier support owners and escalation path.
No tests below have been performed or accepted.
Agree the evidence and acceptance owner with your team and suppliers. Checkmarks apply to this page only and are not acceptance receipts.
Map the installed product, build, options, population, anatomy, inputs, outputs, and enabled functions to K254131 before acceptance.
exact submission · checked 2026-09-04Later product-family features are not evidence that this cleared release includes them.
The exact installed deployment, hosting, service, security, and operational boundary remains unverified and requires site-specific confirmation.
exact submission · checked 2026-09-04FDA-described deployment details do not establish current hosting contracts, security controls, uptime, or local qualification.
The FDA package describes processing of FFDM and DBT studies and localized outputs; exact DICOM, PACS, worklist, and image-return routing require local testing.
exact submission · checked 2026-09-04Test 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. The software is an adjunct and not a primary breast-cancer interpretation or standalone diagnosis or treatment tool. Qualified physicians must review the complete study and account for acquisition and image-quality limits.
exact submission · checked 2026-09-04Define 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, infrastructure, training, service, downtime, upgrade, and replacement costs.
product family · checked 2026-09-04No exact-product price or product-specific reimbursement was established in the reviewed public material.
Monitor K254131 by exact software, hardware, 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: The software is an adjunct and not a primary breast-cancer interpretation or standalone diagnosis or treatment tool. Qualified physicians must review the complete study and account for acquisition and image-quality limits.
exact submission · checked 2026-09-04Revalidate after material software, hardware, model, protocol, interface, or clinical-policy changes.
Regulatory identity
The FDA listing establishes the regulatory identity. It does not by itself establish local workflow fit, pricing, security, or performance in your environment.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
Screened 20 PubMed titles and 10 trial records. Most are unrelated BAC acronym matches; the breast arterial-calcification papers do not identify DeepHealth BAC, K254131, or its tested release. All 30 are quarantined. The current discovery snapshot contains 20 PubMed and 10 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, acr ai central product, fda decision material, peer reviewed literature, clinical trial registry, reimbursement policy, fda device recall, pubmed, clinical trials, openfda device recall
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.
No public list price for the exact cleared product version was established. Obtain a written quote separating license, implementation, interfaces, compute, storage, training, support, upgrades, renewal, and exit costs.
The exact installed deployment, hosting, service, and operational boundary is not established by the reviewed public FDA material.
The FDA decision material does not establish the complete security posture for the exact product and deployment. Obtain architecture, identity, audit, encryption, retention, support-access, vulnerability-management, and incident-response evidence.
7 sources - 3 history items
Scope: identity, purpose, clinicalUse, modality, anatomy, intendedUsers, careSetting, workflowRole, input, output, limitations, evidenceSummary
Scope: regulatoryIdentity, modalityContext
Scope: intendedUsers, careSetting, output, limitations, reportedSensitivity, reportedSpecificity, evidenceSummary, anatomy, evidenceStudies
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: coverage, codingContext
Scope: recallDiscovery, nativeSubmissionMatching
Regulatory record
510(k)
Research record
fda record reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
CureMetrix, Inc.
Authorized purpose: cmAngio processes screening FFDM and DBT mammograms to detect presence or absence of breast arterial calcifications at study and breast level and mark segments for qualified interpreting-physician review; it is not primary breast-cancer interpretation or a standalone diagnostic or treatment decision tool.
DeepHealth, Inc.
Authorized purpose: Concurrent detection and characterization support for screening DBT mammography
Lunit, Inc.
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.
Lunit, Inc.
Authorized purpose: Concurrent CADe/x aid for interpreting physicians to detect and characterize breast-cancer-suspicious lesions in screening DBT exams from compatible systems, marking soft-tissue lesions and calcifications with abnormality scores.
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 destinationPermission 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.
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