Go back to portfolio

Philips · Health

Philips: Use-Error Analysis for IntelliVue Monitors, With More Than 1 Million in Use

Wrote the use scenarios and the use-error analysis for continuous temperature, SpO2 accessories with RFP, and patient management on the bedside monitor.

Role
Usability Engineer
Scope
IntelliVue patient monitoring usability engineering
Focus
Health
Designer
Gideon Awolesi
Philips: Use-error analysis for 1M+ IntelliVue monitors case study cover

My contribution · Philips

IntelliVue patient monitoring usability engineering

Each uFMEA linked the use scenarios to the hazards, their severity, and the mitigations, and it went through cross-functional reviews before the risk file used it.

1M+
IntelliVue monitors in use
3
uFMEAs written and reviewed
~200
uFMEA line items

What I owned

  1. 01Wrote the ContTemp use scenarios, from connecting the Temp Smart Cable to cleaning it.
  2. 02Took over the SpO2 accessories uFMEA, reviewed it row by row, and traced it to the sensor requirements.
  3. 03Analysed patient management on the monitor, from assigning a patient to transfer and merge.

Clickable prototypes

Open the Philips prototypes

Each project has its own clickable patient monitor. Connect temperature probes, set SpO2 and RFP alarms, or assign a patient and dock a transport monitor.

Overview

About the project

Project overview

  1. Role: Usability engineer on Philips patient monitoring, from March 2025 to about October 2025.
  2. What Philips does: Philips makes the IntelliVue patient monitors that hospitals use at the bedside, and more than a million of them are in use. I worked on the Delta monitor programme. On Delta, a clinical user can be responsible for up to eight patients, and they use the monitor in emergencies and during transport. The monitor is one device among many around the patient, so it rarely has the user's full attention.
  3. What I worked on: I joined in March 2025 and took over the use scenarios and uFMEA drafts from the usability engineer before me. I worked through the projects in this order: the continuous temperature (ContTemp) smart cable, then the SpO2 smart cable and its accessories, and then patient management. For each one, I wrote the use scenarios as the steps a clinical user takes and walked them through with clinicians and the product owner. Then I wrote the use-error analysis (uFMEA) for the steps where a patient could be harmed. Across the three analyses, that came to about 200 line items.

I also wrote the use scenarios for Respiration From Pleth (RFP), a respiration rate the monitor derives from the SpO2 pleth signal. That work is in the SpO2 tab.

Prototypes

These were separate projects, so each one has its own tab below. Three of the tabs have an interactive prototype, and the fourth covers how the uFMEA work ran across all of them.

Each prototype follows the use scenarios and the mitigations in the uFMEA for that project. The prototypes run on sample patients, and they aren't Philips software. Where the source documents didn't include a unit or an alarm limit, the value in the prototype is illustrative.

Philips: Use-error analysis for 1M+ IntelliVue monitors, Prototypes, figure 1

Continuous temperature through the Temp Smart Cable

Interactive prototype: Open the prototype. Try this: Connect a second temperature probe and watch the monitor rename both to Temp1 and Temp2. Then open Cleaning and record the cleaning of the cable.

ContTemp measures temperature continuously through a new smart cable. The clinician connects a probe to an adapter cable, the adapter to the smart cable, and the smart cable to the monitor. With a second probe, the monitor measures dual temperature and calculates the difference between the two sites.

The uFMEA covered the whole use of the cable, from gathering the probes at the bedside to cleaning the cable afterwards. It had six use scenarios: collecting the equipment, applying the sensor, applying a second sensor, calculating the temperature difference, disconnecting the patient, and cleaning and disinfecting the equipment.

ContTemp smart cable, Continuous temperature through the Temp Smart Cable, figure 1

The use errors in the ContTemp analysis

In IEC 62366-1 terms, the users are clinical staff at the bedside and during transport. A lot of the hazard-related use errors were about the probe itself. A clinician could pick a probe that doesn't suit the patient or the measurement site, or use an accessory that's damaged or unsupported.

The label is part of the measurement, because each site has its own offset. If the clinician places the probe on a different site from the one in the label, the monitor applies the wrong offset to the reading.

Other rows covered reading the value before the probe reaches equilibrium, cables around the patient, a loose connection or the wrong port, and infection control when the clinician disconnects the probe, disposes of it, and cleans the cable. The analysis has more than 70 line items, and about a third of them are rated S, which means the use error may cause a hazardous situation.

ContTemp smart cable, The use errors in the ContTemp analysis, figure 1

What I did on ContTemp

I picked up the draft use scenarios and uFMEA lines from the usability engineer before me. I reworked the scenarios and validated them again. On 23 May 2025, I ran the cross-functional review with systems engineering, risk management, clinical, and the measurement owner, and recorded the review against each row.

In June 2025, I found that the analysis didn't have any lines for cleaning and disinfection. I checked the cleaning guidance with the biosafety contact and then ran a separate cleaning review. In that review, the team decided to write new cleaning lines for the smart cables, and the SpO2 analysis could reuse them later.

The mitigations are written as “shall” statements, and a lot of them are new. Some went into the instructions for use and the labelling, like the patient group and size on the packaging, and a symbol on the cable and the packaging for probes that aren't safe in an MRI. Others went into the monitor, such as a technical alarm when a probe disconnects, an indication for invalid values, auto-start when a probe is connected, a default label, and an indication of the active port. In the review, the team also requested new requirements, including a compatibility list for the accessories and an inspection interval.

ContTemp smart cable, What I did on ContTemp, figure 1
ContTemp smart cable, What I did on ContTemp, figure 2

Label conflicts and the proposed banner

In August 2025, I went through the label behaviour with the owner of duplicate labels. In the use scenario, selecting a label was optional and marked “if needed”. This was a risk, because a cable can start monitoring under a label whose alarm settings the clinician never checked.

Right now, IntelliVue handles a duplicate label with a full-screen window, and the user can't continue until they pick another label. On the new platform, the plan was for the system to assign a differentiating label automatically, like ABP1 and ABP2, and keep monitoring. The clinician would get a notification, and resolving the conflict would be optional.

My position was that if the label is optional, the risk is still there, so the label should be confirmed, or the clinician should at least see the label of the measurement that's running. I proposed a banner that doesn't block the screen. When a probe is plugged in, the banner shows “Currently monitoring” and the label in bold for three to five seconds. If someone relabelled the cable, for example from a temperature label to a pressure label, the banner would show that it started as a temperature cable and offer Continue or Change label. I took the question to the measurement owner.

ContTemp smart cable, Label conflicts and the proposed banner, figure 1
ContTemp smart cable, Label conflicts and the proposed banner, figure 2

Where the ContTemp work ended

The ContTemp uFMEA went through its cross-functional review in May 2025, and its rows carry the new requirement requests. When I last worked on it in August 2025, the severity of harm on every row was still to be defined with the risk management team. I can't point to an approval or a release for it.

ContTemp smart cable, Where the ContTemp work ended, figure 1

Need this level of detail in your product?

Work through the hard product decisions early.

If you’re a product team, that can mean a focused design, system, or prototype project. If you’re hiring, it’s a chance to look closer at how I work across research, interfaces, and code.