Skip to main content

2016 Medicaid Crossover Study

The AAA is pleased to announce the release of its Medicaid Crossover Survey 2016. A companion to its recently released 2016 Medicaid Rate Survey, the 2016 Medicaid Crossover Survey focuses on each state’s treatment of Medicare crossover amounts (i.e., copayment’s and deductibles).

The survey notes whether a state will pay the full crossover amount, will make a payment only to the extent Medicare’s payment was less than the amount Medicaid would have paid as a primary, or will not make a payment under any circumstances.

We hope members will find this tool useful in comparing their state’s Medicaid reimbursement to neighboring states, and hope it will assist in their efforts to ensure fair and equitable compensation for their services.

The AAA also wants to thank all members that participated in the survey. Without your help, these sort of projects would be impossible.

AAA 2016 State Medicaid Ambulance Rate Survey Results Released

Normally this blog focuses on an area of Medicare reimbursement or compliance.  However, this month I want to talk about Medicare’s companion program, Medicaid.

When you talk to ambulance providers around the country about their State’s Medicaid Program, a universal truth emerges: no one believes their Medicaid Program fairly reimburses them for their services.  This statement is not particularly controversial.  The Government Accountability Office has on several occasions looked at the relationship between our industry’s costs and Medicare’s payment, and has consistently determined that Medicare fails to adequately reimburse us for our costs.  Given that Medicaid payments are usually some fraction of what Medicare pays, there is really no debate that our industry loses money transporting Medicaid patients.

What I find more interesting is the sheer number of people that are convinced – – and I mean absolutely convinced – – that their state has the lowest Medicaid rates in the country.  Call it a reverse Lake Wobegon effect.  Of course, not everyone can be right.  Only one state can have the lowest ambulance rates (answer below).  Conversely, only one state can hold the honor of having the highest rates.  But how to settle these questions?

Well, the AAA has the answer.  On behalf of the AAA, I am pleased to announce the release of the American Ambulance Association’s 2016 State Medicaid Rate Survey.  This survey sets forth the fee-for-service Medicaid rates for all 50 states.  For each state, the Survey lists the rate paid for each of the following procedure codes:

  • A0428 – BLS Non-Emergency
  • A0429 – BLS Emergency
  • A0426 – ALS Non-Emergency
  • A0427 – ALS Emergency
  • A0433 – ALS-2
  • A0434 – SCT
  • A0225 – Neonate Transport
  • A0998 – Treatment, No Transport
  • A0425 – Mileage
  • A0422 – Oxygen
  • A0382/A0398 – BLS/ALS Routine Disposable Supplies
  • A0420 – Wait Time
  • A0424 – Extra Attendant

While I can promise that we have taken steps to verify the information on this Survey, neither the AAA nor myself can guarantee its accuracy.  The rates set out in this survey are based on publicly available information provided by the various State Medicaid agencies, and may not reflect changes to a state’s reimbursement policy that have not been made publicly available.  They will also reflect any emergency budgetary measures or other temporary reductions imposed by a state.  That said, our goal is to make this as accurate as possible.  Therefore, if you believe the rates for your state are inaccurate, I would ask you to please email me at bwerfel@aol.com, and to provide me with updated information.

I can feel some of you thinking at this point: “This is all fine and good, but how does this actually help me?”  Fair question.  At a minimum, it will probably make some of you feel better that your state is not actually the lowest.  Others may be fairly surprised to find that their state, which they believed to be at or near the bottom, is actually closer to the middle of the road.  Many of your states are expanding their managed Medicaid programs, and you find yourself trying to determine whether it makes sense to contract with the MCO (or its transportation broker).  Many of these transportation brokers service multiple states, and may be offering rates based on their rates offered by the State Medicaid agency in the state in which they are headquartered (I know it will come as a shock that many of the new MCOs seem unaware that coverage rules differ in each state).  We are also aware of instances in which a state association has used past rate surveys as part of a comprehensive strategy to lobby their state legislature for a rate increase, e.g., by demonstrating that the current rates paid by the state are far lower than the rates paid in neighboring states.

Regardless of whether (or how) you intend to use this Survey, I encourage all AAA members to check it out.

Answer: New Jersey has the lowest payment for both emergency and non-emergency transport, at a listed rate of $58.00, plus $1.50 per mile (for the first 15 miles, $2.00 for each mile thereafter).  For sake of comparison, a taxi from Newark Airport to midtown Manhattan (a distance of 17 miles) will typically run around $70.00 (plus tip).

 


Have an issue you would like to see discussed in a future Talking Medicare blog? Submit a question today!

 

 

AAA Launches Medicare Audit Activity Survey

In an effort to better determine a pattern of Medicare audit issues facing our members, the AAA has launched a survey to identify the different types of audit activity. The AAA will use the survey to inform federal policymakers about problems identified with the audits and how best to address the issues to reduce the burden of the audits on AAA members. It is therefore critical that you complete the survey to help us determine what audit issues your operation is facing.

Start Survey

The survey is comprised of only 14 questions including contact, demographic and characteristic information about your organization and requests data about your claim denial and audit activity. The information will be kept confidential and privileged and will only be reported in the aggregate with no organization identifying information. Contact information will be used only to follow up should we have any questions.

Should you have any questions regarding the survey, please contact AAA Senior Vice President of Government Affairs Tristan North at tnorth@ambulance.org.

Thank you in advance for completing this important survey.

MedPAC Issues June 2016 Report to the Congress

MedPAC Issues June 2016 Report to the Congress with Chapter on Improving Efficiency and Preserving Access to Emergency Care in Rural Areas

Medicare Payment Advisory Commission (MedPAC or the Commission) has issued its June 2016 Report to the Congress.   The June report includes recommended refinements to Medicare payment systems and identifies issues affecting the Medicare program, broader changes in health care delivery, and the market for health care services.

Chapter 7 focuses on preserving access to emergency care in rural areas.  The Commission recognizes that access to inpatient and emergency services in rural areas is threatened because of the dwindling populations.  Declining populations can lead to fewer hospital admissions and reduced efficiencies that can create financial and staff problems for hospitals.  The Report notes that “[d]eclining volume is a concern because low-volume rural hospitals tend to have worse mortality metrics and worse performance on some process measures.” In addition, “low-volume CAHs have the difficult job of competing with each other for a shrinking pool of clinicians who want the lifestyle of operating an outpatient practice during the day, covering inpatient issues that arise at night, and covering the emergency department.”

Under current policies, most rural hospitals are critical access hospitals (CAHs).  They receive a cost-based payment for providing inpatient and outpatient services to Medicare beneficiaries.  To receive these payments, a hospital must maintain acute inpatient services.  In rural areas, many small towns do not have a sufficient population to support such a model.  Yet eliminating these services would mean giving up the supplemental payments that their hospitals receive through the CAH cost-based payment model.

The hospital prospective payment system serves as the payment model for other hospitals.  Rural providers receive supplemental payments, which are also linked to providing inpatient services.

MedPAC highlights the concerns with cost-based payment models:

  • Cost-based payments do not direct payments toward isolated hospitals having the greatest financial difficulty, but rather reward hospitals in high-income areas with higher non-Medicare margins by providing them with higher Medicare payments.
  • Cost-based payments encourage providers to expand service lines with high Medicare and private-payer shares rather than primarily focus on services that are needed on an emergency basis.
  • Cost-based models reduce the incentive for hospitals to control their costs, which can lead to unnecessary growth in capital costs, despite declining volumes.

In light of these challenges, MedPAC sets forth a two of options that would give isolated rural hospitals the option of converting to an outpatient-only model while maintaining their special payment arrangements.  These models seek to ensure access to essential services:

  • Establishing a 24/7 emergency department model; and
  • Adopting a clinic with ambulance services model.

Under the 24/7 emergency department model, the hospital would be paid under the outpatient prospective payment rates and would receive an annual grant/fixed payment from Medicare to cover the standby costs associated with 24/7 emergency services.  The current supplemental payments would be redirected to support this annual grant/fixed payment amount.  If a hospital chose to use inpatient beds as skilled nursing facility (SNF) beds, it would be reimbursed under the Medicare SNF prospective payment system.  The hospital could be required to use the fixed payment for emergency standby capacity, ambulance service losses, telehealth capacity, and uncompensated care in the emergency department.

Under the clinic and ambulance model, hospitals could convert their existing inpatient facilities into primary care clinics.  These clinics would be “affiliated” with an ambulance service.   Medicare would pay the prospective rates for primary care visits and ambulance transports.  Medicare would provide an annual grant/fixed payment to support the capital costs of having a primary care practice, the standby costs of the ambulance service, and uncompensated care costs.

The Commission recognizes that the “low population density would also make it difficult to retain primary care providers and support an ambulance service.”  It could also be difficult to describe the exact level of primary care and ambulance access that is required to receive the fixed Medicare payment.

MedPAC reiterates its position that “supplemental payments beyond the standard PPS rates should be targeted to isolated rural providers that are essential for access to care.”  Thus, it states that a program to support stand-alone emergency departments should be limited to facilities that are a minimum distance in road miles from the nearest hospital.

 

AAA Issues Response to GAO Claims Report

On May 13, the Government Accountability Office (GAO) issued a report entitled “Claim Review Programs Could Be Improved with Additional Prepayment Reviews and Better Data“. In the report, the GAO recommended that CMS be provided legislative authority to allow Recovery Auditors to use prepayment claims reviews to address improper Medicare payments. CMS fortunately disagreed with the GAO on the recommendation and cited better options such as prior authorization to address potentially improper payments.

The AAA has now issued a Formal Statement in response to the GAO report noting the problems with prepayment claims review for ambulance services and promoting the better alternative of prior authorization for nonemergency BLS transports of dialysis patients. The statement is in follow up to our Member Advisory providing an in-depth review of the report. Please feel free to share the statement if you receive questions about the report.

On June 26, 2015, the AAA had participated in a conference call with the GAO officials conducting the report in which AAA representatives had pushed for recommendations in line with our statement. The AAA will continue to advocate for policies to address improper payments that address the issue but are also the least burdensome to AAA members and help ensure our ability to continue to provide high-quality emergency and nonemergency ambulance services to patients.

Understanding the GAO’s Recent Report on Medicare Prepayment and Postpayment Reviews

On May 13, 2016, the Government Accountability Office (GAO) publicly released a report on the comparative effectiveness of the various audit programs used by the Centers for Medicare and Medicaid Services (CMS) and its various contractors. This report was requested by Senator Orrin Hatch, the Chairman of the Senate Finance Committee, who had asked the GAO to examine: (1) the differences between prepayment and postpayment reviews and the extent to which CMS contractors utilize each, (2) the extent to which contractors focus their reviews on particular types of claims, and (3) CMS’ cost per review, and the amount of improper payments identified by contractors for each dollar they are paid.

To briefly summarize the GAO’s findings:

  • The Recovery Audit Contractors (RACs) generally limited themselves to conducting postpayment reviews. The GAO attributed this to the fact that the RACs were paid contingency fees based on recovered overpayments, i.e., because prepayment reviews result in a claim never being paid in the first place, there is no “overpayment” to be recovered, and, therefore, no contingency fees to be paid. The GAO did note that from 2012 to 2014, CMS conducted a demonstration project in which the RACs conducted prepayment reviews (and were paid contingency fees based on the dollar amount of denied claims), which CMS considered to be a success.
  • The Medicare Administrative Contractors (MACs) generally limited themselves to conducting prepayment reviews.
  • Each contractor also tended to specialize in certain types of claims. For example, the GAO noted that during 2013 and 2014, the RACs tended to focus primarily on inpatient hospital claims. The GAO found that the MACs tended to focus on physician and durable medical equipment claims. Note: the GAO included claims for ambulance services within the larger category of “physician” claims.
  • The RACs identified a total of $4.5 billion in improper payments during 2013 and 2014. For their work, the RACs were paid contingency fees totaling $312 million, a return of approximately $14 in improper payments for every dollar paid to the RACs.
  • CMS lacked reliable data on the costs and effectiveness of its MACs program integrity reviews.

The GAO made two specific recommendations. First, it recommended that CMS seek legislation that would permit its RACs to conduct prepayment claims reviews. Second, it recommended that CMS develop written guidance on how its MACs should calculate the savings attributable to prepayment claims reviews. CMS disagreed with the first recommendation, believing it unnecessary in light of other programs intended to move CMS away from “pay and chase”, including prior authorization and enhanced provider enrollment screening. CMS agreed with the second recommendation.

Focus on the RACs

For the years 2013 – 2014, the GAO found that the RACs focused primarily on hospital inpatient claims. For example, the GAO found that 78% of the FY 2013 claims reviewed by the RACs were hospital inpatient claims. While this number declined to 47% in FY 2014, that decline was largely attributable to CMS, under its own authority and subsequent legislation, prohibiting the RACs from reviewing certain inpatient stays during the first part of FY 2014. If you look only at postpayment reviews, the numbers were even higher, 87% in FY 2013 and 64% in FY 2014.

So why were the RACs focused on hospital inpatient claims, largely to the exclusion of other types of claims? The GAO believes the answer lies in how the RACs are compensated for their work. Recall that the RACs are paid contingency fees (of between 9% – 17.5%) based on the amount of the recovered overpayments. Given this fee structure, the GAO believed it was logical for the RACs to focus on claims with higher average dollar amounts per claim. The following chart shows the average amount of the improper payment identified by the RACs on a per-claim basis:

As you can see, the average overpayment for an inpatient hospital claim was more than $3,000 in FY 2013, compared with slightly more than $300 for a physician (or ambulance) claim. Assuming a 10% contingency fee, this means the RAC could expect to receive $300 for each inpatient hospital claim it reviewed, compared with $30 for a physician claim. Given these financial incentives, the RACs decision to focus on inpatient hospital claims makes sense.

Focus on the MACs

In contrast to the RACs, the Medicare Administrative Contractors focused their program integrity activities almost exclusively on prepayment reviews. The following chart shows the breakdown of MAC reviews by provider type:

As you can see, the MAC largely focused on physician and DME claims, with physician claims (including ambulance claims) accounting for 49% of MAC reviews in FY 2013 and 55% of MAC reviews in FY 2014.

The efficacy of these reviews is unclear. This is largely due to the failure by CMS to collect consistent data on the savings from prepayment claims denials. At least 3 MACs failed to provide data on the specific funds they spent on prepayment and postpayment reviews. Instead, these MACs reported their costs as part of their broader claims processing activities. MAC also used different methods for calculating the savings from prepayment reviews. For example, 2 MACs used the billed amounts by providers to calculate total savings from denied claims, despite the Medicare allowables being significantly lower than the amounts normally billed by providers. 9 MACs used the total Medicare allowable, without differentiating between Medicare’s payment and the payments made by secondary insurers and/or patients. The remaining 5 MACs compared denied claims to similar claims that were paid to estimate what Medicare saved on claims denied as part of prepayment reviews.

Impact on Ambulance Providers and Suppliers

The key finding in this report is the GAO’s belief that prepayment reviews are generally more cost-effective in preventing improper Medicare payments. The GAO believes this is because prepayment reviews “limit the need to recover overpayments through the “pay and chase” process, which requires administrative resources and is not always successful.”

While the GAO and CMS are in agreement that Medicare should move away from postpayment reviews, they appear to disagree on how, exactly, to implement that transition. The GAO’s report makes clear its belief that CMS should devote greater resources to prepayment reviews, with the GAO specifically recommending that CMS seek legislative authority to empower its RACs to take a greater role in conducting prepayment reviews. By contrast, CMS appears to favor prior authorization programs.

Only time will tell which of these views gains prominence. In the meantime, ambulance providers and suppliers should expect to see the RACs take an increasing interest in our industry.


Have an issue you would like to see discussed in a future Talking Medicare blog? Submit your question!

Indian Health Service Issues Final Rule on Payments to Non-Contracted Providers

On March 21, 2016, the Indian Health Service (IHS), an agency with the Department of Health and Human Services, issued a final rule with comment period titled “Payment for Physician and Other Health Care Professional Services Purchased by Indian Health Programs and Medicare Charges Associated with Non-Hospital-Based Care.” This final rule will change the way the Indian Health Service pays for Purchased/Referred Care (PRC), formerly known as Contract Health Services (CHS). The provisions of this final rule will become effective on May 20, 2016.

Under current regulations, payment for PRC services is based on rates established by arms-length negotiations between the physician or other health care provider (including ambulance providers and suppliers) and the IHS, Tribe, Tribal Organization or urban Indian organizations (collectively referred to hereinafter as I/T/U programs). In the absence of an agreement, the health care provider is generally paid its full billed charges.

Provisions of Final Rule

The final rule amends the regulations at 42 C.F.R. 136.1 e. seq. to provide that payment for PRC services will now be based on Medicare payment methodologies. Specifically, payments would generally be set at the lowest of: (1) the amount provided for such service under the applicable Medicare fee schedule or Medicare waiver, (2) the amount negotiated with a specific provider or its agent, or the amount negotiated by a repricing agent, if applicable, or (3) the rate for such service paid by the health care provider’s or supplier’s “Most Favored Customer” (MFC). For these purposes, IHS has indicated that the MFC rate will be evidenced by commercial price lists or paid invoices and other related pricing and discount data.

While the previous paragraph sets forth the general rate-setting regime, a number of important exceptions will apply. First, any negotiated rate between the parties must be equal to or better than the provider’s or supplier’s MFC rate. The AAA is interpreting this requirement to require the provider or supplier to offer better (i.e. lower pricing) to the I/T/U program than it offers to any nongovernmental entities, including insurance plans. However, IHS indicated that this restriction would not apply to the extent the I/T/U program determines that the negotiated rate is otherwise fair and reasonable, and is otherwise in the best interests of the I/T/U (as determined by the I/T/U). Second, in the event that no agreement exists, and the Medicare Fee Schedule amount is greater than the provider’s or supplier’s MFC rate (i.e. the provider or supplier has voluntarily elected to accept a rate lower than the corresponding Medicare allowable from at least one nongovernmental entity), then the rate may not exceed the MFC rate, but may be lower than the MFC rate.

The final rule can be viewed in its entirety here.

The GAO Releases New Report on Claims Review Programs, Recommending Additional Prepayment Review Authority and Written Guidance on Calculating Savings from Prepayment Review

On Friday, May 13, the Government Accountability Office (GAO) publicly released a new Medicare report entitled, “Claim Review Programs Could Be Improved with Additional Prepayment Reviews and Better Data,” which it shared with the Congress and the Centers for Medicare & Medicaid Services (CMS) in April. The report is addressed to the Senate Finance Committee Chairman Orrin Hatch (R-UT) in response to his request.

The Report examines:

1. The differences, if any, between prepayment and post-payment reviews, and the extent to which the contractors utilize these types of reviews;

2. The extent to which the Medicare claim review contractors focus their reviews on different types of claims; and

3. CMS’s cost per review and the amount of improper payments identified by the claim review contractors per dollar paid by CMS.

In compiling the Report, the GAO reviewed Administration documents, interviewed CMS officials, Recovery Auditors (RAs), and Medicare Administrative Contractors (MACs). The GAO also interviewed representatives from 10 Medicare provider/supplier organizations that have experienced claim reviews on both a pre- and post-payment review basis. The AAA worked the GAO by participating in a telephone interview and providing written comments.

The GAO examined three types of contractors – the RAs, the MACs, and the Supplemental Medicare Review Contractor (SMRC). These contractors are responsible for reviewing claims that are at high risk of improper payment and claims that pose the greatest financial risk to Medicare. Only MACs conduct both pre- and post-payment reviews. RAs and the SMRC conduct only post-payment reviews, but RAs did participate in a pre-payment review demonstration project. RAs are paid on a contingent basis from recovered overpayments. During the demonstration, RAs were paid contingency fees based on claim denial amounts.

In its review, the GAO found that few differences exist between pre- and post-payment reviews, but noted that pre-payment reviews “better protect Medicare funds.” The GAO found that CMS is not always able to collect overpayments from post-payment reviews and that post-payment reviews require more administrative resources than pre-payment reviews.

The provider/supplier organizations highlighted two issues that need to be resolved with regard to pre-payment review audits. First, they identified that the option to hold discussions with RAs before payment determinations are made in the context of post-payment reviews can be helpful. These discussions are not part of the pre-payment review process; nor are they part of the MAC process. CMS indicated that it is not practical to have such an option in these contexts because of the timing requirements.

Second, the providers/suppliers noted that pre-payment reviews create cash flow burdens, in light of the appeals process. When appealing a post-payment review, providers/suppliers retain their Medicare payments through the first two rounds of review. If the denial is overturned at a higher level, CMS must pay back the recovered amount with interest accrued. However, for pre-payment reviews, providers/suppliers do not receive payment and CMS does not provide interest on the dollars withheld if the provider/supplier wins on appeal.

MACs have traditionally relied upon post-payment review. MACs will also use post-payment reviews to analyze billing patterns to inform other review activities, such as future pre-payment reviews and educational outreach. CMS has encouraged MACs to perform extrapolation, especially for providers/suppliers that submit large volumes of low-dollar claims with high improper payment rates.

The SMRC reviews often include studies to develop sampling methodologies or other policies that could be rolled out more broadly in the future.

The GAO also found that different contractors focused on different claims during 2013 and 2014. RAs focused on inpatient claim reviews primarily. RAs have the discretion to select the claims they review and the GAO stated that “their focus on reviewing inpatient claims is consistent with the financial incentives associated with the contingency fees they receive, as inpatient claims generally have higher payment amounts compared to other claim types.” The GAO also found that RA claim reviews had higher average identified improper payment amounts per post-payment claim review relative to other claim types in 2013 and 2014. For the upcoming contracts, CMS has indicated that it will more closely monitor RAs to ensure that they are reviewing all types of claims. For DME claims in particular, CMS has increased the contingency fee percentage paid to the RAs for DME, home health agencies, and hospice claims.

In contracts, MAC claim reviews focused primarily on physician and DME claims. DME claims accounted for 29 percent of their reviews in 2013 and 26 percent in 2014, while representing 22 percent of total improper payments in fiscal year 2013 and 16 percent of improper payments in fiscal year 2014. DME claims also had the highest rates of improper payments in both years.

Physician claims is a broadly used term that includes labs, ambulances, and individual physician.

The SMRC focused its claim reviews on studies that CMS directs the contractor to conduct. In 2013, the SMRC reviews focused on outpatient and physician claims, but in 2014 the focus shifted to home health agency claims and certain DME suppliers.

The GAO concluded that both RAs and SMRC generated savings for CMS, but unreliable data prevented comparing these results to those of MACs. CMS paid the RAs an average of $158 per review; the RAs averaged $14 in identified improper payments per dollar paid by CMS in both 2013 and 2014. CMS paid the SMRC an average of $256 per review, and the SMRC averaged $7 in identified improper payments per dollar paid in 2013 and 2014. The higher SMRC costs related to the study costs and extrapolation.

CMS lacks reliable MAC cost and savings data. CMS does not collect reliable data on claim review funding and does not have consistent data on identified improper payments. While CMS has established ways to collect this information, some MACs are not reporting it. MACs also use different methods to calculate and report savings.

The GAO recommended that CMS take two actions:

• In order to better ensure proper Medicare payments and protect Medicare funds, CMS should seek legislative authority to allow the RAs to conduct prepayment claim reviews.

• In order to ensure that CMS has the information it needs to evaluate MAC effectiveness in preventing improper payments and to evaluate and compare contractor performance across its Medicare claim review program, CMS should provide the MACs with written guidance on how to accurately calculate and report savings from prepayment claim reviews.

CMS did not agree with the first recommendation, stating that it has a strategy to move away from “pay and chase” using different policies, such as prior authorization initiatives and enhanced provider enrollment screening. CMS concurred with the second recommendation.

CMS Releases Medicare Provider Utilization and Payment Data for CY 2014 for Ambulance Suppliers, Physicians and Other Part B Organizations

On May 5, 2016, CMS publicly released the “Medicare Provider Utilization and Payment Data: Physician and Other Supplier Public Use File,” which provides information on the services and procedures provided to Medicare beneficiaries by ambulance suppliers, physicians and other healthcare provider groups.  The data file is based on calendar year 2014 data. This release follows on last year’s release of payment data for calendar year 2012.

The database lists all individual and organizations providers by National Provider Identifier (NPI), and provides information on utilization, total payments and submitted charges.  It can also be searched by Healthcare Common Procedure Coding System (HCPCS) code and place of service.

The Public Use File can be obtained here. Please note that you will need to download the desired file and then import it into an appropriate database or statistical software program.  CMS is indicating that Microsoft Excel is not sufficient for these purposes, and that importing it into Excel may result in an incomplete loading of data.

A number of news organizations have already created searchable databases that will allow you to search the CY 2012-2013 data by physician/organizational name, provider specialty, city, state, etc.  It is expected that these news organizations will be updating their websites to incorporate the CY 2014 data in the coming weeks. The searchable database created by the Wall Street Journal can be accessed here.

Prior Authorization Pilot Program – Status Update

CMS released preliminary data on the impact of the prior authorization demonstration program on Medicare payments for ambulance services.  This data is limited to the three states (NJ, PA, and SC) that were included in the demonstration program’s first year.

CMS noted that it has observed a dramatic decrease in expenditures for repetitive non-emergency ambulance transports since the program’s implementation.  CMS released the following data for the first 10 months of the program (i.e. December 2014 – September 2015), comparing that data to the first 11 months of 2014:

  • Payments for repetitive non-emergency ambulance transportation in these states averaged $5.4 million per month, down from nearly $18.9 million per month prior to the program’s implementation. This is a reduction of more than 70%.
  • In the states that were not part of the demonstration program, payments have decreased very slightly for the 10 months in 2014 and are very similar to the payments in the 11 months prior to the program beginning in SC, NJ and PA.
  • 18,367 prior authorization requests were received and finalized by Medicare’s contractors. Of these, 6,430 (35.0%) were approved.

CMS is closely monitoring these results to evaluate its effectiveness. Here is the full status update.

HHS Office of Civil Rights Announces Phase 2 HIPAA Audit Review Program

On March 21, 2016, the Office for Civil Rights of the Department of Health and Human Services announced Phase 2 of its HIPAA Audit Program.  The Health Information Technology for Economic and Clinical Health Act (HITECH) required HHS to perform periodic audits of covered entities and business associates to assess their compliance with the HIPAA Privacy, Security and Breach Notification Rules.  These rules are enforced by the HHS Office for Civil Rights (OCR).

Background on Phase 1

In 2011, OCR implemented a pilot audit program to assess the controls and processes covered entities have adopted to meet their HIPAA obligations.  The pilot audit program was conducted in three phases.  OCR first developed a set of audit protocols that it would use to evaluate covered entities’ compliance.  This protocol was then tested using a limited number of audits.   The final step involved using the revised audit protocols on a larger number of covered entities.  Ultimately, 115 covered entities were selected for review, and all audits were concluded by December 31, 2012.

Phase 2

Phase 2 of the HIPAA Audit Program will focus on the policies and procedures adopted and employed by entities to meet the requirements of the Privacy, Security, and Breach Notification Rules.  OCR has indicated that these audits will be conducted primary through desk audits (i.e., document submissions), although by a limited number of on-site audits will also be conducted.

Unlike Phase 1, which focused exclusively on covered entities, OCR is indicating that Phase 2 will involve audits of both covered entities and their business associates.

As with the initial pilot audit program, Phase 2 will consist of several stages.  The first stage involves verification of a covered entity’s or business associate’s address and contact information.  A sample address verification letter can be viewed by clicking here.  OCR has indicated that emails will be sent to entities requesting accurate contact information for the entity.  OCR will then transmit a “pre-audit questionnaire” to the entity.  These questionnaires will be used to gather data about the size, type, and operations of potential auditees.  Based on this data, OCR will create potential audit subject pools.

Note: OCR has indicated that if an entity fails to respond to OCR’s request to validate its contact information and/or fails to return the pre-audit questionnaire, OCR will use publicly available information about the entity to create its audit subject pool.  As a result, an entity that fails to respond may still be selected for audit and/or compliance review.  OCR is specifically reminding entities to check their email “junk” or “spam” folders for any communications from OCR.

Once OCR has developed its audit subject pools, it will randomly select auditees from these pools.  Auditees will then be notified by OCR of their participation.  OCR has indicated that the first set of audits will focus on covered entities, with a subsequent round of audits focused on business associates.  These audits will focus on compliance with specific requirements of the Privacy, Security, or Breach Notification Rules.  Auditees will be notified of the scope of their audit in a document request letter.  Both of these rounds will be desk audits.  OCR indicated that all desk audits will be completed by the end of December 2016.

A third round of on-site audits will take place after the completion of the desk audits, and will examine a broader scope of requirements under HIPAA.  OCR further indicated that desk auditees may also be subject to on-site audits.

If an entity is selected for audit, OCR will notify them by email.  The email will introduce the OCR audit team, explain the audit process, and discuss OCR’s expectations in greater detail.  The email notification letter will also include initial requests for documentation.  OCR has indicated that it will expect entities to respond to these documentation requests within ten (10) business days.  Documents will be submitted through a new secure online portal.  Once received, OCR’s auditors will review the submitted information and inform the entity of its draft findings.  The entity will then have ten (10) business days to respond with written comments, if any.  OCR will then review the entity’s comments and issue a final audit report within thirty (30) business days.

OCR has indicated that the audits are primarily intended as a compliance improvement activity.  OCR will use aggregated data to better understand compliance with respect to particular aspects of the HIPAA rules.  The goal being to understand what types of technical assistance and/or corrective actions would be most helpful.  In other words, OCR is indicating that the goal of these audits is to improve its understanding of the state of compliance, and not to penalize specific companies for violations.  However, OCR indicated that should an audit reveal a serious compliance issue, OCR may initiate a further compliance review of the company.

OCR indicated that it will not post a list of the audited entities, nor will its findings be available in a format that would clearly identify the audited entity.  However, OCR noted that audit notification letters and other information regarding these audits may be discoverable under the Freedom of Information Act (FOIA).

Additional information from OCR regarding the Phase 2 HIPAA Audit Program can be obtained by clicking here.

CMS Implements Cycle 2 Revalidation Program

By Brian S. Werfel, Esq. AAA Medicare Consultant

Want to learn more?

Join Brian Werfel and Angie Lehman for a 60 minute webinar on Revalidation for All Services.
June 29, 2016 at 2:00 PM EASTERN
Register►

CMS recently announced the start of its Cycle 2 Revalidation Program. This program affects all enrolled Medicare providers and suppliers.

In Cycle 1, which was conducted from 2011 through 2015, the so-called “trigger” to revalidate was a formal request to do so by your Medicare Administrative Contractor (MAC). For Cycle 2, CMS is adopting a new approach. CMS will be assigning revalidation due dates, i.e., dates by which the provider or supplier must revalidate. These due dates will be the last day of a particular calendar month. These due dates are based on the provider’s or supplier’s last successful revalidation or the date of the provider’s or supplier’s initial enrollment with Medicare. In other words, providers or suppliers that last revalidated in 2011 are likely to have new revalidation due dates in 2016, providers or suppliers that revalidated in 2012 are likely to have 2017 due dates, etc. The first set of due dates is May 31, 2016.

CMS has indicated that it will notify providers or suppliers by email within 2-3 months of their due date. These emails will include the following subject line: Urgent: Medicare Provider Enrollment Revalidation Request. If the email is returned as undeliverable, the MAC is instructed to send a paper revalidation notice to at least two of your reported addresses: correspondence address, special payments address, or primary practice address.

Providers or suppliers will be permitted to submit revalidations up to 6 months prior to their scheduled due date. Revalidations can be submitted either on paper or by using the online Provider Enrollment, Chain, and Ownership System (PECOS).

If a provider or supplier fails to submit a timely revalidation packet, CMS has indicated that the entity’s Medicare billing privileges will be deactivated. The entity will be required to submit a complete enrollment application to “reactive” its billing privileges. However, CMS has indicated that no payments will be made for services provided during the interim period.

If you have not received an email from your MAC asking that you revalidate, it is likely that your revalidation due date is more than 3 months out, or has not even been assigned. However, it is possible that the requests to revalidate may have been sent to invalid email addresses, or may have been routed to your email “spam” folder. It is also possible that paper revalidation notices may have been sent to obsolete physical addresses.

For these reasons, the AAA is strongly encouraging members to check the CMS revalidation webpage. That webpage includes a lookup tool that you can use to determine whether your organization has been assigned a revalidation due date. Currently, CMS has assigned due dates through the end of October 2016. Providers and suppliers that have yet to be assigned due dates will display as “TBD”. You can also download the entire list of currently enrolled providers and suppliers into an Excel spreadsheet. This option may be particularly helpful for organizations that bill under multiple Medicare PTANs (which can have separate revalidation due dates) and for billing agents that intend to assist their clients with the revalidation process.

In sum, the new process appears to be a vast improvement over how revalidations were handled during Cycle 2. Assuming things work as intended, AAA members should have a minimum of 2 months prior notice of the need to revalidate, and potentially up to 6 months prior notice. This should be more than enough time to submit the revalidation and avoid any potential disruptions to your ability to bill Medicare.

Medicare Revalidations: Will CMS Get Cycle 2 right?

The Affordable Care Act imposed a new set of screening and enrollment requirements for participation in the Medicare, Medicaid, and CHIP programs. These included additional screening criteria, new disclosures, an enhanced period of oversight for newly enrolled providers and suppliers, and the payment of a new enrollment fee ($554 in 2016). To implement these new requirements, CMS was required to revalidate all existing Medicare providers and suppliers between 2011 and 2015. CMS referred to this first 5-year revalidation period as “Cycle 1.”

As many of you will no doubt recall, Cycle 1 did not go as smoothly as the provider/supplier community (or CMS) had hoped. Looking back, it seems reasonable to conclude that the initial revalidation cycle put the Medicare Administrative Contractors in an impossible situation. The MACs were required, on relatively short notice, to develop policies and procedures that would hopefully permit the thousands of enrolled Medicare providers and suppliers in their jurisdictions to revalidate enrollment information on a relatively compressed time-scale.

The procedure adopted by most of the MACs was to instruct providers and suppliers not to revalidate unless and until instructed to do so by the MAC. Upon receipt of a revalidation request, the provider or supplier would then have sixty (60) days to gather up the required information and submit it to MAC for review. While seemingly reasonable in theory, this procedure proved to be a disaster in practice.

The problem, in a nutshell, was that the MACs (and the Carriers and Fiscal Intermediaries before them) had largely ignored the existing requirements related to revalidation. The enrollment information these MACs had on file for many ambulance suppliers was outdated. For example, the ambulance supplier may have moved its base of operations during the previous decade, but, for whatever reason, neglected to notify its MAC of this address change. As a result, the request to revalidate would end up being sent to an invalid address. In many cases, an ambulance supplier would tell us that the first indication they had that their MAC wanted them to revalidate was the discovery that their provider number had been suspended. When they would contact their MAC to inquire as to why, they would be told that they had failed to revalidate within the required timeframe. In many cases, it was weeks or months before these problems could be rectified, and the provider’s or supplier’s billing number reinstated.

Even if the provider or supplier received the revalidation request, other problems could easily arise.

Many providers or suppliers submitted their revalidation submissions on paper, only to discover the MAC failed to register their receipt. Other times, the MAC would confuse the submission with the name of a similar sounding ambulance provider. Minor mistakes on the enrollment form would lead to a prolonged series of requests for additional information, etc. The end result was endless hours spent on what was intended to be a simple formality.

In sum, Cycle 1 would charitably be described as a difficult time for ambulance providers and suppliers. The question that remained to be answered was whether CMS would learn from its mistakes and change the process the next time around, or whether it would continue the existing process despite its known limitations?

Well, CMS recently published its plans for the second 5-year cycle of revalidations (creatively titled “Cycle 2”), and a preliminary review suggests that CMS has made numerous improvements to the process.

[quote_right]Your organization’s obligation to revalidate will no longer be based on a written request from your MAC. Instead, CMS will assign a due date by which each and every enrolled provider or supplier must revalidate.[/quote_right]The most significant change is to the trigger for each provider’s or supplier’s obligation to revalidate. Your organization’s obligation to revalidate will no longer be based on a written request from your MAC. Instead, CMS will assign a due date by which each and every enrolled provider or supplier must revalidate. This due date will always be the last day of a calendar month (e.g., June 30, 2016, July 31, 2016, etc.). CMS indicated that your assigned due date will likely stay the same though subsequent review cycles.

Beginning March 1, 2016, CMS will make available a listing off all currently enrolled providers and suppliers (excepting DME suppliers). Ambulance organizations due for revalidation within 6 months will display a due date. All other ambulance providers and suppliers will show a “TBD” (To Be Determined) in the due date field.

The list of currently enrolled providers/suppliers can be obtained here. On that same webpage is a searchable tool that permits you to look up your organization by its name and/or NPI. The MAC will also send a revalidation notice via email or regular mail within 2-3 months of a provider’s or supplier’s revalidation due date.

CMS will accept revalidation submissions up to six months prior to an organization’s due date. CMS further indicated that “unsolicited revalidations” (defined to be revalidation applications submitted more than six months prior to the provider’s or supplier’s due date) will be rejected.

As in the past, revalidations can be submitted either on paper using the CMS-855 form or through the Provider Enrollment, Chain, and Ownership System (PECOS).

The other significant change to the process involves situations where the provider or supplier failed to revalidate in a timely fashion. During Cycle 1, this failure would result in the deactivation of the ambulance service’s PTAN. However, the MAC would typically permit you to submit a corrective action plan (i.e., a completed revalidation), and upon its approval, reinstate your billing privileges retroactively back to the date of suspension. However, for Cycle 2, CMS is indicating that if your PTAN is deactivated, you will be required to complete a new enrollment application. While you will ultimately have your PTAN reactivated, the effective date of that reactivation will be the date you submitted a new and complete application. You will not be able to submit claims to Medicare for dates of service that occurred during the resultant gap in coverage.

The new process appears to be a vast improvement over Cycle 1. Assuming everything works as intended (always a big if when CMS and its MACs are involved), ambulance organizations should have more than adequate notice of their revalidation due date. While I would suggest checking the CMS list monthly, even quarterly checks would give a provider at least 90 days to submit the revalidation request. Compared to the theoretical 60 days provided during Cycle 1 (which, in many instances, shrank to 30 days by the time the notices were actually received by the provider or supplier), this is a vast improvement.

In the past, it was convenient to blame the failure to submit these revalidations in a timely fashion on the bureaucratic inefficiency of your MAC. Under the new process, we should have more than adequate notice, meaning any failure to revalidate is likely to be our own fault.

Which leads me to my final suggestion for getting through the Cycle 2 revalidation process without any major problems….

GET YOUR REVALIDATION IN ON TIME!


 

Have an issue you would like to see discussed in a future Talking Medicare blog? Please write to me at bwerfel@aol.com.

Calculating Excess Mileage

The American Ambulance Association receives many questions from members for our expert consultants. Starting in February 2016, we will share responses to common questions on our blog. Have a more complex question? Contact an AAA expert directly.
Medicare | Human Resources & Operations | Labor Relations

Ask An AAA Expert: Ambulance Service Needs Some Direction on Mileage

[dropcap1]Q:[/dropcap1] Our service operates in a large metropolitan area. Within the city limits is a major university medical center. This hospital operates the only Level 1 Trauma Center within 100 miles. It is also the only hospital to offer interventional cardiology services and certain other advanced services within a 50-mile radius. As a result, patients from outlying areas are frequently transferred to this hospital. As the medical center’s contracted ambulance provider, we are often asked to transport patients long distances back to their towns of origin, either to their residences or to a skilled nursing centers (SNF). There are approximately a half a dozen SNFs located within a short distance (approximately five miles) of the hospital. Can you help us determine whether all of the mileage for these long distance transports will be covered by Medicare? If all of the mileage is not covered, can you help us determine the portion of the mileage that would be covered?

[dropcap1]A:[/dropcap1] In this inaugural edition of Ask the Medicare Consultant, we tackle one of the more difficult aspects of Medicare billing: how to determine the number of covered miles for long-distance hospital discharges.

The starting point for answering this question is to recognize that Medicare’s coverage rules will differ depending upon whether the patient is: (1) being returned to his or her residence, (2) is being returned to an SNF where he or she previously resided, or (3) is being transported to an SNF for an initial admission.

Where the patient is being returned to a residence (or a SNF at which they were previously admitted as a resident), Medicare’s coverage rules are relatively straightforward. Section 10.3.1 of Chapter 10 of the Medicare Benefit Policy Manual provides that:

“Ambulance service from an institution to the beneficiary’s home is covered when the home is within the locality of such institution, or where the beneficiary’s home is outside the locality of such institution, but the institution, in relation to the home, is the nearest one with appropriate facilities.”

For these purposes “locality” means the area surrounding the hospital from which patients would normally travel to that hospital for medical care. See Section 10.3.5 of Chapter 10 of the Medicare Benefit Policy Manual. Therefore, to the extent the patient’s residence falls within the “catchment area” of the hospital, the Manual makes clear that all of the mileage back to the patient’s residence will be covered.

To the extent the patient’s residence falls outside the hospital’s catchment area, the test is whether that hospital was the nearest appropriate facility (in relation to the patient’s residence) for the treatment of the patient’s medical condition.

Consider a patient that went to his local hospital with a complaint of chest pain, and who was ultimately diagnosed with a major cardiac blockage requiring bypass surgery. The patient was then transferred to the university medical center for that surgery (the only facility offering interventional cardiology within a 50-mile radius). The patient is now ready to be discharged back to his residence, a distance of 45 miles.

In this instance, the patient’s residence falls outside the catchment area of the medical center. However, the medical center was the nearest appropriate facility for the treatment of the patient’s medical condition. Accordingly, all of the mileage to this patient’s residence would be covered.

Unfortunately, it can sometimes be difficult to apply this test in practice, because the patient’s medical condition does not always manifest itself while at home. For example, what if this cardiac patient did not reside in the area, but rather was in the area visiting a son or daughter? Let’s further assume that the patient actually resided a few hundred miles away, in another major urban center (e.g., Chicago).

The university medical center would clearly not be the nearest appropriate facility when measured in relation to the patient’s home. Therefore, at the onset, it is clear that there is some non-covered mileage. The question then becomes, “how many miles?”

The test indicates that the covered mileage is the mileage from the patient’s residence to the nearest appropriate facility for that treatment. For these purposes, let’s also assume that there is a hospital that offers interventional cardiology located 10 miles from the patient’s residence. Therefore, in this example, the first 10 miles would be covered, and the remaining mileage would be non-covered.

A good rule of thumb: if all of mileage from the patient’s residence to the university medical center would have been covered (whether or not the patient actually traveled to that facility by ambulance), then all of the mileage back to that residence will also be covered.

The test for discharges to a SNF for an initial admission is a bit more complicated. The starting point is Section 10.3 of Chapter 10 of the Medicare Benefit Policy Manual, which provides that “only mileage to the nearest appropriate facility equipped to treat the patient is covered.”

In the original question, it was indicated that there were a number of SNFs located within a short distance of the university medical center. For the purposes of convenience, let’s assume that the nearest SNF is located across the street from the hospital, the next closest is located one mile away, the next closest is located two miles away, etc.

Thus, if the patient is transported to the SNF across the street, the entire mileage would be covered.

If the patient was transported to the next closest SNF, we cannot determine whether all of the mileage is covered without first determining whether the closer SNF had a bed available on that date. Note: a facility is not considered an “appropriate facility” if it does not have an available bed at the time of the transport. In other words, if the closer SNF had a bed on that date, then only the mileage to that SNF would be covered. The extra mileage, approximately 9/10ths of a mile, would not be covered. If, however, that closer facility did not have a bed available at the time, then the SNF to which the patient was transported would be the “nearest appropriate facility,” and all of the mileage would be covered.

Now imagine that the patient was taken the SNF two miles from the hospital. To properly calculate the covered mileage, we would need to know whether: (1) the SNF across the street had a bed available and (2) whether the SNF 1 mile from the hospital had a bed available).

[quote_left]“Does CMS really expect me to call one or more SNFs on every hospital discharge?”[/quote_left]And so on and so on…

At this point, you are probably asking yourself, “How can I possibly know if each of these closer SNFs had a bed available on that date? Does CMS really expect me to call one or more SNFs on every hospital discharge?”

The short answer: Yes, a literal interpretation of the Medicare coverage rules would require you to make those phone calls.

It goes without saying that this sort of process would be burdensome. Depending on the actual miles traveled, it may not even be possible to identify each and every closer SNF. For example, the original question alludes to transports of 50 or more miles. There could be dozens of SNFs located within a shorter distance. Calling each and every one of them is simply impractical.

In a perfect world, the hospital staff would notify you at the time they schedule the call that the patient is being transported beyond the nearest appropriate facility. However, in order to notify you, the hospital would have to know whether the nearby SNFs had a bed available on that date. The only way they could know that information would be to have called themselves. But why would the hospital call? The hospital likely gave the patient a choice, i.e., you can do your rehab in a nearby SNF or you can elect to go to an SNF in your hometown where you can be closer to your friends and family. As you would expect, the patient then elected to go closer to home.

So what to do?

One solution used by a number of ambulance providers is to draw a circle around the hospital that incorporates a sufficient number of SNFs so that they can be reasonably confident that there would be an available bed on any given day. In the original example, let’s assume that is the six SNFs located within five miles of the hospital. These ambulance providers have elected not to question any mileage below this threshold. Instead, they will bill up to five miles for coverage without any questions. These providers then assume that anything over that five-mile threshold is going to be excess mileage, which will need to be billed to the patient.

Please note that I am not suggesting that the first five miles would always be covered. Rather, these providers are engaged in a cost/benefit analysis. They are balancing the chances of having some portion of those five miles disallowed during a Medicare audit against the time and effort involved in calling each of these SNFs.

Please also keep in mind that this mileage circle would vary based on the local geography. In some areas, you may need to go out to 10, 20, or even 30 miles before you can incorporate a sufficient number of SNFs so that you can be assured that at least one would have an available bed on any given date. Of course, the larger the circle, the greater the potential that you may end up billing for substantial amounts of non-covered mileage. Thus, the decision to adopt a mileage parameter is one that should be made in consultation with your legal advisors.


 

Have a Medicare billing question? Do you suspect other AAA members are struggling with the same issues? If so, please let us know.

 

CMS Publishes Medicare Fee-for-Service Provider & Supplier Lists

Earlier today, AAA representatives participated on an invitation-only stakeholder call in which CMS announced the availability of two new public data sets. The first data set shows through an interactive map the availability and use of services provided to Medicare beneficiaries by ground ambulance suppliers and home health agencies. The second data set is a list of Medicare fee-for-service (FFS) providers and suppliers currently approved to bill Medicare. CMS just released the two data sets to the public.

The first data set, the Moratoria Provider Services and Utilization Data Tool, includes interactive maps and a data-set that shows national, state, and county-level provider and supplier services and utilization data that can be used by CMS to determine which geographic and health service areas might be considered for a moratorium on new provider and supplier enrollments. The data provides the number of Medicare providers and suppliers servicing a geographic region, identifies moratoria regions at the state and county levels, and identifies the number of people with Medicare benefits who use a specific health service in that region. The data can also be used to reveal service levels related to the number of providers and suppliers in a geographic region. Utilization data and geographic regions for these services can be easily compared using interactive maps.

You can access the Moratoria Provider Services and Utilization Data Tool at: https://data.cms.gov/moratoria-data
The provider/supplier enrollment data set can be accessed at: https://data.cms.gov/public-provider-enrollment

Medicaid Waivers to End Coverage of Non-Emergency Transportation

By David M. Werfel, Esq | AAA Medicare Consultant
Updated February 16, 2016

Federal law requires that state Medicaid programs cover necessary transportation to and from health care providers in order to ensure access to care. However, as a result of Medicaid expansion under the Affordable Care Act and cost increases, recently, a few states have asked CMS to waive the requirement for non-emergency transportation so they can end coverage of non-emergency transportation.

CMS granted waivers to Iowa and Indiana. Pennsylvania received permission, but the subsequent change in the governor’s office altered the state’s expansion plans and state officials ultimately chose not to use it. Arizona has a pending request to provide prior authorization.

When Iowa was granted the waiver, a beneficiary survey was conducted to determine the impact on access to care. The survey found some beneficiaries with incomes under the poverty level did not have transportation to or from a healthcare visit. Other beneficiaries said a lack of transportation could prevent them from getting a physical exam in the coming year. However, CMS stated the cases of negative impact were not statistically significant enough to discontinue the waiver.

As a result of the complaints, Sen. Ron Wyden (D-OR) and Sen. Frank Pallone, (D-NJ) asked the Government Accountability Office to investigate the impact of these waivers. The report is not expected in the near future. However, when issued, it could embolden other states to seek a waiver.

CMS Issues Final Rule on the Reporting and Return of Medicare Overpayments

On February 12, 2016, the Centers for Medicare and Medicaid Services (CMS) issued a final rule titled “Medicare Program; Reporting and Returning Overpayments.”  This final rule would implement Section 6402(a) of the Affordable Care Act, which imposed a 60-day requirement on Medicare providers and suppliers to report and return overpayments.  The provisions of this final rule will go into effect on March 16, 2016.

The final rule implements changes that were first proposed as part of a February 16, 2012 proposed rule.  The final rule can be viewed in its entirety by clicking here.

Background

Section 6402(a) of the Affordable Care Act requires health care providers and suppliers to report and return a Medicare overpayment within 60 days of the date such overpayment is “identified”.  Any overpayment not returned within this timeframe would become an “obligation” under the False Claims Act.  As a result, any ambulance service that is found to have knowingly retained an overpayment beyond the 60 day period could be subject to False Claims Act liability.  In addition, violations may also subject an ambulance company to civil monetary penalties and possible exclusion from the Medicare program.

Provisions of Proposed Rule

Definition of an “Overpayment”

In the final rule, CMS defined an overpayment as “any funds that a person has received or retained under title XVIII of the Act to which the person, after applicable reconciliation, is not entitled under such title.”  CMS noted that this definition is mirrors the definition of an overpayment that appeared in Section 6402(a) of the Affordable Care Act.
CMS cited examples of certain common overpayments in the proposed rule, including:

  • Payments for non-covered services;
  • Payments in excess of the applicable Medicare allowable
  • Errors and nonreimbursable expenditures included on a cost report;
  • Duplicate payments; and
  • Payment from Medicare when another payor had primary responsibility.

For ambulance providers and suppliers, another common area of overpayments would be payment for excessive mileage.

Note: in the final rule, CMS clarified that, in instances where the paid amount exceeds the appropriate payment to which a provider or supplier is entitled, the “overpayment” would be limited to the difference between the amount that was paid and the amount that should have been paid.  For example, if the overpayment was the result of a claim incorrectly being billed as an ALS emergency, rather than a BLS emergency, the overpayment is not the entire amount of Medicare’s payment.  Rather, the overpayment is limited to the difference in Medicare’s payment for the two base rates.

When an Overpayment has been “Identified”

In its proposed rule, CMS indicated that an overpayment would be “identified” if the ambulance provider or supplier: (1) had actual knowledge of the existence of the overpayment or (2) acted in reckless disregard or deliberate ignorance of the existence of the overpayment.  CMS indicated that this definition was intended to prevent providers and suppliers from deliberately avoiding activities that might uncover the existence of potential overpayments, such as self-audits and outside compliance checks.

CMS further stated its belief that the Proposed Rule would, in some instances, place an affirmative burden on providers and suppliers to investigate whether a potential overpayment exists.  Specifically, CMS indicated that “in some cases, a provider or supplier may receive information concerning a potential overpayment that creates an obligation to make a reasonable inquiry to determine whether an overpayment exists.”  If the provider or supplier then fails to reasonably inquire, it could be found to have acted with reckless disregard or deliberate ignorance.

In the final rule, CMS indicated that an overpayment will be deemed to have been identified to the extent “a person has, or should have through the exercise of reasonable diligence, determined that the person has received an overpayment and quantified the amount of the overpayment.”

Thus, the final rule makes two important changes to the standard of when an overpayment is identified.  The first change is to clarify that an overpayment has not been identified unless and until the provider or supplier is able to quantify the amount of the overpayment.

The second change was to remove the language related to “reckless disregard” and “deliberate ignorance”.  CMS replaced these terms with a standard of “reasonable diligence”.  Under the new standard, an overpayment is identified on the date you can actually quantify the size of the overpayment, or the date on which you would have been able to quantify the overpayment had you proceeded with reasonable diligence to investigate the possibility of an overpayment.  For these purposes, CMS indicated that reasonable diligence would be established to the extent you can demonstrate a timely, good faith investigation of any credible report of a possible overpayment.  Note: CMS indicated that an investigation should take no more than 6 months from the date of receipt of credible information, except in extraordinary circumstances.

To see the impact of these changes, consider the following scenario:

You receive an anonymous report on your compliance hotline that a recent change to your billing software has resulted in the mileage for all Medicare claims being rounded up to the next whole number (as opposed to being submitted with fractions of a mile).  Based on this report, you begin an investigation, and quickly come to the conclusion that the anonymous report is correct.  However, it requires an addition 4 months to review every claim submitted to Medicare since that software change, and to calculate the actual amounts you were overpaid.

Under the standard first proposed by CMS, it was unclear whether the 60-day clock to return over payment started on the day you confirmed the software problem, or whether you have time to look at your entire claims universe to calculate the actual amounts you were overpaid.  By contrast, under the standard set forth in the final rule, it is clear that the overpayment would not be “identified” until you can quantify the actual amounts you had been overpaid.  In the above example, you completed your investigation within 6 months, meaning you would have satisfied the new “reasonable diligence” standard.  Therefore, assuming you make a timely report and refund of the amounts you were overpaid, you would have no liability under the False Claims Act.

Situations in Which a Provider or Supplier would have a Duty to Inquire

In the proposed rule, CMS provided some examples of situations where a provider or supplier would be deemed to have received a credible information regarding a potential overpayment, including the following situations:

  • Where a review of billing records indicates that you were incorrectly paid a higher rate for certain services;
  • Where you learn that the patient died prior to the date of service on a claim that has been submitted for payment;
  • Where you discover that the services were provided by an unlicensed or excluded individual;
  • Where an internal audit discovers the presence of an overpayment.
  • Where you are informed by a government agency of an audit that discovered a potential overpayment, and where you fail to make a reasonable inquiry;

In the final rule, CMS confirmed its belief that official findings from a government agency (or its contractors) would constitute credible evidence of a potential overpayment, and would therefore trigger a provider’s or supplier’s obligation to conduct an investigation with reasonable diligence.  If the provider or supplier ultimately agrees with the Medicare contractor’s findings, it would qualify as having “identified” an overpayment, which would trigger the 60-day period for reporting and refunding that overpayment.  CMS further indicated that when the provider confirms the audit’s findings, the provider or supplier may be deemed to have credible evidence of additional overpayments (i.e., claims presenting the same issues, but which fall outside the contractor’s audit period) that may require further investigation.   CMS did agree, however, that where the provider or supplier elects to appeal the contractor’s findings, it would be reasonable to hold off on conducting an investigation into similar claims until such time as the overpayment identified by the Medicare contractor has worked its way through the administrative appeals process.

Counting 60-Day Period

In the final rule, CMS indicated that the 60-day period for reporting and returning the overpayment would start on the date the overpayment is first identified (i.e., the date the overpayment is first quantified following a reasonably diligent inquiry.  However, in the event a person fails to conduct a reasonably diligent inquiry, the 60-day period will be deemed to run from the date the provider or supplier first received a credible report of a possible overpayment (assuming the provider or supplier was, in fact, overpaid).

Process for Reporting Overpayments

In its February 2012 proposed rule, CMS had indicated that it would require ambulance providers and suppliers to report and return overpayments using the existing process for voluntary refunds.  At that time, CMS also proposed that the overpayment report contain 13 required elements, including a brief statement of the reason for the overpayment, and a description of the steps the provider or supplier intended to take to ensure that the same error would not occur again.  At the time, CMS further indicated that it would develop a uniform reporting form that would replace the various forms currently in use by its Medicare contractors.

In the final rule, CMS abandoned this formulaic approach to the reporting of overpayments.  Instead, CMS elected to permit providers or suppliers to use any of the following to report an overpayment:

  • An applicable claims adjustment;
  • Credit balance;
  • Self-Reported Refund; or
  • Any other reporting process set forth by the applicable Medicare contractor.

In addition to the processes currently used by Medicare contractors, providers or suppliers can also satisfy the reporting obligations of the final rule by making a disclosure under the OIG’s Self-Disclosure Protocol or the CMS Voluntary Self-Referral Disclosure Protocol.  Note: these processes are generally reserved for situations that involve something more than an isolated billing error.

When reporting an overpayment that was calculated using a statistical sampling methodology, CMS indicated that the provider or supplier must describe the actual process used to obtain a statistically valid sample, and the extrapolation methodology used.

Statute of Limitations

In the final rule, CMS adopted a 6-year “lookback period”.  CMS further clarified that this lookback period is measured from the date the provider or supplier identifies the overpayment.  As a result, an overpayment must be reported and returned only to the extent the overpayment is identified within 6 years of the date the overpayment was received.  Overpayments identified beyond the 6-year lookback period would not be subject to the new regulations.

The 6-year lookback period represents a substantial reduction from the 10-year lookback period originally proposed by CMS.  That 10-year period was intended to coincide with the outer limit of the statute of limitations for False Claims Act violations.  However, after considering comments from healthcare providers and suppliers, CMS agreed that a 6-year lookback period was more appropriate.  CMS noted that the change would significantly reduce the burden these new regulations imposed on providers and suppliers.

Change to Regulations Governing Reopenings

To facilitate the reporting and refunding of overpayments under these new regulations, CMS elected to revise its rules regarding reopenings.  CMS will now permit its Medicare Administrative Contractors (MACs) to reopen an initial determination (i.e., a paid claim) for the purpose of reporting and returning an overpayment.

While seemingly minor, this change is needed to ensure that Medicare’s payment files properly reflect that an overpayment has been refunded.  Otherwise, it would be possible for a claim that had previously been refunded to be selected by a Medicare auditor for postpayment review.  This could lead to the auditor attempting to recoup amounts that had previously been voluntarily refunded.

Musings on 2014 Medicare Payment Data (Part 1)

by Brian S. Werfel, AAA Medicare Consultant | Updated February 2, 2016

Every year, the Centers for Medicare and Medicaid Services (CMS) releases data on Medicare payments for the preceding year.The 2015 Physician/Supplier Procedure Master File (PSP Master File) was released in late November 2015.This report contains information on all Part B and DME claims processed through the Medicare Common Working File with 2014 dates of service.

The headline number is that Medicare spent $4.968 million on ambulance services in 2014.This represents a slight increase (0.67%) over the amounts spent on ambulance services in 2013.

Over the next few blog posts, I will be digging a bit deeper into these numbers to highlight a few long-term trends that I believe are noteworthy.

Increase in Medicare Ambulance Volume Trails Increase in Medicare Enrollment

The number of allowed ambulance services has grown steadily since 2007.Using data from the annual PSP Master Files, the number of allowed ambulance transports increased from approximately 17.5 million transports in 2007 to 20.8 million transports in 2014.The Office of the Inspector General and other government agencies have pointed to numbers like these as evidence that ambulance services face an increasing program integrity problem.

While a superficial analysis might suggest that this growth is problematic, I would argue that this growth must be viewed in its proper context.Over this same period of time, CMS Medicare Enrollment Reports show that the Medicare beneficiary population has grown from 44.1 million beneficiaries to approximately 54 million beneficiaries.All things being equal, one would expect the volume of ambulance transports to increase as the total beneficiary population increases.

When one compares the growth of ambulance volume to the growth of the Medicare population, a different narrative becomes apparent.As the chart on the right shows, with the exception of 2011, the increase in ambulance transports has consistently trailed the overall growth of the Medicare population since 2010.This reflects the fact that the earliest members of the Baby Boomer generation started to turn 65 in 2010.In other words, once you adjust for the increase in the Medicare population, ambulance transport volume has been essentially flat over the past 5 years.

Something to keep in mind the next time someone cites the increase in ambulance transports as proof that our industry has failed to adequately police itself.


Have an issue you would like to see discussed in a future Talking Medicare blog post? Please write to me at bwerfel@aol.com.

Question of a “Lifetime”

“Does Medicare still accept a lifetime signature for ambulance claims?”

As the AAA’s Medicare Consultant, I am frequently contacted by members seeking guidance on some of the more complicated aspects of Medicare billing. By a wide margin, the most common question we get is whether Medicare contractors will accept a so-called “lifetime signature.” Unfortunately, there is no easy answer to this question.

The Medicare regulations at 42 C.F.R. §424.36 provide that the beneficiary’s signature is required in order to authorize a healthcare provider to submit a claim to Medicare. The regulation then provides for two exceptions to that general rule. The first states that the beneficiary’s signature is not required if the beneficiary has died. The second states that, if the beneficiary is physically or mentally incapable of signing for themselves, the healthcare provider may obtain an alternative signature on the beneficiary’s behalf from one of the following individuals:

  1. The beneficiary’s legal guardian;
  2. A relative or any other person who receives social security or other governmental benefits on the beneficiary’s behalf;
  3. A relative or other person who arranges for the beneficiary’s treatment or exercises other responsibility for his or her affairs;
  4. A representative of an agency or institution that did not furnish the services for which payment is being claimed, but which did furnish other healthcare services or assistance to the beneficiary; or
  5. A representative of a Part A provider or nonparticipating hospital claiming payment for its services may sign for the beneficiary if, after making reasonable efforts, it is unable to locate or obtain a signature one any of the other authorized individuals referenced above. Note: this option is not available to Part B ambulance suppliers.

This regulation provides guidance on who may sign in order to permit a healthcare provider to submit a claim to Medicare. However, it does not speak to when that signature must be obtained. To answer that question, you must look to a separate regulation, 42 C.F.R. §424.40. That regulation sets forth the situations under which a request for payment (i.e., a patient’s signature) may be effective for more than one claim. Subpart (d) provides that a signed request for payment retained in a Part B supplier’s file may be effective indefinitely. It is this provision that ambulance suppliers have historically relied upon as justification for the use of a lifetime signature.

To understand how these provisions were intended to interact, it is helpful to keep in mind that the signature requirement applies to all Medicare claims, not only ambulance claims. This includes claims for services that can be provided on a non-assigned basis (e.g., physician claims). For these types of claims, the beneficiary’s signature is required to effectuate the assignment of benefits from the beneficiary to the healthcare provider, without which the healthcare provider would be limited to billing the beneficiary directly for its services. In other words, the beneficiary signature requirement was intended to perform a necessary administrative function.

However, in 2007 and 2008, CMS revised the beneficiary signature requirement for ambulance providers and suppliers. As part of these changes, CMS indicated that the beneficiary’s signature on a claim (or other documentation) served as proof that the ambulance services were actually rendered to the beneficiary. In other words, CMS clarified its belief that the beneficiary signature requirement performed a program integrity function.

This shift in CMS’ understanding of the purpose behind the beneficiary signature had far-reaching implications on the validity of the lifetime signature. When understood as a simple assignment mechanism, the lifetime signature is relatively non-controversial. After all, if the patient was willing to consent today to the submission of a claim to Medicare, why shouldn’t they also be able to consent to any future services rendered by that same healthcare provider? However, a patient’s signature obtained today would not establish that any future transports actually took place.

It is this shift in CMS’ stated position regarding the underlying purpose of the beneficiary signature requirement that has led a number of Medicare contractors to no longer accept a lifetime signature for ambulance transports. These contractors argue that a signature obtained prior to the actual date of transport cannot prove that the transport was actually provided. Frankly, I find it difficult to argue with their logic.

The problem is that, while CMS has announced its new position on the purpose of the beneficiary’s signature, it has yet to revise its regulations to specifically exclude ambulance providers and suppliers from relying upon a lifetime signature.

At some point, CMS will be forced to reconcile this apparent contradiction. In the meantime, ambulance providers and suppliers are forced to operate in something of a grey area. Operationally, the lifetime signature makes life a lot easier for our crews and billing office. However, relying upon the lifetime signature puts us at risk of having claims denied as part of an audit. The recent implementation of a prior authorization process for repetitive patients (currently in 8 states and the District of Columbia) has brought this issue to the forefront, as many ambulance services previously relied upon a lifetime signature for their dialysis and other repetitive patients.

So What Should You Do?

As a best practice, I strongly recommend that ambulance providers and suppliers instruct their crewmembers to attempt to obtain the patient’s actual signature or a valid alternative at the time of transport. Doing so should limit the situations in which the lifetime signature might come into play.

The question then becomes how to handle those claims where, for whatever reason, the crew was unable to obtain the patient’s signature or a valid alternative at the time of transport. In these situations, submitting the claim based on a previously obtained lifetime signature is an option. You will need to make a business decision on whether that option is the right one for your organization.

Some factors you should consider in making that decision:

  1. Has your Medicare Administrative Contractor indicated that it will no longer accept a lifetime signature for ambulance claims?
  2. Are you located in one of the states (or DC) where the MAC is currently operating a prior authorization process for repetitive patients? Are you currently under any other type of prepayment review?
  3. If claims are denied for lack of a valid patient signature, are you comfortable with potentially having to appeal all the way up to an Administrative Law Judge?

Depending on how you answer these questions, you may decide that the risks associated with relying upon the lifetime signature are too great. If so, whenever the crew fails to satisfy the patient signature requirement at the time of transport, and assuming you are otherwise unable to satisfy the new alternative for ambulance transports, you will need to send the patient a signature request form (and hold the claim until that request is returned).

So back to the original question: Does Medicare accept a lifetime signature for ambulance transport?
Answer: it depends on who you ask.

AAA members, do you have an issue you would like to see discussed in a future Talking Medicare blog post? Please write to me at bwerfel@aol.com.

CMS Releases Ambulance Cost Data Collection Report

The Centers for Medicare and Medicaid Services (CMS) has released its report on the feasibility of collecting cost data from ambulance service providers.  Under the American Taxpayer Relief Act of 2012, Congress directed CMS to conduct the report entitled “Evaluation of Hospitals’ Ambulance Data on Medicare Cost Reports and Feasibility of Obtaining Cost Data from All Ambulance Providers and Suppliers”. The report can be accessed here.

The report states that due to the diverse nature of our industry with a majority of providers being small entities, traditional mandatory ambulance cost reporting is not feasible.  While it does not make a recommendation on a data collection system, the report highlights the work of the AAA with The Moran Company and will be helpful in our push for a survey approach to collecting ambulance cost data.  Here is AAA’ summary of the report, AAA Summary of CMS Acumen Cost Analysis.

The survey approach to collecting ambulance cost data is a major component of the Medicare Ambulance Access, Fraud Prevention and Reform Act (S. 377, H.R. 745) which would make the current Medicare ambulance increases permanent.  The data collected through the survey would help the AAA make data-driven recommendations to the Congress and CMS on future changes to the Medicare ambulance fee schedule.

The contractor, Acumen, who developed the report, was also asked to look to see if cost data submitted by hospital-based ambulance service providers would be helpful.  Acumen determined that the data submitted varied significantly and thus was not useful.

For questions about the AAA efforts on cost data collection, please contact AAA Senior Vice President of Government Affairs Tristan North at tnorth@ambulance.org.

Stay In Touch!

By signing up, you agree to the AAA Privacy Policy & Terms of Use