Slashdot Mirror


CT Scan "Reset Error" Gives 206 Patients Radiation Overdose

jeffb (2.718) writes "As the LA Times reports, 206 patients receiving CT scans at Cedar Sinai hospital received up to eight times the X-ray exposure doctors intended. (The FDA alert gives details about the doses involved.) A misunderstanding over an 'embedded default setting' appears to have led to the error, which occurred when the hospital 'began using a new protocol for a specialized type of scan used to diagnose strokes. Doctors believed it would provide them more useful data to analyze disruptions in the flow of blood to brain tissue.' Human-computer interaction classes from the late 1980s onward have pounded home the lesson of the Therac-25, the usability issues of which led to multiple deaths. Will we ever learn enough to make these errors truly uncommittable?"

72 of 383 comments (clear)

  1. Will errors ever go away? by s73v3r · · Score: 4, Insightful

    As long as people are involved in some way, no.

    1. Re:Will errors ever go away? by courteaudotbiz · · Score: 3, Insightful

      Mmmmm, anyway, people are always involved if you have a machine. The machine didn't build itself!

    2. Re:Will errors ever go away? by argent · · Score: 4, Funny

      The machine didn't build itself!

      SPEAK FOR YOURSELF, MEATSACK!

    3. Re:Will errors ever go away? by Arthur+Grumbine · · Score: 4, Funny

      The machine didn't build itself!

      SPEAK FOR YOURSELF, MEATSACK!

      Oh, yeah?! Well who built your first model, you bucket o' bolts! And don't give me that FSM nonsense. Everyone knows that the Fantastical Spawning Machine was truly the work of humans, inspired by the intelligently designed schematics given to us by the noodley appendage of the true FSM.

      --
      Now that I think about it, I'm pretty sure everything I just said is completely wrong.
    4. Re:Will errors ever go away? by FatdogHaiku · · Score: 4, Funny

      SPEAK FOR YOURSELF, MEATSACK!

      Scanning with high intensity radiation reveals he is in fact about 60 percent water, 16 percent protein, 15 percent fat, and about 3 percent nitrogen... So, more of a stringy, greasy, slightly gassy water bag really.

      Sorry about the high levels of radiation used to obtain the data, your armpits should stop smoking any minute now.

      --
      You have the right to remain sentient. If you give up the right to remain sentient, you will be elected to public office
    5. Re:Will errors ever go away? by Itninja · · Score: 4, Funny

      Don't be such a dolt. The machine is the product of evolution. Millions of years ago a bolt of lightning hit some random alloys and a simple logic circuit was born. Fast-forward to now, and *poof* CT scanner! It just make sense.

      --
      I judt got a nre Kinesis keybiartf so please excusr ant egregiou typos.
    6. Re:Will errors ever go away? by GrpA · · Score: 2, Interesting

      Or maybe just a simple display that tells you the amount of radiation exposure that the machine is currently set for?

      Then the radiologist could take responsibility for noting it.

      This is simple and things like this often exist in development versions but are taken out later by marketting. Why?

      I once worked for an international company that had a billing system. It wasn't very user friendly and was often wrong.

      On the other hand, we had a local billing system that was accurate and helpful. At some point, bills were issued centrally and needless to say, were all wrong ( usually overbilling the customer - This was a now-disgraced US company... ) When we started to complain internally that the bills were wrong, they investigated and found we had a duplicate system that worked correctly. We were instructed to decommission it.

      The reason? Because the company didn't want the legal hassle if someone sued them for grossly inaccurate invoices and used our records against them.

      To his credit, my manager stood by us and insisted they fix the billing and said we weren't going to take down our system even when they threatened to fire him over the issue. It was a standoff for months and in the end we agreed we wouldn't monitor any other company clients that didn't know about our billing local system and we would bill legacy clients locally. Not really a satisfactory solution. The corporation won, the consumer lost and they never even knew we had a battle.

      But if you have a little radiation readout that tells you something that might highlight bugs or errors in a multimillion dollar piece of medical equipment, then wouldn't you ask the developers to remove it? After all, it's just going to be used against you if someone is killed or injured while using the equipment.

      GrpA

      --
      Enjoy science fiction? "Turing Evolved" - AI, Mecha, Androids and rail-gun battles. What more could you want?
  2. Not the engineers fault by PhasmatisApparatus · · Score: 5, Funny

    Requiring that doctors RTFM is the first step.

    1. Re:Not the engineers fault by betterunixthanunix · · Score: 5, Insightful

      The machine's software should not be capable of triggering the release of that much radiation; any change in the radiation levels should require some kind of hardware interaction. Even an idiot who did not RTFM should not be able to cause harm with the machine.

      --
      Palm trees and 8
    2. Re:Not the engineers fault by smitty777 · · Score: 5, Insightful

      Couldn't disagree more. Unfortunately, enforcing training and reading manuals would probably have little effect. In my 10+ years doing usability for missile systems, you have to build in the mechanisms to keep the users from doing bad things. Even if you force the user to read the *entire manual* before each use, people still have bad days, hangovers, fights with significant others. It has to be designed in.

      --
      "Before God we are all equally wise - and equally foolish"
      Albert Einstein
    3. Re:Not the engineers fault by vertinox · · Score: 4, Insightful

      The machine's software should not be capable of triggering the release of that much radiation; any change in the radiation levels should require some kind of hardware interaction. Even an idiot who did not RTFM should not be able to cause harm with the machine.

      I'm not sure what you mean by this? Most hardware is software these days.

      Or are you talking about having a red button with a safety lock on it that has to be pushed in order to work?

      Either way, people still bypass hardware solutions.

      --
      "I am the king of the Romans, and am superior to rules of grammar!"
      -Sigismund, Holy Roman Emperor (1368-1437)
    4. Re:Not the engineers fault by snowraver1 · · Score: 4, Insightful

      Hardware interaction... Like maybe "[...]resetting the machine to override the pre-programmed instructions that came with the scanner when it was installed."?

      I'm willing to bet that the person that modified the machine has read, at least, the relevant parts of the manual.

      --
      Copyright 2010. All rights reserved. This comment may not be copied in any way including, but not limited to caching.
    5. Re:Not the engineers fault by Serenissima · · Score: 4, Insightful

      I think he means it should be hardwired into the unit to NEVER EVER exceed a certain level of X-Ray radiation. That should be the default. If there's some medical reason why the dosage needs to increase, you should have to turn it UP to that dosage and then the machine should reset itself to the default. There should NEVER be a problem of the machine defaulting to an extremely high level of radiation requiring personnel to turn it down. It should always start out low in case some dumbass technician runs the machine without making any changes.

      --
      Give a man a fire and he'll be warm for a day. But light a man on fire and he'll be warm for the rest of his life.
    6. Re:Not the engineers fault by NonSequor · · Score: 2, Interesting

      Couldn't disagree more. Unfortunately, enforcing training and reading manuals would probably have little effect. In my 10+ years doing usability for missile systems, you have to build in the mechanisms to keep the users from doing bad things. Even if you force the user to read the *entire manual* before each use, people still have bad days, hangovers, fights with significant others. It has to be designed in.

      The story behind Murphy's Law is pretty interesting and it ties in with this design philosophy.

      Basically the story is that a technician incorrectly installed force sensors and in response, Murphy got pissed off and said "If that guy has any way of making a mistake, he will."

      However, other people adapted that statement into "If anything can go wrong, it will," expressing the idea that if a system does not mechanically exclude the possibility of human error, human error can be expected to occur. This makes accounting for human error a design constraint.

      --
      My only political goal is to see to it that no political party achieves its goals.
    7. Re:Not the engineers fault by Sockatume · · Score: 4, Insightful

      Don't even hard-wire it. Engineer it so that operating in the high-dose regime requires physical intervention, a "Kill Handle" with a lock and key. The machine should be physically incapable of generating an above-standard dose when the "Kill Handle" is not being held. Limit the power, or something. (The aformentioned Therac incident happened, in part, because such a hardware interlock did not exist.)

      --
      No kidding!!! What do you say at this point?
    8. Re:Not the engineers fault by Greyfox · · Score: 5, Insightful

      My machine would irradiate the operators by default and would require that a obscure button sequence be pushed in order to irradiate the patient instead. That way the idiot who didn't RTFM would end up dying of radiation poisoning, not the patient. Eventually the survivors who DID RTFM would breed and pass on their proclivity to RTFM. Really it's for the good of the entire human race, if you think about it...

      --

      I'm trying to teach myself to set people on fire with my mind... Is it hot in here?

    9. Re:Not the engineers fault by BigDukeSix · · Score: 5, Insightful

      It's not quite that simple. The CT scanner is set up with a distinct scanning protocol for whatever part of the body you're imaging. If you're trying to get a detailed image of the bones of the pelvis you have to use more power than if you're imaging the lungs. The scan is further individualized by patient size. Given that infants and very large people are imaged on the same scanner, the software has to vary radiation dose over a reasonably wide range, and it's a different setting for every scan.

    10. Re:Not the engineers fault by Geoffrey.landis · · Score: 3, Insightful

      The machine's software should not be capable of triggering the release of that much radiation

      That sentence, essentially, just said "The machine did something bad. It should have been designed so it isn't allowed to do that."

      That's what qualifies as "insightful" these days????

      --
      http://www.geoffreylandis.com
    11. Re:Not the engineers fault by eric-x · · Score: 2, Insightful

      Not true because the proposed button/switch would only need to be used exceptionally.

      There are enough possibilities to make it fool proof.
      For example, there could be two push buttons, one is to reset the scanner to normal levels and one to enable high levels. An electronic timer automatically resets it back the lower level after an hour, or when the scan session ends. To prevent taping down, the buttons must be released before it can be pushed again, this is easy to detect using a few flipflops and AND/XOR ports.

    12. Re:Not the engineers fault by RobertLTux · · Score: 5, Funny

      I see you are about to fry this patient like an egg (doseage set for multiples of normal protocol)
      would you like me to

      1 reset the machine to standard defaults
      2 book you a flight to africa
      3 call your lawyer now
      4 forge the documents to show %person% did the treatment

      or
      You Are about to kill this patient [cancel] or [allow]

      --
      Any person using FTFY or editing my postings agrees to a US$50.00 charge
    13. Re:Not the engineers fault by uncqual · · Score: 3, Funny

      Just make the button detect authorized fingerprints only and require a heartbeat in the finger and also scan the operator's retina and alter lighting to make sure that the iris responds "correctly" to random changes in light level.

      Bet you can't circumvent that with just duct tape. Now, with an Arduino, some peripheral hardware and a few spare evenings....

      --
      Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
    14. Re:Not the engineers fault by Darinbob · · Score: 2, Insightful

      And as I posted earlier, customers have been caught with weights to hold down buttons.

      In this particular case though, that particular dosage may have been appropriate to some uses, but not others. A "maximum allowed dose" can be in effect and still make a patient sick!

      For some machines these doses are controlled mechanically; moving heavy lead and steel plates around, irises, etc. Hardwiring a maximum dosage in this case involves the interaction between many components.

    15. Re:Not the engineers fault by uncqual · · Score: 2, Funny

      Reminds me of "back in the days" of the early mass market terminals that allowed you to program keys to send sequences of arbitrary characters.

      One of the system admins at school was trying out the latest and greatest such beast in his office before deploying it and thought it was a good idea to program F1 to send his userid and password. He also thought that the terminal would not retain the memory when he unplugged it to deploy the device to the public terminal room.

      He learned that two stupid thoughts can be much worse than one stupid standalone thought.

      --
      Why is there an "insightful" mod and why isn't it "-1"? If I wanted insight, I wouldn't be reading /.
    16. Re:Not the engineers fault by ArsonSmith · · Score: 2, Informative

      I'm just going to ductape this authorized doctors finger and eyeball in place and drop an IV into him to keep him fed.

      --
      Paying taxes to buy civilization is like paying a hooker to buy love.
    17. Re:Not the engineers fault by lysergic.acid · · Score: 5, Informative

      Thank god you're not responsible for the design of complex, life-critical systems, like those commonly found on passenger jets, in nuclear power plants, in high-speed rail systems, etc. All of those systems incorporate fail-safe measures so that if something were to go wrong (like an operator losing control) the system would fallback on a safe state.

      Sure, in an ideal world, every operator of a life-critical system would have total understanding of that system, know the value of every system setting at all times, never forget, never be tired, and have an IQ of 200. In the real world, operators are often overworked, susceptible to distractions, minimally qualified, and sometimes under-trained or even improperly trained. Even the most experienced and well-trained veteran airline pilots can lose focus and make deadly mistakes (which is why Cockpit Resource Management has been a major area of research in aviation psychology). You can base your system design on ideal conditions, or you can base it off of real-world conditions; either way, it's going to be operating in the later.

      You also seem to be missing the main purpose of mechanization and automation, which is to simplify a task or make it easier to perform. When you buy a cappuccino machine, you don't want to understand the details of how it operates or be asked for input every step of the process to make a cup of coffee. Eliminating/minimizing the human factor in a particular process is another major advantage of automation. It provides more consistent results and helps to minimize human error. All of this helps to reduce the learning curve and skill level required to perform a task, which confers economic benefits. However, not every well-designed system can necessarily be operated by unskilled personnel—nor would you want a high school drop out to be operating most life-critical systems. Nonetheless, you still want mechanization/automation to simplify the task in these cases. That's because some tasks are so inherently complex and mentally demanding that, without automation, it simply can't be performed.

      Flying a passenger jet is a perfect example of this. Even with all the sophisticated automation (including autopilot) on a modern airliner, it still takes a full cockpit crew (not to mention support personnel on the ground) to safely fly & land the plane. With all of the complex duties that airline pilots need to perform simultaneously, they don't have the time to monitor the status of every system component or manually adjust every actuator on the plane to control its flight surfaces. It may take 50 different mechanical actions to retract the landing gear on a plane, but why clutter the cockpit interface with 50 items when a single switch or button will do? Likewise, doctors and nurses are already required to undergo extensive medical training; they don't need to have to learn how to mechanically calibrate a CO2 laser or calculate the spectrum of an X-ray machine based on the anode material of its emitter and the voltage passed through it. Medical personnel should mainly be trained in medicine and only need to learn how to operate a particular medical device, not how to troubleshoot it or read its blueprints.

      A simple and streamlined interface is much less distracting and more intuitive than a field of buttons and dials for a thousand different minute settings and system readings. Even with the utmost simplification, most industrial machinery and complex systems are still overwhelmingly difficult to operate by an untrained person. It's never just a single "magic button" for the operator to press. A nuclear power plant might take hundreds of different readings from multiple sensors and summarize it with a single status message or indicator light on a controller's console, but that message/light would likely be sitting next to a dozen other status indicators that each take hundreds of other readings. And although a complex process like lowering the reactor temperature might be simplified down to a single "magic button," the c

    18. Re:Not the engineers fault by LWATCDR · · Score: 2, Insightful

      "Even an idiot who did not RTFM should not be able to cause harm with the machine."
      But was this above that limit?
      Different scans REQUIRE different amounts of radiation.
      Nothing can be fool proof. I would bet that there is a limiter but this level could be below that limiter.

      --
      See my blog http://ilovecookes.blogspot.com/ for light hearted technical information.
    19. Re:Not the engineers fault by nobodyman · · Score: 2, Insightful

      he aformentioned Therac incident happened, in part, because such a hardware interlock did not exist.

      Ironically, earlier models of the Therac device *did* have hardware interlocks. These earlier models shared the same software defects as the Therac-25, but hardware interlocks prevented the overdose scenario.

      I haven't RTFA, and I don't even pretend to assume that I could do things better (or even fully grasp the problem). That said, the struggle for efficiency and programmers' tendency to seek out a software solution to any problem seem to be at odds with the multiple levels of redundancy, checks, and balances that are absolutely required for medical technology.

      I would loathe being a software developer in the medical industry. It's a noble thing, but the knowledge that my mistakes could potentially *kill* other people would make me sick.

    20. Re:Not the engineers fault by quanticle · · Score: 2, Insightful

      Well, the Therac-20 "worked fine" in the sense that the mechanical limit on the device prevented the software from delivering lethal doses. It doesn't mean that the Therac-20 was a "good" machine in any sense of the word.

      --
      We all know what to do, but we don't know how to get re-elected once we have done it
  3. Default setting... by courteaudotbiz · · Score: 5, Insightful

    The default setting for an equipment that can be lethal should be "Emit zero radiation". Then for each exposure, set the level of radiation you intend to use. This way, you ALWAYS KNOW the level of radiation the equipment will emit.

    Better investigate "Hey, we got no picture" than "Hey, we got pictures, but everyone dies after that..."

    Didn't RTFA.

    1. Re:Default setting... by eln · · Score: 4, Funny

      That's really not fair...you have no idea that people would die from that radiation. It's at least equally likely they would develop super powers, join up with others who have received similar doses of radiation, and form a crime fighting team of mutants.

      All I'm saying here is we shouldn't just dismiss this as a bad thing until we've fully explored the legislative and societal implications a team of crime-fighting mutants with superpowers would have.

    2. Re:Default setting... by fluffy99 · · Score: 2, Insightful

      Didn't RTFA.

      Well that explains why your comment makes no sense. The system was showing a correct dosage, but was delivering something different since they had been dorking with the protocol definitions. In the Therac-25 case, the error was due to the operators using the program in an undocumented manner and the system incorrectly calculating the required exposures as a result. Also the operator doesn't arbitrarily set a level. He picks a specific protocol from a menu which already has the scanning pattern, timing, and power levels. Don't forget that dosage is power x time, so a low power level run for too long is also a problem.

      If you didn't bother reading TFA, please don't bother posting. Whatever twit modded you insightful should be banned as well.

  4. HULK MAD! by BumbaCLot · · Score: 5, Funny

    Even under normal circumstances, the procedure requires more radiation than most other types of CT scans, said David Brenner, director of radiological research at Columbia University Medical Center in New York.

    Anyone else read this as David Banner?

    1. Re:HULK MAD! by frito_x · · Score: 3, Insightful

      Hate this "immediately moderate when you select an option" feature. meant to mod funny... slip of the mouse goes to overrated... there should be a go/ok button next to the list imho.

      wasted 3 mod points... oh well...
           

    2. Re:HULK MAD! by davidshewitt · · Score: 2, Informative

      If you go to the classic discussion system, this is not a problem. A "moderate" button appears at the bottom of the page for you to confirm your moderations.

  5. Maybe testing it afterwards? by uncledrax · · Score: 3, Insightful

    Maybe next time they will test the damn thing before subjecting patients to it? It's a built in part of my job that I test/confirm a change after I make a change.. because often there's a likely hood of something unexpected or improperly explained that can cause an issue.

    How hard would it have been to stick a dosimeter in the machine after the change and run it though a test?
    (I realize that just a basic dosimeter might not be a sufficient measure.. but it would have been good to get a before/after.. and something like a 8-fold increase would have been easily detectable!)

    --
    ----- The internet has given everyone the ability to have their voice heard equally as loud.. even if they shouldn't be
    1. Re:Maybe testing it afterwards? by RDW · · Score: 5, Insightful

      'How hard would it have been to stick a dosimeter in the machine after the change and run it though a test'

      Supposedly the actual dose would have been displayed on the machine's screen (I wonder how prominently?):

      http://www.latimes.com/news/local/la-me-cedars-sinai14-2009oct14,0,5065886.story

      '"It's in your face on the screen," said Dr. Donald Rucker, chief medical officer for Siemens, a manufacturer of CT scanners.'

      'CT technicians are trained to monitor dose levels, and some hospitals conduct checks before every scan..."There are other places where the techs might be operating more as button-pushers," said Dr. Geoffrey Rubin, a professor of radiology at Stanford University. "The user becomes a little blind to these numbers."'

  6. not idiot proof enough by HNS-I · · Score: 2, Interesting

    While the hospital shouldn't have gone and reprogram the instructions, this should have been prevented at hardware level. The machine should register a patient checking in and the amount of radiation emitted.

  7. In short by Cornwallis · · Score: 2, Insightful

    Will we ever learn enough to make these errors truly uncommittable?"

    No.

  8. Medical Staff were a big part of the problem by CheddarHead · · Score: 4, Interesting

    Along with the usability issues with the design of the Therac-25 it's obvious that the attitude of the medical staff contributed greatly to the problem. Patients complained of being burned, but their complaints were essentially ignored. Meanwhile, they were sent back for multiple treatments. Overwhelming evidence of radiation burns was ignored or given only cursory investigation because medical personal or manufacturer reps claimed that it was impossible for the Therac-25 to be responsible for the burns.

    1. Re:Medical Staff were a big part of the problem by Svartalf · · Score: 2, Informative

      If you read the history...about half of the deaths were due to one-shot incidents where the patent received a lethal dose out of the machine on the first treatment. To be sure, some of the incidents should have been dealt with differently as you indicate- but what about the Tyler, TX incidents, for example?

      Yes... Medical Staff are a big part. But so was the manufacturer of the device- had you read all the evasiveness on AECL's part when the problems started coming in. In the case of the first incident, there WAS an inquiry into what might have been happening but didn't come to light until Tyler's ill-fated mishaps occurred.

      --
      I am not merely a "consumer" or a "taxpayer". I am a Citizen of the State of Texas
  9. Meh... by Machupo · · Score: 2, Funny

    What's a few hundred rem among friends?

    --
    *insert pithy sig here*
  10. The errorless machine... by TemporalBeing · · Score: 4, Insightful

    Will we ever learn enough to make these errors truly uncommittable?"

    There is and never will be such a thing as a machine without the possibility for error. And you'll never get around the old adage/rule - If it can happen, it will. How often it occurs it the key; and while we should always aim to make an error-less machine, it is an impossibility and we can only achieve it by make the occurrence of such errors as few and far between as possible.

    After all, an error-prone human must be involved to make the machine; even if that machine made another machine a human was still involved at some point to make the original. Thus there will always be the possibility for errors. Even if, as demonstrated by the Matrix, iRobot, and many others, the machines make that error on purpose to save humanity - it is still an error.

    --
    Truth is like the sun. You can shut it out for a time, but it ain't goin' away. - Elvis Presley (source: imdb.com)
  11. Film badges? by johnny+cashed · · Score: 2, Interesting

    Would a film badge provide a "check" to determine if the dosage is correct? One x-ray overdose is bad enough, over 200 is really uncool.

  12. Re:No, there will always be risk by Entropius · · Score: 2, Insightful

    Life is brutal, but that doesn't mean we should give up on trying to make it less so. Asking whether CT scanners can be redesigned to make this not happen, and whether it's worthwhile to do so, is very valid.

  13. Feedback? by TopSpin · · Score: 4, Interesting

    Will we ever learn enough to make these errors truly uncommittable?"

    No. As long as correctness can't be proven and operators are permitted to create unanalyzed conditions by altering protocols there will always be risk. There are probably other mis-configured CT scanners out there in use right now that have been overdosing patients for years.

    CT scans use X-rays; an easily detected frequency of light. Why not require that scanners incorporate an independent detector that measures the amount X-ray energy? If that is possible then create an interlock that can shut down the emitter when the net energy gets out of bounds and require that any such incident be NRC reportable. If the detector excluded from alteration by the operators then software bugs, misunderstandings, etc. can be detected even years after the last engineer had contact with the system, either before harm is done or at least before hundreds of patients are literally burned.

    --
    Lurking at the bottom of the gravity well, getting old
  14. Put a dosimeter in there with the patient by ggraham412 · · Score: 2, Insightful

    For patients undergoing scans or treatments involving radiation, why not verify exposure with a 25 cent dosimeter? You'd catch problems right away.

  15. Comment removed by account_deleted · · Score: 5, Insightful

    Comment removed based on user account deletion

  16. Re:Pretty narrow margin by celticryan · · Score: 2, Informative
    Re:

    100s of mSv range

    There are portions of the world that have a very high natural background in the 200 mSv range so you are not quite right with your estimates. In addition, you have to distinguish between whole body dose and localized dose. It is not uncommon to see tumor doses in the 40-50 Sv range.

    The machines were set for .5 Gy (for xrays 1 Gy = 1 Sv) and got 3-4 Gy. A whole body dose of just above 4 Sv is a 50% death in 3-6 weeks (with no medical intervention). (remember that the CT was only to the brain). They are definitely in some dangerous territory, but the article said the median age of the patients was 70. Couple that with the fact that they already had a stroke and it is safe to conclude that long term effects are unlikely to matter.

  17. Re:It's About Automation by antifoidulus · · Score: 5, Insightful

    The advantages of simplified training are not just beneficial on an economic scale. While its unfortunate that this error killed people, think of how many more people would die if complex training was required to use these types of machines. Ultimately, it would lead to fewer operators and thus less access to the machine, which ostensibly helps save lives.

  18. Oh great by Tony+Hoyle · · Score: 2, Funny

    Now there are 206 hulks running around.

    Just don't make them angry.

    1. Re:Oh great by SmlFreshwaterBuffalo · · Score: 2, Funny

      Think they're mad now? Just wait until they get the bill.

  19. Re:Don't be such a wuss by MRe_nl · · Score: 3, Informative

    In 1895, Thomas Edison investigated materials' ability to fluoresce when exposed to X-rays, and found that calcium tungstate was the most effective substance. Around March 1896, the fluoroscope he developed became the standard for medical X-ray examinations. Nevertheless, Edison dropped X-ray research around 1903 after the death of Clarence Madison Dally, one of his glassblowers. Dally had a habit of testing X-ray tubes on his hands, and acquired a cancer in them so tenacious that both arms were amputated in a futile attempt to save his life.

    --
    "Kill 'em all and let Root sort 'em out"
  20. Re:It's About Automation by sunderland56 · · Score: 4, Insightful

    I don't think being trained to fully understand the automobile will decrease the number of automobile related deaths.

    Being trained to fully understand the laws of physics would certainly decrease automobile accidents.

  21. Re:It's About Automation by digitig · · Score: 3, Interesting

    This particular error is the kind that occurs when you simplify complex procedures in the interest of widespread use. It is the fault of specialization, which we typically embrace because it allows us to leverage human labor into increasingly complex areas of inquiry. It's more than just "human oversight" or "machine failure," it's the kind of problem that typically arises when people are trained to use machines without being trained to fully understand those machines.

    A certain segment of society--that's mostly us geeks--strives against this tendency; we become technicians in various fields. But most people, including medical people, get trained by vendors to use a particular piece of software or hardware without reference to its underlying principles or inner workings. This is normal and usually beneficial for various reasons an economist could doubtless relate.

    But one of the things that we geeks should be doing is looking at equipment like this in its overall system context, which includes the operator and which includes the training the operator has received. That's mandatory in the Aviation industry pretty much worldwide (my field); I don't know what the situation is for medical equipment in the USA. No, we will never make such mistakes "uncommittable" -- perfect safety is a myth. But we should be considering possible failure modes, and the likelihood and consequences of those failure modes, to ensure that the risk is tolerable.

    --
    Quidnam Latine loqui modo coepi?
  22. Re:Pretty narrow margin by DragonWriter · · Score: 4, Informative

    It can actually become an issue if someone needs radiation therapy ('chemo')

    "chemo" refers to chemotherapy, where the patient is poisoned in the hopes that the poison will kill the cancer faster than it kills the patient. It is a different form of therapy than radiation therapy, in which the patient is subjected to intense doses of radiation in the hopes that the radiation will kill the cancer faster than it kills the patient. Often, people with cancer will receive both, one after the other, but they aren't the same thing.

  23. Testing wouldn't catch it by Geof · · Score: 2, Informative

    The article is not very detailed, but my reading of it is that the default dose was not unsafe. If I am correct (hard to tell), what happened was that a doctor doing a specialized procedure programmed a custom dose. Then the machine defaulted to this new value for subsequent procedures, but the staff assumed it was using it's previous (safe) default.

    There was a misunderstanding about an embedded default setting applied by the machine . . . Once the scanner was programmed with the new instructions, the higher dose was essentially locked in.

    What is particularly appalling is that it took 18 months to catch this, and they only found out because a patient complained of hair falling out. The FDA recommendation is that doctors double-check that the machine is actually applying the correct dose.

    It seems clear to me that this is a stop-gap that indicates a design flaw. It is not enough for the machine to display the actual dose: the procedures for using it must ensure that this is not missed. From the Therac-25 link:

    There also needs to be greater recognition of potential conflicts between user-friendly interfaces and safety. One goal of interface design is to make the interface as easy as possible for the operator to use. But in the Therac-25, some design features (for example, not requiring the operator to reenter patient prescriptions after mistakes) and later changes (allowing a carriage return to indicate that information has been entered correctly) enhanced usability at the expense of safety.

    This describes perfectly the recent incident. User-friendly defaults resulted in health professionals making unsafe assumptions. Blaming them does nothing to prevent such problems in the future. The system is broken.

    Incidentally, I am not convinced by the lessons learned about Therac-25. It emphasizes proper software engineering practices and licensing. This may be necessary but insufficient.

    Taking a couple of programming courses or programming a home computer does not qualify anyone to produce safety-critical software. Although certification of software engineers is not yet required, more events like those associated with the Therac-25 will make such certification inevitable.

    This might not be enough. Initial testing of the machine had been of hardware only, though the problem was with software. Following the initial reports of an overdose, the company replaced a hardware component. If the real problems fall outside current engineering practices, they may be completely overlooked. In the recent case, the problem appears to include the practices of medical staff. These are part of the technical system, so they need to be treated as such by engineers. Ignoring that is very much like focusing on the hardware to the exclusion of the software. Technical systems are not clearly bounded, and are probably less so as time goes on. There always needs to be a broader view.

    Therac-25 suffered suffered (among other things) from race conditions. The mere idea of having a deadly device that is even theoretically susceptible to race conditions terrifies me: if a race condition programming error is even potentially possible, I would want to make damned sure there's an independent hardware or software check to make sure failures will be caught. Problems like this can be incredibly subtle. I wonder if overconfidence in engineering might lead to complacency.

    What really jumped out at me, however, was the role of the user community, which was formally excluded from the engineering. Following the discovery of one deadly software error, the company (AECL) fixed it and assumed the problem was solved: after which another patient died from a different bug. The users asked for access to the source code. This was denied. Unlike the company (and likely its engineers), the users clearly understood that they were part of the system.

  24. Add a dialog box... by ArcadeNut · · Score: 2, Funny

    That pops up for the operator to respond to....

    Are you sure you want to kill this patient?

    Yes No Retry

    --
    Visit the Arcade Restoration Workshop @ http://www.arcaderestoration.com
  25. Re:It's About Automation by lysergic.acid · · Score: 2, Insightful

    Yes, because we all know that car accidents only kill stupid people...

    I don't think the laws of physics cares how high your IQ is when you get t-boned by a drunk driver at an intersection.

  26. Some quantitative perspective by goodmanj · · Score: 4, Informative

    Typical normal CT scan dose: 1-2 rem
    Faulty CT scan overdose: 8-16 rem
    1950s shoe-salesman's fluoroscope: 10 rem
    Typical normal Therac-25 dose: 200 rem
    Malfunctioning Therac-25 dose: 15-20,000 rem

    Come on, seriously people. Yes, this is a mistake that needs to be fixed, but millions of kids in the '50s got their feet nuked with this much radiation and lived to become healthy normal adults with normal feet.

    The Therac-25 cooked straight through people, leaving a hole of rotting meat behind. This is not even remotely in the same league.

    http://users.rcn.com/jkimball.ma.ultranet/BiologyPages/R/Radiation.html
    http://chestjournal.chestpubs.org/content/107/1/113.full.pdf
    http://www.ccnr.org/fatal_dose.html
    http://www.orau.org/ptp/collection/shoefittingfluor/shoe.htm

    1. Re:Some quantitative perspective by adamdeprince · · Score: 2, Informative

      The expected dose for their treatment was 50 rads, and they received 300-400. http://www.fda.gov/MedicalDevices/Safety/AlertsandNotices/ucm185898.htm. Trying to downplay their dose by comparing it to the therac-25 is a little bit like comparing virtue among whores. They were burned by their dose.

  27. Re:It's About Automation by Ironica · · Score: 4, Insightful

    ...But in that particular accident, the drunk is less likely to suffer severe or fatal injuries. The relaxant effect of alcohol makes their body more resilient to sudden shocks. Also, they're usually having a head-on collision, while they may be striking the other vehicle from the side; as head-on collisions are by far the most common, most of a car's safety features are geared toward mitigating them.

    --
    Don't you wish your girlfriend was a geek like me?
  28. Re:It's About Automation by Lost+Engineer · · Score: 4, Insightful

    The person who reacts correctly to a slide is not doing so because he understands physics in general but because he has driving specific training. There's really no time to do math in that situation.

  29. Re:It's About Automation by westlake · · Score: 2, Informative

    While its unfortunate that this error killed people

    There is no mention of any deaths.

    Even under normal circumstances, the procedure requires more radiation than most other types of CT scans. Radiation exposure increases the likelihood of cancer, though the risk is lower in older patients because they are likely to die of other causes first.

    The median age of these patients is 70 years - and they are surely far more at risk of a second - more dibilitating - stroke than a cancer that might not manifest itself for another five, ten, or fifteen years.

  30. Must have heard wrong... by Kratisto · · Score: 2, Funny

    I always thought it was 10% luck, 20% skill, 50% concentrated power of will, 5% pleasure, 50% pain, 100% reason to remember the name.

    --
    Conscience is the inner voice which warns us that someone may be looking.
  31. Re:It's About Automation by Richy_T · · Score: 2, Insightful

    The watchdog timer on the radiation module detects lack of input and shuts it down?

  32. Re:It's About Automation by Kratisto · · Score: 3, Informative

    Speak for yourself. I mounted a pad of engineering paper to my dash for just such an occasion. Just this afternoon I was drifting to the left due to rain slick roads, and once I had done the necessary calculations, I realized I ought to depress the throttle 16 mm and turn the steering wheel 68.5 degrees in the +x direction in order to regain control.

    --
    Conscience is the inner voice which warns us that someone may be looking.
  33. Re:It's About Automation by dgatwood · · Score: 3, Funny

    Was that before or after your car hit the bottom of the ravine?

    --

    Check out my sci-fi/humor trilogy at PatriotsBooks.

  34. Re:It's About Automation by Tired+and+Emotional · · Score: 3, Funny

    I don't know. I never have really understood Statistical Mechanics and I have probably not already died in a car accident.

    --
    Squirrel!
  35. Re:It's About Automation by jimicus · · Score: 2, Interesting

    I don't know about the US, but in the UK the qualification you take to give CT scans these days is usually a degree - you'd be a diagnostic radiographer. How much more training do you want?

    The problem isn't the qualification, it's the change in protocol. Someone thought it would be a good idea to override the machine's inbuilt safety cutout by resetting it part-way through the scan, proving that being highly qualified is no barrier to making dangerous decisions.

  36. Re:It's About Automation by Ironica · · Score: 4, Informative

    Woops, silly me, repeating what I learned in upper-division Transportation Engineering lecture from professors with decades of experience in the field of road design. Guess I should have checked Wikipedia first, because it never lies!

    Got a cite for your critique?

    It's true that the majority of people who die in alcohol-related crashes have a BAC of .08 or higher (67% according to this site). However, lower down, we see that 37% of single-car crashes involve a BAC of .08 or higher, which is higher than the 22% average rate. Since my point was about the comparative risks to the drunk driver and the sober driver in an accident, single-car crashes are irrelevant. That takes out 67% of the drunk driving crashes overall, and similarly lowers the fatality numbers considerably.

    --
    Don't you wish your girlfriend was a geek like me?
  37. Re:It's About Automation by digitig · · Score: 2, Interesting

    Only if you accept that it will never be reached, and that there is a tradeoff in aiming for it. I'm all too used to the media and government calling for punishment for those who failed to do what could not be done, or processes getting bogged down with "protections" that will probably never protect in the lifetime of the systems they "protect". Safety is best served by realism and honesty, not by a "something must be done" attitude.

    --
    Quidnam Latine loqui modo coepi?
  38. Re:It's About Automation by ResidntGeek · · Score: 2, Funny

    You're saying it's better NOT to find the bug in the code responsible for turning off the X-ray?

    Jesus, what must your code look like?

    --
    ResidntGeek