Not Just a Number: IFU-First Safety in SpO₂ Monitoring

Pulse oximetry feels simple on the surface—attach a probe, read a number. Celeste Smith’s talk was a sharp reminder that the number is only as trustworthy as the validated system behind it. For clinical engineers, the message is practical and urgent: IFUs are regulatory evidence, not nice-to-have PDFs. When we mix and match non-validated probes or cables with a monitor, we step outside the evidence base—precisely when accuracy matters most.

The standards stack that underpins your decisions

Medical devices reach the ward only after a chain of design controls, testing and regulatory review. For SpO₂ monitoring, three anchors matter day-to-day:

• IEC/ISO 80601-2-61 (Pulse oximeter equipment). This particular standard treats the monitor + probe + any probe-cable extender as a single system and sets performance/safety requirements for that system—not for each part in isolation. Accuracy claims must be supported by controlled desaturation studies over the stated range. FDA Access DataISO
• IEC 60601-1 (general safety & essential performance) and its collaterals/particulars set the baseline for electrical/EMC safety for medical electrical equipment. VDE
• ISO 13485 (QMS for medical devices) underpins how manufacturers document design, verification/validation and post-market surveillance—the assurance behind what you read in the IFU. ISO

Taken together, these explain why the IFU lists specific, validated combinations (which sensors/cables with which monitors, and the accuracy you can expect under low perfusion, neonatal use, and low saturation).

Bottom line: if a combination isn’t in the IFU, it isn’t in the evidence—and you may be outside the accuracy envelope when the patient deteriorates.

Why “works on the bench” isn’t good enough

It’s common to see local bench checks on simulators or test sets used to justify generic probes. Smith cautioned that bench checks don’t replace clinical desaturation validation required by 80601-2-61. The problem shows up when SpO₂ falls below ~90%: a few percentage points of additional error can tip clinical decisions (escalation, oxygen, escalation triggers). The standard’s system-level validation is exactly to prevent that drift. ISO

Operator responsibility isn’t optional

IFUs are regulatory documents summarising validated performance and safe-use limits. They’re not marketing copy. They also make responsibilities explicit: users must verify compatibility of monitor, probe and cable before use; manufacturers must list the combinations they’ve validated, with performance claims backed by studies. FDA Access Data

When things still go wrong, report via the MHRA Yellow Card (medical devices route). These reports feed manufacturers’ post-market surveillance and national safety actions—closing the loop that standards expect. yellowcard.mhra.gov.ukGOV.UK

What this means for clinical engineering (do this now)

1) Make IFU compliance visible

• Publish a compatibility matrix (monitors ⇄ probes/cables/extenders) on your intranet.
• Embed IFU-listed SKUs in catalogues and block non-listed substitutes in ordering systems.

2) Write standards into procurement

• Require supplier confirmation of IEC/ISO 80601-2-61 system validation for proposed monitor/sensor/cable combinations (not just “compatible with”). Ask for clinical desaturation evidence summaries, not only bench tests. FDA Access Data
• Keep IEC 60601-1 and essential-performance declarations in your technical file for each platform. VDE

3) Target training where it helps

• Create one-page quick cards per platform: approved combinations, typical accuracy ranges, and what to do if the reading conflicts with the patient.
• Add a 90-second “IFU basics” video to induction and ward huddles (when to check the matrix, how to find the right SKU fast).

4) Build governance into daily work

• Add IFU-compatibility to your acceptance testing and spot-checks.
• Feed device incidents to Yellow Card and log local CAPA actions; review trends with nursing/anaesthetics leads quarterly. yellowcard.mhra.gov.uk

5) Secure the data flows

• If your SpO₂ data streams to clinical systems, align your vendors with ISO/IEC 27001 (ISMS) expectations and your Trust’s DPIA/IG controls. Keep the EPR as system of record; avoid storing unnecessary patient data in device middleware. ISO

Tying it back to NHS priorities

IFU-first practice aligns with the NHS push for safer, interoperable digital care: trustworthy measurements feed better triage/escalation, cleaner records and safer analytics. Engineering standards into procurement and daily practice is how we turn “governance” into fewer incidents and more reliable data at the bedside.

Conclusion

SpO₂ is not “just a number.” It’s the visible tip of a validated system. Stay inside the IFU, buy to the standard, and report what you see. That’s how clinical engineering protects patients when it matters most.