United States: HHS Issues Proposed 340B Program Omnibus Guidance: Five Things To Watch

Shannon Hartsfield Salimone is a Partner in our Tallahassee office Melissa A. Wong is an Associate in our Boston office .


  • The Department of Health and Human Services (HHS) recently issued a proposed omnibus rule to clarify existing guidance relevant to all 340B Drug Pricing Program stakeholders.
  • Comments on this proposed guidance, due by Oct. 27, 2015, likely will focus on new requirements that may present operational challenges in implementation, including a six-part test for determining patient eligibility for 340B drugs and supplemental measures to prevent duplicate discounts.

The 340B Drug Pricing Program (340B Program), established by Section 602 of the Veterans Health Care Act of 1992, is administered by the Health Resources and Services Administration (HRSA) of HHS. The 340B Program requires drug manufacturers to provide outpatient drugs to particular "covered entities" at a reduced price. HHS recently issued proposed guidance on the 340B Program, with the intent "to provide increased clarity in the marketplace for all 340B Program stakeholders and strengthen HHS's ability to administer the 340B Program effectively."1 Although this omnibus guidance consolidates much of the existing 340B Program guidance, the following proposed provisions merit special attention, particularly to those covered entities, drug manufacturers and other 340B Program stakeholders interested in submitting comments to HHS.

1. Defining Covered Outpatient Drugs Eligible for Purchase Under the 340B Program

Although HHS will continue to utilize the same statutory definition of the term "covered outpatient drug" under Sections 1927(k)(2) and 1927(k)(3) of the Social Security Act to determine the drugs eligible for purchase under the 340B Program, the proposed omnibus guidance clarifies how this definition, and particularly, the "limiting definition" under Section 1927(k)(3), would apply. Specifically, the proposed guidance states that a drug, biological product or insulin cannot qualify as a covered outpatient drug under the 340B Program if it meets both of the following conditions:

  • The drug is "provided as part of, or as incident to and in the same setting as," the services listed in Section 1927(k)(3) — such as inpatient hospital, hospice, dental or nursing facility services.
  • The payment for such services may be made under Medicaid and not as direct reimbursement for the drug.

In short, drugs are excluded from 340B Program eligibility if the drug is bundled for payment under Medicaid as part of the service and in the settings listed in the limiting definition. However, if a drug is provided as part of a hospital outpatient service and is separately and directly billed to Medicaid or a third party payor, the drug could still qualify as a covered outpatient drug under 340B.

Although this guidance helps better define the types of drugs eligible under the 340B Program, the implementation of this guidance by covered entities may prove challenging. Covered entities would be required to monitor and record 340B dispensing by payor and payment structure, and also would be required to account for reversals and refunds that may change the payor or payment structure after a claim is billed. Hospital covered entities subject to the 340B Program's prohibition on using group purchase organizations or arrangements to purchase drugs must also carefully identify which drugs could be classified as covered outpatient drugs for the purposes of the 340B Program, or else risk their eligibility as a covered entity. We expect that 340B Program stakeholders will raise several practical concerns about implementing this proposed guidance.

2. New Six-Part Test for Patients of a Covered Entity

The sale or transfer of 340B Program drugs to individuals who are not patients of a covered entity is considered diversion. In the proposed guidance, HHS suggests replacing the current three-part test for determining patient eligibility with a new six-part test that requires a prescription-by-prescription or order-by-order determination that an individual meets all of the following conditions:

  • The individual receives a healthcare service at a facility or clinic site that is registered for the 340B Program and is listed on the public 340B Program database.
  • The individual receives a healthcare service provided by a covered entity provider who is either an employee or independent contractor of the covered entity, such that the covered entity may bill for services on behalf of the provider.
  • The individual receives a drug that is ordered or prescribed by the covered entity provider as a result of the healthcare service.
  • The individual's healthcare is consistent with the scope of the federal grant, project, designation or contract.
  • The individual's drug is ordered or prescribed pursuant to a healthcare service that is classified as outpatient.
  • The individual's patient records are accessible to the covered entity and demonstrate that the covered entity is responsible for that care.

HHS notes that this six-part test was developed as HHS learned more about how the definition of a patient applied in different and diverse health care settings. The difficulty again in this case is how covered entities and other 340B Program stakeholders operationally implement the proposed requirements to ensure each individually dispensed prescription is accurately attributed to an eligible patient.

3. Replenishment, Rebilling and Repayment

Covered entities and contract pharmacies do not necessarily maintain a separate inventory of their 340B drugs, but instead may tally the drugs dispensed to each type of patient and replenish their overall drug supply when needed by reordering from the appropriate accounts. As long as the covered entity or contract pharmacy otherwise complies with all 340B requirements, HHS permits the use of this system. However, according to the proposed guidance, if a covered entity improperly accumulates or tallies its 340B drug inventory, even prior to placing an order, the covered entity would be deemed to have sold or transferred a drug to a person who is not a patient of a covered entity. Similarly, if there is a mismatch between the recorded number of 340B drugs and the actual number of 340B drugs in the virtual or separate physical inventory, HHS also will consider this a violation that constitutes diversion.

If a covered entity identifies diversion, the entity must work with the manufacturer to make a repayment within 90 days of identifying the violation. Manufacturers do retain discretion as to whether they will request a repayment from the covered entity, or instead refrain from requesting repayment in instances where the amount is de minimis or can be corrected through a credit and rebill process. Still, HHS proposes in the guidance that covered entities must notify HHS and each affected manufacturer of diversion. The covered entity is also responsible for reporting a summary of its corrective actions to HHS.

Although 340B Program stakeholders may be supportive of the discretion provided to covered entities for the management of their drug inventories, and to manufacturers in determining whether to request repayment from covered entities, they may raise issue with the concept that diversion can occur even before an order is placed for a 340B drug. In addition, a covered entity's obligation to report diversion to HHS and manufacturers makes no exception for de minimis amounts.

4. How to Prevent Duplicate Discounts

HHS prohibits duplicate discounts, whereby a covered entity cannot obtain a 340B Program discount on a drug that is already subject to a Medicaid drug rebate. HHS maintains the 340B Medicaid Exclusion File as a mechanism to help prevent duplicate discounts. If covered entities elect to purchase and dispense 340B drugs for their Medicaid patients, or to "carve-in," they must inform HRSA upon enrollment in the 340B Program so that they can be listed on the Medicaid Exclusion File accordingly.

The proposed guidance suggests that a Medicaid managed care organization (MCO) may elect to carve-in and dispense 340B drugs to its patients, or "carve-out" and purchase drugs through other mechanisms. The entity can make different determinations to participate by covered entity site and by MCO, as long as the entity provides to HRSA the identifying information of the covered entity site, the associated MCO and the decision to carve-in or carve-out. This information would also be included in the Medicaid Exclusion File.

HHS is soliciting comments on how to supplement the Medicaid Exclusion File, which is only available on a quarterly basis, to allow covered entities to appropriately utilize 340B purchasing for their Medicaid fee-for-service and managed programs, while still ensuring appropriate safeguards that prevent duplicate discounts. In this case, HHS appears to recognize the operational complexity in complying with these requirements and seeks information about potential processes that could be used as a federal standard.

5. New Procedures in the Auditing of Covered Entities and Contract Pharmacies

HHS intends to continue exercising its authority to audit covered entities for 340B Program compliance, especially where diversion and duplicate discounts are concerned. Manufacturers may audit covered entities as well, but only based on a proposed "reasonable cause" standard where diversion or duplicate discounts are suspected at the covered entity, its child sites or contract pharmacies. Covered entities, in turn, are expected to conduct annual audits, as well as proposed "quarterly reviews" that are more limited in scope, to ensure contract pharmacies also comply with 340B Program requirements.

HHS has proposed a new notice and hearing process for covered entities, wherein the entity will be given the opportunity to respond, in writing and within 30 days, to adverse audit findings or a proposed loss of 340B Program eligibility. HHS will subsequently issue its final determination regarding non-compliance, at which point a covered entity may be required to submit a corrective action plan. Corrective action plans must address all findings of non-compliance, and at a minimum should include the following items:

  • correction of each finding of non-compliance
  • implementation of measures to prevent future occurrence of non-compliance
  • plans to make offers of repayments to affected manufacturers, or plans to work with state Medicaid offices to correct duplicate discounts
  • a timeline for corrective actions to be taken

If HHS' final determination includes a finding that the covered entity is no longer eligible for the 340B Program, the entity must repay affected manufacturers for 340B drug purchases made after the date the entity first violates a statutory requirement, rather than a date of discovery or a date of the audit finding. We anticipate that 340B Program stakeholders will provide comments on this provision in particular, and on the other proposed program integrity measures suggested. Stakeholders should watch for final guidance to determine whether changes to their 340B compliance programs will be required. 


1. 80 Fed. Reg. 52300 (August 28, 2015).

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.

In association with
Related Video
Up-coming Events Search
Font Size:
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
Confirm Password
Mondaq Topics -- Select your Interests
 Law Performance
 Law Practice
 Media & IT
 Real Estate
 Wealth Mgt
Asia Pacific
European Union
Latin America
Middle East
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.


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.


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.


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.


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.


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.


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.