Device type · MUD
Oximeter, Tissue Saturation
Last checked: Nov 19, 2026Source: openFDAMethods & limitations
Product code
MUD
General & Plastic Surgery
Device class
Class II
FDA decisions since 2015
37
510(k), De Novo and PMA
Adverse event reports
73
Received Nov 1, 2025 to Nov 19, 2026
How FDA classifies it
- Device type
- Oximeter, Tissue Saturation
- Product code
- MUD
- Device class
- Class II
- Review panel
- General & Plastic Surgery
- Regulation
- 21 CFR 870.2700
- Specialty
- General & Plastic Surgery
- FDA record
- Classification database entry for MUD
Latest FDA decisions
The 8 newest of 37 since 2015.
K262858 · Decided Nov 5, 2026 · 84 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
- Spectrum-2510(k)
K254129 · Decided May 22, 2026 · 151 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
K243324 · Decided Jul 17, 2025 · 267 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
K250519 · Decided Jun 26, 2025 · 125 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
K240596 · Decided Oct 16, 2024 · 226 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
- ODI-Tech510(k)
K241393 · Decided Aug 30, 2024 · 106 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
- SnapshotNIR model KD205Third-party review510(k)
K240601 · Decided Apr 2, 2024 · 29 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
- OxiplexTS200510(k)
K232385 · Decided Mar 1, 2024 · 205 days after receipt
Device type: Oximeter, Tissue Saturation (MUD) · Cardiology
Reports received
73
Received Nov 1, 2025 to Nov 19, 2026
Malfunction reports
73
100% of reports
Injury reports
0
0.0% of reports
Death reports
0
0.0% of reports
Adverse event reports received per month
By the date FDA received each report, stacked by event type. The newest month is incomplete.
- Malfunction
- Injury
- Death
- Other
View as table
| Month | Malfunction | Injury | Death | Other |
|---|---|---|---|---|
| Dec 23 | 3 | 1 | 1 | 0 |
| Jan 24 | 23 | 2 | 0 | 0 |
| Feb 24 | 11 | 0 | 0 | 0 |
| Mar 24 | 6 | 0 | 0 | 0 |
| Apr 24 | 13 | 0 | 0 | 0 |
| May 24 | 4 | 0 | 0 | 0 |
| Jun 24 | 2 | 0 | 0 | 0 |
| Jul 24 | 7 | 2 | 0 | 0 |
| Aug 24 | 15 | 0 | 0 | 0 |
| Sep 24 | 2 | 0 | 0 | 0 |
| Oct 24 | 5 | 1 | 0 | 0 |
| Nov 24 | 40 | 0 | 0 | 0 |
| Dec 24 | 7 | 0 | 0 | 0 |
| Jan 25 | 7 | 0 | 0 | 0 |
| Feb 25 | 11 | 0 | 0 | 0 |
| Mar 25 | 7 | 0 | 0 | 0 |
| Apr 25 | 7 | 0 | 0 | 0 |
| May 25 | 74 | 0 | 0 | 0 |
| Jun 25 | 5 | 0 | 1 | 0 |
| Jul 25 | 6 | 0 | 0 | 0 |
| Aug 25 | 3 | 0 | 0 | 0 |
| Sep 25 | 1 | 0 | 0 | 0 |
| Oct 25 | 3 | 0 | 0 | 0 |
| Nov 25 | 5 | 0 | 0 | 0 |
| Dec 25 | 3 | 0 | 0 | 0 |
| Jan 26 | 0 | 0 | 0 | 0 |
| Feb 26 | 4 | 0 | 0 | 0 |
| Mar 26 | 4 | 0 | 0 | 0 |
| Apr 26 | 3 | 0 | 0 | 0 |
| May 26 | 6 | 0 | 0 | 0 |
| Jun 26 | 4 | 0 | 0 | 0 |
| Jul 26 | 4 | 0 | 0 | 0 |
| Aug 26 | 32 | 0 | 0 | 0 |
| Sep 26 | 6 | 0 | 0 | 0 |
| Oct 26 | 2 | 0 | 0 | 0 |
| Nov 26 | 0 | 0 | 0 | 0 |
Manufacturers named most often
Last 12 months. Bigger sellers get more reports. This is not a ranking of safety.
- Masimo10
Device problems as coded
Last 12 months. FDA's terms. A report can carry several.
- Incorrect Measurement42
- Low Readings10
- Device Alarm System8
- Incorrect, Inadequate or Imprecise Result or Readings8
- High Readings5
- Failure to Analyze Signal4
- Patient Device Interaction Problem4
- Human-Device Interface Problem2
- Inaccurate Information2
- Temperature Problem2
Patient problems as coded
Last 12 months. FDA's terms. A report can carry several.
- No Clinical Signs, Symptoms or Conditions62
- Insufficient Information10
- Superficial (First Degree) Burn3
- Skin Discoloration1
- Swelling/ Edema1
Recent recalls
From FDA's recall database. FDA lists each recalled product separately, so one recall can appear several times. A recall is often a correction or a labeling change, not a removal from the market.
Z-3250-2026 · Started Aug 11, 2026 · Posted by FDA Sep 21, 2026
Reason given: Due to incorrect switching of Channel 1 and 2 on the module and flag labels on the tissue oximetry cables.
Cause as FDA categorized it: Labeling mix-ups
Z-1731-2024 · Started Jan 9, 2024 · Posted by FDA Apr 30, 2024
Reason given: manufacturing defects to sensor cable connectors may result in error codes or non-functioning channel
Cause as FDA categorized it: Process design
Z-1732-2024 · Started Jan 9, 2024 · Posted by FDA Apr 30, 2024
Reason given: manufacturing defects to sensor cable connectors may result in error codes or non-functioning channel
Cause as FDA categorized it: Process design
- Snapshot NIR, REF: KD204Open, Classified
Z-0789-2024 · Started Oct 30, 2023 · Posted by FDA Jan 25, 2024
Reason given: Tissue oxygenation measurement system touchscreens may be unresponsive, which may prevent the viewing of oxygenation images.
Cause as FDA categorized it: Nonconforming Material/Component
- FORE-SIGHT ELITE Absolute Tissue Oximeter, REF: 01-06-3000, Contents: Monitor 1 EA., Accessory Kit 1 EA.Open, Classified
Z-0834-2022 · Started Mar 1, 2022
Reason given: The StO2 values may be inaccurately low when using either the FORE-SIGHT ELITE Tissue Oximeter Module or the FORE-SIGHT ELITE Absolute Tissue Oximeter Monitor with the Fore-Sight Elite large sensor in certain somatic locations (arms and legs). While the StO2 absolute values are impacted, the directional trend remains...
Cause as FDA categorized it: Software in the Use Environment
- FORE-SIGHT ELITE Tissue Oximeter module, REF: HEMFSM10Open, Classified
Z-0835-2022 · Started Mar 1, 2022
Reason given: The StO2 values may be inaccurately low when using either the FORE-SIGHT ELITE Tissue Oximeter Module or the FORE-SIGHT ELITE Absolute Tissue Oximeter Monitor with the Fore-Sight Elite large sensor in certain somatic locations (arms and legs). While the StO2 absolute values are impacted, the directional trend remains...
Cause as FDA categorized it: Software in the Use Environment
Z-0458-2010 · Started Oct 23, 2009 · Posted by FDA Nov 25, 2009
Reason given: A malfunction was detected with one of the components that, under rare circumstances, may result in the overheating of the POD. This overheating, while unlikely to occur, has the potential to cause a burn if the POD is in direct contact with the patient.
Cause as FDA categorized it: Device Design
For information only. Nothing on this page is investment, legal, tax or medical advice, and nothing here is an offer to sell or a solicitation of an offer to buy any security. The data comes from public government sources, which can be incomplete, delayed or wrong. Check the original record before relying on it.