Lesion-level sensitivity
0.686 proportion
- EndpointLesion-level caries sensitivity
- PopulationStandalone evaluation of 400 deidentified bitewing radiographs containing 481 caries lesions
- Tested versionSugarBug 1.x; FDA submission K250264
FDA-cleared profile
Bench7, Inc. · X-ray/Radiography · FDA-cleared (510(k))
Authorized purpose: Provides automated concurrent-read detection and segmentation of caries on bitewing radiographs in patients 18 and older, adding information for the dentist while requiring complete dentist review and judgment.
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: Provides automated concurrent-read detection and segmentation of caries on bitewing radiographs in patients 18 and older, adding information for the dentist while requiring complete dentist review and judgment.
Evidence takeaway. Evidence from the reviewed source record: Study type: Both. Cases: 400. Reported sensitivity: 68.6% (95% CI: 65.5%, 71.7%). Reader-study cases: 300. Readers: 12. Reader-study sensitivity: 67.4% (95% CI: 61.5%, 72.8%)
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.
Exact clinical-use normalization from the FDA packet; this text is also the locked corrections value.
Packet wording: "SugarBug is a radiological, automated, concurrent read, computer-assisted detection software intended to aid in the detection and segmentation of caries on bitewing radiographs." … "uses machine learning to label features that the reader should examine for evidence of decay.". Read from the exact FDA decision document on 2026-11-14.
Packet wording: "caries on bitewing radiographs. The device provides additional information for the dentist to use in their diagnosis of a tooth surface suspected of being carious. Sugarbug is intended to be used on patients 18 years and older." … "Sugarbug processes screen captures as opposed to image file input". Read from the exact FDA decision document on 2026-11-14.
Clinical output reported in the exact-submission ACR model card.
Patient-population text reported in the exact-submission ACR model card; institutional setting may still require vendor confirmation.
Intended-user text reported in the exact-submission ACR model card.
Exact-product limitations and clinician-review boundary from the FDA packet.
Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.
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.
Structured study metadata from the exact-submission ACR model card; this is not an independent evidence synthesis.
Model sensitivity reported by ACR AI Central. Review endpoint, threshold, study population, and tested version before comparison.
This field has not been curated yet.
0.686 proportion
K250264
ACR AI Central summarizes the regulatory study; consult the exact FDA materials before comparative use.
Safety and lifecycle
Recall and adverse-event records are shown only after product matching. Adverse-event reports do not establish incidence or causality.
No native submission-identifier match was found in the checked openFDA radiology recall snapshot. Product-name, manufacturer, and adverse-event searches remain necessary; this does not establish that no recall or safety report exists.
Price not public here; enter your quote
Pricing is recorded, but no exact-product procurement price with a stated offer scope is published in the reviewed sources.
Narrative vendor offer retained without normalizing the dollar symbol into a structured currency field.
Original Medicare dental-service exclusion applies to routine dental care; dental plan and private payer treatment not reviewed
Medicare (Original Medicare, CMS) · United StatesService-level exclusion from the CMS dental coverage page; it does not address this product by name and does not establish coverage or payment by dental plans or other payers.
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: Bitewing radiographs of patients 18 years and older, taken in as screen captures rather than image file input; the device can process images of 300 pixel resolution.
Scope: Exact FDA submission. Packet wording: "caries on bitewing radiographs. The device provides additional information for the dentist to use in their diagnosis of a tooth surface suspected of being carious. Sugarbug is intended to be used on patients 18 years and older." … "Sugarbug processes screen captures as opposed to image file input". Read from the exact FDA decision document on 2026-11-14.
Confirm scanner/model, protocol, series completeness and both software builds.
Field checked 2026-11-14 · FDA 510(k) decision material K250264: SugarBug (1.x)
Source context, not route validation: The exact FDA package describes SugarBug processing screen captures as opposed to image file input, reading the selected image with local processing; images are not imported or sent to a cloud server during routine use. Interface versions and local compatibility require confirmation.
Scope: Exact FDA submission. Packet wording: "Different processing input - Sugarbug processes screen captures as opposed to image file input" … "The software reads the selected image using local processing; images are not imported or sent to a cloud server any time during routine use.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
Name gateways, destinations, transfer rules and failure visibility; a DICOM statement does not prove a route.
Field checked 2026-11-14 · FDA 510(k) decision material K250264: SugarBug (1.x)
Source context, not route validation: Local processing during routine use; the FDA summary states that images are not imported or sent to a cloud server.
Scope: Exact FDA submission. Exact FDA packet routine-use processing description; current enterprise host configuration still requires confirmation.
Confirm processing location, queue ownership, exclusions and exact AI build.
Field checked 2026-09-06 · FDA 510(k) decision material K250264: SugarBug (1.x)
Source context, not route validation: The AI model performs semantic segmentation on bitewing radiographs, assigning a probability value to each pixel for the possibility that it contains decay. A threshold is applied to determine which pixels are labeled in the output. The device outputs labeled regions indicating areas suspected of caries (decay) to aid the dentist in diagnosis.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
Confirm object classes, units, references and whether findings, overlays or measurements reach their intended destination.
Field checked 2026-09-01 · SugarBug (1.x) model card (K250264)
Unresolved route: The AI model performs semantic segmentation on bitewing radiographs, assigning a probability value to each pixel for the possibility that it contains decay. A threshold is applied to determine which pixels are labeled in the output. The device outputs labeled regions indicating areas suspected of caries (decay) to aid the dentist in diagnosis.
Scope: Exact FDA submission. Clinical output reported in the exact-submission ACR model card.
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-01 · SugarBug (1.x) model card (K250264)
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.
Exact FDA packet routine-use processing description; current enterprise host configuration still requires confirmation.
Packet wording: "Different processing input - Sugarbug processes screen captures as opposed to image file input" … "The software reads the selected image using local processing; images are not imported or sent to a cloud server any time during routine use.". Read from the exact FDA decision document on 2026-11-14; this is the release-level description, not current commercial configuration.
The vendor says Sugarbot Detect runs on the desktop, works with existing imaging software without an integration, and can be installed in less than 15 minutes.
product family · checked 2026-09-07Vendor product page; verify exact commercial mapping to SugarBug (1.x).
The vendor says images are processed on-device without cloud upload or an internet connection during the advertised workflow.
product family · checked 2026-09-07Vendor claim only; security, retention, and enterprise controls were not established.
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.
Imaging modality reported in the exact-submission ACR AI Central model card.
Anatomy normalized from explicit exact-submission ACR model-card wording.
Research record
This audit distinguishes completed source review from fields that have not yet been researched.
Stored exact-submission candidate metadata had zero PubMed and ClinicalTrials.gov identifiers; this metadata screening is not a full paper or registry-record review. 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, vendor product page, vendor pricing observation, literature index, trial registry, payer policy, 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.
FDA authorization does not establish the current commercial security posture. Request data-flow diagrams, hosting and retention details, access controls, audit logging, attestations, and incident-response documentation.
Training, onboarding, competency, and support commitments are commercial implementation details that require current vendor documentation.
Local acceptance testing, production monitoring, drift review, update control, and incident escalation require a current vendor and site-specific governance plan.
10 sources - 3 history items
Scope: regulatoryIdentity, purpose, modality, anatomy
Scope: regulatoryIdentity, modalityContext
Scope: purpose, modality, intendedUsers, careSetting, output, reportedSensitivity, evidenceSummary, anatomy, evidenceStudies
Scope: evidenceDiscovery
Scope: evidenceDiscovery, studyStatus
Scope: recallDiscovery, nativeSubmissionMatching
Scope: identity, clinical, evidence, implementation, integration
Scope: buyer_workflow, implementation, clinical
Scope: pricing, implementation
Scope: reimbursement, payerPolicy
Regulatory record
510(k)
Research record
human reviewed
Editorial review
Source-reviewed editorial overlay
Alternatives
Pearl Inc.
Authorized purpose: Acts as a CADe second reader to detect and segment caries on periapical radiographs of permanent teeth in patients aged 12 years and older; clinicians review the contours and percentage analysis in context.
Cube Click, Inc.
Authorized purpose: Aids dentists reviewing bitewing and periapical radiographs of permanent teeth by detecting/segmenting caries and periapical radiolucencies, identifying restorations and dental anatomy, and measuring mesial/distal bone levels; it does not replace dentist review.
Nobel Biocare C/O Medicim NV
Authorized purpose: Analyzes two-dimensional bitewing and periapical radiographs of permanent teeth in patients aged 15 and older to identify and localize caries, calculus, periapical radiolucency, root canal filling deficiency, discrepancy at an existing restoration margin, and bone loss; also supports alveolar bone-level measurement and restoration/dental-anatomy segmentation as an adjunct to dentist review.
Velmeni Inc.
Authorized purpose: Assists dentists in detecting caries, fillings/restorations, fixed prostheses, and implants on digital bitewing, periapical, and panoramic radiographs of permanent teeth in patients aged 15 years and older; final diagnoses and treatment plans remain the dentist's responsibility.
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