Nope, never. I run Arch Linux with projects under nspawn containers, the only AV tool I keep around is ClamAV so when coworkers have USB drives I can slap `clamscan /mnt/auto-sda1` and let them know if it's clean.
I love this! computer science is all about abstractions and guarantees, and it's great to have an option for more control. One thought about graceful degradation: would it be easy/possible to build in configuration to "when guarantee cannot be met, only throw an error x% of the time"? This keeps the situational awareness (errors about different query plans) while having an escape hatch: if postgres is updated & the new version decides to never generate good queries, the queries will still happen for some ~95% of users, just slower until the team can read through the new version's instructions to get the plan they need.
If they're escaping, it raises interesting questions about where they might be going / possibly merging? What a strange view of the universe if two particles under pressure could combine and have different attributes (less mass?).
The QA team brings something significant that developers (myself) will never have: their machines closely represent the customers machines. They use a well-polished methodology to push the models we ship to their limits and provide relatively detailed information about how to reproduce failures.
I can't count the number of times I've tested something 5 times, convinced myself that the code handled tons of error cases, shipped it, and in 10 minutes a customer types "five" into a field expecting an integer which causes the next step to use "0" for processing.
Important distinction to make, most people just think "more money means interest" but the mechanics of the two financial instruments differ and this is the entire selling point for these ISAs, and the reason why one may be a good / bad idea in a situation.
I'm not familiar with the UI, but often for high(er) risk operations we in the CS field ask users to fully type the name of something; in this scenario, instead of autocompleting would it have helped to ask the nurse to fully type in the name of the drug?
This will not help the overworked state and the next issue I can see is confusing two drugs (marketing _loves_ to confuse people, given enough phonemes it would be easy to type the full name in wrong); potentially asking for a brief description of what the caregiver expects to happen, with a quick NLP pass comparing the "effect description attached to drug" paragraph and the 2-3 sentence "expected effect description from caregiver". Yes more paperwork, but saving lives is usually worth the extra effort. Everyone already knows the long-term overwork solution is cut down on admin & hire more personnel.
The article said that after this incident the manufacturers modified the search to match at least 4 letters, not just 2. And matching the 2 required a special override mode to begin with, but apparently that was a common thing to do.
I don't know how these systems are designed and tested, and what regulatory hurdles they have to pass, but it sounds like there is a huge disconnect between how the manufacturer expects them to be used and how they are actually used, with frequent overrides, day to day. It must be a tough industry to work in, either in the patient facing side or the medical devices and software side. I'd hate to be the person who coded all the warnings in that software. "What do you mean they bypassed all 7 warnings? Even the one that said this was a paralyzing agent?!"
I wonder if some of this wasn't a procedural failure too. Like why doesn't a potentially life ending drug require at least two people to vouch? Even in retail a manager has to come and turn a key for some trivial refund, or in our field a reviewer has to approve changes first.
Is it that the hospital cheaped out on staffing so they didn't want two nurses double-checking each other? Was this use case never accounted for in software development? Are all drugs potentially life ending so there's no way for the software to reliably reduce false positives? So many questions...
My spouse is a nurse and at her work, they are required to do "double verification" of narcotics where a 2nd nurses recounts and also signs off on the drugs being taken out. They also don't use any electronic or automated systems. Is the fancy cart a cost saving measure or a safety measure? Seems like its being used to reduce headcount and let nurses work alone.
There is a certain level of cognitive offloading happening with the machine that is uncomfortable to me. Its like the Tesla autopilot giving drivers a false sense of security. One could easily fall to assuming what came out of the cart is the right thing. People are much less trusting with each other.
I also have an RN relative who described the old school processes to control for this sort of error in the old days, and the pharmacists I know have explained that even for them, they have notational conventions whereby ssimilarly spelled drugs get unique capitalizations in digital systems to visually distinguish one long arse name from another.
Also, it seems like a really bad idea to me to mix trade and chemical name in that type of system. You should search one and only one type of name at a time, simply to ensure namespace tripups like this don't happen.
This sounds like cognitive load failure from workload mismanagement.
This is the ideal design, along with an office whose job it is to manually move data from the public side to the private side. These offices usually have a server on the public and private side to make it seem like it's an automated transfer (like putting a file in Dropbox on the public and then seeing it show up on the private side), but in reality you have a security guard making sure nobody's copying up `MSOfficeOfficialThisTime.msi`.
They mean "fewer people willing to cross the bid-ask spread to buy a stock than the number of people willing to cross the bid-ask spread to sell a stock"; what matters is who is crossing the line? if it's the buyer side of the transaction, price trends up. If the seller is accepting a small % loss on the sale, the price trends down.
