Auditing a Compliance Hotline Provider

Compliance Hotline Auditing

Under the Affordable Care Act, medical service providers must establish compliance programs to enroll in the Federal health care programs. HHS has neither issued regulations on the core requirements of these compliance plans nor set a date for mandatory compliance. Providers, however, should consider adopting a compliance hotline program prior to the mandate not only because a requirement is imminent, but also to prevent fraud and demonstrate good faith.

Elements of an Effective Compliance Program

One of the seven elements of an effective compliance program is developing open lines of communication. CMS recommends that lines of communication run in multiple directions and include a process for anonymous reporting to provide an outlet for employees who may fear retaliation.

Many providers utilize an outside vendor to facilitate anonymous reporting. If you elect to use an outside vendor, you should choose a well-managed hotline that is focused on the health care sector. In addition, your organization should periodically audit the hotline to measure its effectiveness.

Considerations of a Compliance Hotline Auditing

When auditing a compliance hotline vendor you should consider (a) does the hotline have established policies and procedures, (b) how is the hotline managed, and (c) does the hotline meet its goals.

Some questions you might use to review the hotline’s management, operation, and effectiveness include:

  1. Does the hotline follow its established policies and procedures?
  2. Do the policies discuss how to document and follow-up calls?
  3. Does the hotline act on calls and/or emails promptly?
  4. Does the hotline follow up with callers who provide contact information?
  5. Are hotline administrators properly trained to answer calls and ask appropriate questions?
  6. Does your department tasked with reviewing hotline reports receive reports in a timely manner?
  7. Are the reports provided by the hotline detailed enough to allow your organization to follow up and investigate?
  8. Is caller anonymity being protected?
  9. Are hotline files protected?

In addition, you should also evaluate your office’s internal use of the hotline by considering the questions below.

  1. Are employees aware and reminded that the hotline is available?
  2. Does the department tasked with handling reports follow up properly?
  3. Are your employees using the hotline?
  4. Do employees seem confident about the effectiveness of the hotline?
  5. Does the department handling hotline reports file and protect reports appropriately?

If you answered “no,” to one or more of these questions, it may be time to consider a new vendor. Call Exclusion Screening, LLC today to discuss our ComplianceHotline, which is staffed by Certified Medical Compliance Officers, today at 1-800-294-0952.

Compliance Hotline Auditing

Ashley Hudson, Associate Attorney at Liles Parker, LLP and former Chief Operating Officer for Exclusion Screening, LLC, is the author of this article.

Pennsylvania Judge Holds that CIA violations May Result in FCA Liability

OIG

 

In late July, a federal district court in Pennsylvania joined in the flurry of False Claims Act (FCA) decisions. These decisions further interpreted the ACA’s amendments to the law. The court in United States ex rel. Boise v. Cephalon, Inc. considered two important issues. The issues regarded when a party has an obligation to pay the government, and when a failure to do so could result in reverse false claims liability. Providers should be on high alert and ensure that they are in compliance with all requirements. This includes the requirement to screen employees monthly in order to avoid being OIG’s next false claims target.

Background

The defendant in Cephalon failed to comply with its Corporate Integrity Agreement (CIA) and OIG sought repayment. OIG alleged that they failed to comply with the CIA, which caused reverse false claims and produced FCA liability.

Cephalon, a drug manufacturer, argued that it could have only had an obligation to pay penalties under the CIA if HHS-OIG actually demanded payment. The relator argued that Cephalon’s obligation to pay actually arose when it breached the CIA’s reporting requirements. The court disagreed with Cephalon and instead held for the relator. The court found that a CIA imposes contractual obligations through reporting requirements. Furthermore, a breach of these contractual obligations could cause a company to be liable for reverse false claims even if OIG had not yet demanded payment. Finally, the court elaborated that “specific contract remedies” like specific penalties create a “less contingent obligation to pay.”

Takeaways

The federal government is taking advantage of the new false claims recoupment tools made available to it through the ACA. If you are not screening your employees and contractors against state and federal exclusion lists, then now is the time to ensure your practice is complying with the law. Call Exclusion Screening, LLC for a free assessment of your needs and costs at 1-800- 294-0952 or fill out the form below.



 

Ashley Hudson

Ashley Hudson, Associate Attorney at Liles Parker, LLP and former Chief Operating Officer for Exclusion Screening, LLC, is the author of this article.

Southern District of New York Provides Clarity on “Identifying” Overpayments

false claims act

In early August of 2015, the Southern District of New York (SDNY) provided insight as to when the 60-day clock for returning an overpayment begins to run under the Patient Protection and Affordable Care Act of 2010 (ACA). This decision is particularly relevant to screening for exclusions because the government has started to penalize providers who submit claims for services provided directly or indirectly by an excluded individual or entity for the greater penalty of submitting a false claim. Simply stated, the government now views claims as legally false if an excluded person provided any part of that claim. This makes providers possibly liable pursuant to the false claims act.

The court’s additional clarity on when the 60-day clock begins to run for false claims act liability may be the OIG’s next tool in retrieving Federal dollars from those providers who fail to screen their employees or contractors monthly. Therefore, those providers could be in receipt of overpayments for monies received from services provided by excluded persons or entities.

I. Background – False Claims Act

The Fraud Enforcement and Recovery Act (FERA), enacted in 2009, amended the False Claims Act and added a “reverse false claims” provision. This reverse false claims provision imposes liability of $5,500 to $11,000 per false claim[1] on persons who “knowingly and improperly avoid[] or decrease[] an obligation to pay or transmit money or property to the Government.”[2] The term “knowingly” includes persons who have “actual knowledge of the information,” as well as those who “act in deliberate ignorance” or in “reckless disregard of the truth or falsity of the information.” The term “require[s] no proof of specific intent to defraud.”[3] In addition, FERA further clarified that an “obligation means an established duty, whether or not fixed, arising from an express or implied contractual, grantor-grantee, or licensor-licensee relationship, from a fee-based or similar relationship, from statute or regulation, or from the retention of any overpayment.”[4]

The ACA added additional clarification to the overpayment retention provision. Specifically, it required that a person who has received an overpayment must  “report[] and return[]” the overpayment “by the later of (A) the date which is 60 days after the date on which the overpayment was identified; or (B) the date any corresponding cost report is due, if applicable.” An overpayment is defined as any monies “received or retained” under Medicare or Medicaid to which a person is not entitled.[5] Failure to repay an overpayment by the 60-day deadline constitutes a reverse false claim under the False Claims Act. However, Congress failed to define “identified” in the statute, which caused ambiguity about when the 60-day clock begins to run.

II. United States ex rel. Kane v. Healthfirst, Inc., et al.

The United States ex rel. Kane v. Healthfirst, Inc., et al., case arose after relator Robert Kane, a former Continuum employee, conducted an internal investigation of the company. The investigation revealed that 900 specific claims amounting to over $1 million may have been wrongly submitted and paid by Medicaid as a secondary payor.[6]

According to the Complaint, Continuum was questioned about a “small number of claims” that the Comptroller’s office concluded were improperly submitted for Medicaid reimbursement.[7] After several conversations, the parties discovered that the problem was related to a software glitch that caused certain claims to contain a code which automatically referred the claim for additional payment for covered services. Continuum was sent a corrective software patch by the software vendor that would ensure that Continuum would not improperly bill any other secondary payors.[8]

Once the software problem was identified in December 2010, Continuum asked Kane to determine which claims were improperly submitted due to the software malfunction.[9] After reviewing the claims, Kane sent an email containing a spreadsheet identifying over 900 claims dating back to May 2009 and totaling more than $1 million. All of these claims contained the problematic code that caused the billing error to Continuum’s Vice President for Patient Financial Services, Continuum’s Assistant Vice President for Revenue Cycle Operations- Systems, and other Continuum management. Kane’s email stated that further scrutiny was necessary to confirm his findings, but the Defendants alleged that he had identified a large portion of the claims that were incorrectly billed. Kane was fired four days after sending this email. According to the Complaint, Continuum did nothing with the alleged overpayments Kane identified except for reimbursing five of the 900 erroneously submitted claims.[10]

The Comptroller, however, continued to review Continuum’s billing and found more claims which it promptly brought to Continuum’s attention from March 2011 through February 2012.[11] Continuum reimbursed the claims identified by the Comptroller beginning in April 2013 until March 2013. Continuum never brought Kane’s research to the Comptroller’s attention and only repaid around 300 claims after the Government issued a Civil Investigative Demand in June 2012. Due to its “intentional and reckless”[12] delay in repaying the alleged overpayment more than 60 days after they were identified, the Government, through Relator Kane, alleged that Continuum is liable for reverse false claims. Therefore, Continuum was allegedly liable for treble damages plus an $11,000 penalty for each overpayment illegally retained more than 60 days after identification.[13]

III. SDNY Court Defines “Identifying” Overpayments

Continuum responded to these allegations by filing a Motion to Dismiss arguing that Kane’s email merely “provided notice of potential overpayments and did not identify actual overpayments so as to trigger the ACA’s sixty-day report and return clock.”[14] The term “identified” was left undefined by Congress in the text of the ACA, which gave rise to Continuum’s motion.

In its motion, Continuum contended that the court should adopt a definition of “identified” as “classified with certainty.” The Government responded that instead “an entity ‘has identified an overpayment’ when it ‘has determined, or should have determined through the exercise of reasonable diligence, that [it] has received an overpayment.’” The Government’s definition would essentially define “identified” as when “a person is put on notice that a certain claim may have been overpaid.”[15]

In an effort to ascertain the plain meaning of “identify,” the court consulted dictionary definitions, but it found that the wide range of definitions alone were not particularly helpful. Next, the court utilized canons of construction, reviewed the ACA’s legislative history, and considered the legislative purpose behind including a mandate to return overpayments within the ACA. The court found the legislative history particularly revealing and noted that Congress chose to adopt the Senate’s version of the bill which contained “identified” instead of the House Bill which employed the term “known.” After a thorough evaluation, the court concluded that “identified” should be defined as the moment “when a provider is put on notice of a potential overpayment, rather than when an overpayment is conclusively ascertained, [which] is compatible with the legislative history of the False Claims Act and FERA.”[16]

The court tempered its decision in stating that “the mere existence of an ‘obligation’ does not establish a violation of the False Claims Act.” Instead, the court held that a reverse false claim is only triggered when “an obligation is knowingly concealed or knowingly and improperly avoided or decreased.” Therefore, the court advised that prosecutorial discretion be employed to avoid filing enforcement actions against “well-intentioned providers working with reasonable haste to address overpayments” because this would be “inconsistent with the spirit of the law.”

IV. Takeaways

This decision is significant because it is the first opinion interpreting the term “identify” as it is used in relation to the ACA’s 60-day overpayment reporting requirement. While it is only binding in the Southern District of New York, it will likely guide other court opinions as they arise.

Providers should be aware that they could be liable for overpayments 60 days after they are “put on notice of a potential overpayment.” Therefore, providers should act with “reasonable haste” in reviewing potential overpayments to demonstrate good faith compliance.

Finally, providers must continue to screen their employees and contractors against the Federal and state exclusion lists monthly. The Government has only recently begun to pursue excluded individuals for False Claims Act violations. The new interpretation of “identify” as being “on notice” could provide the Government with a brand new tactic to retrieve federal monies. One of the reasons we strongly advocate that providers check all federal and state exclusion lists monthly is to find potential exclusions and demonstrate maximum compliance before an exclusion problem arises.

V. Conclusion

Failing to screen thoroughly and verify potential matches each month is not a way to avoid liability. It is unlikely that OIG would excuse overpayment liability if a provider claimed he was not “on notice” about an employee’s excluded status if that provider failed to properly screen and verify employees. Further, if a provider has identified a potential match, then he must work diligently to verify this match and return any monies received for services provided by this employee if he is excluded because the initial identification date could potentially start the 60-day clock for false claims act liability. [17]

Are you taking the necessary precautions to ensure you are not working with an excluded entity? We know it can be difficult to screen every Federal and State exclusion list. Call Exclusion Screening at 1-800-294-0952 or fill out the form below to hear about our cost-effective solution and for a free quote and assessment of your needs.



 

Ashley Hudson

Ashley Hudson, Associate Attorney at Liles Parker, LLP and former Chief Operating Officer for Exclusion Screening, LLC, is the author of this article. Feel free to contact us at 1-800-294-0952 or online for a free consultation.


[1] Opinion and Order at 9 n.12, United States ex rel. Kane v. Healthfirst, Inc., et al., No. 11-2325 (S.D.N.Y Aug. 3, 2015).

[2] 31 U.S.C. § 3729(a)(1)(G) (2011).

[3] Id. § 3729(b)(1).

[4] Id. § 3729(b)(3) (emphasis added).

[5] 42 U.S.C. § 1320a-7k(d)(4)(B) (2010).

[6] Complaint-in-Intervention of the United States of America at 11, United States ex rel. Kane v. Healthfirst, Inc., et al., No. 11-2325 (S.D.N.Y. June 27, 2014).

[7] Id. at 10.

[8] Id.

[9] Id.at 11.

[10] Id.

[11] Id.

[12] Opinion and Order at 11, United States ex rel. Kane v. Healthfirst, Inc., et al., No. 11-2325 (S.D.N.Y Aug. 3, 2015).

[13] Id. at 8.

[14] Id. at 17.

[15] Id.  (emphasis added).

[16] Id. at 23.

[17] Exclusion Screening, LLC is not a law firm and does not provide legal advice. As such, this is not intended, and should not be taken, as legal advice. We strongly recommend that you seek the advice of counsel whenever decisions that may have legal consequences are made.

Medicaid Providers That Are Excluded or Terminated for Cause Often Continue to Participate in Other States According to a New OIG Audit

 

medicaid providersOIG Audit Findings

In a recently released audit, the OIG found that despite the ACA requirement that states terminate Medicaid providers already terminated in another state, 12% of providers already terminated for cause in 2011 in one state (295 out of a sample of 2,539) were still participating in other state Medicaid programs as of January of 2014! There is a lack of state to state coordination identified in both this audit and one issued last March, and a lack of state to Federal coordination identified in separate OIG audit reports. This strongly reinforces our suggestion that providers screen their employees, vendors and contractors on all available State Exclusion Registries in addition to the LEIE and the SAM!

Exclusion, Termination and the ACA

In practical terms, to implement section 6501 of the ACA, states must first find the providers who are terminated from federal healthcare programs. Then, states must identify whether any terminated providers are participating in their Medicaid program. Finally, they must take action to terminate the provider from its own Medicaid program.

According to the report, this is defeated by a general lack of coordination caused in large part by a lack of uniformity of terminology among not only the states, but in existing Federal and state databases. For instance, exclusion and termination are synonymous in many states, but they have distinctly different meanings for CMS. This is also true with such terms as suspension, disbarment, revocation and sanction. Furthermore, what constitutes “cause” in one state may not in another state. The audit also notes that some states have a basic misunderstanding about the relationship between licensure and exclusion or termination. Those states often conclude that if Medicaid providers have an active license from the relevant state board, the state Medicaid agency should defer to the judgment of that board and not terminate the providers for cause.

Principle OIG Recommendations

The OIG reiterated its recommendation from March 2014 that CMS require state Medicaid agencies to report all terminations for cause. The OIG found that a lack of a comprehensive data source of providers terminated for cause creates a challenge for state Medicaid agencies. It also recommended that CMS work with states to develop a uniform terminology, that CMS furnish guidance to state agencies that termination is not contingent on the provider’s active licensure status, and that it require states to enroll providers who participate in their managed care programs.

The Message to Medicaid Providers

This audit report stresses, once again, the importance of screening all state Exclusion databases as well as the LEIE and the SAM. This message reinforces two important ideas: 1) States do not reliably share their information either with other states or with the Feds; and 2) a significant percentage of excluded or terminated physicians, nurses and other employees will take advantage of this lack of coordination to their advantage and your disadvantage!

 

Are you taking the necessary precautions to ensure you are not working with an excluded entity? We know it can be difficult to screen every Federal and State exclusion list. Call Exclusion Screening at 1-800-294-0952 or fill out the form below to hear about our cost-effective solution and for a free quote and assessment of your needs.



OIG Exclusion

Paul Weidenfeld, Co-Founder and CEO of Exclusion Screening, LLC, is the author of this article. He is a longtime health care lawyer whose practice has focused on False Claims Act cases and health care fraud matters generally. Contact Paul should you have any  questions at: pweidenfeld@exclusionscreening.com or 1-800-294-0952.