As a product designer, I can think of 2 reasons why the person that came up with this flow might've made it a popup:
1) That's the default design system pattern for alerts, so whoever was the designer just went with it.
2) There's other alert patterns (alert bar, toast, etc), but sepsis was deemed to be so dangerous to the patient that it deserved to have its own special friction inducing UI element to alert doctors to take action.
>I don't know what it is that draws product designers to keep reaching for that horrible UX pattern
There are legitimate cases for alert modals like this one, but this definitely is an example as to when it shouldn't be used.
Sepsis is indeed an immediate life threatening condition, and I bet the alert was added as some kind of legal/medical ‘oh shit’ type of condition - without thinking through the consequences from a UX perspective.
Have you been on the other side of this? I get dozens of sepsis alerts a day, usually on the same patient, and the criteria that triggers them is so broad and non specific they are functionally useless. Each alert locks down the entire system ironically preventing you from reviewing what triggered it in the first place. You cannot do anything until it is addressed and you are forced to commit to an action without all the data because of it like administer a medication or order fluids, which may not be appropriate. Lots of things mimic sepsis criteria including but not limited to decompensated cirrhosis, HF, cancers, leukemias. The worst is that they don’t even pop up at the right time, they usually pop up usually way after the sepsis has been treated. In the past year, I’ve only had about a half dozen appropriate sepsis pop ups among the hundreds I’ve received.
It blocks the system with a demanded action, but doesn't even show you what triggered the alert condition? I would completely expect a "List of conditions that suspect sepsis" and get those details up front and center.
I'd be putting in medical records "Due to software popping up an un-dismissable sepsis screen that does not show details, I dismissed it due to needing the data it was flagged on".
Yes, really. I’ve had to restart my Citrix session to make it go away or dismiss it like the writer did.
You’ll get something like “sepsis criteria triggered by wbc 13, cr 1.5, hr 101, rr 22.” And that’s it - usually in the middle of a night on a new patient I just got a page for. Can’t open documentation to see the patients med history.
It’s ridiculous. I’m not using Epic but I am using a major EMR.
To be fair I’ve written almost exactly what you mentioned out of sheer frustration once or twice but it’s not ideal
Yes, in almost every case, the default "popup" GUI library call is also a modal dialog. You cannot access anything else, anywhere else, in the entire program (even if the program had multiple separate windows open). All you can do is read the dialog's text, and hit the "ok" button to dismiss it (or pick from one of a set of "buttons" that are shown on the popup to dismiss it).
The worst ones also do a global grab, with the result that you can't even switch away to another unrelated application on the system without first "interacting" with and dismissing the popup.
To see the version that is built into Javascript in the browser, put the following into the URL field of a new bookmark, and save the new bookmark.
javascript:(function(){alert("hello");})();
Then, while here on HN (or anywhere else), click that new bookmark you just made, which will pop up the default built in Javascript alert box, and try to interact with the rest of the page it pops up in front of.
UI engineers need to be held legally responsible for false alarms like this.
My older car regularly hallucinates an incoming frontend collision and takes over the speedometer with a flashing red/black screen.
The new one (Kia) overrides the steering and forces the car to depart the lane (usually over double yellow lines).
If the alert regularly produces false positives then such behavior (and the behaviors of these EMRs) should open the vendor to civil and criminal liability. The courts should just assume the behavior will lead to loss of life, in the same way as discharging a firearm randomly in the city might.
It probably makes sense to have a short grace period to push a patch. Maybe one week after 0.1% of users complain?
If your vehicle has a safety defect then you should file a formal complaint with the NHTSA. These things won't get fixed unless customers follow the process.
Safety defect: my Tesla has a really distracting giant screen in the drivers field of view. WTF?
Closed: Working as Intended, Elon has us by the balls.
It’s similar to alarm fatigue in the ED. In most, every piece of equipment is alerting on at least one thing at any given moment, if just because the patients pulse-ox sensor is not attached super well.
But they came in because of a diabetic emergency and we’re just waiting to make sure the treatment worked and 99% of the time it does, so no one really cares, but the UX around silencing it isn’t great (and may be a liability if used). Like in this example.
Because maybe this is one of those 1/1000 cases where the insulin didn’t work, and they lost all peripheral circulation and that pulse-ox sensor’s bad reading is warning you that they are about to lose all their fingers.
Appreciate the added and specific context. I'm not in the medical field but I have worked on EMRs.
What, by your estimation, would be the better user experience for alerting the imminently life threatening situation?
It sounds like a signal to noise ratio with false positives, but IMO I'd rather a provider be at least given the time to pause and consider the diagnosis. I'm not sure about the optimal way to do it.
We are grading a tool which might not need to be there at all. It shouldn't get points for coming in six hours later saying that the patient being treated for sepsis might have sepsis. See what I'm saying? There's a cost to every flag you wave.
UX is sort of the issue in the sense that people have been trained to ignore pop-ups because they are used for so much irrelevant garbage that it is a "boy who cried wolf" situation. The questions of: "How do you force a computer user to take something seriously?" is fundamentally a UX question.
When people encounter a jarring interaction with a computer, most people's default response is to blame the computer for not doing what they expected it to... even when the computer is telling them that they need to do something differently. This makes it very difficult to guide users into changing their behavior. And if the user has experienced this message erroneously in the past, they have been conditioned to presume it is erroneous.
Anyone who has ever worked helpdesk can tell you that people call in with "computer errors" all of the time that are simply messages telling the user to do something... but it doesn't occur to them to actually follow the instructions. This is a fundamental HCI issue that is tough to solve, and usually isn't solved by someone who is just building a form to check off a compliance item.
If you are actually trying to do something to resolve the situation, why would you want a progress stopping pop-up forcing you out of actually doing the thing you need to do? Especially if it forces you to pick out of two options when the thing you are trying to do is figure out which option is appropriate?
Using EMR systems are nightmares for anyone actually doing things, but great for figuring out what was documented later. The two are rarely related.
If someone is trying to land a plane, would a pop-up about an engine fire that takes over all control input also be a good idea?
Have you read any of the details? The provider was unable to take appropriate action because the progress halting popup was preventing taking that action.
Of course I did. You're wrong. The provider CHOSE not to take the appropriate action. The appropriate action was ordering the medication because the automated diagnoses was in fact correct.
PS - I would suggest avoiding rhetoric like "did you even read" as per the guidelines. It's just a waste of everyone's time.
> Agyare had instructed Banerjee to hydrate Sam right away but to wait for the results of Sam’s lab work before ordering a chest X-ray or the strong antibiotics used to treat sepsis.
> But Banerjee, a novice, got stuck. He couldn’t figure out how to navigate the template to make some but not all of the auto-populated orders. “This was my first patient that triggered the sepsis pathway,” he explained, in testimony. So he asked Connor Welsh, a third-year resident, for help.
> At 8:50 p.m., Welsh showed Banerjee how. From his own computer, he clicked into a field on Sam’s chart to assert that sepsis was not likely: “Based on my evaluation,” the automated note said, “this patient does not meet clinical criteria for bacterial sepsis.”
The provider was instructed (possibly wisely) to take some of the automated sepsis actions and to defer others. The computer did not allow this without generating an automated note saying “ this patient does not meet clinical criteria for bacterial sepsis.”
Imagine if your email UI auto-classified one particular email as so high priority that it would allow you to do nothing else, including reading other emails, until you archived the priority email and, to for good measure, would auto-reply “no action needed” when you hit archive. You get a priority email, and you determine that the correct action is to wait up to 20 minutes for another email that you expect and, while waiting 20 minutes, to read other emails from the same sender. But you can’t because your UI won’t allow it. So you archive it, send the “no action needed” reply (which is outrageously inappropriate but you don’t actually have any control here), and hope you remember in 20 minutes while you are horribly overworked.
ISTM the patient’s family should consider suing the software vendor.
Kind of my thinking here... the fact that popups are abused for BS doesn't mean that they don't serve a purpose and this is one of those times.
The fact that it was confusing and a second Doctor went ahead and bypassed it altogether that hadn't seen the patient is a bit problematic to me.
Beyond this, as much as I empathize with the family here, people still die... I had two similar ER visits in my life and it's only chance I wasn't sent home both times... when I came down with Guilliam-Barre and when I had ketoacidosis. The former, was about to be sent home when one of the residents recognized my symptoms (sudden onset weakness all over). In the latter, urgent care said it was just a cold/virus etc.. but I couldn't even keep water down, after 4 days I couldn't stand up and called for an ambulance I dropped over 50# of weight in under a week. I remember thinking to myself "if I go back to sleep I won't wake up."
> The fact that it was confusing and a second Doctor went ahead and bypassed it altogether that hadn't seen the patient is a bit problematic to me.
Doctors are humans, and humans have cultures. In this culture, it was normal for people to dismiss popups that seemed to be distracting, and one human shared with another human this useful tidbit of information.
People need to get real about who doctors are. They are not super-people.
The system was set up in such a way that the popup became a distraction, and humans naturally want to get rid of distraction.
I’m really shocked that nobody stopped and thought “doctors have special training and should be expected to diagnose and treat Sepsis if reminded about the possibility.” I don’t think it was appropriate to block the entire flow, and I’m surprised nobody thought it was possible to want some but not all of the actions for sepsis. If the developers are really making popups that make life or death decisions then maybe EMR customizations should have a tighter safety class.
If it were me, I would have also named the developer or administrator who implemented the popup. It sounds like a key stumbling block in a medical device.
1) That's the default design system pattern for alerts, so whoever was the designer just went with it.
2) There's other alert patterns (alert bar, toast, etc), but sepsis was deemed to be so dangerous to the patient that it deserved to have its own special friction inducing UI element to alert doctors to take action.
>I don't know what it is that draws product designers to keep reaching for that horrible UX pattern
There are legitimate cases for alert modals like this one, but this definitely is an example as to when it shouldn't be used.