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
Steps to Achieve Clean Claims Submission Ratio – 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

Steps to Achieve Clean Claims Submission Ratio

Clean Claims Submission Ratio
What is Clean Claims?

A clean claims has no defect, impropriety or special circumstance, including incomplete documentation that delays timely payment. A provider submits a clean claim by providing the required data elements on the standard claims forms, along with any attachments and additional elements, or revisions to data elements, attachments and additional elements, of which the provider has knowledge.

Submitting clean claims is more important than ever for physician practices. Declining fee schedules, changes due to procedure bundling and the growth of high-deductible health plans all leave groups with little margin for error when it comes to cash flow

Have you ever analyzed how many claims does your practice or center submit to carriers daily?

Do you track the percentage of claims that get paid at first submission?

Each time carriers deny your claims they accumulate in your accounts. The claims have to be revisited and denials have to be identified, appropriate action has to be taken and the claim cycle begins again. There is a substantial time and resource utilization in doing the submission process all over again.

The average percentage of claims that get paid at the first submission determines the clean claim percentage. It is ideal to keep this percentage high for running a profitable surgery center where resources are tight and time spend is crucial.

So how do you ensure optimum percentage of clean claims and build a continuous process?

Here are the seven steps that will help ensure clean claims submissions percentage over 95%:

1.  Ensure correct and updated patient information on claims.

Information to verify- patient demographic information, policy information and medical information.

2. Procedure authorization at-least five days prior to the date of service.

Information to verify- type of procedure, checking with carriers if a certain scheduled procedure requires a prior authorization and verifying if the procedure is covered under the patient plan type.

3. Verify patient eligibility and benefits at-least two days prior to the date of service.

Information to verify- primary, secondary and if applicable tertiary insurances, policy effective dates, in-network/ out-of-network benefits entitlement, services or procedure coverage, copays and deductibles.

4. Ensure correct modifier usage.

Information to verify- application of correct modifier, appending the modifier on the correct procedure. Create customized National Correct Coding Initiative (NCCI) edits guideline to determine modifier usage.

5. Undertake quality checks prior to submission.

Information to verify- Examine each claim for demographic, coding, submission errors prior to submission.

6. Follow carrier specific coding guidelines.

Information to verify- CPT and ICD compatibility, submission process- paper based or electronic. Create carrier specific Local Coverage Determination (LCD) guidelines to verify coding compatibility. Surgery center can also explore the option of automation the claims scrubbing process by building rules engine software systems or by partnering with other companies providing this service.

7. Detailed medical documentation.

Information to verify- case history, need of service documentation, procedure documentation, patient medication history. If required by carriers, medical documents act as supplemental records for claims processing.

Learn more about physician revenue cycle management services and how we can help your practice grow revenue and maintain positive cash flow.

Schedule a free demo http://localhost/main-site-update/live-demo/

Leave A Comment