Want to read Slashdot from your mobile device? Point it at m.slashdot.org and keep reading!

 



Forgot your password?
typodupeerror
×
Businesses Communications IT Science

Big HMO Jolted By Email, System Failures 171

JoanofAlaska writes "The Wall Street Journal is running a front page story about the internal mass e-mail that exposed the failing $4 billion dollar electronic medical record system at Kaiser Permanente, the biggest non-profit HMO in the country. When word of the system's meltdown quickly spread back in November, one reporter obtained a 722 page internal document that showed patient safety lapses as a result of the system's problems. Then in February, the Los Angeles Times had a front page story in which a systems analyst who worked on the project called it 'the worst [technology] project I have seen in my 25 years in the business.' They've created a website to try to rebuild confidence in the project, and they say their goal for system availability is 99.7% (they're currently at 99.2%)."
This discussion has been archived. No new comments can be posted.

Big HMO Jolted By Email, System Failures

Comments Filter:
  • Smoke, meet fire... (Score:5, Informative)

    by Anonymous Coward on Friday April 27, 2007 @08:53AM (#18899641)
    Here's the first e-mail [kaiserthrive.org]. Their CEO sent out an e-mail response [blog-city.com] to all their employees the next day (the same day it looks like the CIO suddenly resigned effective immediately).

    I don't know what to say about the first e-mail until I see more but the CEO sounds like a real jack ass in the second one. And if that 99.2% number is right then they got bigger problems than some email - that's all I can say!

    ac
    • by arth1 ( 260657 ) on Friday April 27, 2007 @09:11AM (#18899873) Homepage Journal
      To put the 99.2% figure in perspective, it amounts to almost 3 full 24-hour days of downtime a year.
      • Re: (Score:3, Insightful)

        by volsung ( 378 )
        I'd like to see more places quote availability numbers as a percentage AND the longest downtime interval in the previous year. 12 minutes of downtime every night at midnight sucks, but 3 solid days of downtime is a disaster.
      • Re: (Score:3, Informative)

        by aaarrrgggh ( 9205 )
        I think in 2006 they had 2-3 major incidents in each of their two data centers. Power might have only been out for around 15 minutes each, but system recovery took well over 8 hours for many of the problems. There were also several planned shutdowns for construction activities, which accounted for another 4-5 6 hour scheduled system outages. ...And all the while, IBM is telling them they just need an N+1 UPS system...

        Looks like things are getting better now; they have brought in several IT and facilities
        • Re: (Score:3, Informative)

          by R2.0 ( 532027 )
          What's wrong with N+1 redundancy? While I agree it requires an attentive response from Facilities to replace the failed unit quickly, my experience with facilities departments is that, if there is greater redundancy, they tend to rely on it to stretch out response and replacement intervals.

          For instance, we stated having failures of refrigeration units in a new facility I helped build. Everything was going fine, until we stated getting calls regarding multiple equipment failures and risk to the product ins
    • by eyeye ( 653962 )
      I've been reading up on this and it is disgusting, it is a not for profit organisation but cronyism is siphoning millions or billions out of it. Someone with a wikepedia account should note this controversy on the Kaiser Permanente [wikipedia.org] page.
  • If you want to see the oldest computer gear simply go to a hospital, insurance company or doctors offices. These places hate to spend money on IT and let old gear sit in place for almost ever. A local hospital here has several Windows 98 pc's still in use. Most doctors offices have antiquated IT gear (Dentists as well) and when my wife was in Insurance billing before she got her CPA she worked on old wyse 75 terminals and this was for a HUGE rich insurance company.

    • If you want to see the oldest computer gear simply go to a hospital, insurance company or doctors offices

      While the use of old technology at a physicians office may be true, I wouldn't generalize hospitals in that category. I have consulted at two different hospital systems in the past six years. At each location, the hospital was pushing to the forefront of technology. My last hospital was in the early stages of virtualizing all of their hardware environment and was using the most recent UNIX hardware

    • Re: (Score:3, Insightful)

      by Applekid ( 993327 )
      Considering how maintaining accuracy of patient history, treatment records, billing records, allergies, lab reports, and others is paramount I'd say if it ain't broke don't fix it. Could you imagine the change controls in an environment like that? "Potential impact: PEOPLE WILL DIE DIE DIE."

      • Re: (Score:3, Informative)

        by Enry ( 630 )
        What parent said. WYSE terminals aren't that bad, given that a lot of the medical data industry got it start from what is now known as VistA [sourceforge.net]. By some strange coincidence, the name of its predecessor was DHCP. Anyway, it worked on dirt-old VAX systems and output to text-only terminals over serial lines. Worked just fine.
    • Re: (Score:3, Insightful)

      by prgrmr ( 568806 )
      when my wife was in Insurance billing before she got her CPA she worked on old wyse 75 terminals and this was for a HUGE rich insurance company.

      There are several legacy, "green screen" apps in the insurance industry still kicking around out there. Some of these were initially developed as far back as the late 1970s. They are capable of high transaction rates in comparison to java-driven, web-based, "thin client" applications. Many of today's OLTP applictions would be better suited for ASCI-based interf
    • Re: (Score:3, Interesting)

      If you want to see the oldest computer gear simply go to a hospital, insurance company or doctors offices.

      I was involved in a project a few years back where a hospital's IT system ran on a bunch of OpenVMS systems, because the main application only ran on OpenVMS. (Which I concede is a capable operating system (logicals are even more powerful than symlinks, etc. etc.) but was outdated even in 2001.) They were also - by a factor of four or so - the largest deployment of the software, so they ran into all

    • My dentist office still uses DOS/text mode on a PC (no idea what's the setup -- maybe a 386?).
    • Re: (Score:2, Insightful)

      by NTT ( 92764 )
      Hospitals generally don't keep old computer equipment because they are cheap bastards. Because of the patient safety issues, and related federal/state regulations, most medical related software have *extremely* narrow specs. They keep the old hardware around because the software provider will only certify the product's reliability on a specific class of computer. And this carries over to other responsibilities seemingly unrelated to direct patient care. I once had to maintain a quite old hospital food inven
    • Re: (Score:3, Insightful)

      by gstoddart ( 321705 )

      If you want to see the oldest computer gear simply go to a hospital, insurance company or doctors offices. These places hate to spend money on IT and let old gear sit in place for almost ever.

      That's not being cheap. That's being a very conservative organization who can't really gamble on things suddenly not working.

      I have seen numerous projects where a company with some older machines (say, mainframes) is being sold a piece of software to replace their 20 year old system -- and replace it with a Windows bo

      • I worked for a steam cleaning company on their billing computer. Small company, 10 employees tops.
        Eventually the printer died. The app (dos, running on a 486) was hard coded for only three possible printers.
        Guess how many I was able to find? none. not on ebay, not supported with emulation. none. I contacted the person who wrote the app and asked if I could have a copy of the source, to update the printer driver. I offered to sign an NDA and a non-redistribution agreement, as well as giving the source c
    • Nononono.... Auto dealerships.

      I had personally, in 1999, had to go in and call Texas Instruments specifically to special-order a logic board for an ailing TI-931 terminal (early 80's model). I'm betting it's still there, right next to the old COMBAT 300-baud modem they used to call in their accounting sheets to Ford Motor Company every night.

      (Then again, I was living in my hometown in Northwest Arkansas at the time, so draw your conclusions from that too...)

      /P

      • I saved a dozen Televideo terminals from the dumpster in the early 90s when my company upgraded. I used them to dial in to my shell account. When I moved into a smaller house in 99 or 00 and had to sell them I was shocked to find many eager buyers. I could get a hundred dollars easy.
    • Re: (Score:3, Interesting)

      by sphealey ( 2855 )
      > If you want to see the oldest computer gear simply go to a
      > hospital, insurance company or doctors offices. These places
      > hate to spend money on IT and let old gear sit in place for
      > almost ever.

      Except that this article shows why that might be: true critical systems need to be reliable and understandable. Systems that have been in production for many many years often meet those requirements. That is why you often see 3270 green screen applications in large medical offices, and DOS or (old,
  • by xxxJonBoyxxx ( 565205 ) on Friday April 27, 2007 @09:03AM (#18899755)

    In a blistering 2,000-word treatise, Mr. Deal wrote: "We're spending recklessly, to the tune of over $1.5 billion in waste every year, primarily on HealthConnect, but also on other inefficient and ineffective information technology projects."


    C'mon, it really can't be that bad, can it?

    Kaiser refutes Mr. Deal's assessment of its custom software system, developed by Epic Systems Corp.


    Oh, Epic Systems? No wonder. Dude, you're f****ed.
    • Man. And you thought it was just DNF.
    • by Mumpsman ( 836490 ) on Friday April 27, 2007 @09:23AM (#18900053)
      Oh, Epic Systems? No wonder. Dude, you're f****ed.

      *sigh* - too true. Epic requires a monumental effort just to get the off-the-shelf product to work properly. Kaiser is doing a massive amount of internal development in addition to trying to implement as Epics biggest customer.

      Part of me wants to think that Justin is just fresh meat who hasn't put in the time to become as jaded as the rest of us in HIS. The other part of me thinks he might be right and that Kaiser has bitten off way more than it can chew. Failure to understand the effort involved is just as pervasive as the massive waste he's critiquing, and just as harmful.
      • Re: (Score:3, Interesting)

        by drgonzo59 ( 747139 )
        Exactly. Just do a search for Epic Systems employment and you'll find plenty info Epic. I am sure your "sigh" means that you already do know. I wouldn't wish even my enemy to work for Epic Systems. That place is so messed up, it is scary. Their CEO and founder Judy Faulkner is crazy, she decorated the place with bright yellow and blue walls, crazy wierd "art" pieces and she never shows up to interact with anyone and just hides for days on end. That is still the best part. They hire naive fresh grads, promis
    • I work for a fairly large healthcare system that is in the midst of deploying Epic's products, the first go-live is coming soon. I've heard the project is a mess, and people are quitting left and right. I guess I'll find out more soon...

      Anybody got some useful references on how much Epic sucks and how screwed we are? I'd like to know ahead of time so I can start looking for a new job.
    • That figures. I applied to work for Epic and they couldn't even keep up with managing my phone number, contact info and interview appointment times. Then they had me take a test and one of the possible languages to write the test in was Cobol. Yeah, a paper and pencil programming test in Cobol. Sure they had C, C++ and Java but they also had Cobol for goodness' sake.

      Then I asked the recruiter what database systems they use and they mentioned CACHE and the MUMPS language. MUMPS is some archaic pre-C

  • More horrors [worsethanfailure.com] than you want to imagine.
  • The problems with the new Kaiser software are obvious to anyone who's been to Kaiser recently or spoken to a doctor or nurses who work there. Test results disappear, appointments disappear.... sometimes the people on the phone can't schedule appointments at all and tell people to call back later.
    • Test results disappear, appointments disappear.... sometimes the people on the phone can't schedule appointments at all and tell people to call back later.

      I experience poor service whenever I deal with any organization in Health Care. Of course, where I live, Kaiser isn't a significant presence, so I can't blame them or their new software. I just blame it on the shitty system of Health Care we have here in the US.

      • Re: (Score:3, Funny)

        by CmdrGravy ( 645153 )
        You actually have healthcare in the US ? I didn't realise that, the impression I got is that when you get ill in the States you have to go off to the market rather than a clinic or hospital like you do elsewhere. I guess once you get to market you can swap your cow or goat, or whatever, for advice from the wise women who live there ?

        • Puleeezzze.

          Ever since the '40s we've been trading in zebra finches. Much easier to carry, and you can swap 2 finches for a goat and 10 finches for a Cow at any local farmer's market.
  • For the benefit of those of us who aren't Americans, why not say what an HMO is?
    • by binaryspiral ( 784263 ) on Friday April 27, 2007 @10:11AM (#18900767)
      For the benefit of those of us who aren't Americans, why not say what an HMO is?

      If only there was a way for someone to find information on the internet. Like a centralized tool or website that indexes other websites and allows people to search for it when they don't understand.

      Or wait, even better - how about an encyclopedia like website that could contain vast amounts of knowledge.

      Ah, that would be grand.

      • Journalism rule no.1: Know your audience. Ensure your work can be understood by your audience. Slashdot is read by people outside the USA.
        • by nasch ( 598556 )

          Slashdot is read by people outside the USA.

          Firstly, Slashdot is intentionally US-centric [slashdot.org]. If people from France or Japan or wherever don't like that, they should look for other news websites, because this one is apparently not for them. Secondly, the GP's point is that Google and Wikipedia are also read by people outside the USA, and in this case should have been. Here are the results from a Google search on HMO [google.com], the first of which is the Wikipedia page on it, with "Health Maintenance Organization" spelled out right on the search results page.

    • Comment removed based on user account deletion
  • So what? (Score:3, Insightful)

    by 0123456 ( 636235 ) on Friday April 27, 2007 @09:20AM (#18899997)
    From what I understand the British government have blown about $25,000,000,000 on a computer system for the National Health Service which doesn't work worth a damn and which the doctors didn't want in the first place.

    Private incompetence pales in comparison to government incompetence.
    • I think there's a whole load of incredibly expensive and functionally useless computer systems in the NHS, this latest one is in good company.
    • Re: (Score:3, Insightful)

      by sfjoe ( 470510 )
      Private incompetence pales in comparison to government incompetence.

      Actually, the oposite is true. For example, the US Medicare system spends about 98% of its funding on patient care. Even the largest and most efficient private insurers only can manage about 90%. The radical right-wing wants to preserve the profits of private insurers and so they spend a great deal of their propaganda efforts highlighting mistakes in the public sector so it appears that government is less efficient than it actually is.
      • Re: (Score:3, Interesting)

        by swillden ( 191260 ) *

        For example, the US Medicare system spends about 98% of its funding on patient care.

        Administrative overhead is just about the worst possible measure of efficiency. What you want to measure is amount of needed services delivered for the cost. Medicare's low administrative overhead means that it doesn't have the administrative capacity to avoid paying for unnecessary procedures or to catch providers upcoding visits or procedures or outright inventing them. Even ignoring the question of how much of the services Medicare pays for are actually necessary, Medicare has a huge rate of outrigh

  • by msblack ( 191749 ) on Friday April 27, 2007 @09:22AM (#18900031)
    This 45-year old lifetime Kaiser patient believes the media frenzy has blown this out of proportion. Kaiser Permanente undertook the monumental task of converting its patient records system into an electronic information system. Converting the hundreds of paper records for each of millions of patients is truly a monumental task and some problems will occur.

    Let me tell you of my experience visiting my doctor yesterday (Thursday). During my visit, my doctor pulled up recent lab results on the exam room console. He was able to prescribe new medication and schedule follow-up lab test through the system (no paper). I went down the hall to get a tetanus booster, then walk downstairs to pick up my prescription. All with no paperwork. I believe their system is phenomenally successful. I won't dispute the cost of this project.

    I've undergone a number of procedures and consumed considerable medical resources during the past year. All of my records are computerized and information is easily shared among their medical professionals. The doctors, nurses, lab technicians have access to information required to deliver quality medical care to me.

    • Re: (Score:3, Interesting)

      by Mumpsman ( 836490 )
      As someone who was up until 1:30 this morning frantically loading RAs into Chronicles in preparation for my Sunday go-live, I really needed to read your comment today. Dealing with Epics goat cluster of poor design decisions can easily lead an IS shop into a downward spiral of negativity and depression, loosing sight of the real purpose - patient care.

      Does the "pain" I feel really matter when there are actual sick people up in that building relying on providers who need up-to-date and accurate informati
    • Re: (Score:3, Insightful)

      by juuri ( 7678 )
      As a 45 year Kaiser member you should. What they have done and are still tuning is nothing special. Other HMO/MMOs have already done such and many did this years ago for a far cheaper price. Yes, what you saw was convenience yesterday and that is an awesome selling point. What you didn't see what the horrendous roll-out time for this project, the multiple attempts at re-inventing the wheel and the wasted excess in monies spent which is passed on.

      It really pains me every-time I see one of these large organiz
      • In many cases it would be *just* as fast and more importantly *cheaper* to create a new internal division or ramp up their own IT staff to complete these projects.

        I seem to remember that Kaiser had an internal division which was working on a electronic-medical records project back in 2000/2002. They shut down the project, laid off a bunch of staff, and started over with a whole new system.

        I know that not everyone has had a good experience. I have used Kaiser in the past, and it was horrible. For us, this ne
  • by Mad_Rain ( 674268 ) on Friday April 27, 2007 @09:27AM (#18900099) Journal
    There is a Computerworld article [computerworld.com] from the previous slashdot story that seems pretty helpful in understanding the meltdown of their electronic medical records systems. They say that they are running the world's largest Citrix server system, and it does not scale well for their purposes.

    As someone who has been frustrated by a variety of Electronic Medical Records systems in different medical settings, I must say that my "favorite" has been VistA [vistasoftware.org] (the medical records software used by the Veteran's Administration, and no relation to Microsoft Vista). Currently, I'm using GE's Centricity [gehealthcare.com] at my work site and have had some minor problems that have resulted in delays in entering my data. (Problems with VistA were more related to the entire network being down - problems with Centricty have been with database connectivity... I wish I could say more about it, but I'm not an IT person, I'm just a lowly end-user).
    • Citrix? Hah! No wonder they have issues. Citrix servers are an absolut pain to properly maintain.
    • How is the VA's system to work with? As far as I know, it's a huge success story compared to the British and KP failures.
    • The VistA system uses a very interesting database/programming language called MUMPS - long story short, it was doing 20 years ago what Oracle and EJB 3.0 are doing today. Variables declared in the correct way in MUMPS are automatically created in the database - the programmer doesn't have to worry about how that's done, or how to connect to the database. They just make up their variables, define their methods, and the system does the rest. There are newer implementations such as Cache that use the MUMPS
  • by eln ( 21727 ) on Friday April 27, 2007 @09:31AM (#18900161)
    If only these guys had used Hyperion to manage their data, they wouldn't be having this issue. Hyperion can effortlessly manage up to 12 GIGABYTES of data, and all you have to do is partition it into 3 different pieces.

    Hyperion: If it's good enough for Google, it's good enough for you.
  • by WarlockD ( 623872 ) on Friday April 27, 2007 @09:39AM (#18900285)
    Dell offers contracts for 99.9% system availability. This means that if you pay the service contract, your within 30 miles of a depot, they guarantee the system won't go down because of hardware for 8.76 hours out of the year. In training we were calculating all that. Technically, it calculates to two "no post" service calls out of the year. So it looks really good when you market 99.9% reliability.

    It's also why many companies can say 99% uptime as that's close to 88 hours of downtime out of a year.

    Hours in a year 8760
    99% = 87.6 hours
    99.2% = 70.08 hours
    99.7% = 26.28 hours

    If they are at 99.2% right now, I wonder how the heck they are going to get that extra 0.5% percentage points with all the problems they have now.
    • Re: (Score:3, Insightful)

      You know what's sad? I started my IT career with Compaq at it's (nee DEC) non-stop computing department. 99.99999% uptime for these suckers. Redundant everything, hotswapping of HDs, all in 1999. Can't believe people are touting 99.9% hardware availability as a success. Not when 99.8% availability for critical apps is becoming a de-facto minimum....
      • by renoX ( 11677 )
        I think you're wrong..
        Sure there are computer with 5 9 availability, my first job was programming on a Stratus, an expensive but very reliable computer, but
        1) even with a Stratus those 5 9 are mostly theoretical, in one year, I've seen:
        - power outage: the maintenance guy cut the wrong cable.
        - several software failures.

        2) a complex system is usually less reliable than the parts used to build it.
        • True - the seven nines were theoretical, and I hadn't seen any data on one of those machines running for a year. However, I don't count application failure as part of the server going down. Those 7 nines were strictly for the server itself being up... which definitely cuts down on the complexity. I agree that if you start adding actual applications into the mix, you'll be very lucky to even get to three nines.

          I think though that if you start with hardware that is only 99.9% reliable, it will be impossible t
    • In fairness, they had some huge growing pains with the project that simply were not properly planned out. They outgrew all of their data centers at once, bought a new one that they thought they could just move right into... and had to spend $100M to upgrade it. That forced them to stay in the facilities that were bursting at the seams longer, and work through some extremely high risk activities.

      In theory, 99.7% uptime is a system outage of 6 hours once a quarter for maintenance. It might take them a coup
      • by jhfry ( 829244 )
        Scheduled maintenance windows are usually not calculated in uptime measurements. Nor are times the system is unavailable during batch processing, or other predictable downtimes.

        I cannot say that is a High Availability system, such as this, that they use the same standards.

        And to say that they can't achieve 99.9% availability for power is entirely false. Rackspace, who hosts my companies website, has far better than 99.9% uptime on their infrastructure. That's what redundancy and backup generators are for
  • 'the worst [technology] project I have seen in my 25 years in the business.'

    Yikes. If his 25 years of experience are anything like my 10 years, then that's saying a LOT.

  • Maine does a system cutover over 2 years ago, and its still broken. Doctors go out of business because they can't get paid, and everything's a mess. I think this one wins :-/

    http://www.cio.com/article/20133/Maine_s_Medicaid_ Mistakes [cio.com]

  • by ericferris ( 1087061 ) on Friday April 27, 2007 @09:45AM (#18900367) Homepage

    From the ComputerWorld article: Deal and an IT employee, who spoke to Computerworld on the condition of anonymity, said part of the problem with the HealthConnect system is that the Citrix Application Delivery infrastructure implemented by Kasier just can't handle the load of the Epic Systems.

    "We're the largest Citrix deployment in the world," Deal said. "We're using it in a way that's quite different from the way most organizations are using it. A lot of users use it to allow remote users to connect to the network. But we actually use it from inside the network. For every user who connects to HealthConnect, they connect via Citrix, and we're running into monumental problems in scaling the Citrix servers."

    So instead of deploying the app on N thousands Windows desktop, they deciced to use Citrix to remotely connect to a pool of servers. The Citrix server and the Windows machine at the other end could not stand the load. Big surprise.

    The way normal people would do it is use an X11 graphic application (X11 is available for Win32), or use a Java webstart client, or even do everything within a browser, or... But there are many, many way to architect a distributed app these days.

    The ONE thing you shouldn't do is deploy lots of Windows servers, use the half-baked ICA protocol, and expect everything to be peachy.

    Remember, CIO boys and girls: Uncle Bill's broken OS just cost lil' Cliff Dodd his job. Don't be the next one. Keep Win32 where it belongs, outside the server room.

    • by kahei ( 466208 )

      "We're the largest Citrix deployment in the world," Deal said. "We're using it in a way that's quite different from the way most organizations are using it.

      Considering the performance and flexibility problems observed even on small, normal Citrix installations, I'd have to say the above sounds like a bad move -- probably one among many in this project.

      Heck, what could be sillier than basing a critical system on a Citrix deployment of untested scale and unconventional topology?

      The way normal people would do
    • Citrix? *snicker* Yeah, I'm not surprised that they have issues. I monitor those babies for a living, and they are the most temperamental systems I've ever seen. Not to mention incapable of properly scaling or working under load. You want scale? Get a new citrix server, and hope to god the load-balancing doesn't barf. I'm not sure Win32 is their culprit, but Citrix is definitely one of their problems.
    • Yeah, I'm sure this is Windows' fault. Because I've never seen a successfull application like this one (sans the Citrix shit) running on Windows. And I've certainly never seen an application being fucked up on UNIX. So therefore the fact that this thing is broken cannot possibly be the result of bad decisions, bad design, bad management, etc. Let's blame "Uncle Bill's broken OS", because it's fashionable and gets us lots of karma on Slashdork.
  • by Pedrito ( 94783 ) on Friday April 27, 2007 @09:50AM (#18900437)
    Having been, unfortunately, a former user of Kaiser-Permanente's services, I can say with confidence that their problems span way beyond software problems. 7 years ago, I was misdiagnosed with asthma by 3 Kaiser doctors. A 4th finally agreed that I didn't have asthma (and I don't). My actual problem was panic attacks caused by excessive adrenaline production, which no Kaiser doctor was able to determine. I had to go outside of Kaiser to find a doctor competent enough to determine the actual problem and treat me appropriately (with beta-blockers for the adrenaline instead of mind-numbing drugs like Paxil and Valium).

    Add to this the reports of KP dumping homeless patients on the streets. There was the kidney transplant scandal. The patient information becoming available online scandal. And all of this in just the past 2 years. Kaiser is clearly flawed from top to bottom. They are the poster-child for real health care reform in this country.
    • Those who can, do. Those who can't, teach. Those who can't teach work for Kaiser. They're the lowest-rent motherfuckers in the US health industry and everyone knows this.
  • by DrDitto ( 962751 ) on Friday April 27, 2007 @09:50AM (#18900453)
    Epic Systems-- selling $4b systems based on clunky, non-relational databases you've never heard of.
  • by TheGeneration ( 228855 ) on Friday April 27, 2007 @10:06AM (#18900699) Journal
    My father had a heart attack about a month ago. He is a member of Kaiser. Kaiser has it's own hospitals, doctors, and entire network that you must use. His heart attack resulted in him needing to undergo heart surgery. (The advantage to this sort of system is that my father's heart surgeon performed over 1000 bypasses every year and as a result is in the top tier of experts.)

    For me the biggest issue came when it was time for discharge. The handed me a hand written sheet with about 12 different medications scribbled in "Doctorese" cursive writing. I couldn't read half of the sheet, and only the briefest of notes for each medication was listed. I was shocked that I didn't receive a computer printout with the medication instructions, especially for medications needed to be taken in the case of quadruple bypass heart surgery.

    After many hours of sorting through the medications, trying to figure out if he had already been given a dose at the hospital or not, etc... I realized that when I had visited a non-Kaiser emergency room for a sprained ankle I got a multi-page printout with very thorough instructions for the medication and aftercare. On another visit when I had 107 temperature it was the same thing. I was very certain of the doctors orders for post-visit care.

    With Kaiser though I was left confused with short hand written notes about a dozen medications. Confusion is not a state I wanted to be in when I'm charged with the care of one of the most important people in the world (to me) who has a life threatening condition!
    • by barzok ( 26681 )
      Did you ask for the instructions to be rewritten so you could read them? Ask for more detailed notes? Ask which meds had been administered already, and when?

      If so, did you get satisfactory results? If not, why?

      I really hope you didn't walk away saying "ok, so this is what they give me, I guess I have to figure it out on my own." As a patient or care-giver, IMHO if you don't understand or can't read what you've been given, you need to get it straightened out before you leave the hospital/doctor. And the hos
      • Yes I did ask for more details, and never recieved them. It took them 3 hours to get a wheelchair to his room so they could discharge him. Apparently there is one wheel chair for the entire cardiac unit (there were about 40 patients.) At that point I was worried that if I started insisting they do anything else that we would miss our "wheelchair" and it'd be reassigned to another room and we'd spend another 3 hours waiting for our turn in the round robin scheme for discharges they had going on. I also
        • I forget to mention that the nurses were all Filipino spoke broken English and were nearly impossible to convey ideas to/from. While they were excellent nurses, the language barrier was significant and complicated the post-care instructions considerably.
      • As someone who not only has been discharged from fairly major surgery, including an angiogram of the brain and eye surgery that involved entering the brain cavity, and dealt with the problems of getting other loved ones out of complicated medical situations, I think I can say affirmatively when getting someone discharged the top priority is keeping things comfortable and sane for the discharged patient. It can do more harm to the person you love to make them wait 4 hours while you argue with nurses who clea
    • your post-visit care presumably involved being placed in a wooden box and having your relatives say nice things about you.
  • While maybe he thought he was doing a great thing by bringing a wild injustice to light... there isn't a chance in hell I'd hire him for anything remotely considered a computer or communication device - I bet many others won't either.

    Repeat after me: sir, can you spare some change?

    That'll be a useful skill for you.
    • Re: (Score:2, Insightful)

      by Wolvie MkM ( 661535 )
      Yea... How selfish of him doing the right thing trying to bring to light the potential endangerment of thousands of lives... Big trouble maker.

      The world needs more people with spines like this kid, good for him.
  • First, the article is nothing new. It basically says the same thing as before, "some 22-year old got out of college and worked at Kaiser for 6 months only to find out that, hey, big IT is not perfect." I can't figure out why anyone cares what some dumbass kid is blabbering about. It would be completely different if it was the CIO saying this.

    Second, it is true that the medical health system they're implementing is super-complicated but name one that isn't that does what everyone wants. The FBI spent $100m+ [washingtonpost.com]

  • Ha! Witness the failure of American-style capitalism to produce REAL waste! Why, here in the UK our glorious NHS have just recently thrown away 12bn of public money on a computer system that has ZERO percent uptime -- because nobody could decide what it was for and nobody wanted it! Compare that to the paltry few billions your private enterprise was able to throw away!

    And that's not all! The graft, corruption, bribery and crime surrounding the NHS system was such that Accenture *refused to work on it* -
  • Not to put too fine a point on it, I'd likely get fired for achieving that metric.
  • they say their goal for system availability is 99.7% (they're currently at 99.2%)."

    Reminds me of a PHB speech in a Dilbert book... Typed from fuzzy memory:

    "This year our goal is 0 serious injuries! In hindsight, last year's goal of just 20 serious injuries was a mistake. We had to seriously injure 6 people to meet that goal."

"The whole problem with the world is that fools and fanatics are always so certain of themselves, but wiser people so full of doubts." -- Bertrand Russell

Working...