Testing precedent from 510(k) summaries

See the performance, safety and software testing that recent clearances in your product code submitted, which standards they tested to, and how they reported results, so your test plan matches what FDA already accepted.
Updated Oct 12, 2026

The problem

Test plans are expensive to get wrong. Under-test and you get an Additional Information request; over-test and you burn months and budget. The evidence for what FDA expects is in hundreds of 510(k) summaries, and most teams only read the handful they already know.

How Bearnier AI does it

  1. 1

    Name the device and code

    Describe the device or enter its product code. Bearnier AI gathers every recent clearance under it.

  2. 2

    See the testing side by side

    Bearnier AI lists the bench, software, biocompatibility, electrical safety and clinical testing each summary describes, with the page behind every row.

  3. 3

    Turn it into a plan

    Export the comparison to Word as the starting point for your test plan or the testing summary in your submission.

Questions to try

Pick one to run it, or write your own.

US FDA devices: 510(k), De Novo, guidance, 21 CFR

A finished answer

What predicates have recent AI triage devices cited, and what testing did FDA expect?

Cited 7 sources · counted 88 FDA records
  1. Mapping the question to product code QAS
  2. Reading 88 records under 21 CFR 892.2080
  3. Opening De Novo decision summary DEN170073
  4. Opening 510(k) summaries K261085, K260729 and K261317
  5. Extracting predicates and standalone performance

AI triage devices are cleared under product code QAS, a Class II device regulated at 21 CFR 892.2080 , with 88 510(k) records in openFDA . The category was created by De Novo DEN170073, Viz.ai’s ContaCT .

Recent submitters cite an earlier cleared triage device, not the De Novo. K261085, iSchemaview’s Rapid VO, cleared Jul 13, 2026 , flags suspected large vessel occlusion on adult head CTA and names the company’s own Rapid CTA 360, K251151 . K260729, GuideAI Health’s VAOT, cleared Jun 18, 2026 , names Aidoc’s BriefCase LVO Triage, K220709 , although VAOT flags occlusions in the aorta and the iliac, femoral and popliteal arteries . Aidoc’s own Special 510(k), K261317, also names K220709 .

FDA accepted standalone performance on a few hundred multi-site cases, reported as sensitivity and specificity with 95% confidence intervals, plus time to notification:

  1. K261085: 314 CTA cases from 33 clinical sites (99.0% US), 282 evaluable with 113 positive and 169 negative . Sensitivity 0.956 (95% CI 0.901–0.981), specificity 0.905 (95% CI 0.852–0.941), mean time to notification 3.2 to 3.3 minutes
  2. K260729: 317 cases from US sites, 165 positive and 152 negative . Sensitivity 0.915 (95% CI 0.862–0.953), specificity 0.901 (95% CI 0.842–0.944), time to notification under 5 minutes

In both, ground truth came from three board-certified radiologists by majority vote .

13 citations
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Open
Follow your product codeGet an email when FDA clears a device whose testing you should know about.

Know what FDA already cleared.