Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Deprecated: Optional parameter $attach_id declared before required parameter $height is implicitly treated as a required parameter in /home/linkenwd/wws.wonderws.com/wp-content/plugins/case-theme-core/inc/helpers/resize-image.php on line 23

Deprecated: Optional parameter $img_url declared before required parameter $height is implicitly treated as a required parameter in /home/linkenwd/wws.wonderws.com/wp-content/plugins/case-theme-core/inc/helpers/resize-image.php on line 23

Deprecated: Return type of YITH_WCWL_Wishlist::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 865

Deprecated: Return type of YITH_WCWL_Wishlist::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 882

Deprecated: Return type of YITH_WCWL_Wishlist::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 831

Deprecated: Return type of YITH_WCWL_Wishlist::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist.php on line 847

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetExists($offset) should either be compatible with ArrayAccess::offsetExists(mixed $offset): bool, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 651

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetGet($offset) should either be compatible with ArrayAccess::offsetGet(mixed $offset): mixed, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 668

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetSet($offset, $value) should either be compatible with ArrayAccess::offsetSet(mixed $offset, mixed $value): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 617

Deprecated: Return type of YITH_WCWL_Wishlist_Item::offsetUnset($offset) should either be compatible with ArrayAccess::offsetUnset(mixed $offset): void, or the #[\ReturnTypeWillChange] attribute should be used to temporarily suppress the notice in /home/linkenwd/wws.wonderws.com/wp-content/plugins/yith-woocommerce-wishlist/includes/class-yith-wcwl-wishlist-item.php on line 633

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the ninja-forms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the mailchimp-for-wp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redux-framework domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the consultio domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

Deprecated: Function Redux::getOption is deprecated since version Redux 4.3! Use Redux::get_option( $opt_name, $key, $default ) instead. in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131
How Claims Audit Can Make You Sick – WWS
Deprecated: Function WP_Dependencies->add_data() was called with an argument that is deprecated since version 6.9.0! IE conditional comments are ignored by all supported browsers. in /home/linkenwd/wws.wonderws.com/wp-includes/functions.php on line 6131

How Claims Audit Can Make You Sick

How To Make Your CLAIM AUDIT Look Like A Million Bucks?

HME businesses face increasing numbers of pre- and post-payment audits, which can be very stressful and costly events. Without a sound strategy for maintaining accurate and retrievable documentation, an audit request can disrupt operations and put your organization at financial risk.

When an audit strikes, the response must be swift and precise. The best approach to an audit letter is a quick response with proof that all documentation complies with requirements.

Five steps HME providers can take to give a speedy response and make sure all claims are audit-ready include:

1. Give Customer Service Representatives tools to improve intake:
  • Knowledgeable customer service representatives at the front end are essential to collecting the right information at the start of service, but staff turnover and constantly changing requirements make it difficult to keep CSRs up-to-date on payer requirements.
  • Technology can fill the knowledge gap if it does more than just park the data in a form prompting CSRs to collect specific documentation, which enables correction of the claim before it is filed.
2. Document to payer-specific rules:
  • Improve efficiency by helping CSRs collect payer-specific requirements through established validation rules.
  • While Medicare rules may call for a document to support specific Healthcare Common Procedure Coding System (HCPCS) codes, other payers may have a looser set of rules for that procedural code, which don’t require the same level of documentation saving time for the CSR.
3. Enable quick response to the audit letter:
  • Staff should be able to quickly access the documentation when responding to an audit letter, which is not always easy in the case of long-term service.
  • Establishing a link between billing records and the sales order documentation eliminates the risk of error when pulling documentation and ensures the information can be gathered efficiently.
  • In addition, advanced HME systems allow users to collect, submit and track documentation electronically in response to CMS audits.
4. Automate document review within the workflow:
  • There are times a critically needed product must be delivered before documentation is complete.
  • This increases the need for a careful documentation review before submission of the claim to ensure progress notes support medical need and meet requirements.
  • HME providers can easily determine whether or not to delay confirmation of a claim until the file is complete and the claim is substantiated by automating the review process throughout the workflow, utilizing optical character recognition technology and installing checkpoints that alert staff to missing or inaccurate information.
5. Capture data on all patient-care related interactions:
  • Setting up a process to capture all telephone calls to patients, verbal orders from physicians or communication with other providers is critical, but difficult with the number of people involved in each case.
  • Technology that documents actions by time, date and personnel involved provides additional support as an HME provider demonstrates compliance with billing requirements.

There’s no sure way to guarantee you won’t go through an audit; however, by ensuring the good HME business technology is in place you can take on most any audit challenge. With proactive compliance and timely response submission, audits can be resolved and claims are paid faster leading to improved cash flow.

Don’t wait for an audit Make every claim audit-proof from the start and For more information email us at support@wonderws.com

Leave A Comment