Medicare billing snafus hurt Minnesota rural hospitals



Medicare payment problems are generating steep financial hardships for some of Minnesota’s rural hospitals at a time when many are struggling to stay afloat.

State hospital leaders and officials at several rural hospitals say they have been vexed by a recent payment processing change by the federal Centers for Medicare & Medicaid Services that is effectively holding back millions of dollars needed to pay the bills.

“We're burning through the cash that we had in our bank, and we're running out,” said Andrew Knutson, CEO of the Mille Lacs Health System, a central Minnesota operation based in Onamia that draws about 60 percent of its income from Medicare.

The Centers for Medicare & Medicaid Services has withheld about $2.5 million in Medicare payments from the Mille Lacs Health System since early January, he added.

If they cannot resolve the issue with Medicare officials in Washington, “we will run out of money and won’t be able to pay anybody, so we'll have to close,” within six to eight weeks, said Knutson, who employs some 420 people.

New process, new pain

Knutson and other hospital leaders point the finger at a fairly new billing regimen by the Centers for Medicare & Medicaid Services put in place nationally that is supposed to do a better job preventing improper Medicare billing.

But a significant issue with the online software system that health care providers use to submit and manage their Medicare enrollment information has led to the denial of claims for so-called critical access hospitals — health care centers vital to the health of rural America.

The updated billing method is intended to simplify administrative processes for those hospitals while ensuring compliance with Medicare requirements.

But the enrollment data from these hospitals did not transfer correctly when the federal agency implemented its new system, resulting in claim denials and delayed Medicare payments.

Mille Lacs Health System discovered that some of their health care providers had not been enrolled because they had been inadvertently removed from the CMS system in the system changeover.

“As we re-enrolled them, we found that CMS was deactivating them from Mille Lacs Health System. Not all of them, but some of them,” Knutson said. “And when we tried to figure out why they were doing that, they didn't really have a great answer for us.”

Employees in the health systems’ billing department often call CMS multiple times a day to seek solutions. But Knutson noted that the information they receive can vary significantly based on who answers the phone.

A Centers for Medicare & Medicaid Services spokesperson said that “while most claims are being processed on schedule, the agency is aware that some providers are experiencing delays and is working closely with contractors to address issues as quickly as possible.”

The agency “remains committed to both protecting taxpayer dollars and ensuring that hospitals and health systems receive the payments they are owed,” the spokesperson wrote in a statement to MPR News.

Knutson said his employees trying to work through the snafus are frustrated because they cannot call back the same Medicare representative. Instead, they must keep dialing the hotline, and each time the call is routed to a different representative.

‘A dire situation’

Medicare, the federal health insurance program available to people age 65 and older and younger adults with long-term disabilities, is vital to the health of rural Minnesota and its care operations. 

If the current problems do lead to hospitals closing, it could be a huge problem for rural Minnesotans who depend on having health care nearby and would face much longer distances to get needed treatment.

Joe Schindler, the vice president of finance policy for the Minnesota Hospital Association, said they are very concerned that Medicare is “seemingly unable” to pay their bills, and especially in rural parts of the state. "We've heard this from many hospitals across Minnesota."

Rural hospitals across the country are dealing with the same problems, he added.

Many rural hospitals in Minnesota are already operating on razor thin margins. Knutson noted that beyond the $2.5 million that Medicare is holding back, the Mille Lacs health system is also owed about $1 million from UCare, one of the largest health insurers in Minnesota. 

UCare announced in November it would be shutting down and transferring its accounts to Medica, the Minnesota nonprofit health system.

In Aitkin, Minn., about an hour’s drive from Onamia, Riverwood Healthcare Center said it is also struggling with the delay in Medicare payments. Its three primary care clinics and critical access hospital serve just under 33,000 people in a region that includes Aitkin, Garrison and McGregor. 

Riverwood is awaiting $2.5 million in payments owed to it from Medicare, said Casey Johnson, the chief financial officer. 

“The net impact to us then is that there's all this money that's being held, and it is really creating some hardships for us,” said Johnson, adding that he has people calling Medicare administrative contractors daily about the matter.

For the past three months, he said, Riverwood has had to cover all its expenses with 75 percent of its income.

Johnson expressed hope the situation will get resolved and payments expedited within the next month. If not, it may force decisions that would have lasting effects on Riverwood.

“Hopefully we don't get there, and I don't think we're there now, but that's always the worry,” Johnson said.

If the Medicare billing woes seen by Mille Lacs, Riverwood and other rural care operations are not resolved soon, “this would be quite a major shock to the system,” Schindler said. “These hospitals are barely surviving. So, it is a dire situation at this point in time.”



Source link

Leave a Reply

Subscribe to Our Newsletter

Get our latest articles delivered straight to your inbox. No spam, we promise.

Recent Reviews


Apigee Edge – Table of Content

What is Apigee Edge?

Apigee Edge is an API gateway management tool. It was originally founded in 2004  in Santa Clara, California with the name Sonoa Systems and later rebranded as Apigee in 2010. Google has acquired Apigee in the year 2016. Apigee Edge is used for developing and managing APIs. Many websites and applications are connected together with APIs to provide data feeds. The Apigee Edge provides an abstraction for backend service APIs. It mainly offers security, rate limiting, quotas, analytics, and other features for the APIs.

Apigee Edge provides a secure way of access to the backend services with a well-defined API. This API will be easy to consume by any type of application. Even if the backend is changed or data is changed, the API won’t get affected. When applications or app developers access the APIs, they access an API proxy that is created on the Edge. The API proxy acts as a mapping of the HTTP endpoint to the backend service. The Edge will handle the authorization and security to protect the backend services.

Features of Apigee Edge

  • Here are the features of Apigee Edge.
  • Apigee Edge provides a user-friendly platform through which users can design, secure, publish, analyze, monitor, monetize the APIs. 
  • It provides configurable security policies like OAuth, API key verification, JWT, Access control, etc.
  • Versions of APIs are supported at multiple levels. 
  • Message transformation, data parsing, and validation can be done through Edge mediation.
  • Java, JavaScript, Node.js, and Python are the supported languages that Apigee Edge provides for API management.
  • It is a multi-tenant platform for both on-premises and in the cloud. 
  • The updates and fixes can be rolled out quickly.
  • It offers analytics capabilities such as dashboards, custom reports, GeoMaps, etc.

Become a Apigee Certified professional  by learning this HKR Apigee Training!

Components of Apigee Edge

Apigee Edge consists of the below 3 components.

Edge API runtime

This is where APIs are created and consumed. It contains services such as API Gateway, Connectors, Programmability, API First, Security, and Federated runtime. Users can configure API proxies, set up API products, and manage app developers and client apps. It addresses the main concerns that are related to API management. It lets the users add security policies to the API proxies. The behavior of the API proxy can be customized using custom scripts. 

Edge monitoring & analytics

Apigee Edge provides tools to generate reports that show the usage trends of your APIs. When data is passed through the Edge, several types of default information such as URL, user ID, IP are collected. Users can customize this to collect information such as query parameters, headers, portions of a request or response, etc without affecting the API performance. This information will be useful to create reports for latency, error data, and more. All the metrics are presented in a browser-based dashboard. 

Apigee Training

  • Master Your Craft
  • Lifetime LMS & Faculty Access
  • 24/7 online expert support
  • Real-world & Project Based Learning
Edge developer ecosystem

The developer ecosystem provides developer services such as SmartDocs, Self-Service, Customizable portals. It lets the users formalize their relationships with internal and external developers. Users can manage the app developers that use the services. An Edge customer can create a developer portal either in the cloud or on-premises. The app developers can connect to the portal to access API documentation. Edge customers can create two types of portals.

  • Integrated portal – a quick and easy to use developer portal.
  • Drupal-based portal – a fully customizable developer portal.

Flavors of Apigee Edge

Apigee Edge is available in three flavors.

Public cloud

A completely Apigee hosted SAAS version of the environment. Users can build APIs without worrying about the infrastructure.

Apigee hybrid 

APIs can be managed on Google Cloud Platform (GCP), or on-premise, or a mix of both. It lets the users handle both the internal and external APIs with Google Cloud. Users will be able to leverage existing local compliance and governance policies.

Private cloud

Users have to configure their own environment and carry out administrative processes such as installation, upgrade, and maintenance. The private cloud won’t be able to provide all the features offered by the public cloud. 

Want to know more about Apigee, visit here Apigee Tutorial.

Basic terminology

Let’s look at some basic terms that are frequently used in API management.

API

An application programming interface (API) is used to consume data or services from one application to another. APIs make it easy for developers to access and reuse application logic that is built by another developer. For the web APIs, the data will be accessed over the network.

API proxy

It is an abstraction or a facade for one or more APIs on the Edge. Implementing a set of configuration files, policies, and code to utilize some resources is referred to as an API proxy. The API proxies can even be created in a text editor or an IDE. It protects the backend services from code changes by developers. Users can customize the email signature by setting multiple interfaces to the same API.

API basepath and resources

An API consists of a base path and a set of API resources. The base path in an API proxy is compulsory, and the API resource paths are optional. An API management can simply be referred to as a set of URIs. Developers can attach policies and codes to these URIs. Several APIs of an application may share a common base path. 

, others, apigee-edge-description-0, , others, apigee-edge-description-1

Subscribe to our YouTube channel to get new updates..!

API product

API product is a collection of API resources (URIs) with a service plan published at design time. Developers can bundle multiple API products together for monetization to make an API package. One or more API products has an API key that permits an app to consume the API.

API package

It is a bundle of several API products generally associated with a rate plan.

App

An application built with any programming language, technology, or platform is referred to as an app. An app can either be mobile or web that consumes an API. To let the apps consume an API, they have to be registered in the API provider’s organization on Apigee Edge. Once the registration is done, the app will get an API key and secret. The API key should be embedded in the app to authorize API consumption.

Environment

It is the runtime execution for API proxies. To make an API proxy accessible, it should be deployed in an environment. Test and prod are the environments provisioned by default to an organization.

Organization

An organization acts as a container for objects in the Apigee Edge account, such as API proxies, API products, API packages, Apps, and developers. A user should have a user account to work in an organization. A user can have accounts in multiple organizations.

Policy

A policy is a reusable unit of logic that can be executed within an API proxy processing flow. A policy is generally used to transform message formats, masking sensitive data, calling remote services, access control, and more. A policy can be executed based on the context of a request, or content, or response message.

API resource path

The API resource path is a RESTful concept and a URI (uniform resource identifier) that locates the resource path to the resource available. 

Top 30 Frequently Asked Apigee Interview Questions !

Version

It is the term used to define the next edition of a developer-facing API interface. 

Revision

It is a numbered version-controlled package of API Proxies. The API interfaces have versions and the API proxies have revisions.

Tips for API proxy development

Here are some useful tips that will help you while deploying API proxies.

  • Configure a sequence of steps as an API proxy to execute in response to a request. An API proxy typically includes resource paths, an HTTP verb, body requirements, etc. Although it is called an API proxy, it is generally an API.
  • Define the path of processing logic in the flows in Apigee Edge. You can apply logic and behavior in stages of the processing path.
  • You can access the variables that represent the execution state of an API proxy. You can access them from the XML that configures API proxies and policies.
  • You can specify conditions on the API proxy state. Based on the state of the API proxy, you can execute the code conditionally to process the request.
  • You can arrange policies in a sequence of steps within a flow to execute them in order.
  • The errors of an API proxy can be customized by configuring a fault handler. 
  • You can examine the API proxy’s execution flow using a trace tool for debugging and testing. 

Apigee Training

Weekday / Weekend Batches

Conclusion

Organizations want to make the backend resources available on the web to make them accessible for mobile applications and web applications. Apigee Edge makes it easy to visually code, or configure API policies, and customize API behavior. It safeguards your data from threats and other attacks. Users can track live API calls, traffic surges, API traffic info with real-time insights. It also decreases the meantime to diagnosis (MTTD). Apigee Edge provides a seamless customer experience to partners, customers, and application developers. Major companies like Burberry, eBay, Walgreens, Shell, First Data, Live Nation, etc., use Apigee Edge. 

Related Articles: 



Source link