510(k) Report

510(k) · Cleared

Cleared

ScanX Swift 2.0, ScanX Swift View 2.0

K230095510(k) SpecialCleared Feb 6, 202325-day reviewClass II21 CFR 872.1800

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

Durr Dental SE · MUH System, X-Ray, Extraoral Source, Digital

Cleared on Feb 6, 2023 as substantially equivalent to K202633 (Dürr Dental SE, 2020) after a 25-day review. Its family tree reaches back 6 generations to 1994.

Decided
Feb 6, 2023
Review
25 days
Class
Class II
Product code
MUH
Recalls
None
Predicates
1

Its longest line of descent runs back 6 generations to K934949 (1994). 7 ancestors in all. No later device cites it as a predicate yet.

  1. Root · 6 generations backK934949 DigoraOrion Corporation Soredex · 1994
  2. 5 generations backK041050 Digora Optime (or Digora Ontime)Soredex Palodex Group OY · 2004 · Recalled
  3. 4 generations backK131442 Firecr Dentalimaging System3Disc Americas · 2013
  4. 3 generations backK160788 RIOScan (RPS500)Ray Co., Ltd. · 2016
  5. 2 generations backK170733 ScanX Intraoral ViewDuerr Dental AG · 2017
  6. 1 generation backK202633 ScanX EdgeDürr Dental SE · 2020
  7. This deviceK230095 ScanX Swift 2.0, ScanX Swift View 2.0Durr Dental SE · 2023
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−6K934949DigoraOrion Corporation Soredex1994—
−5K041050Digora Optime (or Digora Ontime)Soredex Palodex Group OY20044
−4K131442Firecr Dentalimaging System3Disc Americas2013—
−3K160788RIOScan (RPS500)Ray Co., Ltd.2016—
−2K170733ScanX Intraoral ViewDuerr Dental AG2017—
−1K202633ScanX EdgeDürr Dental SE2020—
0 (this device)K230095ScanX Swift 2.0, ScanX Swift View 2.0Durr Dental SE2023—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
201410
FIG. 1 — Lineage of K230095, 1994–2023Source: 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 MUH? 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 MUH device

  1. #1 K242778 X Sensor (Model: IOS-A15IF, HDI-15DGF)score 16.0 · 7 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
*K202633ScanX Edge
Summary page 4
…stem Regulatory Class: II Product Code: MUH 3. Legally Marketed Predicate Device Information: Trade/Device Name: K202633, ScanX Edge Regulation Number: 21 CFR 872.1800 Regulation Name: Extraoral source x-ray system…
Dürr Dental SE2020—

What descends from it?

No later submission names this one as a predicate yet.

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 29 years and passes through 7 companies; a new generation was cleared every 3.4 years on median.
  • 1 of the 7 ancestors has a recall of any class.

How does its category compare?

All MUH devices

MUH System, X-Ray, Extraoral Source, Digital: FDA decisions, review times, recalls and adverse event reports over 20 years. 2023, this device’s year, is highlighted.

FDA decisions per year · MUH

3in 2025

2007: 112008: 82009: 92010: 92011: 102012: 92013: 92014: 82015: 122016: 62017: 92018: 32019: 52020: 52021: 102022: 72023: 112024: 42025: 32026 (partial year): 2
2007high 12 (2015) · low 3 (2018)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · MUH

159in 2025

2007: 48 days median2008: 64 days median2009: 88 days median2010: 174 days median2011: 89 days median2012: 81 days median2013: 172 days median2014: 168 days median2015: 111 days median2016: 47 days median2017: 84 days median2018: 29 days median2019: 64 days median2020: 36 days median2021: 80 days median2022: 57 days median2023: 57 days median2024: 144 days median2025: 159 days median
2007high 174 (2010) · low 29 (2018)2026

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

Recalls per year · MUH

1in 2015

2008: 12009: 22013: 12014: 12015: 1
2007high 2 (2009) · low 0 (2007)2026

Class I (0 since 2007) Class II/III not classified

Adverse event reports per year · MUH

1in 2025

2009: 122010: 92012: 52013: 12014: 52015: 32016: 12017: 42018: 102019: 62021: 12023: 12025: 1
2007high 12 (2009) · low 0 (2007)2025

MAUDE reports naming product code MUH, not matched to any one device; reports are not rates.

View these four charts as a table
YearDecisionsMedian 510(k) review, daysRecalls (Class I)MAUDE reports
2007114800
200886410
2009988212
2010917409
2011108900
201298105
2013917211
2014816815
20151211113
201664701
201798404
2018329010
201956406
202053600
2021108001
202275700
2023115701
2024414400
2025315901
20262—0—

What is it indicated for?

The ScanX Swift 2.0 is intended to be used for scanning and processing digital images exposed on Phosphor Storage Plates (PSPs) in dental applications.

The ScanX Swift View 2.0 is intended to be used for scanning and processing digital images exposed on Phosphor Storage Plates (PSPs) in dental applications.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K230095: ScanX Swift 2.0, ScanX Swift View 2.0.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 5, 2026. https://510kreport.com/device/K230095

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