Slashdot Mirror


Loss of a Single Laptop Leads to $50k Fine Against Idaho Hospice

netbuzz writes "Losing a single laptop containing sensitive personal information about 441 patients will cost a non-profit Idaho hospice center $50,000, marking the first such HIPAA-related penalty involving fewer than 500 data-breach victims. Yes, the data was not encrypted. 'This action sends a strong message to the health care industry that, regardless of size, covered entities must take action and will be held accountable for safeguarding their patients' health information,' says the Department of Health and Human Services."

36 of 188 comments (clear)

  1. This is why God invented encryption by kriston · · Score: 4, Insightful

    This is why God invented encryption.

    --

    Kriston

    1. Re:This is why God invented encryption by Cryacin · · Score: 3, Informative

      Ummmm, at least Christians would say you're idolizing the wrong J.C.

      http://voices.yahoo.com/basic-cryptology-caesars-encryption-method-5295779.html

      --
      Science advances one funeral at a time- Max Planck
    2. Re:This is why God invented encryption by webmistressrachel · · Score: 3, Funny

      Yeah, he could at least idolize one with a three-letter UID - ~Jeremiah Cornelius. Have *some* class...

      --
      This tagline was transcoded to result in at least one smirk. If you experience failure to smirk, please consult your Gen
    3. Re:This is why God invented encryption by Bill_the_Engineer · · Score: 2

      Encryption is slow. If you have ever did healthcare data, there is just so much data that encryption can add hours to your tasks.

      No excuse. I deal with tons of data and by federal directive my laptop must have full disk encryption. It took 5 days to completely encrypt my laptop but now that it is encrypted, it has not added "hours" to my tasks. In fact it is barely noticeable. You do not have to have the data stored on your laptop either, you could have remote access to patient records.

      Combined with the fact that Health care organizations are just starting to invest into skilled workers, but still are dominated by a bunch of people who worked their way into IT, they were in accounting or in billing who got transferred to IT 20 years ago.

      These self learned and worked in the institution so long they really don't know how to think in terms of security. They bitch and moan when a vender wisely disables FTP. And will do stupid think like export a SQL db to access, so they can report on it.

      I doubt your statement is accurate. The main hospital in my home town always hired competent IT staff. In fact they influenced the type of computer courses offered at the local university since the early 80s.

      HIPAA combined with Meaning Full Use. Has made these older healthcare IT obsolete, however organization that suppose care wont fire them. Creating problems for the new set of people skilled in IT. And having a bunch of stupid tasks that distract them from doing the right thing.

      What do you base this on? The main hospital in my area do regular HIPAA compliance audits and employee training. People have actually gotten fired for violating the hospital privacy rules.

      --
      These comments are my own and do not necessarily reflect the views or opinions of my employer or colleagues...
    4. Re:This is why God invented encryption by kriston · · Score: 2

      This is just not true. I had a three-year-old laptop converted to full hard disk encryption and the change was not noticeable. Most CPUs now have hardware encryption acceleration, and those that don't have it already have fast enough math processors to handle the encryption.

      I should mention that in the federal space there are new "data at rest" security requirements and many of the databases in use today are already encrypted on disk.

      --

      Kriston

  2. Being non-proft does not justify being incompetent by gweihir · · Score: 4, Insightful

    Yes, it is tragic, but effective encryption is free (TrueCrypt, e.g.) and a non-profit still does not have any business being incompetent.

    --
    Most ACs are not even worth the keystrokes to insult them. Be generically insulted by this and ignored otherwise.
  3. Re:It works! by DoofusOfDeath · · Score: 3, Insightful

    It's hard to tell if you're being sarcastic or not.

  4. Government penalizers doing... by Anonymous Coward · · Score: 5, Insightful

    ...what govt penalizers do best: pick on those least capable of defending themselves... in other words go after the low hanging fruit and don't bother with the really hard stuff like rich, for-profit hospitals and clinics that routinely violate HIPAA... because those have armies of high-dollar lawyers who'll make life hard on the govt if they attempt to go after them.

    1. Re:Government penalizers doing... by Cryacin · · Score: 4, Funny

      Yeah, bunch of HIPAA-crits

      --
      Science advances one funeral at a time- Max Planck
    2. Re:Government penalizers doing... by icebike · · Score: 2

      Exactly.

      Any large hospital would have fought this out in court and prevailed.
      Banks, State Agencies, Military, Doctors and Clinics all over the country have data losses all the time, but
      nobody gets fined. Because they all have insurance and lawyers.
      But find one little agency, who's patients never live long enough to sue them and they therefore don't need
      to retain a huge legal staff, and BAM sue them into the ground.

      --
      Sig Battery depleted. Reverting to safe mode.
    3. Re:Government penalizers doing... by wmelnick · · Score: 2

      BS - They have already gone after Blue Cross/Blue Shield and many large practices. There have been multi-million dollar settlements. This was a warning shot to smaller providers that they have to keep their patients' data safe too because many are too lazy to do so.

    4. Re:Government penalizers doing... by Anonymous Coward · · Score: 2, Informative

      Banks, State Agencies, Military, Doctors and Clinics all over the country have data losses all the time, but
      nobody gets fined. Because they all have insurance and lawyers.

      Nobody gets fined? Are you kidding? Large organizations get fined all the time, often for amounts of money that aren't measured in "K". It is, by the way, the reason that said organizations have insurance. And lawyers. This one is making the news precisely because it's a small organization and a small data breach.

    5. Re:Government penalizers doing... by stormpunk · · Score: 2

      It took years before there were any fines. The BCBS fine of $1.5m was for 1m records. The only warning that says is that it is cheaper to ignore the regulations than do anything about it.
      Also, if you're going to lose records then lose big and you get a discount. It cost the hospice over $100 per record and BCBS $1.50. There does appear to be something to the statement that larger agencies have less to worry about.

    6. Re:Government penalizers doing... by ColdWetDog · · Score: 3, Insightful

      Nice rant. Too bad you're mostly wrong. HIPAA actually does manage to get data protection pushed far and wide in an industry that fights tooth and nail against any change. It's hardly perfect but it's not terribly onerous and most of the edge cases and implementation problems have been sorted out.

      I'm not sure why they chose to beat up on some rural Hospice provider - they've had plenty of chances to hit some big boys and girls, but this will send out a signal that you shouldn't fuck around and avoid doing simple things. It isn't much of an expense to encrypt laptops. It's not hard to put locks on doors, HIPAA has made it easier to transfer data back and forth between providers because everyone is working off the same set of rules.

      Maybe you should bash your head with your copy of Atlas Shrugged a few more times until things are clearer.

      --
      Faster! Faster! Faster would be better!
  5. Re:It works! by Alwin+Henseler · · Score: 4, Insightful

    No it doesn't. For starters: such a fine is a good thing, but it should be payable to the victims of the data breach (as in: the people whose sensitive data was dumped on the street). One way or another, they suffer damage from a data breach, they should be compensated.

    Secondly, it won't prevent further breaches like they happen so often these days. Maybe if fines are stiff enough, and handed out often enough, over time it will produce an effect. I wouldn't hold my breath though. When it comes to keeping data private, a new idiot is born every day. Sometimes an idiot in charge, but that's not always necessary.

  6. How to ensure it gets encrypted... by Anonymous Coward · · Score: 3, Interesting

    Require the people in charge of an organization to store THEIR personal data in any such repository. Then maybe they'd have more incentive to make sure it gets PROPERLY encrypted.

  7. Re:It works! by icebike · · Score: 3, Informative

    No it doesn't. For starters: such a fine is a good thing, but it should be payable to the victims of the data breach (as in: the people whose sensitive data was dumped on the street).

    You did read the article right?

    Of course not.

    Nobodies data was abused. They didn't suffer any damages from the data breach.
    (You do know what a Hospice is, right? You understand that their clients could not possibly care less about a data breach?).

    Be that as it may, fines are NEVER payable to individuals. The government simply pockets the money.
    Nobody is taught any lessons, other than to raise their prices to pay for even more insurance.

    --
    Sig Battery depleted. Reverting to safe mode.
  8. Re:Hospice prices go up by sunking2 · · Score: 3, Insightful

    Hopsice prices can't just arbitrarily go up for 99.9% of people who use insurance or medicaid. They work on prenegotiated rates. They can charge all they want, insurance is only going to pay them what they agreed to.

  9. Did they ignore the regulations at the start? by Kwyj1b0 · · Score: 2

    At a university where I work, there is a requirement that any project involving storing personal data must go through several periodic reviews and has to meet some strict requirements - encryption is a must (without it, the project won't even get off the ground). I'd be very surprised if there are no regulations dictating how hospitals must store and protect data.

    I read TFA, but I couldn't see whether such requirements are a must for hospices. Did they just go ahead and ignore the requirements? In which case, the fine is too small. Or are there no regulations for healthcare industry (I'd find that very surprising)? Can someone more knowledgeable tell me if this was negligence or outright violation of protocol?

  10. Why are you doing it in the first place? by rudy_wayne · · Score: 2

    Every time I see one of these stories I wonder about the same thing. Why is sensitive patient information on a laptop in the first place, and why is that laptop leaving the hospital.

    If you are a business executive, I can understand that you would be carrying a laptop which contains emails and other documents. But I cannot think of a single good reason (GOOD REASON) why a hospital's patient information would ever need to be stored on a laptop. Seriously, if you have employees carrying around laptops loaded with patient information, you're doing it wrong.

    1. Re:Why are you doing it in the first place? by wvmarle · · Score: 2

      That requires a network connection. Not every home has an Internet connection, and many that have, do not have easy facilities to connect a visitor's computer to the Internet. And as this is set in the US, I wouldn't consider mobile (3G, 4G data) coverage a given either. So VPN is not an option.

  11. What a Joke by Charliemopps · · Score: 4, Interesting

    Having worked on many projects involving various levels of government regulation and compliance, and seeing all the different facets of security and what-not, I can state for a fact that a case like this will be looked at like "It was only a $50k fine? This security hardening project is costing us well over $200k and we still might have a breach that would lead to such a fine. Why are we even bothering?"

    We had a project that was basically just a fuzzy match for numbers that looked like credit card or social security numbers and delete them if it found them, just in case they got into a part of the database they shouldn't (like a customers stuck their social security number into their address, and yes, it's happened before) That project cost us $22,000. It ended up being a single line of SQL that ran as part of a service every hour. $50k is laughable. Security breaches like this should nearly bankrupt a company, there is no other way they'll be taken seriously. I'm involved in 5 different projects right now, each of them billing out at over $100k each, 3 of them revolve around privacy issues and government compliance. The fines issued for such breaches aren't even in our paperwork as a concern. The cost of a breach in regards to public image however has a very specific, very large number near the top of the chart. But we're in a business where people are paying attention to such things. These fines should START in the millions because preventing them costs in the hundreds of thousands of dollars.

    1. Re:What a Joke by Guido69 · · Score: 3, Funny

      If you've seriously got a viable business model where encrypting a single laptop can bring in $N00k, please let me know.

      --
      - If we aren't supposed to eat animals, then why are they made out of meat? - Steven Wright
    2. Re:What a Joke by twistofsin · · Score: 2
      I'm trying to wrap my head around how you went from

      1. Recognizing the risk 2. Spending 22k 3. And ending up with 1 line of code for it.

      I mean, at what point in that expenditure was that line of code developed? That 1 line of code is obviously includes a search string for the databases, and a command to delete them. How was that not obvious to implement?

    3. Re:What a Joke by jklovanc · · Score: 3, Interesting

      Perhaps the fine was sized to cause pain to the organization and not kill it. Everyone makes mistakes and there are consequences but those consequences should not be fatal. Now if it happened a second time the fines should be much larger. A third time should bankrupt the company.

  12. Re:Being non-proft does not justify being incompet by Kaenneth · · Score: 3, Interesting

    Question; is there a differance between 'effective' encryption, and 'HIPAA Approved' encryption?

    From a legal standpoint, would cheap/free encryption like Truecrypt/PGP be acceptable, or do you need HIPAA certified encryption with enterprise key management, etc. for $1000 a seat?

    What stops your medical records being 'encrypted' with ROT13?

  13. Re:It works! by Enry · · Score: 4, Insightful

    Yes, and the next time some Hospice official thinks about not encrypting their data, they're going to remember this event and think better of it.

    HIPAA violations are serious. People have likely lost their jobs over this. Even though I'm not in a position to routinely work with patient data, my employer requires that my laptop is encrypted - in the case of my Linux laptop I was able to convince them that using encrypted LVM was sufficient.

  14. Re:Being non-proft does not justify being incompet by Anonymous Coward · · Score: 4, Informative

    Question; is there a differance between 'effective' encryption, and 'HIPAA Approved' encryption?

    Yes, HIPAA stipulates that it must be FIPS-accredited. AES-encrypted zip files are acceptable; the older standard of zip file encryption (whatever that was) isn't.

    What stops your medical records being 'encrypted' with ROT13?

    The above.

  15. -or- they learned another lesson... by bradorsomething · · Score: 3, Insightful

    When you lose one laptop worth of patient data, don't tell anybody.

  16. Re:Being non-proft does not justify being incompet by Guido69 · · Score: 4, Informative

    FIPS 140-2 to be more specific. There are plenty of free options.

    --
    - If we aren't supposed to eat animals, then why are they made out of meat? - Steven Wright
  17. Re:It works! by mlts · · Score: 3, Insightful

    I'm happy HIPAA is being enforced. We have already had way too many breaches, either tapes left in unsecured locations, or laptops "going missing".

    We already have had a decade of businesses giving security the hind teat, since it is viewed as a cost center, and the belief that "calling Geek Squad" after the fact can fix things. Having it made public that if laws/regs are broken, that fines will be levied might get places to zip their flies.

    Encryption of laptops is not hard, especially Windows laptops that are the mainstay in business that have TPM chips. With any Windows version newer than Vista, Bitlocker is very easy to enable on an enterprise level. For most things, just forcing BitLocker via GPO on laptops, even if the user is a full admin is more than good enough for security.

    For laptops without a TPM, Windows 8 and Windows Server 2012 allow for a password to be set before boot.

    Almost all new major operating systems have some form of DAR/WDE encryption ready to go. Linux has LUKS, BSD has gbde, AIX has EFS, Solaris has encrypt(1), OS X has FileVault II. Enabling this may not be trivial, but it is doable.

    Of course, almost all new backup programs have encryption, usually create/import a key, set a button to encrypt, and let fly. Netbackup has the Media Server Encryption Option, but even better, if one uses LTO-4 or newer media, NBU can just use the tape drive native AES encryption directly.

    There is no excuse for encrypting laptops and media these days. None.

  18. Should not be on there in the first place, at all. by markdavis · · Score: 2

    I love all the immediate "encrypt it" comments. Yes, that would be helpful, but the bigger question to ask is:

    "Why would such data be copied onto a laptop in the first place?"

    We keep hearing stuff like lost laptops and flash drives over and over. The reality is that sensitive data like this shouldn't be on those devices in the first place. One would think it would be accessed only on secure servers through approved clients and methods. Most facilities' HIPAA guidelines specifically forbid copying such information off the servers in the first place (expect by I.T. for backup) regardless if it is encrypted or not. Seems like employees in the organizations just ignore that.

    Encryption can be broken.

  19. Re:It works! by NotQuiteReal · · Score: 2

    Next time I am dying I will be sure to carefully review the HIPPA compliance record for the hospice of my choice.

    --
    This issue is a bit more complicated than you think.
  20. Re:Being non-proft does not justify being incompet by adolf · · Score: 2

    FIPS 140-2 to be more specific. There are plenty of free options.

    Are there? Last time I looked into FIPS 140, it was the case that only certain software versions were validated by NIST, and none of the validated incarnations were either free-beer or free-libre.

    Even the folks behind Truecrypt "To our best knowledge, TrueCrypt complies with the following standards, specifications, and recommendations...", before failing to mention FIPS 140 at all.

    Indeed, looking again at the list of validated FIPS 140 wares, it does seem to be lengthy, but it is mighty specific and I do not see a single instance of anything free-as-in-beer, let alone "plenty of free options."

    The only thing that stands out is that Red Had has had some OSS software validated as being FIPS-140, but only when installed according to their posted Security Policy, which seems to require RHEL, which is not free.

    So. [citation needed], and stuff: If you've got the goods, give 'em up. (And no, "To our best knowledge" is not a defense against a HIPPA violation: It either is validated to FIPS 140(-2), or it is not.)

  21. Re:A 'Big' fine? by afidel · · Score: 3, Insightful

    Dude, it's a small nonprofit hospice, it's doubtful they HAVE an IT guy, more likely a consultant they bring in to fix something every few years. I know because I worked consulting in a practice focused largely on smb medical and only our largest and/or most profitable customers ever engaged us for anything more than break/fix. I got out just as HIPPA enforcement was coming online and almost none of our clients was prepared despite the fact that we had sent along information for several years pointing them to organizations that could help them write their policies (we got nothing directly out of this, though given the state of many of their IT systems they would have needed services to become compliant with legal minimum practices).

    --
    There are 4 boxes to use in the defense of liberty: soap, ballot, jury, ammo. Use in that order. Starting now.
  22. Shit software by Jarno+Hams · · Score: 5, Interesting

    I am going to assume the hospice is in a similar boat we are... and i will explain how its not as simple as the wand waivers above try to make it sound. I'm essentially the brat mentioned above. Small practice with about 7 providers and about 50 machines... Probably 50/50 desktops and laps. we use a shitbox EHR that was shoved down our throats because our old vendor sold the code to the highest bidder to acquire clients. Me and and 3,000 other clients are stuck with a "new" shit product, $100,000 in debt and India to call for "support". we don't have $22k for one line of SQL code. the EHR requires local users to be admins. Mind blowing. A gpo restriction against data to the local renders the box useless. No matter how many learning moments, hand slaps and write ups you have , users will never understand the difference between My Documents and the shared network drive where stuff is supposed to go. Ironically doctors are the worst. I wrote hundreds of pages of HIPAA policy and then tried to figure out how to encrypt and secure 50 xp machines running on aging dell 2350's/3000's and d510's. state hipaa auditor says we need essentially another $100,000 worth of new stuff and encryption. There is zero IT budget. I just yanked all the drives and am pxe booting thinstation to a terminal session. in the follow up, the auditor agreed it satisfies the encryption issue 100%, and she had never heard of that or seen it done but applauded me. There are thousands of office just like me who have no budget and are already drowning in debt from the non-free software rapists. The number one argument you will get from the business owners is no budget. dwindling reimbursements coupled with exponentially expensive responsibilities like this article make for a rough combo. I feel bad for the chaps in bumblefuck Idaho. They are probably barely scraping by, then this... I'd pitch the same solution i used that passed the hipaa audit to any of these other offices out there you might find who need help but can't afford anything else. Pass it on. /$.02