DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Health IT execs mull fixes on health record privacy

Posted on March 7, 2008October 24, 2024 by Dissent

Maureen McKinney writes in Government Health IT:

Health information technology executives this week called for the development and dissemination of a more lucid set of policies on consumer access to health records in order to allay public fears that using a personal health record would put their health privacy at risk.

In a Web conference sponsored by the Agency for Healthcare Research and Quality, Dr. David Lansky, president and chief executive officer at the Pacific Business Group on Health, said that despite public interest in PHRs, security was a major consumer concern that would hinder public participation in the medium.

“Because people believe that they could suffer from insurance discrimination, job discrimination or stigma if something about them becomes known, that anxiety becomes a damper on how the information is shared across the network,” said Lansky, who recently left his post as senior director at the Markle Foundation.

Recent studies by the Markle Foundation demonstrate consumers’ enthusiasm for PHRs, Lansky said. Close to 70 percent of surveyed patients expressed a desire to look for errors in their medical records, and the same percentage said they would use a PHR to check and fill prescriptions. Still, vulnerability of medical information was a significant worry, he said.

The solution, Lansky said, is a clear and concise policy framework for consumer access that addresses issues like whether or not the Health Insurance Portability and Accountability Act applies to PHRs. In addition, elements of the record such as authentication, rules for secondary use and transparency need to be clearly delineated to remove any unease or distrust, he said.

Standards for PHRs are available, according to Dr. John Halamka, chairman of the Healthcare Information Technology Standards Panel, and the chief information officer at Beth Deaconess Israel Medical Center in Boston. Halamka pointed out that a national standard for PHR information exchange does exist in the form of the Continuity of Care Document.

The CCD is a data transmission standard, endorsed by HITSP, which provides a vehicle for applications that gather data from hospitals, laboratories and other sources, Halamka said.

These standards are now part of the requirements for government technology purchases for the Defense and Veterans Affairs departments, Halamka said. “That means we are converging on a single means of data exchange.”

Halamka said he is optimistic that HITSP’s efforts will increase interoperability among stakeholders and new standards will be incorporated into PHRs like those introduced by Google and Dossia.

When a caller posed a question about who would be responsible for policing security for massive PHRs like Google, Halamka admitted there is currently no government watchdog group. Instead, Google has an advisory council, made up of industry experts, who ensure no data mining or advertising occurs. “It’s a start,” he said.

Source – Government Health IT


Related:

  • JFL Lost Up to $800,000 Weekly After Cyberattack, CEO Says No Patient or Staff Data Was Compromised
  • Massachusetts hospitals Heywood, Athol say outage was a cybersecurity incident
  • Heritage Provider Network $49.99M Class Action Settlement
  • Integris Health Agrees to $30 Million Settlement Over 2023 Data Breach
  • They were victims of a massive data breach in 2009. Interior Health denied it for a decade.
  • Watsonville Community Hospital had a data breach -- or two. It would be helpful to know which.
Category: Health Data

Post navigation

← Chronology of Breaches for 2008 uploaded
245 computers stolen from 19 universities in Japan →

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • District of Massachusetts Allows Higher-Ed Student Data Breach Claims to Survive
  • End of the game for cybercrime infrastructure: 1025 servers taken down
  • Doctor Alliance Data Breach: 353GB of Patient Files Allegedly Compromised, Ransom Demanded
  • St. Thomas Brushed Off Red Flags Before Dark-Web Data Dump Rocks Houston
  • A Wiltshire police breach posed possible safety concerns for violent crime victims as well as prison officers
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Almost two years later, Alpha Omega Winery notifies those affected by a data breach.
  • Court of Appeal reaffirms MFSA liability in data leak case, orders regulator to shoulder costs
  • A jailed hacking kingpin reveals all about the gang that left a trail of destruction
  • Army gynecologist took secret videos of patients during intimate exams, lawsuit says

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • Lawmakers Warn Governors About Sharing Drivers’ Data with Federal Government
  • As shoplifting surges, British retailers roll out ‘invasive’ facial recognition tools
  • Data broker Kochava agrees to change business practices to settle lawsuit
  • Amendment 13 is gamechanger on data security enforcement in Israel
  • Changes in the Rules for Disclosure for Substance Use Disorder Treatment Records: 42 CFR Part 2: What Changed, Why It Matters, and How It Aligns with HIPAAs

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net
Security Issue: security[at]databreaches.net
Mastodon: Infosec.Exchange/@PogoWasRight
Signal: +1 516-776-7756
DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.