510(k) Report

510(k) · Cleared

Cleared

BoneView

K222176510(k) TraditionalCleared Mar 2, 2023223-day reviewClass II21 CFR 892.2090

Data to Oct 25, 2026 (FDA decisions) Oct 12, 2026 (recalls) Sep 30, 2026 (MAUDE) refreshed weekly, last Nov 3, 2026

Gleamer · QBS Radiological Computer Assisted Detection/Diagnosis Software For Fracture

Cleared on Mar 2, 2023 as substantially equivalent to K212365 (Gleamer, 2022) after a 223-day review. Its family tree reaches back 3 generations to 2018. 1 later device descends from it.

Decided
Mar 2, 2023
Review
223 days
Class
Class II
Product code
QBS
Recalls
None
Predicates
1

Its longest line of descent runs back 3 generations to DEN180005 (2018). 1 later device descends from it, 1 citing it directly.

Descendants, by year cleared 2025: 1 descendant clearedDEN180005 · OsteoDetect · Imagen Technologies, Inc. · 2018K193417 · FractureDetect (FX) · Imagen Technologies, Inc. · 2020K212365 · BoneView · Gleamer · 2022201620182020202220242026
Descendants, by generation 1 generation forward: 1 descendant K212365 · BoneView · Gleamer · 2022K193417 · FractureDetect (FX) · Imagen Technologies, Inc. · 2020DEN180005 · OsteoDetect · Imagen Technologies, Inc. · 20180
  1. Root · 3 generations backDEN180005 OsteoDetectImagen Technologies, Inc. · 2018
  2. 2 generations backK193417 FractureDetect (FX)Imagen Technologies, Inc. · 2020
  3. 1 generation backK212365 BoneViewGleamer · 2022
  4. This deviceK222176 BoneViewGleamer · 2023
  5. Descendant · cites it directly · 0 of its ownK242171 TechCare TraumaMilvue · 2025

Most influential descendants

Showing 1 of 1 · See all
  • K242171TechCare TraumaMilvue · 2025 · cites it directly0descendants
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−3DEN180005OsteoDetectImagen Technologies, Inc.2018—
−2K193417FractureDetect (FX)Imagen Technologies, Inc.2020—
−1K212365BoneViewGleamer2022—
0 (this device)K222176BoneViewGleamer2023—
+1K242171TechCare TraumaMilvue2025—

Descendants by year cleared

Year clearedDevicesWith a Class I recall
202510
FIG. 1 — Lineage of K222176, 2018–2025Source: FDA 510(k) summaries, read by 510(k) Report · How lineage is built

Get the monthly Device Review Tracker

Notable FDA decisions, review times and new Class I recalls. See an issue.

Sources: FDA 510(k) database (decision fields), the FDA summary (predicates and indications), FDA recall and enforcement reports, and MAUDE; processed by 510(k) Report. Verify on FDA.gov · Methodology and accuracy.

Planning a device in QBS? A 510(k) Report weighs predicate choices, recall history and review times for a new device like this one.

Top candidate predicates for a new QBS device

  1. #1 K260378 Rayvolvescore 15.2 · 4 generations · no Class I recall
  2. #2 Held for the reportin the report
  3. #3 Held for the reportin the report
Get a 510(k) Report

What was it cleared against? (1)

Devices the submitter claimed this one is substantially equivalent to (*), and reference devices cited for a specific test or feature (†), as written in the FDA summary.

TypeNumberDeviceApplicantDecidedRecalls
*K212365BoneView
Summary page 4
…CFR 892.2090 Product Code QBS Classification Class II 3. Predicate Device Predicate Device Gleamer BoneView 510(k) reference K212365 GLEAMER 5 avenue du Général de Gaulle, 94160 Sa…
Gleamer2022—

Also cleared against K212365: 1 other device →

What descends from it? (1)

1 later device cites it directly; ranked here by how many devices descend from each in turn.

NumberDeviceApplicantDecidedDescendants
K242171TechCare TraumaMilvue20250

Has anything in its family been recalled? (0 Class I)

No FDA recall names this device.

No ancestor or descendant has a Class I recall.

What does this lineage say?

  • The line of descent spans 5 years and passes through 2 companies; a new generation was cleared every 1.6 years on median.
  • None of the 3 ancestors has a recall.
  • Of its descendants, K242171 (Milvue, 2025) has gone furthest, with 0 descendants of its own.
  • 1 other device also cites its predicate K212365.

How does its category compare?

All QBS devices

QBS Radiological Computer Assisted Detection/Diagnosis Software For Fracture: FDA decisions, review times, recalls and adverse event reports over 20 years. 2023, this device’s year, is highlighted.

FDA decisions per year · QBS

3so far in 2026, the most since 2007

2018: 12020: 12022: 22023: 22024: 22025: 12026 (partial year): 3
2007high 3 (2026) · low 0 (2007)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · QBS

123in 2026

2026 (partial year): 123 days median
2007high 123 (2026)2026

Receipt to decision; years with fewer than 3 clearances left blank.

Recalls per year · QBS

No recall names QBS since 2007.

Adverse event reports per year · QBS

No MAUDE report names QBS since 2007.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
20070—00
20080—00
20090—00
20100—00
20110—00
20120—00
20130—00
20140—00
20150—00
20160—00
20170—00
20181—00
20190—00
20201—00
20210—00
20222—00
20232—00
20242—00
20251—00
202631230—

What is it indicated for?

BoneView 1.1-US is intended to analyze radiographs using machine learning techniques to identify and highlight fractures during the review of radiographs of:

Ankle, foot, knee, tibia/fibula, wrist, hand, elbow, forearm, humerus, shoulder, and clavicle in adults and children/adolescents; and pelvis, hip, femur, ribs, thoracic spine, and lumbosacral spine in adults only. Compatible radiographic views are frontal, lateral, and/or oblique views as applicable to the study type.

BoneView 1.1-US is intended for use as a concurrent reading aid during the interpretation of radiographs.

BoneView 1.1-US is for prescription use only.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K222176: BoneView.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 6, 2026. https://510kreport.com/device/K222176

Report an extraction error

Tell us what is wrong; we check it against the FDA summary.

Are you the manufacturer?

Send a correction or an update to this page, for example a newer model or a public statement about a recall.

Record history
  • FDA decision record loaded May 2, 2026
  • Summary read Oct 13, 2026 (extraction version 9eaa42aa01ed)
  • Lineage and recalls computed Nov 3, 2026
  • Page last updated Nov 3, 2026