New Omnibus Rule Released: HIPAA Puts on More Weight

by Davis Wright Tremaine LLP

On Jan. 17, 2013, the Department of Health and Human Services (HHS) released the long-awaited “Omnibus Rule,” which amends the administrative simplification provisions of the Health Insurance Portability and Accountability Act (HIPAA). The Omnibus Rule, which is expected to be published Jan. 25, 2013, implements most of the privacy and security provisions of the Health Information Technology for Economic and Clinical Health (HITECH) Act and significantly extends the reach and limits of HIPAA. The Omnibus Rule, in part, expands certain HIPAA obligations to business associates and their subcontractors, modifies the breach notification standard, expands patient rights to access and to restrict disclosure of protected health information (PHI), imposes new rules governing uses and disclosures of PHI, clarifies enforcement approaches, and addresses obligations under the Genetic Information Nondiscrimination Act of 2008 (GINA).

In response, covered entities should consider:

  • Performing a gap analysis to determine what policies and procedures must be revisited in light of the Omnibus Rule;
  • Revising privacy and security policies and procedures to bring the organization into compliance—this is a good opportunity to review and fine-tune existing policies based on guidance and experience;
  • Revising breach notification policies, procedures, and breach response plans, particularly with respect to conducting a risk assessment for determining whether notification is required;
  • Amending notices of privacy practices (and making sure the revised notices are properly posted and distributed);
  • Training workforce and promoting more ongoing awareness;
  • Revising business associate contract templates and beginning the painful process of amending/renegotiating each one;
  • Determining whether any forms, such as requests for access, should be updated or created;
  • Continuing—or making an increased effort—to take advantage of the safe harbor provision by encrypting PHI according to HHS’ guidance; and
  • Making sure an updated risk analysis is in place and reflects vulnerabilities addressed in HHS guidance, such as mobile devices.

Business associates and their subcontractors will need to create and implement a HIPAA compliance program if they have not already done so. This includes performing (or possibly revisiting) their risk analysis and risk management processes, developing and implementing appropriate policies and procedures, and training workforce.

The compliance date is Sept. 23, 2013, although the Omnibus Rule grandfathers certain current HIPAA provisions. We will be providing a webinar overviewing the Omnibus Rule on Jan. 25, 2013, and a webinar addressing business associate issues from the perspective of covered entities, business associates, and subcontractors on Jan. 30, 2013. You may register for one or both webinars here.

Into the breach: Major change in breach notification standard and other changes to the breach notification rule

New breach standard

In a somewhat surprising development, the Omnibus Rule materially revises the definition of a “breach,” which seems to make breach notification more likely. The HITECH Act requires covered entities and business associates to provide notification following discovery of a breach of unsecured PHI. Breach means the acquisition, access, use, or disclosure of PHI in a manner not permitted under the HIPAA privacy rule that “compromises the security or privacy” of the PHI unless an exception applies. Under the interim final breach notification rule, the privacy or security of PHI was deemed to be compromised if there was a significant risk of financial, reputational, or other harm to the individual as a result of the impermissible use or disclosure of PHI (commonly referred to as the “harm standard”). In other words, if the entity could demonstrate there is no significant risk of harm, then the incident did not rise to a reportable breach.

The harm standard has been controversial since its inception. Commenters who opposed the harm standard (including certain members of Congress) argued that it sets too high a bar for triggering breach notification and that it is too subjective, resulting in inconsistent interpretations. The Omnibus Rule replaces this “harm standard” with (according to HHS) a more objective process for assessing whether PHI has been compromised. The new standard, however, still appears to leave covered entities and business associates with a lot of questions.

The Omnibus Rule amends the definition of breach to clarify that the impermissible acquisition, access, use, or disclosure of PHI is presumed to be a breach and breach notification is necessary unless a covered entity or business associate can demonstrate, through a documented risk assessment, that there is a low probability that the PHI has been compromised. To do so, the Omnibus Rule identifies four factors that must be considered in a risk assessment:

  • The nature and extent of the PHI involved;
  • 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.

The preamble to the Omnibus Rule provides substantial guidance on how to apply these factors, and notes that other factors may be considered where necessary. HHS indicates that covered entities and business associates must evaluate the overall probability that PHI has been compromised by considering all combined factors in a thorough risk assessment. HHS states that it will issue additional guidance in the future to aid covered entities and business associates in performing risk assessments with respect to frequently occurring scenarios.

Interestingly, the Omnibus Rule has deleted the definition of “compromises the privacy or security” of PHI (which was the harm threshold). Now, covered entities and business associates have mandated factors and a presumption to overcome but no definition of the term “compromises.” HHS, however, declined to adopt a bright-line standard requiring notification of all impermissible uses and disclosures without any assessment of risk, recognizing that some unauthorized acquisition, access, use, or disclosure is so inconsequential that it does not warrant notification.

Limited data set exception removed

In addition, the Omnibus Rule removes the exception for limited data sets that do not contain birth dates or ZIP codes. By removing this exception, the Omnibus Rule requires that the impermissible acquisition, access, use, or disclosure of limited data sets, even those that do not contain birth dates or ZIP codes, be subject to a risk assessment to demonstrate that breach notification is not required.

Clarification of notification to HHS

The HITECH Act requires covered entities to notify HHS of breaches of unsecured PHI, with the timing of such notification based on the size of the breach. As has been the case, the Omnibus Rule requires notification of breaches affecting 500 or more individuals contemporaneously with notification of the affected individuals. For breaches affecting fewer than 500 individuals, the Omnibus Rule clarifies that covered entities must notify HHS within 60 days after the end of the calendar year in which the breaches were “discovered,” not in which the breaches “occurred.”

Some good news, some bad news: New restrictions and flexibility on using and disclosing PHI


HHS offered some welcome news to health care providers by expanding the use and disclosure of PHI for fundraising purposes. Previously, a covered entity could use or disclose only demographic information and dates of service for fundraising. A longstanding complaint among health care providers has been that these limits do not allow appropriate targeting of fundraising efforts. In response, HHS expanded the categories of PHI that may be used and disclosed for fundraising to also include department of service, treating physician, outcome information, and health insurance. Accordingly, a health care provider seeking to raise funds for a new cancer center can target its efforts to oncology patients who had positive outcomes.

Additionally, the HITECH Act requires covered entities to provide individuals with greater opportunity to opt out of receiving fundraising communications. While the privacy rule already required an opportunity to opt out with each fundraising communication, the Omnibus Rule requires that:

  • The opportunity to opt out be “clear and conspicuous”;
  • The method of opting out not require undue burden (the preamble indicates that requiring the individual to write a letter to opt-out would be an undue burden); and
  • The covered entity not make fundraising communications to the individual after the individual has opted out (the prior rule required only a “reasonable effort”).

The Omnibus Rule explicitly provides that a covered entity may provide an individual who has opted out with a method to opt back in to future fundraising communications.

Finally, the Omnibus Rule requires the covered entity’s notice of privacy practices to indicate that an individual may opt out of fundraising communications.


In accordance with the HITECH Act, the Omnibus Rule expands what uses and disclosures of PHI are considered marketing and, therefore, require an individual’s authorization. The Omnibus Rule requires authorization for all treatment and health care operations communications that encourage the use of a product or service when a covered entity receives “financial remuneration” (as opposed to plain old remuneration) for making the communication from the third party whose product or service is being marketed. For example, prior to the compliance date of the Omnibus Rule, an authorization would not be required for a hospital to send a flyer to all of its patients about the availability of a new imaging device being made available by the hospital, even if the communication was paid for by the manufacturer of the imaging device. Under the Omnibus Rule, the hospital no longer would be permitted to send communications about its new imaging device if the manufacturer of the device pays the hospital for the communications, unless the hospital first obtains authorizations from its patients.

The Omnibus Rule includes an exception, as provided in the HITECH Act, for communications about a drug or biologic that currently is prescribed to the individual as long as any remuneration is reasonably related to the covered entity’s cost of making the communications. Accordingly, a drug manufacturer may subsidize a physician’s cost for sending out refill reminders.

The new marketing restrictions do not impact a covered entity’s face-to-face communications with individuals.

Sale of PHI

The Omnibus Rule limits a covered entity or business associate in receiving remuneration in exchange for PHI. HIPAA never has allowed a covered entity to simply sell PHI without an authorization. Previously, however, there was no restriction on a covered entity receiving payment for a disclosure of PHI that the privacy rule permitted. In contrast, the Omnibus Rule generally prohibits the “sale of PHI” by a covered entity or business associate unless an authorization is obtained or an exception applies.

Exceptions include disclosures: (1) for treatment and payment; (2) for public health; (3) as part of the sale, transfer, merger, or acquisition of a covered entity (or related due diligence) where the recipient is or will become a covered entity; and (4) as required by law. In such cases, there is no cap on the amount of payment the disclosing covered entity may receive.

The Omnibus Rule includes a general exception for any permissible disclosure if remuneration is limited to the cost of preparation and transmittal. The other exceptions, which were specified in the HITECH Act, have limited impact. There is an exception for business associates or subcontractors where the only remuneration is for the business associate’s or subcontractor’s activity, but this has limited impact since the preamble clarifies that remuneration for services, rather than PHI, is not a violation. The Omnibus Rule also excludes disclosures to provide an individual with access to the individual’s PHI or to provide an accounting of disclosures, but in both cases HIPAA otherwise limits any permissible payments to a reasonable, cost-based fee. The Omnibus Rule also includes an exception for research, but payment is limited to a reasonable, cost-based fee to cover the cost of preparation and transmittal, which is the same limit the Omnibus Rule generally applies to other types of disclosures.


While not addressed in the HITECH Act, the Omnibus Rule finalizes HHS’ proposal to allow a blending of “conditioned” and “unconditioned” authorizations into a single document. Generally, HIPAA does not allow a covered entity to condition treatment on an individual executing an authorization. One of the exceptions is for clinical research, where the covered entity may condition the research-related treatment on execution of an authorization to use and disclose the individual’s PHI in the research. Previously, however, HIPAA prohibited combining such a conditioned authorization with an authorization that could not be conditioned, such as an authorization to use and disclose the individual’s PHI for a tissue bank.

The Omnibus Rule will permit the combining of conditioned and unconditioned authorizations, allowing the individual to opt-in to the unconditioned authorization. This is welcome news for the research community, as it simplifies authorization paperwork. For example, a researcher will be able to rely on a single authorization for a clinical trial that requires execution of the authorization to participate in the trial and that also includes an opt-in (such as a check box or a second signature line) authorizing the covered entity to use and disclose the individual’s PHI for a tissue bank. The authorization must make clear that the individual may choose not to opt in to the tissue bank and that the choice will not impact treatment, payment, or benefits.

The preamble of the Omnibus Rule also includes a change of interpretation of HIPAA that will be a boon for the research community. Previously, HHS interpreted that an authorization for research must be study specific. A valid authorization could not authorize use and disclosure of PHI for future research. The research community long has stated that this interpretation stands as a significant impediment to beneficial secondary research efforts. HHS clarifies that it has changed its interpretation and now permits an authorization to encompass future research studies. The language of the authorization must adequately inform the individual that the individual’s PHI may be used in future research studies. HHS did not amend the regulation itself with respect to this issue.

Decedent information

The Omnibus Rule provides covered entities greater flexibility with respect to the PHI of deceased individuals. Previously, a covered entity had to apply the protections of HIPAA to decedent information without regard to how long ago the individual died. The Omnibus Rule limits HIPAA protections to 50 years after an individual’s death.

Additionally, the Omnibus Rule provides covered entities with greater flexibility to disclose a decedent’s PHI to persons who were involved in the decedent’s care or payment. Previously, a covered entity could disclose PHI to a family, friend, or other person involved in an individual’s care or payment, but could no longer disclose PHI to such persons after the individual’s death unless the person was the decedent’s personal representative. This limit frequently was problematic, such as when a decedent’s estate was not open, and the covered entity could not identify a personal representative. While not addressed in the HITECH Act, the Omnibus Rule allows covered entities to continue to communicate with involved family and friends after an individual’s death, unless contrary to the individual’s previously expressed preference.

Student immunization records

While not required by the HITECH Act, the Omnibus Rule provides covered entities with greater flexibility to disclose student immunization records. Specifically, a covered entity will be permitted to disclose the immunization record of a student or prospective student to a school if: (1) state law requires the school to have proof of immunization; and (2) the covered entity obtains and documents the agreement of the parent or guardian. The parent or guardian’s agreement may be in writing (but need not satisfy the requirements for a HIPAA authorization) or oral, in which case the covered entity must document the agreement.

Genetic information

The Omnibus Rule, in accordance with GINA, clarifies that genetic information is a type of health information and prohibits health plans (other than long term care plans) from using or disclosing genetic information for underwriting purposes. As with other regulations under GINA, “genetic information” is broadly defined to include manifestation of a disease or disorder in a family member of an individual in addition to genetic tests of individuals and family members and requests for and receipt of genetic services. The preamble clarifies that the actual manifestation of a disease or disorder in the individual would not be considered genetic information. A health plan that intends to use or disclose PHI for underwriting purposes must add a statement to its notice of privacy practices providing that it will not use or disclose genetic information for such purposes. Other than clarifying that genetic information is health information, the provision does not impact health care providers.

Expanded individual rights create rites of passage for covered entities

Expanded rights for access to electronically-stored PHI

The Omnibus Rule has expanded an individual’s right to obtain an electronic copy of PHI stored electronically in a designated record set (e.g., medical records, billing records, and other records relied upon to make decisions about the individual). This is a relatively minor change. HIPAA already provided that an individual has the right to receive access in the form and format requested by the individual, if readily producible. If not readily producible, HIPAA previously required the covered entity to provide a hard copy. The HITECH Act changed this, providing that if the covered entity maintains the PHI in an electronic health record and cannot readily produce the requested form and format, then it must provide the individual with an electronic copy. The Omnibus Rule expands the right to an electronic copy to any PHI stored electronically in a designated record set, rather than limiting it to the electronic health record. In sum, an individual continues to have a right to a copy of the individual’s designated record set in the individual’s requested form and format if readily producible, but now has the right to an electronic copy if the designated record set is maintained electronically and the requested form and format is not readily producible.

If the covered entity cannot readily produce the form and format requested by an individual, then it must offer other electronic formats that it can provide. If the individual does not agree to any alternate electronic formats offered by the covered entity, then the covered entity must provide a hard copy as an option to fulfill the access request. A covered entity is not required to purchase new software or systems to accommodate the requested electronic format. That said, to the extent some legacy or other systems are not capable of providing any form of electronic copy, the preamble to the Omnibus Rule indicates that covered entities will need to invest in additional technology so that they can meet the basic requirement to provide some form of electronic copy of the information maintained in those systems.

The individual also has the right to direct that the copy of the PHI be transmitted directly to another person designated by the individual. A covered entity must comply with such a directive, as long as it is in writing, signed by the individual, and clearly identifies both the designated person and where to send the PHI. An authorization would no longer be required in such a situation.

As clarified in the preamble to the Omnibus Rule, if an individual requests that a copy of his or her PHI be sent via unencrypted email, then a covered entity is permitted to do so, as long as the covered entity has advised the individual of the risks and the individual still prefers the unencrypted email.

Of note, covered entities now have 30 days fewer to respond to requests for access. Electronic and hard copy PHI, no matter where located, must be provided within 30 days with a single 30-day extension permitted if the covered entity provides notice of the delay to the requesting individual. The Omnibus Rule also clarifies the fees that may be charged.

Right of individuals to request restrictions on uses and disclosures of PHI

The Omnibus Rule incorporates the HITECH Act requirement that a covered entity comply with an individual’s request to restrict disclosure to a health plan (or the plan’s business associate) of his or her PHI that pertains solely to a health care item or service for which the health care provider has been paid out-of-pocket and in full. There is an exception to this right for disclosures required by law, such as mandatory claim submission provisions under Medicare and similar requirements under Medicaid or state law.

This right extends to situations where a family member or other person, including another health plan, pays for the service on behalf of the individual.

It may be advisable for providers to collect payment up front in connection with these requests, to the extent permitted by law. According to the preamble, if payment by an individual making a restriction request is dishonored, HHS expects providers to make a reasonable effort to contact the individual and obtain payment prior to billing the health plan. What efforts a health care provider must make is left to the provider’s policies and individual circumstances, consistent with its usual payment and collections processes.

With regard to referrals to and treatment by other providers in the future, it is the responsibility of the individual—not the provider—to notify subsequent providers of a restriction request. HHS, however, encourages providers to alert such future providers or at least engage in a dialogue with the patient so that he or she is aware of the patient’s responsibility to request restrictions with subsequent providers.

Updates to notices of privacy practices

Providers and health plans likely will need to update their notices of privacy practices (NPPs). The updated NPPs must advise individuals of the Omnibus Rule’s required changes, specifically including, as applicable: (1) the prohibition on the sale of PHI without the express written authorization of the individual; (2) the duty of a covered entity to notify affected individuals of a breach of unsecured PHI; (3) the individual’s right to opt out of receiving any fundraising communications from the covered entity; and (4) the right of the individual to restrict disclosures of PHI to a health plan with respect to health care for which the individual has paid out-of-pocket and in full. In addition, most health plans will need to inform individuals of the prohibition against using or disclosing genetic information for underwriting purposes. Covered entities also will want to review their NPPs to ensure that they accurately describe their privacy practices, especially in light of the Omnibus Rule’s new requirements.

The requirements for distributing updated NPPs have been modified for health plans but not health care providers. Health plans may include their revised NPP in their next annual mailing as long as they prominently post the revised NPP on their web sites by the effective date of the material change to the NPP. Health plans that do not have customer service web sites are required to provide the revised NPP, or information about the material change and how to obtain the revised notice, to individuals covered by the plan within 60 days of the material revision to the NPP.

Throwing business associates under the Omni-bus

Expansion of the definition of “business associate”

The Omnibus Rule expands the definition of a “business associate” to generally include all those entities that create, receive, maintain, or transmit PHI on behalf of a covered entity. This expanded definition seems likely to bring certain organizations into the business associate fold that previously may not have been affected, such as certain document storage organizations. The Omnibus Rule also specifically identifies as business associates: (1) subcontractors (discussed below); (2) patient safety organizations; (3) health information organizations (and similar organizations); (4) e-prescribing gateways; and (5) vendors of personal health records that provide services on behalf of a covered entity.


The Omnibus Rule pulls subcontractors into the definition of business associates. Under the Omnibus Rule, a subcontractor is 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. This means that a subcontractor of a business associate that creates, receives, maintains, or transmits PHI on behalf of the business associate is now itself a business associate and subject to the HIPAA provisions applicable to business associates. Interestingly, the Omnibus Rule did not change the definition of business associate, but instead simply adds subcontractors to the list of entities that are included as business associates.

HHS states that privacy and security protections “should not lapse beyond any particular business associate.” Therefore, the business associate who contracts with the covered entity, the business associate’s subcontractor, and any subcontractor of a subcontractor—all the way down the chain – are business associates to the extent they create, receive, maintain, or transmit PHI. Of note, the Omnibus Rule makes clear that a covered entity is not required to enter into a contract or other arrangement with a business associate that is a subcontractor—that is the responsibility of the primary or first tier business associate.

Despite public comments suggesting that HHS provide subcontractors with additional time to comply, HHS declined to delay application of the requirements to subcontractors, stating that the security rule already requires covered entities to establish business associate contracts that require business associates to ensure that their subcontractors implement reasonable and appropriate safeguards to protect the security of electronic PHI they handle.

Direct liability

As expected, the Omnibus Rule makes business associates directly liable for compliance with many of the same standards and implementation specifications under the security rule and applies the same penalties to business associates that apply to covered entities. Under the privacy rule, business associates may use or disclose PHI only in accordance with their business associate contracts or as required by law. Moreover, a business associate may not use or disclose PHI in a manner prohibited by the privacy rule if done by a covered entity (unless HIPAA specifically permits such use and disclosure for business associates). The Omnibus Rule notes that not all of the requirements of the privacy rule apply to business associates. For example, business associates do not need to provide a notice of privacy practices or designate a privacy official (unless the covered entity has chosen to delegate such a responsibility to the business associate, which then would make it a contractual requirement for which contractual liability would attach). Furthermore, business associates must obtain “satisfactory assurances” in the form of business associate contracts from their subcontractor business associates. Finally, business associates must furnish any information that HHS requires to investigate whether the business associate is in compliance with the regulations.

Business associates are directly liable under HIPAA for the following:

  • Impermissible uses and disclosures;
  • Failure to provide breach notification to the covered entity;
  • Failure to provide access to a copy of electronic PHI to either the covered entity, the individual, or the individual’s designee (whichever is specified in the business associate contract);
  • Failure to disclose PHI where required by HHS to investigate or determine the business associate’s compliance with HIPAA;
  • Failure to provide an accounting of disclosures; and
  • Failure to comply with the applicable requirements of the security rule.

Business associates remain contractually liable for other requirements of the business associate contract.

Agency liability

The Omnibus Rule makes covered entities and business associates (as principals) liable for the acts of their business associate that are agents, in accordance with the federal common law of agency. This significantly impacts the relationship of covered entities and their business associates, potentially requiring greater monitoring by the covered entity when the business associate is an agent. An analysis of whether a business associate is an agent will be fact specific, taking into account the terms of a business associate contract as well as the totality of the circumstances involved in the ongoing relationship between the parties. (See below for additional discussion of agency liability.)

Business associate contracts

The Omnibus Rule makes business associate contracts applicable to arrangements involving a business associate and a subcontractor of that business associate in the same manner that business associate contracts apply to arrangements between a covered entity and its direct business associate. If a subcontractor creates, receives, maintains, or transmits PHI, then a business associate must have a business associate contract with the subcontractor.

HHS emphasizes the continued need for business associate contracts even though business associates now are held directly accountable for many provisions of HIPAA. HHS notes that business associate contracts are necessary to clarify and limit permissible uses and disclosures of PHI, ensure business associates are contractually responsible for activities for which they are not directly liable under HIPAA, and clarify respective responsibilities related to patient rights, such as access to PHI. Of note, each agreement in the business associate contract chain must be as or more stringent than the one above it regarding the uses and disclosures of PHI.

The Omnibus Rule provides an important transition period for existing business associate contracts. A business associate contract may be grandfathered for a period of time if: prior to Jan. 25, 2013, the business associate contract complies with current HIPAA requirements; and the business associate contract is not renewed or modified between March 26, 2013 and Sept. 23, 2013. If these conditions are met, the parties can operate under the existing business associate contract until the earlier of: the date on which the business associate contract is renewed or modified (after Sept. 23, 2013); or Sept. 22, 2014.

Enforcement: It’s not just for HIPAAchondriacs anymore

HHS’ HIPAA enforcement powers have been significantly strengthened by the HITECH Act and the interim final enforcement rule. The Omnibus Rule left intact much of the HIPAA enforcement approach with some additional expansion and clarification.

Business associates (including their subcontractors) now are subject to civil money penalties and other enforcement actions for noncompliance with applicable provisions of HIPAA. Like covered entities, business associates may be liable for violations by their agents.

The Omnibus Rule generally provides HHS with the discretion to resolve violations of HIPAA by informal means; however, HHS may move directly to a civil money penalty without exhausting informal resolution efforts. This may be especially likely when HHS determines that noncompliance is due to willful neglect.

Willful neglect

The Omnibus Rule retains the definition of willful neglect as “conscious, intentional failure or reckless indifference to the obligation to comply” with HIPAA. The HITECH Act requires HHS to formally investigate a complaint, which anybody can file, if a preliminary investigation indicates a possible (as opposed to probable) violation due to willful neglect. To implement that change, HHS has amended the enforcement rule to eliminate its investigatory discretion in such cases, require a compliance review of the offending party, and mandate civil money penalties if willful neglect is found. Absent a preliminary finding of willful neglect, HHS retains the discretion to investigate and to resolve complaints by informal means. Accordingly, HHS likely will place a greater focus on enforcement of noncompliance due to willful neglect.

Liability for acts of agents

The Omnibus Rule retains the concept of vicarious liability for the acts of person’s agent, with agency determined under federal common law. HHS believes that using that definition of agency assures nationwide uniformity in HIPAA implementation and consistency with other federal statutes. In the preamble, HHS clarifies that the essential factor in determining the existence of an agency relationship is whether the principal has the authority to control the questioned conduct of the agent in the performance of the agent’s duties. If the principal lacks that authority (e.g., the principal’s only recourse would be to modify the underlying agreement or sue for its breach), then the agency relationship does not satisfy the federal definition and the principal will not be liable for the agent’s conduct. HHS further noted that the existence of federal agency will depend on the facts and circumstances of each relationship. Federal common law has identified several analytical factors that must be considered:

  • When, where, and why the agent acted the way it did;
  • Whether an agent’s conduct was subject to the principal’s control;
  • Whether the agent was doing something that typically is done by such agents; and
  • Whether the principal reasonably expected the agent to engage in the questioned conduct.

The Omnibus Rule removes the exception for vicarious liability for agents that are business associates when a valid business associate contract is in place.

Definition of reasonable cause

The Omnibus Rule modifies the definition of reasonable cause, which relates to violations due to reasonable cause and not to willful neglect. Reasonable cause means an act or omission in which a covered entity or business associate knew, or by exercising reasonable diligence would have known, that the act or omission violated HIPAA but in which the covered entity or business associate did not act with willful neglect. HHS indicated that this change addresses the required mental state (called the “mens rea”) associated with the violation.

Factors relevant to determining civil money penalty amounts

HHS has identified five categories of factors that it will consider in determining the amount of any civil money penalty:

  • The nature and extent of any violation, including the number of individuals affected and the duration of the violation;
  • The nature and extent of any individual’s resulting physical, financial, or reputational harm, including any hindrance to the individual’s ability to obtain health care;
  • The history of prior noncompliance, including similar prior indications of noncompliance and the offending party’s responses to them;
  • The financial condition of the offending party, including difficulties that could have affected compliance or that could cause a money penalty to jeopardize the future provision of health care; and
  • Such other matters as justice may require.

Davis Wright Tremaine will host a series of webinars covering the new rule. The first two will be:


DISCLAIMER: Because of the generality of this update, the information provided herein may not be applicable in all situations and should not be acted upon without specific legal advice based on particular situations.

© Davis Wright Tremaine LLP | Attorney Advertising

Written by:

Davis Wright Tremaine LLP

Davis Wright Tremaine LLP on:

Readers' Choice 2017
Reporters on Deadline

"My best business intelligence, in one easy email…"

Your first step to building a free, personalized, morning email brief covering pertinent authors and topics on JD Supra:
*By using the service, you signify your acceptance of JD Supra's Privacy Policy.
Custom Email Digest
- hide

JD Supra Privacy Policy

Updated: May 25, 2018:

JD Supra is a legal publishing service that connects experts and their content with broader audiences of professionals, journalists and associations.

This Privacy Policy describes how JD Supra, LLC ("JD Supra" or "we," "us," or "our") collects, uses and shares personal data collected from visitors to our website (located at (our "Website") who view only publicly-available content as well as subscribers to our services (such as our email digests or author tools)(our "Services"). By using our Website and registering for one of our Services, you are agreeing to the terms of this Privacy Policy.

Please note that if you subscribe to one of our Services, you can make choices about how we collect, use and share your information through our Privacy Center under the "My Account" dashboard (available if you are logged into your JD Supra account).

Collection of Information

Registration Information. When you register with JD Supra for our Website and Services, either as an author or as a subscriber, you will be asked to provide identifying information to create your JD Supra account ("Registration Data"), such as your:

  • Email
  • First Name
  • Last Name
  • Company Name
  • Company Industry
  • Title
  • Country

Other Information: We also collect other information you may voluntarily provide. This may include content you provide for publication. We may also receive your communications with others through our Website and Services (such as contacting an author through our Website) or communications directly with us (such as through email, feedback or other forms or social media). If you are a subscribed user, we will also collect your user preferences, such as the types of articles you would like to read.

Information from third parties (such as, from your employer or LinkedIn): We may also receive information about you from third party sources. For example, your employer may provide your information to us, such as in connection with an article submitted by your employer for publication. If you choose to use LinkedIn to subscribe to our Website and Services, we also collect information related to your LinkedIn account and profile.

Your interactions with our Website and Services: As is true of most websites, we gather certain information automatically. This information includes IP addresses, browser type, Internet service provider (ISP), referring/exit pages, operating system, date/time stamp and clickstream data. We use this information to analyze trends, to administer the Website and our Services, to improve the content and performance of our Website and Services, and to track users' movements around the site. We may also link this automatically-collected data to personal information, for example, to inform authors about who has read their articles. Some of this data is collected through information sent by your web browser. We also use cookies and other tracking technologies to collect this information. To learn more about cookies and other tracking technologies that JD Supra may use on our Website and Services please see our "Cookies Guide" page.

How do we use this information?

We use the information and data we collect principally in order to provide our Website and Services. More specifically, we may use your personal information to:

  • Operate our Website and Services and publish content;
  • Distribute content to you in accordance with your preferences as well as to provide other notifications to you (for example, updates about our policies and terms);
  • Measure readership and usage of the Website and Services;
  • Communicate with you regarding your questions and requests;
  • Authenticate users and to provide for the safety and security of our Website and Services;
  • Conduct research and similar activities to improve our Website and Services; and
  • Comply with our legal and regulatory responsibilities and to enforce our rights.

How is your information shared?

  • Content and other public information (such as an author profile) is shared on our Website and Services, including via email digests and social media feeds, and is accessible to the general public.
  • If you choose to use our Website and Services to communicate directly with a company or individual, such communication may be shared accordingly.
  • Readership information is provided to publishing law firms and authors of content to give them insight into their readership and to help them to improve their content.
  • Our Website may offer you the opportunity to share information through our Website, such as through Facebook's "Like" or Twitter's "Tweet" button. We offer this functionality to help generate interest in our Website and content and to permit you to recommend content to your contacts. You should be aware that sharing through such functionality may result in information being collected by the applicable social media network and possibly being made publicly available (for example, through a search engine). Any such information collection would be subject to such third party social media network's privacy policy.
  • Your information may also be shared to parties who support our business, such as professional advisors as well as web-hosting providers, analytics providers and other information technology providers.
  • Any court, governmental authority, law enforcement agency or other third party where we believe disclosure is necessary to comply with a legal or regulatory obligation, or otherwise to protect our rights, the rights of any third party or individuals' personal safety, or to detect, prevent, or otherwise address fraud, security or safety issues.
  • To our affiliated entities and in connection with the sale, assignment or other transfer of our company or our business.

How We Protect Your Information

JD Supra takes reasonable and appropriate precautions to insure that user information is protected from loss, misuse and unauthorized access, disclosure, alteration and destruction. We restrict access to user information to those individuals who reasonably need access to perform their job functions, such as our third party email service, customer service personnel and technical staff. You should keep in mind that no Internet transmission is ever 100% secure or error-free. Where you use log-in credentials (usernames, passwords) on our Website, please remember that it is your responsibility to safeguard them. If you believe that your log-in credentials have been compromised, please contact us at

Children's Information

Our Website and Services are not directed at children under the age of 16 and we do not knowingly collect personal information from children under the age of 16 through our Website and/or Services. If you have reason to believe that a child under the age of 16 has provided personal information to us, please contact us, and we will endeavor to delete that information from our databases.

Links to Other Websites

Our Website and Services may contain links to other websites. The operators of such other websites may collect information about you, including through cookies or other technologies. If you are using our Website or Services and click a link to another site, you will leave our Website and this Policy will not apply to your use of and activity on those other sites. We encourage you to read the legal notices posted on those sites, including their privacy policies. We are not responsible for the data collection and use practices of such other sites. This Policy applies solely to the information collected in connection with your use of our Website and Services and does not apply to any practices conducted offline or in connection with any other websites.

Information for EU and Swiss Residents

JD Supra's principal place of business is in the United States. By subscribing to our website, you expressly consent to your information being processed in the United States.

  • Our Legal Basis for Processing: Generally, we rely on our legitimate interests in order to process your personal information. For example, we rely on this legal ground if we use your personal information to manage your Registration Data and administer our relationship with you; to deliver our Website and Services; understand and improve our Website and Services; report reader analytics to our authors; to personalize your experience on our Website and Services; and where necessary to protect or defend our or another's rights or property, or to detect, prevent, or otherwise address fraud, security, safety or privacy issues. Please see Article 6(1)(f) of the E.U. General Data Protection Regulation ("GDPR") In addition, there may be other situations where other grounds for processing may exist, such as where processing is a result of legal requirements (GDPR Article 6(1)(c)) or for reasons of public interest (GDPR Article 6(1)(e)). Please see the "Your Rights" section of this Privacy Policy immediately below for more information about how you may request that we limit or refrain from processing your personal information.
  • Your Rights
    • Right of Access/Portability: You can ask to review details about the information we hold about you and how that information has been used and disclosed. Note that we may request to verify your identification before fulfilling your request. You can also request that your personal information is provided to you in a commonly used electronic format so that you can share it with other organizations.
    • Right to Correct Information: You may ask that we make corrections to any information we hold, if you believe such correction to be necessary.
    • Right to Restrict Our Processing or Erasure of Information: You also have the right in certain circumstances to ask us to restrict processing of your personal information or to erase your personal information. Where you have consented to our use of your personal information, you can withdraw your consent at any time.

You can make a request to exercise any of these rights by emailing us at or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

You can also manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard.

We will make all practical efforts to respect your wishes. There may be times, however, where we are not able to fulfill your request, for example, if applicable law prohibits our compliance. Please note that JD Supra does not use "automatic decision making" or "profiling" as those terms are defined in the GDPR.

  • Timeframe for retaining your personal information: We will retain your personal information in a form that identifies you only for as long as it serves the purpose(s) for which it was initially collected as stated in this Privacy Policy, or subsequently authorized. We may continue processing your personal information for longer periods, but only for the time and to the extent such processing reasonably serves the purposes of archiving in the public interest, journalism, literature and art, scientific or historical research and statistical analysis, and subject to the protection of this Privacy Policy. For example, if you are an author, your personal information may continue to be published in connection with your article indefinitely. When we have no ongoing legitimate business need to process your personal information, we will either delete or anonymize it, or, if this is not possible (for example, because your personal information has been stored in backup archives), then we will securely store your personal information and isolate it from any further processing until deletion is possible.
  • Onward Transfer to Third Parties: As noted in the "How We Share Your Data" Section above, JD Supra may share your information with third parties. When JD Supra discloses your personal information to third parties, we have ensured that such third parties have either certified under the EU-U.S. or Swiss Privacy Shield Framework and will process all personal data received from EU member states/Switzerland in reliance on the applicable Privacy Shield Framework or that they have been subjected to strict contractual provisions in their contract with us to guarantee an adequate level of data protection for your data.

California Privacy Rights

Pursuant to Section 1798.83 of the California Civil Code, our customers who are California residents have the right to request certain information regarding our disclosure of personal information to third parties for their direct marketing purposes.

You can make a request for this information by emailing us at or by writing to us at:

Privacy Officer
JD Supra, LLC
10 Liberty Ship Way, Suite 300
Sausalito, California 94965

Some browsers have incorporated a Do Not Track (DNT) feature. These features, when turned on, send a signal that you prefer that the website you are visiting not collect and use data regarding your online searching and browsing activities. As there is not yet a common understanding on how to interpret the DNT signal, we currently do not respond to DNT signals on our site.

Access/Correct/Update/Delete Personal Information

For non-EU/Swiss residents, if you would like to know what personal information we have about you, you can send an e-mail to We will be in contact with you (by mail or otherwise) to verify your identity and provide you the information you request. We will respond within 30 days to your request for access to your personal information. In some cases, we may not be able to remove your personal information, in which case we will let you know if we are unable to do so and why. If you would like to correct or update your personal information, you can manage your profile and subscriptions through our Privacy Center under the "My Account" dashboard. If you would like to delete your account or remove your information from our Website and Services, send an e-mail to

Changes in Our Privacy Policy

We reserve the right to change this Privacy Policy at any time. Please refer to the date at the top of this page to determine when this Policy was last revised. Any changes to our Privacy Policy will become effective upon posting of the revised policy on the Website. By continuing to use our Website and Services following such changes, you will be deemed to have agreed to such changes.

Contacting JD Supra

If you have any questions about this Privacy Policy, the practices of this site, your dealings with our Website or Services, or if you would like to change any of the information you have provided to us, please contact us at:

JD Supra Cookie Guide

As with many websites, JD Supra's website (located at (our "Website") and our services (such as our email article digests)(our "Services") use a standard technology called a "cookie" and other similar technologies (such as, pixels and web beacons), which are small data files that are transferred to your computer when you use our Website and Services. These technologies automatically identify your browser whenever you interact with our Website and Services.

How We Use Cookies and Other Tracking Technologies

We use cookies and other tracking technologies to:

  1. Improve the user experience on our Website and Services;
  2. Store the authorization token that users receive when they login to the private areas of our Website. This token is specific to a user's login session and requires a valid username and password to obtain. It is required to access the user's profile information, subscriptions, and analytics;
  3. Track anonymous site usage; and
  4. Permit connectivity with social media networks to permit content sharing.

There are different types of cookies and other technologies used our Website, notably:

  • "Session cookies" - These cookies only last as long as your online session, and disappear from your computer or device when you close your browser (like Internet Explorer, Google Chrome or Safari).
  • "Persistent cookies" - These cookies stay on your computer or device after your browser has been closed and last for a time specified in the cookie. We use persistent cookies when we need to know who you are for more than one browsing session. For example, we use them to remember your preferences for the next time you visit.
  • "Web Beacons/Pixels" - Some of our web pages and emails may also contain small electronic images known as web beacons, clear GIFs or single-pixel GIFs. These images are placed on a web page or email and typically work in conjunction with cookies to collect data. We use these images to identify our users and user behavior, such as counting the number of users who have visited a web page or acted upon one of our email digests.

JD Supra Cookies. We place our own cookies on your computer to track certain information about you while you are using our Website and Services. For example, we place a session cookie on your computer each time you visit our Website. We use these cookies to allow you to log-in to your subscriber account. In addition, through these cookies we are able to collect information about how you use the Website, including what browser you may be using, your IP address, and the URL address you came from upon visiting our Website and the URL you next visit (even if those URLs are not on our Website). We also utilize email web beacons to monitor whether our emails are being delivered and read. We also use these tools to help deliver reader analytics to our authors to give them insight into their readership and help them to improve their content, so that it is most useful for our users.

Analytics/Performance Cookies. JD Supra also uses the following analytic tools to help us analyze the performance of our Website and Services as well as how visitors use our Website and Services:

  • HubSpot - For more information about HubSpot cookies, please visit
  • New Relic - For more information on New Relic cookies, please visit
  • Google Analytics - For more information on Google Analytics cookies, visit To opt-out of being tracked by Google Analytics across all websites visit This will allow you to download and install a Google Analytics cookie-free web browser.

Facebook, Twitter and other Social Network Cookies. Our content pages allow you to share content appearing on our Website and Services to your social media accounts through the "Like," "Tweet," or similar buttons displayed on such pages. To accomplish this Service, we embed code that such third party social networks provide and that we do not control. These buttons know that you are logged in to your social network account and therefore such social networks could also know that you are viewing the JD Supra Website.

Controlling and Deleting Cookies

If you would like to change how a browser uses cookies, including blocking or deleting cookies from the JD Supra Website and Services you can do so by changing the settings in your web browser. To control cookies, most browsers allow you to either accept or reject all cookies, only accept certain types of cookies, or prompt you every time a site wishes to save a cookie. It's also easy to delete cookies that are already saved on your device by a browser.

The processes for controlling and deleting cookies vary depending on which browser you use. To find out how to do so with a particular browser, you can use your browser's "Help" function or alternatively, you can visit which explains, step-by-step, how to control and delete cookies in most browsers.

Updates to This Policy

We may update this cookie policy and our Privacy Policy from time-to-time, particularly as technology changes. You can always check this page for the latest version. We may also notify you of changes to our privacy policy by email.

Contacting JD Supra

If you have any questions about how we use cookies and other tracking technologies, please contact us at:

- hide

This website uses cookies to improve user experience, track anonymous site usage, store authorization tokens and permit sharing on social media networks. By continuing to browse this website you accept the use of cookies. Click here to read more about how we use cookies.