The cupcake is a lie.

Very nice. A friend of mine just wrote an easy to use cloud app that does many of these steps automatically. Free yourself from GoDaddy!

https://laterdaddy.herokuapp.com/

This is simply not true.

If you are legitimately speeding (safely) to perform an urgent operation, the police may escort you to the hospital, enter with you, verify you are about to do an operation, then leave you without a ticket (it happened to several of my colleagues, usually late at night.)

Just being pulled over and showing your hospital badge / white coat is not going to help you 99+% of the time. *Especially* if you were driving in a dangerous fashion. One of my friends has a funny story on how he tried it after being pulled over, and his ID says:

".... ..., MD
DERMATOLOGY"

The police officer laughed and gave him the maximum fine.

Totally agree with you. I'm a cardiologist, and this article just is full of alarmist oversimplification. Leaders in this industry are not complete idiots, and currently all of the connectors that they describe ARE incompatible (except, as you note, the intrathecal, as it is often essentially stock IV tubing, but ports are covered with a big warning / sticker.)

Making "special" tubing, as the article glosses over, may make the problem worse (e.g. situation:

Nurse: Quick, we need an IV in this patient in the ER, his pressure is low.
Tech: We don't have any IV tubing in this bay, but there is some black intrathecal tubing.
Nurse: Let's just use that for now (a tube is a tube) for the IV and change it later. It is an emergency.
Tech: Ok.

5 minutes later, somebody comes along with spinal anesthetic, and now that it is "safe" with a color-coded tube, doesn't trace the tube to the insertion and just injects it into the patient.)

All safety legislation / efforts have consequences, and may not actually make people safer. Here, the situations described are *EXTREMELY RARE*, and frankly, likely due to negligence (I don't have exact details for each instance, but likely the person did not trace the tube, or jury-rigged incompatible connectors together.) Safety cabling may lead to a false sense of security, and current connectors are already incompatible. There is no shortcut or excuse for constant vigilance.

Probably a lot of books written on it -- Atul Gawande did a pretty big "study" with safety checklist prior to OR activation. We have several checklists (independent of anesthesia) before starting any invasive procedure, so this is kind of behind the times. It is more targeted at foreign hospitals or places that have a lot of mid-level providers that are not used to things. If you are interested, the full study can be found here:

http://content.nejm.org/cgi/content/full/NEJMsa0810119

gbutler69 writes:
>Says who? Citation Please?
[snip a bunch of rhetorical questions]

From your questions I infer you are completely out of touch with this field in any sort of form. If you want a citation, do a tad of research on your own and you will discover things; I won't spoon-feed.

Poke around here to start (but some of this might be biased the *other* way.) Do a good deal of academic reading and you will get a good feel of what is going on:

http://www.sickoflawsuits.org/

Again, ridiculously simplistic analysis.

>you should be excited every time you hear a doctor is being sued for malpractice.

You have got to be kidding; that statement is simply ludicrous. I don't engage in some sort of weird schadenfreude when somebody gets sued, even if it were somewhat legitimate. Medical school is relatively difficult to enter, selects for the most driven people, and is a long process where several dozen people work with you and gauge your progress and abilities. *OF COURSE* bad doctors need to be stopped, just like "bad pilots" or "bad computer programmers." Indeed, a lawsuit is one of many ways, in fact a poorly targeted way, of doing this. There are many other options including board registration, hospital credentialing, and outcomes monitoring. Life is not black and white.

The second paragraph of your post makes little sense. Can't have it both ways? Are you advocating ruining the career of good physicians in the hope of catching bad ones with a broad net? I am not advocating increased lawsuits, as the *vast majority* of them are groundless. That is not an opinion.

And yes, I am a doctor. You can check my long posting history for a bit of confirmation or at least support.

Ok, I'm responding to a troll, I know. But here goes. The post has a core of truth, but like all Slashdot-postings the "It's so simple I could just figure it out and do better" high-school naivety predominates.

>Doctors and surgeons routinely **** up on the most basic things, like which side of the body they're operating on, often in some VERY serious, permanent operations, like amputations.

  - I have done thousands of operations and never a wrong-side operation. It is something that is taken *extremely* seriously, and we have at least three checks that guard against this. With over a billion procedures done per year, yes, there will be many that make the news, not unlike planes taking off on the wrong runway, etc., etc.

>Doctors and nurses, time and time again, have been shown to not practice the most simple procedures for infection control, like washing their hands before/after every patient.

  - True again to a small degree, but everybody at my hospital does this. It probably could make a bit of difference if done nationwide, but again, this is taken extremely seriously.

>A couple of doctors in the Boston area have a)left patients on the operating table (opened up!) to run an errand at the bank b)shown up drunk or high for operations c)been beyond unprofessional to staff 'below' them (screaming, throwing things etc.)

  - a) I was a resident at the very same major hospital when this happened. I know the inside story, and it was nowhere near as simple as it sounds.
  - b) ?? The MD would be promptly fired. I don't understand what kind of life you imagine we lead.
  - c) Yes, I agree this is a problem. This is a very big problem that the medical "culture" has some deficiency with. Equally bad is an antagonistic attitude by people "below" the MD who try to passive-aggressively sabotage things or "protect the patient" by alienating the rest of the staff. We need to work as a team, and at my hospital I strive to make sure that is always done.

> When the *** up, the malpractice covers the lawsuit.

Again, you have some sort of "fantasy" about M.D.s that is not remotely grounded. I'm guessing you wanted to go to med school and never had the wherewithal to go through with it? Or maybe had some unfortunate experiences as a patient?
  - Nobody, NOBODY wants to get sued. The idea that we just sit in a lounge and make patients wait, etc., is pure nonsense. I work my a$$ off every day, and my friends with similar education and ethic get paid twice what I do. I am far from "among the most highly paid in society."

If you want a realistic sense of what may go on during a suit, read this piece:
http://www.nytimes.com/2009/12/29/health/views/29case.html?_r=1

I'm surprised nobody brought up -- needless encryption makes a *huge* headache for running diagnostics on any sort of server. If any sort of script is not working, there is difficulty in evaluating what is happening, and even network diagnostics is much more complicated.

Additionally, encryption wastes a lot of CPU cycles if not needed. Although a small argument, this slows down networks and costs $$$ by burning fuel.

Finally, you have to make sure encryption is done right to be secure. If you encrypt everything, it is more difficult to see where there might be a vulnerability because there is more to audit. Think of the analoy to personal encryption -- unless you work for the NSA or something it is much better / easier to encrypt a directory on your disk with personal stuff than trying to encrypt your whole logical volume.

Which would be easier to recover from if you had a hardware fault / disaster?

I thought the headline of the article was actually a joke; these systems are found in almost all major hospitals. There are companies that will install them:

http://www.swisslog.com/index/hcs-index/hcs-systems/hcs-pts/hcs-pts-translogic.htm

this is an established industry, and nothing new... Each hospital in the conglomerate that I work in uses a pneumatic tube system.

Weird that somebody picked up this Stanford "press release" and found it suitable for Slashdot...

I know that I'm arguing with a trolling AC, but for the other readers of slashdot, you should know that the grandparent's post refers to the controversy regarding the analysis of the Patriot system during the first Gulf war. There was a huge propaganda machine behind the Patriot's "successes" which turned out to be very near zero indeed. This was covered in a series of hearings in the early 90's...

http://www.fas.org/spp/starwars/docops/pl920908.htm

You can also read up on this from transcripts from the hearings after the war.

In the interests of fairness, here is a rebuttal / review.

http://www.fas.org/spp/starwars/docops/zimmerman.htm

I remain unconvinced -- from reading this (almost 20 years ago) I concluded that at best, the military did not know for sure that these worked well.

It was at Harvard in the mid 90's, but I don't think the course is THAT unique (I know that MIT, Carnegie Mellon, University of Michigan, and numerous other colleges have similar courses.)

The schematics for the computer we build is available -- appears that they still build the same computer!

http://www.courses.fas.harvard.edu/~phys123/classnotes/bigpic_0409_bw.png

This is almost exactly what Woz did -- after the course you still have a wonderful respect for him, but at the same time realize that it is humanly do-able, not taking anything away from his great work. Some of the subsequent projects other groups in our course did were incredible; one guy built a custom video D/A output with sprite-drawing subroutines so you could play his custom assembly-written pacman with the hex keypad on a standard oscilloscope. I still have photos of mine in action somewhere.

Agreed. This is little more than assembling something from a recipe (IKEA, anyone?) that teaches you little. The descriptions "solder that resistor" and the fact he clearly doesn't understand the details of things makes it a less interesting experience.

I would recommend a course on digital electronics instead -- many of these courses (including mine in college) have you assemble a 6502 computer yourself from components, and then you will understand the role of the memory and data buses, counter, memory addresses, A/D converters, in addition to understanding CPU timing, latches, machine code, and elementary programming, etc., etc. We built one that displayed output on an oscilloscope and hex LEDs. It will be 10 times as much effort, but infinitely more rewarding. One of the most difficult yet fun courses that I took in my life.

Exactly. People overvalue the concept of "idea" and undervalue the concept of aggressive business positioning, development, marketing, capital, and a lot of, well, work.

I was at Harvard when facebook was "born." I was persistently skeptical about the whole thing, as the concept was not new *at all*, and friendster was reigning supreme, which I kind of thought was a silly fad. I was subsequently astounded over the years how facebook has taken off. (I am still astounded.) But, had the founders listened to me, or saw that their idea was "taken," it would have gone nowhere.

That being said, I wouldn't give a highly established potential competitor research data that you have gotten to get your idea off the ground. Despite my words, I also hold a few patents, but these are mostly defensive positioning and required by my corporation.

Nebulous "ideas" have an insignificant chance of being "thought of" already. What you need to do is get honest feedback about the barriers to implementation, then just go and do it!

I am happy to see some thought go in to "routine" matters like this -- too often I feel that laptop keyboards have abominable designs, such as shrunken space bars and control keys, miniscule arrow keys, or nonstandard placement of arrow keys, etc.

However, I would say the esc enlargement on my Lenovo is unneeded -- its location above the other keys means it is struck accurately. I would venture to say the same for the delete key, which I could locate with my eyes closed by its characteristic placement. I think the aesthetics of the vertical extension of these keys is going to be negative.

For my money, I wish they would just lay off the IBM keyboard design. Thinkpads should not have a Windows key. :)