Go back to portfolio

Bayer · Health

Bayer: ICU Angel, Estimated to Save Up to 2 Million Lives a Year, and Four More Projects

Designed ICU Angel trial screening, wrote the FemHub design scope and ran its usability test, and co-authored the navigation concept tests for the healthcare professional portal.

Role
Senior Product Designer
Scope
ICU Angel, FemHub, and HCP portal navigation
Focus
Health
Designer
Gideon Awolesi
Bayer: ICU Angel, estimated to save up to 2M lives a year case study cover

My contribution · Bayer

ICU Angel, FemHub, and HCP portal navigation

In the team's own estimate from the prototype reviews, clinicians went from about 30 seconds to less than 5 seconds to spot a critical change.

2M
lives a year, the platform's estimate
10
FemHub test participants
3
navigation concepts tested

What I owned

  1. 01Designed the ICU Angel pre-screening queues, the patient Development timeline, and the steps from consents to randomization.
  2. 02Wrote the FemHub design scope, ran the first usability test with 10 participants, and designed the fixes for booking a screening.
  3. 03Co-authored the moderated test of three navigation concepts for the healthcare professional portal, and built the test prototype with a colleague.

Clickable prototypes

Open the Bayer prototypes

Each project has its own interactive piece. Screen ICU patients for a trial, book a screening in FemHub, compare the navigation concepts, explore the CKD journey map, or prepare a UX test of an AI assistant.

Overview

About the project

Project overview

  1. What I worked on: I worked on five separate projects at Bayer, and each one has its own tab below. The largest was ICU Angel, a digital platform for acute respiratory distress syndrome (ARDS) in intensive care, where I designed the Eligibility Checker and ran the research with ICU staff. I also designed and tested FemHub, a women's health app, and helped run a usability test of three navigation concepts for Bayer's portal for healthcare professionals. The last two tabs cover a patient journey for chronic kidney disease and my work on AI and UX testing.
  2. Outcome: Once the design was complete and the MVP was built, ICU Angel went into a pilot. None of the other four projects has a recorded launch, so each of those tabs ends with what was planned next.

About the tabs and the prototypes

Each tab with an interactive prototype opens with a link to it. The prototypes follow the original screen designs and wireframes, and they run on fictional sample data. They aren't Bayer's production software.

The CKD patient journey and the AI and UX testing tabs cover research, analysis, and test planning, so they don't have a prototype.

Bayer: ICU Angel, estimated to save up to 2M lives a year, About the tabs and the prototypes, figure 1
Bayer: ICU Angel, estimated to save up to 2M lives a year, About the tabs and the prototypes, figure 2

ICU Angel and the Eligibility Checker

Interactive prototype: Open the prototype. Try this: Open the patient with the red alert banner and press Request diagnosis, then Request authorization. After that, go to Screening and take the patient through the four steps to Start Randomization.

Bayer built ICU Angel as a digital platform for ARDS in intensive care, alongside a new ARDS medication. ARDS can develop in a patient who's already in the ICU for something else, such as sepsis or pneumonia, and the ICU team has to notice it early enough to enrol the patient in a clinical trial.

I designed the Eligibility Checker, the ICU Angel module for finding patients who are developing ARDS and recruiting them into an ARDS clinical trial. It has two pages. On Pre-screening, the ICU team follows each patient's ARDS severity and sends the requests for the diagnosis and for authorization from the study investigator. On Screening, the team checks each authorized patient against the trial's inclusion and exclusion criteria and takes them through the steps to randomisation.

ICU Angel, ICU Angel and the Eligibility Checker, figure 1

How ICU Angel organises critical care data

In a critical care unit, the data for a clinical study is spread over a lot of hospital systems. On the ICU Angel service board, the platform collects data from the systems on the hospital's premises: the lab, the electronic medical record (EMR), the hospital information system, PACS imaging, and the ICU equipment. It organises that data in a clinical trial dashboard and shares it with the electronic case report form (eCRF) that the study uses outside the hospital.

The concept came from interviews with specialists inside and outside Bayer. It was meant to support clinical research first, and to be the technical foundation for a decision support tool later on. Handling medical-grade data needs CE marking, and the board lists that as a regulatory constraint on the platform.

ICU Angel, How ICU Angel organises critical care data, figure 1

The suite of services and the user for each one

ICU Angel was planned as a suite of six services: an Eligibility checker, a Data availability checker, an Impact Calculator, a Trial set-up tool, Optimisation, and a To-do list.

I mapped the services on value proposition canvases, one for each service. Each canvas has the main user's pains and gains, a user story, the key features, and a low-fidelity wireframe. The principal investigator is the user for the Impact Calculator and the Eligibility checker. The Data availability checker is for the study nurse and the study monitor, and Optimisation is for the ICU manager.

For the Impact Calculator, the canvas starts from an estimate of the number of patients on the trial. It then calculates the extra effort in minutes per day and the extra costs, and it compares the total resources with the trial-specific ones, per day or per shift, for resource planning.

The Eligibility Checker is the service I took through to a full interface design, and the rest of this tab is about it.

ICU Angel, The suite of services and the user for each one, figure 1

Mapping the clinical study journey

To find the points where trial recruitment breaks down in the ICU, I mapped the journey of an ARDS clinical study as a swimlane map, with a lane for each role: the principal investigator, the study nurse, the ICU healthcare professional, the study monitor, and the patient. The ICU healthcare professionals often aren't part of the research team, but they're the ones who spot possible participants and care for them.

The journey starts when a patient shows ARDS symptoms and an ICU clinician makes the diagnosis and records it. The clinician checks if the patient could fit the study and lets the principal investigator or the study nurse know. After that, consent is obtained, the study nurse confirms the diagnosis and checks the inclusion and exclusion criteria, and the principal investigator authorizes screening. Once the patient is included, they're randomised within a strict time window and start the study treatment. The team then records data every day and enters it in the eCRF, up to the follow-up assessments at the end of the study.

The map also lists the channels for each step, such as email and phone calls, and the systems involved, from the EMR and the lab system to the randomisation system and the eCRF.

ICU Angel, Mapping the clinical study journey, figure 1

Pain points on the study journey

The pain points on the map come from every stage. ARDS is hard to diagnose in time, and after the diagnosis, the team works under time pressure to obtain consent and strict deadlines for randomisation. A patient can be left out of the study if the ICU doesn't have time for screening. It's hard to teach every clinician in the ICU the selection criteria, and the timelines to reach the investigator are short, especially when the investigator is away.

Later in the journey, the team has to capture data that isn't usually noted in the ICU and copy it from the hospital systems into the eCRF. When missing data is noticed late, it's hard to find and fill in, and some staff don't have access to the systems they need.

The Eligibility Checker covers two of these pain points directly. For the late diagnosis, the pre-screening cards track ARDS severity against the Berlin criteria, and a red banner alerts the team when a patient's severity rises to severe. For the short timelines to reach the investigator, the confirmation of an authorization request has a reminder to call the study investigator for a quicker response.

ICU Angel, Pain points on the study journey, figure 1

Who I designed for

Doctors needed a reliable view of ARDS progression to support their treatment decisions. In the existing systems, important changes could get buried in a large volume of patient data.

Nurses needed an interface that fits daily ICU work without adding steps. Alarm fatigue and slow data entry were taking time away from patient care, and nurses and doctors had to check several systems to understand a change in a patient's status.

The study investigator receives the authorization requests from the ICU team and authorizes the patients who go forward to screening.

ICU Angel, Who I designed for, figure 1

Research with ICU staff

I started with interviews with ICU physicians and nurses about the problems they faced while managing ARDS. I also watched how ICU teams worked and mapped the existing workflows, including the points where information or time got lost.

More than 30 ICU staff answered a survey about alarm fatigue and system usability.

Six clinicians and three principal investigators reviewed the designs with me in daily stand-ups and regular calls. A pilot group tested the early wireframes against the clinical requirements and the safety-critical tasks.

ICU Angel, Research with ICU staff, figure 1

Pre-screening

To enrol a patient in an ARDS trial, the ICU team has to notice early that the patient is developing ARDS, and then get the diagnosis and the screening authorization in place. Pre-screening is the page where the team does this.

The page opens on the Non-ARDS patients group, with a card for each patient. The card has the patient's ID and bed, the ARDS severity, and a trend line of how the severity has changed. Under the severity, a row of icons covers the Berlin criteria, the clinical definition of ARDS: timing, chest imaging, the origin of the respiratory failure, and oxygenation. An icon is greyed out while that criterion isn't met.

ICU Angel, Pre-screening, figure 1

How the cards show ARDS severity

Before the redesign, the screen used traffic-light colours everywhere, and none of the colours stood out. For ICU Angel, I gave ARDS severity its own colour ramp, from pale pink for Mild to dark plum for Severe, and the same colour runs down the left edge of each card. A dash means the patient doesn't have a severity score yet.

Red only appears on the critical alert banner and on values that need attention, such as a failed trial criterion or a long time after diagnosis.

From the prototype reviews, the team's own estimate was that clinicians took about 30 seconds to spot a critical change on the old screen, and less than 5 seconds with the new visual hierarchy.

ICU Angel, How the cards show ARDS severity, figure 1

Alerts, diagnosis requests, and authorization requests

I used two banner styles. A red banner with a warning triangle is for a critical change, for example: "Jane Doe's ARDS severity level has increased to severe, please request ARDS diagnosis." A grey-blue banner with an info icon is for status updates, like a confirmed diagnosis. This way, the clinician picks out a critical change by its colour and its icon.

Each card in the Non-ARDS group has a Request diagnosis button. Once the patient is diagnosed, they move to the ARDS patients group. There, the card shows the time after diagnosis, and the button changes to Request authorization. Longer times, like 48h20min, are in red.

Request authorization sends the request to the study investigator. A confirmation appears with a reminder to call the study investigator for a quicker response, and the card shows the date and time of the request in place of the button.

ICU Angel, Alerts, diagnosis requests, and authorization requests, figure 1
ICU Angel, Alerts, diagnosis requests, and authorization requests, figure 2

Finding a patient

Each patient group switches between cards and a list. The list adds two columns, On ECMO and On invasive ventilation, and it sorts by ARDS severity. Filters at the top narrow the patients by group and ARDS severity, and a search modal looks up a patient by name or by bed number.

ICU Angel, Finding a patient, figure 1

The Development timeline

Before a clinician requests an ARDS diagnosis, they need to understand how the patient got to this point. When they open a patient from pre-screening, the Development tab has a timeline of the patient's ARDS severity, by day or by hour, in bands from Mild to Severe.

Under the chart, two lanes follow the same dates. Diagnostic events lists findings such as sepsis and bilateral lung opacities. Intervention lists steps such as starting ventilation and changing the ventilation parameters. Hovering over a point on the line opens the event and its time, for example "Jan 19 10:30, Worsening respiratory symptoms were detected."

I put the events and the interventions on the same time axis as the severity line. This way, the clinician reads a jump from Moderate to Severe next to the findings and the ventilation changes from the same days.

ICU Angel, The Development timeline, figure 1

The Berlin criteria evidence

The Berlin criteria tab sets out the evidence for the diagnosis. The checklist covers the four criteria: timing within one week of the clinical insult, bilateral opacities on the chest X-ray, respiratory failure that cardiac failure or fluid overload doesn't fully explain, and oxygenation. Under oxygenation, the band that matches the patient is in bold, and the other two are greyed out.

Next to the checklist, two vertical gauges show the PaO2/FiO2 ratio in mmHg and the PEEP in cm H2O, with a pointer at the current value. The PaO2/FiO2 scale runs from red at the low end to green at 300, the upper limit for mild ARDS in the Berlin definition. For the sample patient, the pointer is at 93, in the severe range.

Below that, the imaging carousel pairs each chest X-ray with a heat-map overlay, with the date and time under each pair. Tapping an image opens it full screen.

Both tabs end with the Development log and Request diagnosis buttons. A clinician who has just checked the evidence requests the diagnosis from the same page, without going back to the patient list.

ICU Angel, The Berlin criteria evidence, figure 1
ICU Angel, The Berlin criteria evidence, figure 2

The screening list

When the study investigator authorizes screening, a grey-blue banner confirms it, and the patient moves to the Screening page. The list only includes patients at step 2 of the trial flow, and I put an orange note above the table to make that clear.

Each row is a patient, and each column is one of the trial criteria: the trigger factor, non-pregnancy, age, invasive ARDS, hypoxemia, and EVLW. A cell has a green check when the patient meets the criterion, a red cross when they don't, and a pink To be tested cell when the result isn't in yet. Every column has its own filter, and a checkbox limits the list to the patients who meet the inclusion criteria.

ICU Angel, The screening list, figure 1

Checking one patient against the trial criteria

Opening a patient from the list brings up a four-step flow at the top of the page: Obtain consents, Check criteria, Make decision, and Start Randomization. The time after diagnosis is next to the ARDS severity, because several criteria have time windows.

The Inclusion and exclusion criteria tab lists each criterion with its value. When a value is still missing, like the pregnancy test, the row has To be tested and a Request test link. After the test, the clinician presses Step 2 is completed, and the flow moves on to Make decision.

The Development and Berlin criteria tabs from pre-screening are on this page too, and the clinician reviews the same evidence during screening.

ICU Angel, Checking one patient against the trial criteria, figure 1

Setting up the trial criteria

A Settings page lists the inclusion criteria and the exclusion criteria on separate tabs, and each criterion is marked as automatic or manual.

ICU Angel, Setting up the trial criteria, figure 1

Testing the ICU Angel prototype

ICU staff and principal investigators then worked through the interactive prototypes in moderated sessions. I used these sessions to check if the information hierarchy helped people decide on the next action for a patient.

Doctors asked for adjustable alert thresholds, and nurses asked for shorter data-entry forms. IT staff needed clear security controls for the clinical data.

ICU Angel, Testing the ICU Angel prototype, figure 1

The ICU Angel pilot

Once the design was complete and the MVP was built, the platform went into a pilot. ICU Angel is estimated to save up to 2 million lives a year. That estimate is for the platform as a whole, and I don't claim it as a result of the interface design on its own.

ICU Angel, The ICU Angel pilot, 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.