Risk
9/16/2011
12:55 PM
Connect Directly
RSS
E-Mail
50%
50%

HIPAA Pain: How To Cope

Although providers worry about hugh fines for leaking patient data, keeping this information secure isn't that hard--but it soon will be.

InformationWeek Healthcare - September 19, 2011 InformationWeek Green
Download the entire September 19, 2011 issue of InformationWeek Healthcare, distributed in an all-digital format as part of our Green Initiative
(Registration required.)
We will plant a tree for each of the first 5,000 downloads.

HIPAA Pain: How To Cope

As information technology pervades every aspect of healthcare, complying with federal regulations on patient privacy and security is becoming an even bigger issue.

More often than not, it's human error and process mistakes--not the technology itself--that have caused the biggest HIPAA violations. Earlier this year, the Department of Health and Human Services began listing health data breaches affecting 500 or more individuals on www.hhs.gov. As of late August, 306 HIPAA violations were listed on HHS's "Hall of Shame" site, most of them involving stolen or lost computers, USB drives, or documents, not hacking or snooping.

In one of the largest penalties so far since the revised HIPAA rules were signed into law under the HITECH Act in 2009, Massachusetts General Hospital in February was fined $1 million to settle what HHS called "potential HIPAA violations" related to the loss of paper documents listing names, appointments, and other information for 192 patients of Mass General's infectious disease outpatient practice. A Mass General employee commuting to work left the documents on a train.

According to HHS, the government's investigation of the incident indicated that Mass General "failed to implement reasonable, appropriate safeguards to protect the privacy of PHI when removed from Mass General's premises and impermissibly disclosed PHI potentially violating provisions of the HIPAA Privacy Rule."

How IT Departments Are Coping

The revised HIPAA regulations have forced IT organizations to put more emphasis on data in transit, says Mony Weschler, director of ancillary informatics at Montefiore Medical Center in New York. When it comes to electronic communications with patients, "it's not just as simple as cutting a report and emailing it. You can't do that," Weschler says. Rather, healthcare providers need to set up secure passwords and IDs, and then provide patients with links to patient portals to pull reports up, he says.

Securing patient data on mobile devices--which are at the center of many of the data breaches reported on the HHS site--isn't an issue for Montifiore. "We don't store patient data on devices like smartphones and iPads."

Unfortunately, securing doctor-patient communication isn't the only HIPAA issue keeping IT managers up at night. Any data exchanged among clinicians also has to be secure.

Dell, through its Perot services unit, offers products and services to address those needs. Its cloud-based services, for instance, can encrypt medical images "three ways, before, during, and after" transmission, says Dave Marchand, Dell's health and life sciences CTO.

To read the rest of the article,
Download the September 2011 issue of InformationWeek Healthcare

Comment  | 
Print  | 
More Insights
Register for Dark Reading Newsletters
White Papers
Cartoon
Current Issue
Dark Reading, September 16, 2014
Malicious software is morphing to be more targeted, stealthy, and destructive. Are you prepared to stop it?
Flash Poll
Video
Slideshows
Twitter Feed
Dark Reading - Bug Report
Bug Report
Enterprise Vulnerabilities
From DHS/US-CERT's National Vulnerability Database
CVE-2014-3090
Published: 2014-09-23
IBM Rational ClearCase 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML document containing a large number of nested entity references, a similar issue to CVE-2003-1564.

CVE-2014-3101
Published: 2014-09-23
The login form in the Web component in IBM Rational ClearQuest 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 does not insert a delay after a failed authentication attempt, which makes it easier for remote attackers to obtain access via a brute-force attack.

CVE-2014-3103
Published: 2014-09-23
The Web component in IBM Rational ClearQuest 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 does not set the secure flag for the session cookie in an https session, which makes it easier for remote attackers to capture this cookie by intercepting its transmission within an http...

CVE-2014-3104
Published: 2014-09-23
IBM Rational ClearQuest 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 allows remote attackers to cause a denial of service (memory consumption) via a crafted XML document containing a large number of nested entity references, a similar issue to CVE-2003-1564.

CVE-2014-3105
Published: 2014-09-23
The OSLC integration feature in the Web component in IBM Rational ClearQuest 7.1 before 7.1.2.15, 8.0.0 before 8.0.0.12, and 8.0.1 before 8.0.1.5 provides different error messages for failed login attempts depending on whether the username exists, which allows remote attackers to enumerate account n...

Best of the Web
Dark Reading Radio