Related Links

Related Stories

  • Securing Electronic Health Records
    Electronic health records are supposed to improve the efficiency and accuracy of healthcare delivery. However, with electronic records come security headaches, and the potential for data breaches. John Sterlicchi examines what the industry is doing thus far to facilitate a secure transition toward electronic health records
    Members' Content
  • US standards drive Canadian information security
    An absence of legislation and the presence of the laissez-faire attitude has resulted in Canada being rather lax when it comes to information security compliance. Robin Arnfield looks at how US standards are driving the Canadian information security marketplace
  • Healthcare hacks on the rise
    Attempts to hack healthcare organizations doubled in the fourth quarter of last year, according to Atlanta-based managed security firm SecureWorks, setting the sector aside from others.
  • Weekly brief – August 24, 2009
    In this week’s information security news: Microsoft patch exploited by hackers; Office 2010 sandbox security welcomed by security industry; hackers get their revenge on police; and more…
  • Weekly Brief - May 26 2009
    Information security attacks, defenses, vulnerabilities, and losses

Feature

Is Patient Data Privacy on its Sickbed?

03 August 2009
Danny Bradbury

As we stand on the cusp of a massive healthcare modernization program, we face increasing challenges over healthcare data privacy. Danny Bradbury explores what’s happening in the US from a technological perspective, and what it means for our sensitive data

British Romantic wit Alexander Pope had it right when he said: “Reason’s whole pleasure, all the joys of sense, lie in three words,—health, peace, and competence.” In today’s modern healthcare environment, health requires a whole different type of competence; we’ll only achieve peace of mind when we secure private patient information in an increasingly digital environment.

The American healthcare system is poised to undergo one of the most significant changes in its history. Electronic healthcare records have been on the agenda for some time, but with the recent change in the administration, modernizing the system has become a priority. President Obama has pledged to revolutionize the healthcare system using funds provided by the American Recovery and Reinvestment Act stimulus package Bill passed in February.

As soon as he came into office, Obama pledged to computerize the nation’s health records within five years. However, that carries significant challenges from an information security perspective. How is it going to happen, and who is going to protect our data as it does?

The core of the modernization initiative will be a Nationwide Health Information Network, which will connect a series of regional networks called Health Information Exchanges together across a broader backbone. The US Department of Health and Human Services is overseeing the system, and has commissioned 15 contractors to produce prototypes.

That initiative will hopefully take care of the communications infrastructure that will enable records to be exchanged between different parts of the country (so that, for example, a doctor in Florida could access the records of a retiree from Minnesota who is spending the winter in the Sunshine State). The Healthcare Information Technology Standards Panel, created by the American National Standards Institute, will take care of the format for electronic health records.

The Meaning of Privacy

Where do privacy and security lie in this massive modernization program? Dr Deborah Peel, a practicing physician who also founded non-profit special interest group Patient Privacy Rights, isn’t convinced that they have been given enough thought.

"The Bush administration de-regulated the consumer protections across the board, and one of hte places where they did that was the HIPAA privacy rule."
Deborah Peel, Patient Privacy Rights

There may be a legal definition of what privacy means in the US, but there isn’t a government-ratified one pertaining to health, she warns. “Congress has not set a definition of what that means, in the portion of the stimulus package that is about health technology,” she says. The National Committee on Vital and Health Statistics developed a definition in 2006, but the Department of Health and Human Services did not adopt it, she recalls.

But surely the Health Insurance Portability and Accountability Act (HIPAA) should provide some protection? Passed in 1996, the legislation is designed to provide some privacy for healthcare information. Entities covered by the legislation include healthcare providers, healthcare clearing houses, and health plans.

Title two of the Act focuses on preventing healthcare fraud and abuse, and entails five rules revolving around privacy, transactions and code sets, security, unique identifiers, and enforcement.

HIPAA’s privacy rule requires covered entities to disclose protected health information (PHI) to an individual within 30 days of a request, and they must also fix errors in that information when asked to. They must also tell individuals how that information is being used.

"At present, Google and Microsoft have created very strong policies, and they are not covered by HIPAA, so patients have to trust those policies."
John Halamka, Harvard

The Role of Security

The Security role is another significant one. It focuses on electronically held PHI, and mandates administrative, physical, and technical safeguards. These are many and varied, but include, for example, the requirement to adopt a rigorous set of privacy procedures, and the designation of a privacy officer. Covered entities should have a contingency plan for dealing with security breaches, and must protect their computer systems from intrusion. Encryption must be used when transmitting data over open networks.

Peel doesn’t feel that HIPAA offers consumers the protection that they deserve, however. “HIPAA eliminated the right to privacy,” she says. “The Bush administration de-regulated the consumer protections across the board, and one of the places where they did that was in the HIPAA privacy rule,” she says, arguing that a 2002 amendment eliminated the right of individuals to give their consent to healthcare providers wishing to share their information with others.

“They literally take the individuals out of it, and the decisions about when information will be used, and for what purposes, are in the hands of businesses,” she says. The amendment applies to ‘covered entities’, which applies to most businesses operating in the healthcare sector, she adds. “They totally turned HIPAA into a data miner’s dream.”

There is alternative legislation on the table, however. The Protect Patients and Physicians Privacy Act was introduced into the House of Representatives in May by Rep. Ron Paul (R-TX). It has been referred to the Committee on Energy and Commerce as well as the Committee on Ways and Means, as part of the long, arduous process to make a Bill law. If passed, the Act would reinstate some of the patient privacy rules that Peel says were cut out of HIPAA.

This may be true, but nevertheless there are some entities not covered by HIPAA that perhaps should be. In particular, there are some companies hoping to act as stewards for consumer health information that is not subject to the same rigorous controls that health plans face.

Google launched its Health service in April 2008, while Microsoft rolled out its Healthvault service in October 2007. The two services have similar goals: to help consumers store and manage their own health information, rather than leaving it purely in the hands of medical practitioners.

“Google Health is free to anyone, much like other Google products we offer, including Google News and iGoogle,” says Google, about its service. “This is just another step in helping us fulfill our mission to organize all of the world’s information and make it universally accessible and useful.”

The Benefits of Sharing

The potential benefits of these systems are enormous. They are connecting with networks of medical institutions such as pharmacies, making it possible for patients to pool their prescription and healthcare data into their own account managed on either Microsoft or Google’s servers. They can then choose who sees that information, and in some cases can make more informed searches about their healthcare questions.

“There is a way in which we can securely hold information about patients, giving them the ability to share their information, under their control, very explicitly”, says John Coulthard, director of healthcare and life sciences at Microsoft. “There is a cohort of individuals that want to search for healthcare information, learn about what it tells them, save that information, and then act upon it”.

"People's health information will potentially be more at risk of being used for commercial and marketing purposes."
Deven McGraw, CDT

That’s all well and good, but who is going to police these services? John Halamka, chief information officer and dean for technology at Harvard Medical School, who helped to develop the Google Health service, admits that it does not fall under HIPAA regulation. Although he says, the companies have been co-operative in agreeing to their own standards.

“At present, Google and Microsoft have created very strong policies, and they are not covered by HIPAA, so patients have to trust those policies,” he says.

However, Peel, who is trying to put together an evaluation system for privacy protection in healthcare information systems, says that only Microsoft replied when she invited several companies to contribute. Google didn’t get back to her, she says.

Commercial Activity

She is not the only person concerned over the safety of electronic health records within some of these privately owned services. “People’s health information will potentially be more at risk of being used for commercial and marketing purposes,” warns Deven McGraw, director of the health privacy project at the Centre for Democracy and Technology in Washington, DC. “The volume of that kind of activity will ramp up considerably in a health and information system that is all commercially run”.

"There is a way in which we can securely hold information about patients, giving them the ability to share their information, under their control, very explicitly."
John Coulthard

Such issues could become more problematic as these companies begin using their expertise in social networking tools to enhance the value of these healthcare records. Google has already launched a social networking function as part of its Health service, and it is unlikely to be the last (although it has vowed not to use advertising as part of its healthcare system). Microsoft executives have already talked about the benefits of such features.

The balance between security and usability is always a fine one, and in the case of healthcare it is particularly politically charged. On the one hand, the appeal of managing one’s own personal health information is obvious, as is the opportunity of plugging it into innovative services that can add value to it.

On the other hand, there is a need to protect patients’ personal information, both from commercially motivated cyber criminals, and also from special interests that could use those records for their own ends. Let’s hope that as we continue to modernize our systems, our privacy remains in good health.

 

This article is featured in:
Compliance and Policy Public Sector

 

Comments

Peter Bachman says:

04 September 2009
The vast amount of information that is required to manage the health care process creates both privacy and security concerns that have not been ignored by the stakeholders, including privacy advocates who have done in depth analysis of HIPAA. The questions of how to implement privacy and security beyond the usual best practices which apply to all secure systems do present some unique problems that go beyond financial losses, especially if someone's electronic health records or continuity of care document loses integrity and inaccurate data (perhaps from another patient) is added. One positive note is that laws regarding data breaches have been strengthened, and enforcement by the HHS Office of Civil Rights and the FTC have begun to show teeth. Those of us in the security profession realize how difficult this task really is and expect that when a statement is made that privacy is taken seriously, that this is in fact the reality, and not boilerplate on a web site. In a successful prosecution where prescriptions were thrown out by store personnel into the dumpster along with customer information attached, most of us would agree that this violated customer's privacy. In other cases, the rights of celebrities were violated when hospital personnel accessed the patients protected health information beyond the scope of care, and were subsequently disciplined or fired. What is changed is the process of determining whether the software is secure is sent through CCHIT, standards are being approved which are less purely medical centric and more IT centric, and the entire process has been done in a transparent manner. Having attended both the NHIN and HITSP meetings in which privacy and security were very carefully addressed I can tell you that the subject is not being ignored, and the ability to network information has more to do with crossing information security domains, than tracking who touches that information. For one thing medical professionals and institutions already have identifiers which they must use. Patient identifiers on the other hand are done by probabilistic matching, but as RAND pointed out, HHS approved patient identifiers as covered under HIPAA. Given that patients will have the choice of creating voluntary identifiers which then can be used to track transactions through out the system, this has the benefit of merging records together from different sources at the point of service, as well as tracking access in a way that pulling papers from a paper medical file cabinet can not duplicate. Primarily the issues are the methods by which data suppliers, processors, and consumers maintain data at rest, and what they network, the format in which that data is communicated and how much personal information is required. This is going to be done very carefully since there's no similar out of refunding the money lost to data loss. As such the penalties are very severe. The more complicated issues are in fact quite complicated, such as the re-identification of data, after it has been de-identified by unauthorized parties. Of course, Health Care reform that does not create a service failure related to the fact that people can not get health care because of pre-existing conditions would lessen the amount of pressure that this PHI currently creates in terms of keeping it private. For the most part, standard best practices are going to the way to go, but when information is sent into a message bus using SAML, and XACML in a multicast fashion, as NHIN Connect is using in the current version, issues regarding the security of this approach from an architectural point of view are unlikely to make it on to the radar, versus the current point to point contracts, or regional health information networks. If you think about it, the majority of health care is delivered locally.

Note: The majority of comments posted are created by members of the public. The views expressed are theirs and unless specifically stated are not those Elsevier Ltd. We are not responsible for any content posted by members of the public or content of any third party sites that are accessible through this site. Any links to third party websites from this website do not amount to any endorsement of that site by the Elsevier Ltd and any use of that site by you is at your own risk. For further information, please refer to our Terms & Conditions.

Comment on this article

You must be registered and logged in to leave a comment about this article.