Home -> Law Blog Directory -> Health Law Blogs -> HealthBlawg
(866) 635-2689 for Personal Injury or (866) 635-9402 for Criminal Defense
Find a Local Lawyer
Divorce (866) 635-6190
Personal Injury (866) 635-2689
Criminal Defense (866) 635-9402
Health Law
: HealthBlawgComments on HITECH Act breach notification rule - from Capitol Hill
By David Harlow
Regulations are written to implement legislation. If all legislation were perfectly clear and easily understood by all, there would be little need for regulations.
In late August, HHS issued an interim final rule, effective late September, with a 60-day comment period, to implement the breach notification requirements of the HITECH Act. One element of the rule involved establishing a standard not included in the legislation. More specifically, HHS elected to read a "harm" standard into the breach notification rule; to use a sports analogy: no harm, no foul. The thinking is: Why trigger breach notification requirements if, for example, an employee of a health care facility inadvertently accessed a patient record that he shouldn't have, where he immediately realized his error and closed the computer file without reading it or retaining any information from the file?
Well, Congressional leaders responsible for drafting the law in the first place disagree, saying that the squishiness inherent in any determination of whether or not there was any harm to a patient as a result of such a breach led them to back off of the harm standard, which was in an early draft of the law but was explicitly abandoned. (Thanks to Alan Goldberg and Bob Coffield for highlighting the comment letter sent October 1 by Representatives Waxman, Rangel, Dingell, Pallone, Stark and Barton.)
So, the letter says that was the Congressional intent; of course, as any litigator could tell you, there are two sides to every story . . . .
Speaking of strict standards in statute translated to use in the real world by more flexible regulations . . . . Remember OBRA 1987? That was the law that led to the development (over the next ten years) of the current SNF survey and certification schema. The statute had a "zero tolerance" standard in its conditions of participation; HCFA (now known as CMS) concluded that since most SNFs were not in 100% compliance, and since Congress probably didn't mean to shut down the entire industry, it would promulgate a "substantial compliance" standard instead.
I do not recall whether there was any legislative history showing what Congress meant when it enacted OBRA 1987 with a zero tolerance standard. (Anybody? Help me out here.) I bet there are other examples out there of regulations implementing "zero tolerance" statutes with "substantial compliance" sorts of standards. (Feel free to note them in the comments.)
What do you think? Is the standard too squishy? Should the regs be pulled back to reflect the avowed legislative intent?
David Harlow
The Harlow Group LLC
Health Care Law and Consulting
Full post as published by HealthBlawg on October 06, 2009 (boomark / email).
Torts
Introduction to Torts
Copyright Lawsuits: Critical Issues Before Filing Copyright
Federa Rule 11(b) Considerations
US Auto
Meeting Notification Regarding $10 Million Class Action Settlement.
Princeton Review
Sarasota Student Data Breach Prompts Class Action
US Army Corps of Engineers
Class action dismissed for allegedly failing to protect New Orleans from the levee breach.
Security Breach
Check 'N Go to pay $220,000 settlement in personal information lawsuit.
Data Breach
USSearch.com to pay $250,000 settlement in information lawsuit.
Expedia
$184 Million Breach of Contract Settlement Reached

FTC Issues Proposed Rules for Security Breach Notification under HITECH
8/25/09 webinar to discuss soon-to-be-implemented breach notification requirements of the HITECH Act
HITECH/HIPAA: Notification in the case of breach (unsecured PHI).
Let the Breach Notifications Begin! . . . (in 30 days, or so)
HITECH Help Is On the Way! August 19, 2009
New Data Breach rules and preemption








