United States: A Summary And Analysis Of HRSA's Proposed 340B Program Guidance

On August 28, 2015, the US Department of Health & Human Services (HHS) Health Resources and Services Administration (HRSA) published its long-awaited, if still only proposed, 340B program guidance (Proposed Guidance). 80 Fed. Reg. 52300 (Aug. 28, 2015).

Created in 1992, the 340B program requires manufacturers to make outpatient drugs available at a substantial discount to certain, defined "covered entities." Over the past 23 years—during which time program participation has exploded to include over 11,000 health care providers and 600 drug manufacturers—the program has been intermittently regulated through the issuance of periodic notices, policy releases, and FAQs issued by HRSA (and its prime vendor, Apexus).

The net result of this informal regulation has been growing confusion on the part of both manufacturers and covered entities as to the precise contours of many of the program's most important components. The Proposed Guidance addresses most, if not all, of these issues. In many cases, the Proposed Guidance, if adopted, would simply codify the positions most recently set forth by HRSA and Apexus in the "authorities" referenced above. In other cases, however—such as the proposed definition of a patient of a covered entity—the Proposed Guidance arguably reflects a sea change.

Set forth below is a summary and analysis of some of the most significant provisions of the Proposed Guidance. Comments on the Proposed Guidance are due on or before October 27, 2015.

Patient eligibility

Patient definition

The prohibition on dispensing drugs purchased under the 340B program to individuals who are not "patients" of the covered entity has been a continual source of confusion. HRSA published a fairly cryptic "patient" definition in 1996 and then proposed (but never adopted) a substantially revised definition in 2007.

During its recent compliance audits of covered entities, HRSA "learned more about how the definition of patient is applied in different health care settings" and, based on this education, is now proposing a much more detailed—and, at least arguably, a much narrower—definition of "patient" in the Proposed Guidance. Specifically, and with a few limited exceptions, the Proposed Guidance would establish the following six-part test for determining, "on a prescription-by-prescription or order-by-order basis," whether an individual is a "patient" of a covered entity for 340B purposes:

  1. The individual receives a health care service at a covered entity site which is registered for the 340B Program and listed on the public 340B database."
  2. "The individual receives a health care service from a health care provider employed by the covered entity or who is an independent contractor of the covered entity such that the covered entity may bill for services on behalf of the provider." (According to HRSA, "[s]imply having privileges or credentials at a covered entity is not sufficient to demonstrate that an individual treated by that privileged provider is a patient of the covered entity for 340B Program purposes.")
  3. "An individual receives a drug that is ordered or prescribed by the covered entity provider as a result of the service described in (2)." "An individual will not be considered a patient of the covered entity if the only health care received by the individual from the covered entity is the infusion of a drug or the dispensing of a drug." Significantly, the "use of telemedicine, telepharmacy, remote, and other health care service arrangements ... is permitted, as long as the practice is authorized under State or Federal law and otherwise complies with the 340B Program."
  4. "The individual receives a health care service that is consistent with the covered entity's scope of grant, project, or contract."
  5. "The individual is classified as an outpatient when the drug is ordered or prescribed. The patient's classification status is determined by how the services for the patient are billed to the insurer (e.g., Medicare, Medicaid, private insurance). An individual who is self-pay, uninsured, or whose cost of care is covered by the covered entity will be considered a patient if the covered entity has clearly defined policies and procedures that it follows to classify such individuals consistently."
  6. "The individual has a relationship with the covered entity such that the covered entity maintains access to auditable health care records which demonstrate that the covered entity has a provider-to-patient relationship, that the responsibility for care is with the covered entity, and that each element of this patient definition in this section is met for each 340B drug."

The fact that the investigation is on a prescription-by-prescription basis is significant. For example, the Proposed Guidance notes that "[a]n individual who sees a physician in his or her private practice ... even as follow-up to care at a registered site, would not be eligible to receive 340B drugs for the services provided at these non-340B sites." However, if "the patient returns to the covered entity for ongoing medical care, subsequent prescriptions written by the covered entity's providers may be eligible for 340B discounts." Similarly, it appears that outpatient drugs prescribed to patients on discharge after receiving an inpatient service may not be eligible for 340B pricing. ("[A]n individual cannot be considered a patient of the entity furnishing outpatient drugs if his or her care is classified as inpatient.")

Covered entity employees

In the preamble to the Proposed Guidance, HRSA takes the opportunity to emphasize that simply because an individual is employed by a covered entity does not mean that the employee automatically qualifies as a patient of the covered entity for 340B purposes. "The 340B Program does not serve as a general employee pharmacy benefit or self-insured pharmacy benefit. ... Employees of covered entities do not become eligible to receive 340B drugs solely by being employees, but by being a patient as defined in this guidance."

This is true, moreover, even if the covered entity has sole "financial responsibility for employees' health care, and contract[s] with prescribing health care professionals loosely affiliated or unaffiliated with the covered entity." In that case, HRSA posits, the "covered entity would be acting primarily as the insurance provider for these individuals and not as the health care provider of these individuals." For 340B Program purposes, "there is a fundamental difference between the individuals for whom the covered entity provides direct health care services and meets all criteria in this section and employees for whom a covered entity only provides insurance coverage."

Handling diversion

An issue that frequently arises is how to address inadvertent drug diversion and similar errors; for example, a covered entity (1) dispenses a drug purchased at a non-340B price to an individual who is 340B-eligible, or (2) inadvertently dispenses a drug purchased at a 340B price to an individual who does not meet the program's definition of "patient" (i.e., an inpatient).

  • Under the first set of circumstances—where the economic harm of the error falls on the covered entity—HRSA notes that some covered entities "have attempted to retroactively look back over long periods of time at drug purchases not initially identified as 340B eligible" and then (1) "re-characterize[d] these purchases as 340B eligible" and (2) "purchase[d] 340B drugs on the basis of these previous transactions." While the Proposed Guidance would not prohibit this so-called "banking" practice, it does provide that if a covered entity "wishes to re-characterize a previous purchase as 340B," it "should first notify manufacturers and ensure all processes are fully transparent with a clear audit trail that reflects the actual timing and facts underlying a transaction."
  • Under the second set of circumstances—where the economic harm of the error falls on the manufacturer—HRSA states that it is "aware that manufacturers and covered entities currently work together to identify and correct errors in purchasing within 30 days of the initial purchase through a credit and rebill process" and the agency "encourages manufacturers and covered entities to continue this practice." In all events, the agency states, covered entities "are expected to work with manufacturers regarding repayment within 90 days of identifying the violation" and a "manufacturer retains discretion as to whether to request repayment based on its own business considerations. ... For example, a manufacturer may prefer not to accept payments below a de minimis amount or to process repayments owed through a credit/rebill mechanism."

Covered entity eligibility

Parents and children

A second issue that has been a source of some confusion over the years relates to where a 340B covered entity begins and ends. In the Proposed Guidance, HRSA clarifies that in the case of covered entities that are hospitals, "[a]ll off-site outpatient facilities and clinics (child sites) not located at the same physical address as the parent hospital covered entity...are able to purchase and use 340B drugs for eligible patients" as a child site, provided the hospital's most recently filed Medicare cost report demonstrates to HRSA that (1) "each of the facilities or clinics is listed on a line of the cost report that is reimbursable under Medicare," and (2) "the services provided at each of the facilities or clinics have associated outpatient Medicare costs and charges."

Impact of losing eligibility generally

HHS also clarifies that if it loses its eligibility, a "covered hospital entity must immediately notify HHS," which will then "list that date on the public 340B database as the termination date." The Proposed Guidance further clarifies that "[a]n off-site outpatient facility's eligibility to participate in the 340B Program is tied to the eligibility of the parent hospital." Thus, "[i]f a parent hospital loses eligibility to participate in the 340B Program, all registered child sites will simultaneously lose eligibility and must immediately cease purchasing and using 340B drugs."

Conversely, "[a] child site may lose eligibility separately from the parent covered entity in certain circumstances." For example, "an off-site hospital outpatient facility registered as a child site will lose 340B Program eligibility" if the parent covered entity's Medicare cost report "demonstrates the facility is no longer reimbursable or services provided at the facility no longer have associated outpatient costs and charges under Medicare."

Where a covered entity has been terminated from the 340B program, HHS proposes that the provider will be able to re-enroll in the program "during the next regular enrollment period after it has satisfactorily demonstrated to HHS that it will comply with all statutory requirements moving forward and has completed, or is in the process of offering repayment to affected manufacturers as necessary."

GPO prohibition

Where 340B program eligibility turns on compliance with the so-called group purchasing organization (GPO) prohibition, the Proposed Guidance appears to adopt a two-pronged approach:

  • If the violation is an "isolated error" (and not a "systematic violation")—terms that are not defined in the Proposed Guidance—the covered entity will not be removed from the program but will be required to submit a corrective action plan (CAP).
  • If the violation is not isolated, then (subject to certain narrow exceptions) the covered entity (or child site, if isolated to a child site) would be (1) "deemed ineligible for the 340B Program as of the date of the violation,"  (2) "immediately removed" from the program, and (3) "required to offer repayment to affected manufacturers for any 340B drug purchase made after the first date of violation of the GPO prohibition."

Notwithstanding the above, in the preamble to the Proposed Guidance, HHS also states that it is "aware that manufacturers and covered entities may currently work together to identify and correct errors in GPO purchasing within 30 days of the initial purchase through a credit and rebill process as a standard business practice." The agency further states that it "encourages manufacturers and covered entities to continue this practice." This raises several questions, most notably perhaps the following: if an error is identified and corrected within 30 days, does that moot the two-pronged approach described above?  For example, if the error at issue was isolated, does the manufacturer-covered entity cooperation moot the need for a CAP in order to remain in the program?

Duplicate discounts

Background

Another area that has been a source of some confusion over the years relates to the confluence of two government discount programs: the 340B program and the Medicaid drug rebate program (MDRP). The 340B program requires manufacturers to sell drugs dispensed to 340B-eligible patients at a substantial discount. The MDRP requires manufacturers to pay a rebate to the Medicaid program for each unit of their drugs that are dispensed to Medicaid beneficiaries. In the absence of some relief, then, where a covered entity dispensed a 340B drug to a Medicaid beneficiary, the manufacturer would be subject to two mandated price reductions on the same unit of the same drug: the (up-front) 340B discount and the (back-end) MDRP rebate.

Recognizing this, Congress required HHS to implement a system to avoid such "duplicate discounts." This system generally works as follows:

  • If a covered entity wishes to dispense 340B drugs to Medicaid patients—a "carve-in" entity for 340B program purposes—then the entity must notify HHS of this fact and provide its NPI and/or Medicaid billing numbers to the agency. These numbers then get included in HRSA's 340B program "Exclusion File." If Covered Entity X is "carve-in" and has included its NPI and/or Medicaid billing number in the Exclusion File, state Medicaid agencies will not seek MDRP rebates from manufacturers on drugs dispensed by the covered entity to Medicaid beneficiaries (because the manufacturers already will have sold those drugs to Covered Entity X at the (discounted) 340B price).
  • If a covered entity does not wish to dispense 340B drugs to Medicaid patients—a "carve-out" entity for 340B program purposes—then, once again, the entity must notify HHS of this fact. The covered entity's NPI and Medicaid billing numbers will not be included in Exclusion File. If Covered Entity Y is "carve-out" and neither its NPI nor Medicaid billing number has been included in the Exclusion Database, state Medicaid agencies will seek MDRP rebates from manufacturers on drugs dispensed by the covered entity to Medicaid beneficiaries (because the manufacturers will not have sold those drugs to Covered Entity Y at the (discounted) 340B price).

Note that some States require covered entities to select one option or the other.

Fee for service v. managed care

In the Proposed Guidance, HHS states that whereas a covered entity must be either carve-in or carve-out with respect to its Medicaid fee for service (FFS) patients, it "may make a different determination regarding carve-in or carve-out status for MCO [managed care organization] patients ... by covered entity site and by MCO," as long as the covered entity provides HRSA with the "identifying information of the covered entity site, the associated MCO, and the decision to carve-in or carve-out." That information will then "be made available on a 340B Medicaid Exclusion [F]ile."

HHS cautions, however, that "[w]hile the proposed use of a 340B Medicaid Exclusion File would identify the covered entity billing practices used for MCO patients, HHS encourages covered entities, States, and Medicaid MCOs to work together to establish a process to identify 340B claims." For example, covered entities "should have mechanisms in place to be able to identify MCO patients." Further, covered entities and states "should continue to work together on various methods to prevent duplicate discounts on Medicaid MCO drugs.

Currently, covered entities report using Bank Identification Numbers, Processor Control Numbers, and National Council for Prescription Drug Programs (NCPDP) codes, among other methods, to identify Medicaid MCO patients and 340B claims. In some cases, States may require covered entities to follow additional steps to prevent duplicate discounts, including use of certain modifiers and codes which identify individual claims as associated with 340B drugs and therefore not eligible for rebate. Such billing instructions are beyond the scope of the 340B Program.

Contract pharmacies

The government has had a longstanding concern about the risk of double discounting in the contract pharmacy setting. "Due to these heightened risks of duplicate discounts," the Proposed Guidance provides that "when a contract pharmacy is listed on the public 340B database it will be presumed that the contract pharmacy will not dispense 340B drugs to Medicaid FFS or MCO patients."

If a covered entity wishes to dispense 340B drugs to its Medicaid FFS or MCO patients through a contract pharmacy, the covered entity will have to "provide HHS a written agreement with its contract pharmacy and State Medicaid agency or MCO that describes a system to prevent duplicate discounts." Once approved, "HHS will list on the public 340B database a contract pharmacy as dispensing 340B drugs for Medicaid FFS and/or MCO patients."

Contract pharmacy arrangements

In addition to addressing contract pharmacies in the context of the duplicate discount issue, the Proposed Guidance also addressed contract pharmacy arrangements more generally. According to HHS, through its audits of covered entity/contract pharmacy arrangements, the agency "has observed that not all covered entities have sufficient mechanisms in place to ensure their contract pharmacies' compliance with all 340B Program requirements." To address this issue, the Proposed Guidance provides that (1) each covered entity is "expected to conduct quarterly reviews and annual independent audits of each contract pharmacy location," and (2) "[a]ny 340B Program violation detected through quarterly reviews or annual audits of a contract pharmacy should be disclosed to HHS."

Program integrity

HRSA audits of covered entities

  • For several years now, HRSA has been conducting audits of covered entities. In the Proposed Guidance, the agency proposes the adoption of a "notice and hearing" process pursuant to which a covered entity will have "the opportunity to respond to adverse audit findings and other instances of noncompliance or to respond to the proposed loss of 340B Program eligibility." This process would be "conducted based on the written submissions of the involved parties." More specifically:
  • HHS would "initiate the notice and hearing process by providing written notice to a covered entity of a proposed finding of noncompliance with specific 340B Program requirements."
  • The covered entity would then have 30 days to respond "in writing to each issue of noncompliance, providing details and documentation where appropriate."
  • After reviewing "all documents and information submitted by the covered entity," HHS will issue "a final written notice with its final determination regarding noncompliance."
  • If HHS's final determination of noncompliance "includes a finding that the covered entity is no longer eligible for the 340B Program," the covered entity will be removed from the 340B Program" and the entity will be responsible "for repayment to affected manufacturers for 340B drug purchases made after the date the entity first violated a statutory requirement."
  • If the agency's final determination of noncompliance does not relate to program eligibility, "the covered entity may have to submit a [CAP]." If the CAP "addresses all findings of noncompliance, HHS may determine that the covered entity can continue to participate in the 340B Program."

Manufacturer audits of covered entities

By statute, a drug manufacturer participating in the 340B program also is authorized to audit a covered entity's compliance with the statutory prohibitions against duplicate discounts and diversion (but not program eligibility). HHS proposes a "reasonable cause" standard, pursuant to which a manufacturer, prior to initiating an audit, would have to document "to HHS's satisfaction that a reasonable person could conclude, based on reliable evidence, that a covered entity, its child sites, or contract pharmacies may have violated" the diversion or duplicate discount prohibitions. According to the agency, "reasonable cause" would include, by way of example only:

  • "Significant changes in quantities of specific drugs ordered by a covered entity without adequate explanation by the covered entity"
  • "Significant deviations from national averages of inpatient or outpatient use of certain drugs without adequate explanation by the covered entity"
  • "Evidence of duplicate discounts provided by manufacturers or State Medicaid agencies"
  • At least under some circumstances, a "covered entity's refusal to respond to manufacturer questions related to 340B drug diversion and duplicate discounts"

Under the Proposed Guidance, a manufacturer would be required to "submit an audit work plan for HHS approval" prior to conducting an audit. HHS would then "review the reasonable cause documentation and the scope of the audit work plan" and "may limit the scope of the audit to ensure that the audit is conducted with the least possible disruption to the covered entity."

If approved, the audit would have to: (1) be undertaken by an independent certified public accountant, (2) be performed "in accordance with Government Auditing Standards," (3) protect the confidentiality of patient information, (4) cover a period of no more than one year, and (5) be paid for by the manufacturer. Following completion of the audit, the auditors would be required to prepare a final audit report and submit it to HHS.

HRSA audit of manufacturers

By statute, HHS is authorized to audit a manufacturer or wholesaler to ensure 340B program compliance. The Proposed Guidance provides that these audits "may include either an on-site review, an off-site review of documentation requested by HHS, or both." Following the audit, "if HHS determines that a manufacturer has violated the 340B Program, the manufacturer will be provided opportunity for notice and hearing." Specifically, HHS will "send the manufacturer written notification of any audit findings and will notify the manufacturer of the deadline to respond with its agreement or disagreement with each proposed finding." If a manufacturer disagrees with an HHS finding, the agency will "review any documentation submitted" by the manufacturer, make a final determination, advise the manufacturer, and "request corrective action, as needed."

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
Events from this Firm
26 Sep 2018, Conference, New York, United States

Dentons is delighted to support a global IT services and consulting firm Miratech as an event host partner at their annual conference called M-Force18 New York on September 27th. The event will be held at Dentons New York office in the heart of Midtown Manhattan, opposite Rockefeller Center.

2 Oct 2018, Seminar, Dallas, United States

We are pleased to offer a program of five sessions designed specifically for in-house counsel. Topics will include:

  • In-house corporate ethical issues
  • What recent Supreme Court decisions mean for business
  • Keeping lawyers out of your benefit plans
  • Litigation tactics for in-house counsel
  • Employment issues in the age of #MeToo
Similar Articles
Relevancy Powered by MondaqAI
Ostrow Reisin Berk & Abrams
 
In association with
Related Topics
 
Similar Articles
Relevancy Powered by MondaqAI
Ostrow Reisin Berk & Abrams
Related Articles
 
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
Registration (you must scroll down to set your data preferences)

Mondaq Ltd requires you to register and provide information that personally identifies you, including your content preferences, for three primary purposes (full details of Mondaq’s use of your personal data can be found in our Privacy and Cookies Notice):

  • To allow you to personalize the Mondaq websites you are visiting to show content ("Content") relevant to your interests.
  • To enable features such as password reminder, news alerts, email a colleague, and linking from Mondaq (and its affiliate sites) to your website.
  • To produce demographic feedback for our content providers ("Contributors") who contribute Content for free for your use.

Mondaq hopes that our registered users will support us in maintaining our free to view business model by consenting to our use of your personal data as described below.

Mondaq has a "free to view" business model. Our services are paid for by Contributors in exchange for Mondaq providing them with access to information about who accesses their content. Once personal data is transferred to our Contributors they become a data controller of this personal data. They use it to measure the response that their articles are receiving, as a form of market research. They may also use it to provide Mondaq users with information about their products and services.

Details of each Contributor to which your personal data will be transferred is clearly stated within the Content that you access. For full details of how this Contributor will use your personal data, you should review the Contributor’s own Privacy Notice.

Please indicate your preference below:

Yes, I am happy to support Mondaq in maintaining its free to view business model by agreeing to allow Mondaq to share my personal data with Contributors whose Content I access
No, I do not want Mondaq to share my personal data with Contributors

Also please let us know whether you are happy to receive communications promoting products and services offered by Mondaq:

Yes, I am happy to received promotional communications from Mondaq
No, please do not send me promotional communications from Mondaq
Terms & Conditions

Mondaq.com (the Website) is owned and managed by Mondaq Ltd (Mondaq). Mondaq grants you a non-exclusive, revocable licence to access the Website and associated services, such as the Mondaq News Alerts (Services), subject to and in consideration of your compliance with the following terms and conditions of use (Terms). Your use of the Website and/or Services constitutes your agreement to the Terms. Mondaq may terminate your use of the Website and Services if you are in breach of these Terms or if Mondaq decides to terminate the licence granted hereunder for any reason whatsoever.

Use of www.mondaq.com

To Use Mondaq.com you must be: eighteen (18) years old or over; legally capable of entering into binding contracts; and not in any way prohibited by the applicable law to enter into these Terms in the jurisdiction which you are currently located.

You may use the Website as an unregistered user, however, you are required to register as a user if you wish to read the full text of the Content or to receive the Services.

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 or with the prior written consent of Mondaq. You may not use electronic or other means to extract details or information from the Content. Nor shall you extract information about users or Contributors in order to offer them any services or products.

In your use of the Website and/or Services you shall: comply with all applicable laws, regulations, directives and legislations which apply to your Use of the Website and/or Services in whatever country you are physically located including without limitation any and all consumer law, export control laws and regulations; provide to us true, correct and accurate information and promptly inform us in the event that any information that you have provided to us changes or becomes inaccurate; notify Mondaq immediately of any circumstances where you have reason to believe that any Intellectual Property Rights or any other rights of any third party may have been infringed; co-operate with reasonable security or other checks or requests for information made by Mondaq from time to time; and at all times be fully liable for the breach of any of these Terms by a third party using your login details to access the Website and/or Services

however, you shall not: do anything likely to impair, interfere with or damage or cause harm or distress to any persons, or the network; do anything that will infringe any Intellectual Property Rights or other rights of Mondaq or any third party; or use the Website, Services and/or Content otherwise than in accordance with these Terms; use any trade marks or service marks of Mondaq or the Contributors, or do anything which may be seen to take unfair advantage of the reputation and goodwill of Mondaq or the Contributors, or the Website, Services and/or Content.

Mondaq reserves the right, in its sole discretion, to take any action that it deems necessary and appropriate in the event it considers that there is a breach or threatened breach of the Terms.

Mondaq’s Rights and Obligations

Unless otherwise expressly set out to the contrary, nothing in these Terms shall serve to transfer from Mondaq to you, any Intellectual Property Rights owned by and/or licensed to Mondaq and all rights, title and interest in and to such Intellectual Property Rights will remain exclusively with Mondaq and/or its licensors.

Mondaq shall use its reasonable endeavours to make the Website and Services available to you at all times, but we cannot guarantee an uninterrupted and fault free service.

Mondaq reserves the right to make changes to the services and/or the Website or part thereof, from time to time, and we may add, remove, modify and/or vary any elements of features and functionalities of the Website or the services.

Mondaq also reserves the right from time to time to monitor your Use of the Website and/or services.

Disclaimer

The Content is general information only. It is not intended to constitute legal advice or seek to be the complete and comprehensive statement of the law, nor is it intended to address your specific requirements or provide advice on which reliance should be placed. Mondaq and/or its Contributors and other suppliers make no representations about the suitability of the information contained in the Content for any purpose. All Content provided "as is" without warranty of any kind. Mondaq and/or its Contributors and other suppliers hereby exclude and disclaim all representations, warranties or guarantees with regard to the Content, including all implied warranties and conditions of merchantability, fitness for a particular purpose, title and non-infringement. To the maximum extent permitted by law, Mondaq expressly excludes all representations, warranties, obligations, and liabilities arising out of or in connection with all Content. In no event shall Mondaq 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 of the Content or performance of Mondaq’s Services.

General

Mondaq may alter or amend these Terms by amending them on the Website. By continuing to Use the Services and/or the Website after such amendment, you will be deemed to have accepted any amendment to these Terms.

These Terms shall be governed by and construed in accordance with the laws of England and Wales and you irrevocably submit to the exclusive jurisdiction of the courts of England and Wales to settle any dispute which may arise out of or in connection with these Terms. If you live outside the United Kingdom, English law shall apply only to the extent that English law shall not deprive you of any legal protection accorded in accordance with the law of the place where you are habitually resident ("Local Law"). In the event English law deprives you of any legal protection which is accorded to you under Local Law, then these terms shall be governed by Local Law and any dispute or claim arising out of or in connection with these Terms shall be subject to the non-exclusive jurisdiction of the courts where you are habitually resident.

You may print and keep a copy of these Terms, which form the entire agreement between you and Mondaq and supersede any other communications or advertising in respect of the Service and/or the Website.

No delay in exercising or non-exercise by you and/or Mondaq of any of its rights under or in connection with these Terms shall operate as a waiver or release of each of your or Mondaq’s right. Rather, any such waiver or release must be specifically granted in writing signed by the party granting it.

If any part of these Terms is held unenforceable, that part shall be enforced to the maximum extent permissible so as to give effect to the intent of the parties, and the Terms shall continue in full force and effect.

Mondaq shall not incur any liability to you on account of any loss or damage resulting from any delay or failure to perform all or any part of these Terms if such delay or failure is caused, in whole or in part, by events, occurrences, or causes beyond the control of Mondaq. Such events, occurrences or causes will include, without limitation, acts of God, strikes, lockouts, server and network failure, riots, acts of war, earthquakes, fire and explosions.

By clicking Register you state you have read and agree to our Terms and Conditions