The United States Health Insurance Portability and Accountability Act (HIPAA) of 1996 was established to standardize mechanisms for electronic data interchange (EDI), security, and confidentiality of all healthcare-related data. Most healthcare organizations have until April 21 of this year to meet the final security requirements of HIPAA. Will they make it? Our sister site, SearchSecurity.com interviewed IT, security and compliance professionals across the United States over a two-month period to learn more about their progress in meeting this final HIPAA deadline. Check out the various case studies, interviews and articles to learn more about what your peers are doing to meet all HIPAA requirements.
Health insurance companies say HIPAA simply reflects rules they've had to live by all along. That doesn't mean every operation is ironclad.
Here's what you need to know at a glance.
Enterprises don't have to work directly with patients to be affected by HIPAA's security rules.
If upper management is supportive and the right people oversee security, hospitals are doing right by HIPAA. But those ingredients aren't always there.
One's walking on air; the other walked out the door. The experiences of two IT professionals show what's critical to the success of any HIPAA security plan.
Consultants spend their days trying to help healthcare organizations understand security. The Marblehead Group's Kate Borten offers one view from the trenches.
If your local dentist isn't complying with HIPAA's security rules, he's not alone. Experts say most doctors' offices aren't getting it.
The security market is bulging with products IT administrators can use to manage HIPAA security compliance. Here's what some professionals are using.
From the tech guy to the compliance consultant, everyone seems to agree HIPAA's security rule is necessary -- pain and all.