United States: The Omnibus Final HIPAA Rule Is Here

Last Updated: January 30 2013
Article by Rebekah Monson, Sharon Klein and Henry C. Fader

On January 17, 2013, the Office of Civil Rights of the U.S. Department of Health and Human Services (HHS) announced the omnibus final rulemaking (Omnibus Rule). According to HHS, this Omnibus Rule is needed to strengthen privacy and security protections established under the Health Insurance Portability and Accountability Act of 1996 (HIPAA) for individuals' information maintained in electronic health records and other formats.

The much-anticipated and long-awaited Omnibus Rule is 563 pages long and covers many topics, issues and concerns that have emerged during the 15-plus years since the passage of HIPAA and the implementing privacy, security and enforcement regulations, and the nearly four years since the passage of the Health Information Technology for Economic and Clinical Health (HITECH) Act in February 2009. Throughout the Omnibus Rule, HHS responds to public comments submitted under the various prior proposed rulemakings and notes that it will be providing additional guidance on certain topics.

In addition to providing a brief overview of the Omnibus Rule, this Alert highlights some of the modifications directly impacting business associates and key changes to the breach notification rule.

Overview of the Omnibus Rule

The Omnibus Rule actually is comprised of the following four final rules. HHS decided to combine these rules in an effort to reduce the impact on regulated entities and to reduce the number of times regulated entities would need to undertake certain compliance activities.

1. Final modifications to the HIPAA Privacy, Security, and Enforcement Rules mandated by the HITECH Act, and certain other modifications to improve the Rules, which were issued as a proposed rule on July 14, 2010. These modifications include:

  • making business associates of covered entities directly liable for compliance with certain of the HIPAA Privacy and Security Rules' requirements
  • strengthening the limitations on the use and disclosure of protected health information (PHI) for marketing and fundraising purposes
  • prohibiting the sale of PHI without individual authorization
  • expanding individuals' rights to receive electronic copies of their health information and to restrict disclosures to a health plan concerning treatment for which the individual has paid in full out-of-pocket
  • requiring modifications to, and redistribution of, a covered entity's notice of privacy practices
  • modifying the individual authorization and other requirements to facilitate research and disclosure of child immunization proof to schools, and to enable access to decedent information by family members or others
  • adopting the additional HITECH Act enhancements to the Enforcement Rule not previously adopted in the October 30, 2009 interim final rule, such as the provisions addressing enforcement of noncompliance with the HIPAA Rules due to willful neglect.

2. Final rule adopting changes to the HIPAA Enforcement Rule to incorporate the increased and tiered civil money penalty structure provided by the HITECH Act, originally published as an interim final rule on October 30, 2009.

3. Final rule on Breach Notification for Unsecured PHI under the HITECH Act, which replaces the breach notification rule's "harm" threshold with a more objective standard and supplants an interim final rule published on August 24, 2009.

4. Final rule modifying the HIPAA Privacy Rule as required by the Genetic Information Nondiscrimination Act (GINA) to prohibit most health plans from using or disclosing genetic information for underwriting purposes, which was published as a proposed rule on October 7, 2009.

Despite the breadth of the Omnibus Rule, there remain some anticipated rules from HHS implementing the HITECH Act requirements. In particular, the Omnibus Rule does not address the proposed rulemaking for the accounting of disclosures requirement under the HITECH Act, which was the subject of a May 2011 notice of proposed rulemaking.

Timing

The Omnibus Rule will be effective 60 days after publication in the Federal Register – on March 26, 2013. In general, covered entities and business associates must comply with the requirements of the Omnibus Rule 180 days after the effective date of the rules – by September 23, 2013.

There are two notable exceptions to this timeline. First, for those business associate agreements that qualify for the transition exception, the parties will have until the earlier of (1) the date the existing agreement is renewed or modified, or (2) September 22, 2014, to bring their agreements into compliance. Second, with respect to compliance with the notification requirements for breaches of unsecured PHI, the standards provided in the interim final rule continue to apply until the compliance date for the Omnibus Rule of September 23, 2013.

Business Associates and Business Associate Agreements

The Omnibus Rule finalizes rules directly impacting business associates of covered entities, and subcontractors to business associates. Under the HIPAA Privacy Rule, business associates (and by extension subcontractors) are permitted to use and disclose PHI only in accordance with their business associate contracts or as required by law.

Who Is a Business Associate?

Addressing the pivotal question of "who is a business associate," the Omnibus Rule makes a number of modifications to the existing definition of "business associate." HHS has added the word "maintains" to the definition to clarify that entities that store or maintain PHI are business associates. Generally, a business associate includes a person (or entity) who creates, receives, maintains or transmits PHI on behalf of a covered entity (emphasis added). Additionally, the definition now includes the HITECH Act-mandated specific inclusion of:

  • Health Information Organization, E-prescribing Gateway, or other person that provides data transmission services with respect to PHI to a covered entity and that requires access on a routine basis to such PHI, and
  • a person that offers a personal health record to one or more individuals on behalf of a covered entity.

Additionally, through the Omnibus Rule HHS finalized its proposal to extend the HIPAA rules to subcontractors. Subcontractors are specifically included right in the modified definition of "business associate."

A subcontractor that creates, receives, maintains, or transmits PHI on behalf of the business associate. (A subcontractor is now defined as a person to whom a business associate delegates a function, activity, or service, other than in the capacity of a member of the workforce of such business associate.)

In adopting its proposal, HHS maintains that it has authority to do so under the HITECH Act and notes that the intent of this extension of the rules was to "avoid having privacy and security protections for protected health information lapse merely because a function is performed by an entity that is a subcontractor rather than an entity with a direct relationship with a covered entity." HHS clarifies that this extension of the rules is not limited to "first tier" subcontractors but also applies to downstream contractors that create, receive, maintain or transmit PHI for or on behalf of business associates or subcontractors.

Direct Liability of Business Associates and Subcontractors

With the final adoption of these changes, business associates and subcontractors are directly liable for violations of applicable HIPAA privacy, security and breach notification rules, including:

  • compliance with the HIPAA Security Rule's administrative, physical and technical safeguards and certain documentation requirements
  • impermissible uses and disclosures of PHI and certain other requirements under the Privacy Rule, including providing an accounting of disclosures of PHI and failing to disclose PHI as needed to respond to an individual's request for an copy of electronic PHI
  • notification of a covered entity of a breach of unsecured PHI
  • compliance with documentation requirements including executing business associate agreements
  • failing to disclose PHI when required by the Secretary of HHS to determine the business associate's compliance.

This direct liability is in addition to contractual liability under business associate agreements. In discussing the modifications to the Security Rule requirements, HHS notes that as business associates, and their subcontractors, are already contractually obligated to comply with these requirements, compliance will only require "modest improvements." HHS does also recognize, however, that some business associates may not have engaged in the formal administrative safeguards such as performing the risk analysis. Notwithstanding HHS's view of the size of the task ahead, coming into compliance with the HIPAA Rules will be a significant undertaking for business associates and business associate subcontractors who will need to conduct, or revisit, their risk analysis and develop and implement a HIPAA compliance program.

Business Associate Agreements

Covered entities and business associates are required to obtain "satisfactory assurances" through execution of business associate agreements with their business associates and subcontractor business associates. The Omnibus Rule includes modifications to the requirements for business associate agreements, both within the Privacy Rule and within the Security Rule. One such change clarifies that the obligation to obtain satisfactory assurances from a business associate that is a subcontractor is the obligation of the business associate and not an obligation of the covered entity. Another provision imposes the obligation on a business associate that is aware of non-compliance by a subcontractor to respond as a covered entity would be required to, including terminating the agreement if necessary. Despite receiving many comments questioning the continued need for business associate agreements, HHS declined to eliminate the requirement and states that they continue to see a need for business associate agreements.

HHS discusses and confirms that both covered entities and business associates are liable for the violations due to the acts or omissions of their agents, under the federal common law standard of agency. Not all business associates are automatically agents of covered entities and not all subcontractors are agents of covered entities. Such liability depends on whether there is an agency relationship and whether the act or omission was within the scope of the agency.

Changes to Breach Notification Rule

One of the most significant developments in the Omnibus Rule is HHS's change in the definition of what constitutes a breach. Under the 2009 interim final Breach Notification Rule for Unsecured PHI (Interim Rule), a breach required a finding that the access, use or disclosure of PHI poses "a significant risk of financial, reputational or other harm to an individual." This harm threshold, which had to be met before breach notification was triggered, has always been controversial. The Omnibus Rule replaces the "harm threshold" with a new standard, which will likely result in more breach notifications to patients.

Under the Omnibus Rule, the breach is presumed upon the occurrence of an impermissible acquisition, access, use or disclosure of PHI such that notification is required unless a risk assessment demonstrates that there is a low probability that the PHI has been compromised.

Four factors to be considered in conducting the risk assessment are:

  • the nature and extent of the PHI involved (such as types of identifiers and risk of re-identification)
  • the unauthorized person who used the PHI or to whom the disclosure was made
  • whether the PHI actually was acquired or viewed, and
  • the extent to which the risk to the PHI has been mitigated.

Additionally, HHS removed the exception on limited data sets that do not contain any dates of birth and zip codes. Thus, the breach standard and risk assessment apply to limited data sets as well.

Other provisions of the Interim Rule related to breach notification largely remain unchanged. However, the Omnibus Rule did clarify that notice to HHS for breaches affecting less than 500 individuals should be no later than 60 days after the end of the calendar year in which the breaches were discovered, not in which the breaches occurred.

In summary, the Omnibus Rule has set the default position in a security incident involving PHI as sending breach notifications unless there is some showing of low probability that PHI has been compromised. In HHS's opinion, this focus on whether the PHI (not the individual) has been harmed is a more objective standard. Questions still will arise since the Omnibus Rule has not defined what "compromised" means. HHS encourages covered entities and business associates to take advantage of the safe harbor by encrypting PHI thus avoiding this issue altogether.

No Time to Delay

With the publication of the Omnibus Rule, it is clear that health care providers, other HIPAA-covered entities, business associates and business associate subcontractors all will need to re-invest in HIPAA/HITECH Act compliance efforts in 2013. These tasks will include conducting (or updating) risk analysis, risk management activities, policy and procedure implementation or updates, and reviewing and amending or executing business associate contracts with business associates and subcontractors. With the limited time to come into compliance afforded by the Omnibus Rule, combined with HHS's increasing emphasis on enforcement, these efforts will require committed investment of both resources and funds.

The final rulemaking is to be published in the Federal Register on January 25, 2013, and until then the pre-publication rulemaking is available at https://www.federalregister.gov/public-inspection.

The content of this article is intended to provide a general guide to the subject matter. Specialist advice should be sought about your specific circumstances.

To print this article, all you need is to be registered on Mondaq.com.

Click to Login as an existing user or Register so you can print this article.

Authors
Rebekah Monson
Henry C. Fader
 
In association with
Related Video
Up-coming Events Search
Tools
Print
Font Size:
Translation
Channels
Mondaq on Twitter
 
Register for Access and our Free Biweekly Alert for
This service is completely free. Access 250,000 archived articles from 100+ countries and get a personalised email twice a week covering developments (and yes, our lawyers like to think you’ve read our Disclaimer).
 
Email Address
Company Name
Password
Confirm Password
Position
Mondaq Topics -- Select your Interests
 Accounting
 Anti-trust
 Commercial
 Compliance
 Consumer
 Criminal
 Employment
 Energy
 Environment
 Family
 Finance
 Government
 Healthcare
 Immigration
 Insolvency
 Insurance
 International
 IP
 Law Performance
 Law Practice
 Litigation
 Media & IT
 Privacy
 Real Estate
 Strategy
 Tax
 Technology
 Transport
 Wealth Mgt
Regions
Africa
Asia
Asia Pacific
Australasia
Canada
Caribbean
Europe
European Union
Latin America
Middle East
U.K.
United States
Worldwide Updates
Check to state you have read and
agree to our Terms and Conditions

Terms & Conditions and Privacy Statement

Mondaq.com (the Website) is owned and managed by Mondaq Ltd and as a user you are granted a non-exclusive, revocable license to access the Website under its terms and conditions of use. Your use of the Website constitutes your agreement to the following terms and conditions of use. Mondaq Ltd may terminate your use of the Website if you are in breach of these terms and conditions or if Mondaq Ltd decides to terminate your license of use for whatever reason.

Use of www.mondaq.com

You may use the Website but are required to register as a user if you wish to read the full text of the content and articles available (the Content). You may not modify, publish, transmit, transfer or sell, reproduce, create derivative works from, distribute, perform, link, display, or in any way exploit any of the Content, in whole or in part, except as expressly permitted in these terms & conditions or with the prior written consent of Mondaq Ltd. You may not use electronic or other means to extract details or information about Mondaq.com’s content, users or contributors in order to offer them any services or products which compete directly or indirectly with Mondaq Ltd’s services and products.

Disclaimer

Mondaq Ltd and/or its respective suppliers make no representations about the suitability of the information contained in the documents and related graphics published on this server for any purpose. All such documents and related graphics are provided "as is" without warranty of any kind. Mondaq Ltd and/or its respective suppliers hereby disclaim all warranties and conditions with regard to this information, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. In no event shall Mondaq Ltd and/or its respective suppliers be liable for any special, indirect or consequential damages or any damages whatsoever resulting from loss of use, data or profits, whether in an action of contract, negligence or other tortious action, arising out of or in connection with the use or performance of information available from this server.

The documents and related graphics published on this server could include technical inaccuracies or typographical errors. Changes are periodically added to the information herein. Mondaq Ltd and/or its respective suppliers may make improvements and/or changes in the product(s) and/or the program(s) described herein at any time.

Registration

Mondaq Ltd requires you to register and provide information that personally identifies you, including what sort of information you are interested in, for three primary purposes:

  • To allow you to personalize the Mondaq websites you are visiting.
  • To enable features such as password reminder, newsletter alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our information providers who provide information free for your use.

Mondaq (and its affiliate sites) do not sell or provide your details to third parties other than information providers. The reason we provide our information providers with this information is so that they can measure the response their articles are receiving and provide you with information about their products and services.

If you do not want us to provide your name and email address you may opt out by clicking here .

If you do not wish to receive any future announcements of products and services offered by Mondaq by clicking here .

Information Collection and Use

We require site users to register with Mondaq (and its affiliate sites) to view the free information on the site. We also collect information from our users at several different points on the websites: this is so that we can customise the sites according to individual usage, provide 'session-aware' functionality, and ensure that content is acquired and developed appropriately. This gives us an overall picture of our user profiles, which in turn shows to our Editorial Contributors the type of person they are reaching by posting articles on Mondaq (and its affiliate sites) – meaning more free content for registered users.

We are only able to provide the material on the Mondaq (and its affiliate sites) site free to site visitors because we can pass on information about the pages that users are viewing and the personal information users provide to us (e.g. email addresses) to reputable contributing firms such as law firms who author those pages. We do not sell or rent information to anyone else other than the authors of those pages, who may change from time to time. Should you wish us not to disclose your details to any of these parties, please tick the box above or tick the box marked "Opt out of Registration Information Disclosure" on the Your Profile page. We and our author organisations may only contact you via email or other means if you allow us to do so. Users can opt out of contact when they register on the site, or send an email to unsubscribe@mondaq.com with “no disclosure” in the subject heading

Mondaq News Alerts

In order to receive Mondaq News Alerts, users have to complete a separate registration form. This is a personalised service where users choose regions and topics of interest and we send it only to those users who have requested it. Users can stop receiving these Alerts by going to the Mondaq News Alerts page and deselecting all interest areas. In the same way users can amend their personal preferences to add or remove subject areas.

Cookies

A cookie is a small text file written to a user’s hard drive that contains an identifying user number. The cookies do not contain any personal information about users. We use the cookie so users do not have to log in every time they use the service and the cookie will automatically expire if you do not visit the Mondaq website (or its affiliate sites) for 12 months. We also use the cookie to personalise a user's experience of the site (for example to show information specific to a user's region). As the Mondaq sites are fully personalised and cookies are essential to its core technology the site will function unpredictably with browsers that do not support cookies - or where cookies are disabled (in these circumstances we advise you to attempt to locate the information you require elsewhere on the web). However if you are concerned about the presence of a Mondaq cookie on your machine you can also choose to expire the cookie immediately (remove it) by selecting the 'Log Off' menu option as the last thing you do when you use the site.

Some of our business partners may use cookies on our site (for example, advertisers). However, we have no access to or control over these cookies and we are not aware of any at present that do so.

Log Files

We use IP addresses to analyse trends, administer the site, track movement, and gather broad demographic information for aggregate use. IP addresses are not linked to personally identifiable information.

Links

This web site contains links to other sites. Please be aware that Mondaq (or its affiliate sites) are not responsible for the privacy practices of such other sites. We encourage our users to be aware when they leave our site and to read the privacy statements of these third party sites. This privacy statement applies solely to information collected by this Web site.

Surveys & Contests

From time-to-time our site requests information from users via surveys or contests. Participation in these surveys or contests is completely voluntary and the user therefore has a choice whether or not to disclose any information requested. Information requested may include contact information (such as name and delivery address), and demographic information (such as postcode, age level). Contact information will be used to notify the winners and award prizes. Survey information will be used for purposes of monitoring or improving the functionality of the site.

Mail-A-Friend

If a user elects to use our referral service for informing a friend about our site, we ask them for the friend’s name and email address. Mondaq stores this information and may contact the friend to invite them to register with Mondaq, but they will not be contacted more than once. The friend may contact Mondaq to request the removal of this information from our database.

Emails

From time to time Mondaq may send you emails promoting Mondaq services including new services. You may opt out of receiving such emails by clicking below.

*** If you do not wish to receive any future announcements of services offered by Mondaq you may opt out by clicking here .

Security

This website takes every reasonable precaution to protect our users’ information. When users submit sensitive information via the website, your information is protected using firewalls and other security technology. If you have any questions about the security at our website, you can send an email to webmaster@mondaq.com.

Correcting/Updating Personal Information

If a user’s personally identifiable information changes (such as postcode), or if a user no longer desires our service, we will endeavour to provide a way to correct, update or remove that user’s personal data provided to us. This can usually be done at the “Your Profile” page or by sending an email to EditorialAdvisor@mondaq.com.

Notification of Changes

If we decide to change our Terms & Conditions or Privacy Policy, we will post those changes on our site so our users are always aware of what information we collect, how we use it, and under what circumstances, if any, we disclose it. If at any point we decide to use personally identifiable information in a manner different from that stated at the time it was collected, we will notify users by way of an email. Users will have a choice as to whether or not we use their information in this different manner. We will use information in accordance with the privacy policy under which the information was collected.

How to contact Mondaq

You can contact us with comments or queries at enquiries@mondaq.com.

If for some reason you believe Mondaq Ltd. has not adhered to these principles, please notify us by e-mail at problems@mondaq.com and we will use commercially reasonable efforts to determine and correct the problem promptly.