DataBreaches.Net

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

Coalition for Patient Privacy Calls on HHS to Repeal the Breach Notification Rule

Posted on October 28, 2009 by Dissent

The Coalition for Patient Privacy urges the Department of Health and Human Services to revise and repeal the interim final rule (IFR) establishing requirements for notification of breaches of unsecured protected health information.

“We are dismayed and disappointed with the IFR, particularly with the inclusion of a ‘harm standard’. HHS went far beyond the intent of Congress. This is a real blow to accountability and transparency,” said Ashley Katz, Executive Director of Patient Privacy Rights, the organization that leads the Coalition.

On October 1, leadership from the House Ways & Means Committee and Energy & Commerce Committee urged HHS Secretary Sebelius to revise or repeal the harm standard.

Under HHS’ interpretation, an entity responsible for a breach may avoid providing notice of a breach if that entity determines there is no “significant risk of financial, reputational or other harm to the individual.” This exclusion weakens the breach notification requirement dramatically, granting the company that would like to avoid the cost and consequences of breach notification the power to decide if they will notify.

There was no mention of any harm standard in HHS’ previous Request for Information, thwarting any opportunity for public debate.

Currently, individuals have higher standards and expectations for our financial data than we do for our health data. With a breach of financial records, a consumer faces a significant headache, but ultimately can have their credit and funds restored; this is not the case with health records. A stigmatizing diagnosis, condition or prescription in the wrong hands can cause irreversible damage and discrimination.

Ensuring ironclad protections against theft and misuses of PHI must be the price of doing business in health care. “If an entity cannot or will not protect our most sensitive data, they should not be in the health care business,” said Katz.

Signing organizations to the HHS letter include: American Association of People with Disabilities, American Civil Liberties Union, American Council of the Blind, Clinical Social Work Association, Consumer Action, JustHealth, The Multiracial Activist, The National Coalition of Mental Health Professionals and Consumers, Patient Privacy Rights, Private Citizen, Inc., Telecommunications for the Deaf & Hard of Hearing, Inc., and the U.S. Bill of Rights Foundation.

Letter from Coalition for Patient Privacy:
http://www.patientprivacyrights.org/site/DocServer/HHS_CommentsIFRBreach_Final.pdf?docID=6161

Source: Coalition for Patient Privacy


Related:

  • Uncovering Qilin attack methods exposed through multiple cases
  • Predatory Sparrow Strikes: Coordinated Cyberattacks Seek to Cripple Iran's Critical Infrastructure
  • Ex-CISA head thinks AI might fix code so fast we won't need security teams
  • ModMed revealed they were victims of a cyberattack in July. Then some data showed up for sale.
  • Confidence in ransomware recovery is high but actual success rates remain low
  • Protected health information of 462,000 members of Blue Cross Blue Shield of Montana involved in Conduent data breach
Category: Breach LawsCommentaries and AnalysesFederalLegislation

Post navigation

← Client blows whistle on data theft in BPO
Former state tax department employee arrested →

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

  • 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
  • The Case for Making EdTech Companies Liable Under FERPA
  • NHS providers reviewing stolen Synnovis data published by cyber criminals

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

  • 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
  • Always watching: How ICE’s plan to monitor social media 24/7 threatens privacy and civic participation
  • Who’s watching the watchers? This Mozilla fellow, and her Surveillance Watch map

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.