United States: Huge Stark Law Hospital Settlements And Physician Culpability - The New Normal Post-Tuomey?

After the federal government's victory against Tuomey Hospital, we have seen an increasing number of large False Claims Act (FCA) settlements with hospitals involving Stark Law allegations. Relators are even citing, as evidence of ongoing recklessness, that hospital executives have been e-mailing articles about the Tuomey case to their staff. Given the Stark Law's intricate requirements, it is un-surprising that many hospitals are presented with Stark Law compliance questions. However, the U.S. Department of Justice (DOJ) has not shown much leniency in its treatment of these cases, as shown by two recent settlements.

First, there is the settlement with Columbus Regional Healthcare System (Columbus) and Dr. Andrew Pippas to resolve two separate qui tams filed by a former Columbus executive, Richard Barker, in the Middle District of Georgia. Mr. Barker alleged both billing and Stark Law misconduct in his complaints. While the first complaint largely focused on allegations of improper evaluation and management upcoding and intensity-modulated radiation therapy billing, it also included some cursory allegations of improper physician financial relationships. The government declined to intervene in this case in 2013. In 2014, Mr. Barker filed a second qui tam alleging compensation to Dr. Pippas in excess of fair market value, determined in a manner that took into account the volume or value of his referrals, and paid pursuant to an employment agreement that would not have been commercially reasonable but for Dr. Pippas' referrals to Columbus. On September 4, Columbus entered into a FCA settlement to pay up to $35 million to resolve both cases.

The Columbus settlement contains several noteworthy characteristics:

  • While DOJ declined Mr. Barker's first qui tam, DOJ intervened in both cases at the time of settlement. This is common, but it appears that Mr. Barker's second complaint may have prompted DOJ to take a closer look at the financial relationship between Columbus and Dr. Pippas. Mr. Barker's second complaint alleged that Columbus compensation failed the Stark employment exception's fair market value, "volume or value" and commercial reasonableness tests. He alleges this because it was more than what Columbus collected from his personally performed professional services; took into account the value of his chemotherapy and other referrals to Columbus; and was based in significant part on productivity that was allegedly artificially inflated by the productivity of other practitioners and his own upcoding of patient visits.  
  • Even though the settlement resolves the allegations in both complaints, the Office of Inspector General's (OIG) corporate integrity agreements (CIA) only contains provisions for oversight of financial arrangements with physicians and no billing/claims review. This difference would seem to indicate that OIG may have maintained its view that the billing allegations were weak or very difficult to prove or quantify from a damages perspective, and thus did not merit the inclusion of remedial measures in the CIA.
  • Columbus was able to wrap conduct disclosed to the Centers for Medicare & Medicaid Service (CMS) self-referral disclosure protocol (SRDP) in October 2013 into the settlement. This strategy ensured that Columbus resolved all pending Stark Law issues with the government at once—avoiding an additional payment to CMS once it completed its review of the SRDP submission.
  • DOJ viewed Dr. Pippas culpable enough to require a separate payment from him of $425,000. Consistent with the DOJ's September 9, 2015, release of the "Yates Memorandum," this requirement is an example of the government pursuing both entities and individuals that it believes are responsible for the conduct, particularly physicians on the other side of the financial relationship.
  • The settlement payment is an example of how DOJ's financial ability-to-pay process works. Generally, if the defendant expresses an inability to pay the amount DOJ believes is appropriate to resolve the case, DOJ's financial auditors will examine the defendant's financial situation to determine the amount the defendant can afford to pay. This examination is done with an eye towards fulfilling DOJ's objective—maximizing the taxpayer's recovery—and DOJ applies very strict standards when conducting this analysis. To achieve the highest payment possible, DOJ often will seek payments over time and contingency payments along the lines of the Columbus settlement. Here, Columbus is obligated to pay at least $25 million, with $10 million upfront and $3 million per year over the next five years. In addition, Columbus may owe up to $10 million more if it meets certain net-revenue targets or sells certain assets. This structure may be an indication that DOJ was seeking more than $35 million to resolve this case, or would not agree to an amount lower than $35 million, but limited the recovery to what DOJ believed Columbus could afford to pay.

Another Stark Law qui tam settlement was unsealed on September 11, 2015, for $69.5 million with North Broward Hospital District (Broward) in the Southern District of Florida. This case alleged compensation to numerous employed physicians that did not meet the Stark employment exception. The relator alleged that the compensation was excess of fair market value and commercially un-reasonable, because it was over the 90th percentile of total cash compensation as published in physician compensation surveys, and generated substantial practice "losses" for Broward. In addition, because the physicians' compensation was not financially self-sustaining from professional income alone, but would be self-sustaining if one added the value of facility fees, which Broward tracked, the complaint argued that the compensation took into account the volume or value of referrals to Broward for hospital services. The complaint also alleged that Broward pressured physicians to limit charity care, even though Broward is a public entity, and to keep referrals in-house, even when physicians believed the patient's care needs were better served by another facility.

The FCA settlement only alleges Stark violations concerning nine physicians' compensation. The agreement does not identify with which of the relators' legal theories and factual allegations DOJ agreed. It is possible that DOJ was persuaded that the physicians were simply paid above fair market value based on their cash compensation as compared to their personal productivity. But DOJ has questioned before, the propriety of compensation that, in combination with practice overhead expenses, is in excess of collections from the physician's personally performed services. And a DOJ fair market value expert has asserted in litigation that physician arrangements, even for employed physicians, for departments that "lose" money are commercially un-reasonable while conceding that there is no statutory or regulatory basis for such an assertion. DOJ has, moreover, asserted that hospitals that tolerate practice "losses" because of the value of the employed physician's referrals to the hospital are highly suspect.

In other words, DOJ appears to advance an interpretation of the Stark Law that puts at risk vertically integrated health systems that treat a physician as a professional component cost of delivering a bundle of professional and facility/technical component services to patients and payors. Despite the fact that DOJ's expert views on fair market value, including its subjective interpretation of the results of physician compensation surveys, are rarely tested in actual litigation before a judge or a jury, DOJ does not appear to accept that there are plenty of commercially legitimate reasons for a hospital to employ a physician who may not "cover" their costs from professional fees alone, such as the payor mix of the hospital the amount of un-compensated care; other clinical and non-clinical services provided by the physician; the need for the specialty in the community; and the fact that Medicare and Medicaid rates commonly pay below costs. Additionally, a fully integrated hospital-physician system will necessarily view its finances on an integrated and not piecemeal basis.

Hospitals may view Columbus and Broward with some comfort in this respect—DOJ did not base its theory solely on the allegation that the physician compensation failed to meet the employment exception because the physician's professional fee collections did not cover their costs. In Columbus, DOJ could point to allegations of upcoding and that the compensation model encouraged upcoding, which, if true, would cause direct financial harm to the federal health care programs. In Broward, the complaint raised allegations of compromising the physician's medical judgment and the public health mission of a county hospital. This could suggest the DOJ is attempting to look for additional allegations of "bad" conduct in pursuing a FCA theory. However, the allegations were not tested in litigation, and Columbus and Broward would likely dispute the truth of those allegations. Given the general way in which the covered conduct is typically described in settlement agreements, it is difficult to determine DOJ's position.

Tuomey casts a long shadow over any hospital defending Stark Law allegations. The tremendous financial exposure under the Stark Law makes challenging DOJ's positions on physician compensation un-tenable for many hospitals. Columbus' chief executive officer explained why he settled with DOJ: he "learned from other hospitals fighting these types of lawsuits that going to trial was very risky." Arguably, this dynamic serves neither the government nor the hospital community well. Settlements do not provide clear guidance to providers on how to properly structure arrangements and neither do relator or DOJ complaints or briefs—they simply advocate a particular position in litigation. CMS, the agency responsible for interpreting the Stark Law, is largely silent in this adversarial process.

At the same time, CMS is also encouraging greater clinical integration between physicians and hospitals as a step towards payment based on quality rather than quantity. Practically, the clearest way to get physicians on board with clinical integration is for hospitals to financially integrate with (or employ) physicians. But if "losses" on a physician based solely on professional collections is going to put the hospital-employer at risk of catastrophic Stark and FCA liability, this un-certainty may delay and distort clinical integration efforts at the same time that evolving payment systems are designed to incentivize such integration. This state of affairs is not tenable over the long term.

Huge Stark Law Hospital Settlements And Physician Culpability - The New Normal Post-Tuomey?

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

Terms & Conditions and Privacy Statement

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

Use of www.mondaq.com

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

Disclaimer

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

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

Registration

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

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

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

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

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

Information Collection and Use

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

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

Mondaq News Alerts

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

Cookies

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

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

Log Files

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

Links

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

Surveys & Contests

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

Mail-A-Friend

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

Security

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

Correcting/Updating Personal Information

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

Notification of Changes

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

How to contact Mondaq

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

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