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

Warning: Cannot modify header information - headers already sent by (output started at /home/linkenwd/wws.wonderws.com/wp-includes/functions.php:6131) in /home/linkenwd/wws.wonderws.com/wp-includes/feed-rss2.php on line 8
unique Medicare number – WWS https://wws.wonderws.com Empowering HME Providers Nationwide Mon, 09 Oct 2017 12:40:06 +0000 en-US hourly 1 https://wordpress.org/?v=6.9.4 CMS Reveals New Medicare Card Design https://wws.wonderws.com/2017/10/09/cmc-reveals-new-medicare-card-design/ https://wws.wonderws.com/2017/10/09/cmc-reveals-new-medicare-card-design/#respond Mon, 09 Oct 2017 12:40:06 +0000 http://www.wonderws.com/?p=6546 Today, The Centers for Medicare & Medicaid Services (CMS) gave the public its first look at the newly designed Medicare card. The new Medicare card contains a unique, randomly-assigned number that replaces the current Social Security-based number.

New Medicare Card Design

CMS will begin mailing the new cards to people with Medicare benefits in April 2018 to meet the statutory deadline for replacing all existing Medicare cards by April 2019. In addition to today’s announcement, people with Medicare will also be able to see the design of the new Medicare card in the 2018 Medicare

“The goal of the initiative to remove Social Security numbers from Medicare cards is to help prevent fraud, combat identify theft, and safeguard taxpayer dollars,”

CMS has assigned all people with Medicare benefits a new, unique Medicare number, which contains a combination of numbers and uppercase letters. People with Medicare will receive a new Medicare card in the mail, and will be instructed to safely and securely destroy their current Medicare card and keep their new Medicare number confidential. Issuance of the new number will not change benefits that people with Medicare receive.

Healthcare providers and people with Medicare will be able to use secure look-up tools that will allow quick access to the new Medicare numbers when needed. There will also be a 21-month transition period where doctors, healthcare providers, and suppliers will be able to use either their current SSN-based Medicare Number or their new, unique Medicare number, to ease the transition.

This initiative takes important steps towards protecting the identities of people with Medicare. CMS is also working with healthcare providers to answer their questions and ensure that they have the information they need to make a successful transition to the new Medicare number.

When you get your new card, we’ll ask you to safely and securely destroy your current Medicare card.  Make sure you bring the new card to your doctors’ appointments, and always keep your new number confidential.  This will help protect your personal identity and prevent medical identity fraud because identity thieves can’t bill Medicare without a valid Medicare number.

Additionally, you and your health care providers will be able to use secure online tools that we’re developing that will support quick access to your Medicare number when needed.

For more information, please visit: www.cms.gov/newcard

]]>
https://wws.wonderws.com/2017/10/09/cmc-reveals-new-medicare-card-design/feed/ 0