510(k) Report

510(k) · Cleared

Cleared

Oxiscan II Data Management System

K080348510(k) TraditionalCleared Oct 9, 2008241-day reviewClass II21 CFR 870.2700

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

Airsep Corp. · DQA Oximeter

Cleared on Oct 9, 2008 as substantially equivalent to K033307 (Nonin Medical, Inc., 2004) after a 241-day review. Its family tree reaches back 3 generations to 1991.

Decided
Oct 9, 2008
Review
241 days
Class
Class II
Product code
DQA
Recalls
None
Predicates
1

Its longest line of descent runs back 3 generations to K913695 (1991). 4 ancestors in all. No later device cites it as a predicate yet.

  1. Root · 3 generations backK913695 Nellcor (R) N-180 Pulse OximeterNellcor, Inc. · 1991
  2. 2 generations backK961450 Score SoftwareNellcor Puritan Bennett, Inc. · 1996
  3. 1 generation backK033307 Nvision Data Management SoftwareNonin Medical, Inc. · 2004
  4. This deviceK080348 Oxiscan II Data Management SystemAirsep Corp. · 2008
View FIG. 1 as a table

Line of descent and top descendants

GenerationNumberDeviceApplicantDecidedRecalls
−3K913695Nellcor (R) N-180 Pulse OximeterNellcor, Inc.1991—
−2K961450Score SoftwareNellcor Puritan Bennett, Inc.1996—
−1K033307Nvision Data Management SoftwareNonin Medical, Inc.2004—
0 (this device)K080348Oxiscan II Data Management SystemAirsep Corp.2008—

Other ancestors by year cleared

Year clearedDevicesWith a Class I recall
200110
FIG. 1 — Lineage of K080348, 1991–2008Source: 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 DQA? 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 DQA device

  1. #1 K221282 Empatica Health Monitoring Platformscore 20.1 · 38 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
*K033307Nvision Data Management Software
Summary page 1
…ftware is substantially equivalent to Nonin Medicals "InVISION" software (K033307) Device Description: OxiScan 11 Oximetry Data Management Software is an…
Nonin Medical, Inc.2004—

Also cleared against K033307: 2 other devices →

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 17 years and passes through 4 companies; a new generation was cleared every 4.7 years on median.
  • None of the 4 ancestors has a recall.
  • 2 other devices also cite its predicate K033307.

How does its category compare?

All DQA devices

DQA Oximeter: FDA decisions, review times, recalls and adverse event reports over 20 years. 2008, this device’s year, is highlighted.

FDA decisions per year · DQA

15in 2025

2007: 202008: 222009: 352010: 292011: 152012: 142013: 152014: 112015: 132016: 142017: 92018: 182019: 192020: 152021: 102022: 202023: 132024: 142025: 152026 (partial year): 8
2007high 35 (2009) · low 9 (2017)2026

2026 to Oct 25, outlined.

Median 510(k) review, days · DQA

182in 2025

2007: 122 days median2008: 97 days median2009: 117 days median2010: 127 days median2011: 195 days median2012: 120 days median2013: 182 days median2014: 175 days median2015: 158 days median2016: 246 days median2017: 200 days median2018: 260 days median2019: 158 days median2020: 126 days median2021: 174 days median2022: 265 days median2023: 317 days median2024: 285 days median2025: 182 days median2026 (partial year): 187 days median
2007high 317 (2023) · low 97 (2008)2026

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

Recalls per year · DQA

3in 2024

2007: 62008: 52009: 292010: 42011: 12014: 22015: 12018: 322024: 3
2007high 32 (2018) · low 0 (2012)2026

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

Adverse event reports per year · DQA

399in 2025

2007: 3252008: 3122009: 2812010: 1852011: 1642012: 3222013: 4682014: 1,1242015: 2,0822016: 1,7752017: 1,1902018: 6942019: 5482020: 4262021: 5532022: 4782023: 3922024: 5452025: 399
2007high 2,082 (2015) · low 164 (2011)2025

MAUDE reports naming product code DQA, 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
2007201226325
200822975312
20093511729281
2010291274185
2011151951164
2012141200322
2013151820468
20141117521,124
20151315812,082
20161424601,775
2017920001,190
20181826032694
2019191580548
2020151260426
2021101740553
2022202650478
2023133170392
2024142853545
2025151820399
202681870—

What is it indicated for?

OxiScan II Oximetry Data Management Software (OxiScan II) is a central server based software system that uses a personal computer based application written in Microsoft Dot Net protocol to capture oximetry data from an oximeter, and then transmit this data, in a secure encrypted file, via internet, to the central server. At the central server the data is used to render a standard report that is then transmitted via fax and/or email to the prescribing…

Read the full statement (248 words)

OxiScan II Oximetry Data Management Software (OxiScan II) is a central server based software system that uses a personal computer based application written in Microsoft Dot Net protocol to capture oximetry data from an oximeter, and then transmit this data, in a secure encrypted file, via internet, to the central server. At the central server the data is used to render a standard report that is then transmitted via fax and/or email to the prescribing physician. The intended use of the report is to provide a physician with information to help determine the best pulmonary treatment.

The OxiScan I1Oximetry Data Management Software is intended to collect, report and archive oximetry trend data to provide information to a medical professional, as a supplemental tool to assist in the timely identification of pulmonary needs.

The OxiScan II Oximetry Data Management Software is intended to (1) transfer oximetry data from a pulse oximeter to a central server data base in order to maintain unique records per patient and test of this pulse oximetry data, and (2) to generate and archive standard reports drawn from this data. A list of approved oximeters appears in the Capture software.

The OxiSean IL Oximetry Data Management Software is not a diagnosis tool. It is a decision management support tool that allows medical personnel to securely and accurately upload and view data related to pulse oximetry and to provide output reports as feedback which may be used by a Heathcare professional to form a patient history.

Indications for use as stated in the FDA summary.

Cite this page

510(k) Report. “K080348: Oxiscan II Data Management System.” Lineage record from FDA 510(k) data and the FDA summary. Updated Nov 3, 2026. Accessed Nov 3, 2026. https://510kreport.com/device/K080348

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