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 to deal with Misspelled name on Insurance cards? – 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 to deal with Misspelled name on Insurance cards?

When it comes to medical billing and coding for small health care practice, like a family doctor’s office or a small specialty clinic, you would think that it would not be too hard to keep your medical coding and billing in-house. However, you might be failing to account for the unexpected problems that you can’t predict, but that will inevitably slow down your revenue cycle.

These kinds of problems easily fall into the category of “Nobody’s Fault” but your practice still has to deal with them.  Major problem that is becoming increasingly common is Name misspellings on insurance cards.

How to correct the name misspellings on Insurance Card?

  1. Nowadays, There is no shortage of sources for confusion when it comes to how people spell their names.
  2. There are a lot of names which have similar spellings, so it is easy for insurance carriers to make a typo.

For Example, A customer’s name may be listed (correctly) in your system as “Davidson” but their insurance company may have misspelled their name as “Davidston”.

  1. Things may get even more complicated when patients have hyphenated last names, but they may use only one of the names with their insurance company.
  2. There are also patients who have last names that are two separate words, which can cause trouble when health care offices or insurance carriers get confused and think the second name is a middle name, or even part of the patient’s first name.

Difficulty of Filling out Claim Forms with Misspelled Names:

When the customer’s name is misspelled on the insurance card, many well-meaning office staff members at small physician’s offices immediately think to submit the claims form with the correct spelling. However, if you do that, your claim will automatically be rejected by the patient’s carrier whether the patient has private insurance, Medicare or Medicaid

Therefore, most medical billing professionals actually recommend submitting the claim using the incorrect spelling, and then contacting the customer to let them know that they need to contact their insurance carrier to make a change.

When it comes to misspelled names on insurance cards, the inordinate amount of time it takes for the staff at a small physician’s office to clarify the error and figure out what to do will inevitably interfere with the practice’s billing efficiency. If your staff makes the wrong choice and the claim is rejected, it will automatically increase your AR days.

Of course, you may also run into trouble if the patient has already realised the error and contacted their insurance carrier to have the name misspelling changed in the carrier’s system, but without changing their insurance information at your practice.

But even if your staff ultimately makes the right choice, the confusion will have drained valuable time and resources, and possibly caused them to fall behind on other patient billing. Once that happens, it can be hard to get back on track, indefinitely slowing down your revenue cycle.

To avoid like name misspellings on insurance cards, you might want to think about outsourcing your medical billing to professionals. The experts at WWS are well equipped to handle these complex problems, allowing health care professionals to focus on what they do best.  Request us a Live demo http://localhost/main-site-update/live-demo/ for more information!

Leave A Comment