Health Product Dashboard

Last updated on May 23rd, 2018 at 05:42 pm CT

Now In-Process – All Experian Health’s Financial Products, TLS 1.2 Security
Immediate Action Required – PCI Compliance and TLS 1.2 Security Deadlines
This week, we will be continuing to block all non-TLS 1.2 connectivity from our financial products.
The next scheduled cut-over is Friday, May 25, starting at 8:00a.m. CST.  OneSource applications will be first, then followed by eCareNEXT.  Previous issues identified on May 4th have been resolved. We will continue testing both internally as well as with selected clients.

TLS 1.2 Compliant Security and Connectivity is required for all Experian Health’s domains and products. In the event your location has not been able to meet the previous deadlines, please immediately reach out to us at customer.support@experianhealth.com so that we can audit the progress of your required upgrades.  Tomorrow, Friday, May 25, 2018, Experian Health will continue to enforce TLS 1.2 Security for our Financial Product applications. 

[05.17.2017]
Now In Process – TLS 1.2 Security, All Experian Health’s Financial Products
Immediate Action Required – PCI Compliance and TLS 1.2 Security
In the event your location has not been able to meet the previous deadlines, please immediately reach out to us at customer.support@experianhealth.com so that we can audit the progress of your required upgrades.

 All Experian Health’s Financial Products – TLS 1.2 Security Deadline
Due to PCI Compliance and TLS 1.2 Security Requirements, clients or end users who process payments using any of our Financial Products (PaymentSafe, Link2Gov or L2G, Concord/First Data, Patient Self-Service, Cash Tracking) must complete the following actions.  In consideration of the efforts being made by our clients to achieve compliance, please be advised of the following:

• Internet browsers must be TLS1.2 compliant.
• Whitelisting of Domains and IPs need to be Added or Updated.
• NextBar and PIC updates must be updated by June 30, 2018

Inform and communicate with your IT Staff and/or Network Administrators, to ensure that each of the following URLs and IP addresses are included and/or added in your Network Configuration and “Whitelisted” for any of your network proxy servers and firewalls.  To avoid any service disruptions in the near future, and/or end-user access, please complete these actions.

URL/Domain – paymentsafe.experianhealth.com
Whitelist IP Range – 199.96.232.175/199.96.233.175

URL/Domain – collections.ecarenext.com
Whitelist IP Range – 199.96.232.176/199.96.233.176

Non-Financial Products by June 30, 2018
Clients who use our Non-Financial Products, must complete their upgrades by: June 30, 2018

• Browsers must be TLS1.2 compliant by 6/30
• NextBar and PIC updates must be updated by 6/30

Download – TLS 1.2 Readiness Document
Includes Instructions, Checklist, FAQs, Compatibility, and Product Testing

Product Specific Actions Required for TLS 1.2 Deadlines

eCare NEXT Bar and IntelliSource (PIC)
In addition to enabled TLS 1.2 Internet Browsers, eCare NEXT (Click-Once, MSI, IPS), IntelliSource, and Medical Necessity clients must upgrade their applications. Instructions for enabling and testing TLS 1.2 can be downloaded in our TLS 1.2 Readiness Document, that provides Checklist, FAQs, Compatibility, and Product Testing.

• If you have Financial Products –
  Please immediately upgrade your Internet browser and NextBar/PIC.
  
• If you don’t have Financial Products –
  Your Deadline is June 30, 2018 to Upgrade Your Browser and NextBar/PIC.

Medical Necessity
Use this link to download the TLS 1.2 requirements and upgrade instructions for the
Medical Necessity – Thin Client.  This is only for clients who use the Legacy Order Checker application (a/k/a Healthworks and IntelliSource Medical Necessity). This update does not apply to clients who use Order Checker within their eCare NEXT platform.

[Previously post of 05.04.2018]

NOTICE – All Experian Health’s Financial Products
TLS 1.2 Security Deadline, Today,
Friday, May 4, 2018 at 8:00a.m. CT

Immediate Action Required – PCI Compliance and TLS 1.2 Security Deadlines, Tomorrow
In the event your location cannot meet these deadlines, please immediately reach out to us at customer.support@experianhealth.com so that we can audit the progress of your required upgrades.

All Experian Health’s Financial Products – TLS 1.2 Security Deadline
Due to PCI Compliance and TLS 1.2 Security Requirements, clients or end users who process payments using any of our Financial Products (PaymentSafe, Link2Gov or L2G, Concord/First Data, Patient Self-Service, Cash Tracking) must complete the following action.  In consideration of the efforts being made by our clients to achieve compliance, please be advised of the following:

• Browsers must be TLS1.2 compliant by 8:00a.m. CT, May 4, 2018.
• Whitelisting of Domains and IPs need to be Added or Updated by 8:00a.m. CT, May 4, 2018.
• NextBar and PIC updates must be updated by June 30, 2018

Inform and communicate with your IT Staff and/or Network Administrators, to ensure that each of the following URLs and IP addresses are included and/or added in your Network Configuration and “Whitelisted” for any of your network proxy servers and firewalls. To avoid any service disruption and/or end-user access, please complete this action prior to 8:00a.m. CT, Friday, May 4, 2018.

URL/Domain – paymentsafe.experianhealth.com
Whitelist IP Range – 199.96.232.175/199.96.233.175

URL/Domain – collections.ecarenext.com
Whitelist IP Range – 199.96.232.176/199.96.233.176

Non-Financial Products by June 30, 2018
Clients who use our Non-Financial Products, must complete their upgrades by: June 30, 2018

• Browsers must be TLS1.2 compliant by 6/30
• NextBar and PIC updates must be updated by 6/30

Download – TLS 1.2 Readiness Document
Includes Instructions, Checklist, FAQs, Compatibility, and Product Testing

Product Specific Actions Required for TLS 1.2 Deadlines

Care NEXT Bar and IntelliSource (PIC)
In addition to enabled TLS 1.2 Internet Browsers, eCare NEXT (Click-Once, MSI, IPS), IntelliSource, and Medical Necessity clients must upgrade their applications. Instructions for enabling and testing TLS 1.2 can be downloaded in our TLS 1.2 Readiness Document, that provides Checklist, FAQs, Compatibility, and Product Testing.

• If you have Financial Products –
  Your Deadline is 8:00a.m. CT May 4, 2018 to Upgrade Your Browser and NextBar/PIC.
• If you don’t have Financial Products –
  Your Deadline is June 30, 2018 to Upgrade Your Browser and NextBar/PIC.

Medical Necessity
Use this link to download the TLS 1.2 requirements and upgrade instructions for the
Medical Necessity – Thin Client.  This is only for clients who use the Legacy Order Checker application (a/k/a Healthworks and IntelliSource Medical Necessity). This update does not apply to clients who use Order Checker within their eCare NEXT platform.

[Previously Posted]

Soon Approaching – TLS 1.2 Security Deadlines
Again, we want to remind you about our ongoing TLS 1.2 project and to ensure you are aware that this initiative requires your immediate attention.  Experian Health is focused on helping our customers improve their security by using the latest security protocols. At Experian Health, we take the protection of our customer’s data very seriously.

(Previous Posts - References)
Originally Posted: March 1, 2018 - Attention:  TLS 1.2 Security Deadline, April 2, 2018 – Take Immediate Action 
Originally Posted: Feb. 21, 2018 - Attention:  Immediate Action Required – TLS 1.2 Security Deadline – April 2, 2018
Originally Posted: Feb 15, 2018 - Initiation of TLS 1.2 Browser Notification Message - Thursday, February 15, 2018  
Originally Posted: Jan. 19, 2018 - Attention: Immediate Action Required – TLS 1.2 Security Deadline – April 2, 2018
Originally Posted: Sept. 02, 2017 - Immediate Action Required – TLS 1.2 Security Requirements Deadline –  April 2, 2018  

Last updated on May 23rd, 2018 at 01:09 pm CT

[05.23.2018]
QualCare continues to have some performance issues. If you are sending transactions for Members whose ID begins with an M, you may see a change in the response that does not include as much benefit information. We continue to work with the payer to resolve these issues.

[05.22.2018]

Unscheduled Maintenance – QualCare, May 22, 2018,  7:00p.m.-7:00a.m. CT (5/23)
We have been notified that QualCare will be conducting unscheduled maintenance tonight, May 22, 2018,
between 7:00p.m. – 7:00a.m. CST (5/23).  We apologize for any inconvenience this may cause.

Last updated on May 21st, 2018 at 08:53 pm CT

On Wednesday 5/23/2018, Sprint Release 7.1 will be deployed to Production. Detailed documentation of the changes are posted on the application home pages. We also wanted to remind you via this dashboard post of the important changes and updates, and ask that you please refer to the Highlights document for complete details.

Sprint Release 7.1 Highlights

Multiple Applications – Enhancements

• Report Selection Streamlining
• GPCI Selection Enhancements

Contract Manager for Medical Groups – Enhancements 

• New Cigna HealthSpring Payment Dispute Form   
• New UnitedHealthcare Community Plan Claim Reconsideration Request Form
• Updated Amerigroup Medicaid Appeal Form 
• Undercharges Summary Report 
• Self-Service Contract Maintenance  
• Bilateral Logic Update

Contract Manager for Hospital and Health Systems – Enhancements

• Present on Admission (POA) Indicators
• Added Workflow Reason for Rounding 
• Accommodate up to 4 Modifiers 
• New Detail Selected Claim Print Option 
• Batch Import Carveouts 
• Import/Export ASC Groupers 
• DRG High and Low Trim points 
• Copy Contracts Updates

Contract Analysis for Hospital and Health Systems – Enhancements 

• Result Summary by Account Report

Claim Scrubber – Updates and Enhancements

• Change Frequency Limit Over Time for Medicare 
• Frequency Limit Over Time for Commercial 
• Display Disabled Edits Option 
• New Edit for Diagnosis Primary Position Review 
• Test Scrub within the Portal 
• Global Period Logic for CPT 99024

Last updated on May 23rd, 2018 at 05:44 pm CT

[Updated 05.23.2018]  As previously published, we have extended our migration schedule for another week.  Please take note of our new schedule below as indicated in blue.

[Updated 05.14.2018]  As previously published, we have extended our migration schedule for another week.  Please take note of our new schedule below as indicated in blue.

[Updated 05.07.2018]  As previously published, we have extended our migration schedule for another week.  Please take note of our new schedule below as indicated in blue.

Important Notification – Datacenter Migrations, Products – Rescheduled June 7, 2018
Experian Health will be moving systems located in our Plymouth, Minnesota datacenter to a new datacenter in Brentwood, Tennessee.  The Datacenter Migration Project represents an upgrade with increased capacity and a more robust production environment. This will result in an improvement in our ability to manage growth and more tightly integrate with other Experian Health products. Future migrations will require special maintenance periods for the following products:

• Thursday, June 7, 2018 – From 8:00 p.m. CT to 2:00 a.m. CT.  June 8 (approx. 6 hours)
  Our Identity Verification, Patient Financial Clearance, Return Mail, and SkipTracing products will be unavailable.
  

You will receive further details as we get closer to the migration dates for each of these products. We appreciate your patience. Updates when available, will be posted on our product dashboard.

Important Notification – VPN Migrations, Connectivity –  June 2018
All client VPNs will be migrated as part of this process. Client Services personnel are actively reaching out to client technical contacts to schedule meetings to discuss this change.

• This process needs to be completed by Tuesday, June 5, 2018.
  Failure to provide access to needed technical resources may result in a service outage.

 In order to maximize efficiency and reduce risk throughout the process, we will implement new tunnels so that services may be thoroughly tested without interrupting production traffic.  Once connectivity has been tested, cutover to the tunnel may be scheduled to meet your organizations change control or usage requirements.  Please notify all users, managers, and IT teams directly involved with the service before performing the cutover.

While Experian Health resources are not required for the final cutover, staff will be available for assistance as needed. If you plan to make the final cut over after hours please let us know so that we may notify on-call staff to be available in case of problems.  If you have immediate questions, please contact us at ehcmgqueue@experian.com.

Last updated on May 11th, 2018 at 02:57 pm CT

“Due to an internal system outage which occurred on 5/7/18, ERA delivery for the following payers may be delayed:

•             Anthem BCBS of VA
•             Palmetto Home, Health & Hospice
•             Palmetto Railroad
•             KY Medicare Parts A and B
•             NC Medicare Parts A and B
•             OH Medicare Parts A and B

We’ll update this post once we’ve verified that all ERA files have been delivered.”

Last updated on May 9th, 2018 at 03:39 pm CT

[05.09.2018]
This update only pertains to real-time transactions.   It does not pertain to Batch Claim and ERA file transfers.

WPS Real Time processing is currently functional to a certain degree of operability. Their teams have made numerous updates to their systems and they have shown some improvement.  They are continually working towards getting real-time at complete operability with minimal errors.  We will communicate any updates as needed going forward to complete resolution.

Impacted Services Include:

• Real Time 270/271 transaction
• Real Time 276/277 transaction

Affected Payers/Lines of Business

• TRICARE For Life
• TRICARE Overseas
• TRICARE East
• ARISE Health Plan
• WPS Health Insurance
• VAPC3 (276/277 only)

[05.01.2018]
Experian Health has now downloaded and processed all files made available to us by WPS.  We’ve determined that there are still some ERA files which we do not have and WPS is working to locate those which remain missing.  Connectivity for all lines of business has been fully restored and claims are no longer being held.  We’ll continue to provide updates as things progress.

[04.27.2018]
WPS was able to restore partial connectivity with Experian.  As such, WPS has begun the process of reposting all missing ERA files and Experian is processing these files as they’re received.  WPS will continue to work throughout the day to deliver all missing  ERA files and any new files we receive will be processed upon receipt.  Efforts continue to restore connectivity for claim submission and responses.

[04.25.2018]
WPS continues to experience connectivity issues with its new Gateway.  Experian Health is working with WPS to identify an alternate method for transmitting/receiving files until WPS can stabilize the Gateway.  Providers may continue to submit claims to us; however, the claims will be held until WPS restores connectivity.  We’ll continue to provide updates as things progress.

[04.24.2018]
WPS is experiencing connectivity issues which is impacting claim submission, claim responses, and ERA file delivery for the following payers.  WPS is aware of the issue and is working toward resolution;  however,  no ETA has been provided.

• Tricare:  Tricare East, Tricare for Life, and Tricare Overseas
• TriWest VAPC3:  Regions 3, 5A, 5B, and 6
• Medicare:  Nebraska, Michigan, Missouri, Kansas, Iowa, Indiana, Part A National

Last updated on April 17th, 2018 at 03:45 pm CT

Delaware Medicaid (DMAP) – Claims
Attention:  All Providers
Claims currently suspending due to new 2018 Healthcare Common Procedure Coding System (HCPCS) codes.

• DMAP is in the process of updating the new 2018 HCPCS codes with an effective date of 1/1/2018.
• DMAP will be processing these suspended claims in the near future.
• Claims included in this process are for dates of service beginning January 1, 2018 and forward.
• This information will appear on a future Remittance Advice (RA).
• There will be further communication regarding the timing of this update for dates of service 1/1/2018 and forward.

Last updated on April 11th, 2018 at 10:36 am CT

As you are aware, the HSN Server upgrade began in March to comply with the Massachusetts Executive Office of Technology Services and Security requirements.  HSN has recommended that  facilities continue the submission of claims during this Server upgrade.  Facilities should continue submitting all 837I, 837P, 837D and POPS claims as well as Emergency Room Bad Debt (ERBD) recoveries and Free Care Endowment Income when applicable.

In addition, facilities are asked to use this time to work with the HSN Operations team to resolve any outstanding claims processing issues and/or HSN denials.  Any questions can be directed to the HSN Helpdesk via email or by calling (800) 609-7232.

Last updated on April 16th, 2018 at 01:55 pm CT

See Also  – Tricare, Message in Error – Primary Payer is Tricare East Contractor – 04.16.2018

Tricare West recently made a change to their eligibility system. They will no longer return eligibility for members outside of the west region. The response for these members will contain the message below.

“PRIMARY PAYER IS TRICARE EAST CONTRACTOR”

Eligibility requests for these members will need be directed to Tricare East. The mapping for that payer is TRICARE-East.  Please contact customer support if you have any additional questions regarding this message.

customer.support@experianhealth.com.

Last updated on March 30th, 2018 at 01:56 pm CT

Contact Health Safety Net for any questions or concerns.  800-609-7232 or HSNHelpdesk@state.ma.us

Reporting of Primary Payer(s)
This HSN Billing Update Affects All Providers Who Submit 837I & 837P (Read Detailed Notice)
Reporting of Correct Primary Payer Carrier Code on HSN Secondary Claims…
Effective for HSN claims submitted on or after August 15th 2018, HSN has implemented a new reporting requirement as it relates to HSN Claims where HSN is not the primary payer….

Reminders:
Important Health Safety Net Billing Updates – March (Read Detailed Reminders)

• Behavioral Health Meds Management at CHC’s:  Effective January 1st 2018, New 99484 HCPC code….
• HSN Eligibility Denials in December and January:  Providers may have received eligibility denials….
• CAS Code 167 and $0 payments:  HSN noted for MH Limited 837I & 837P claims containing….
• HSN 837I Partial Claims:  For 837I claims, providers report remaining HSN Deductible….
• HSN 837P Partial Claims:  For 837P claims, providers should report….
• MassHealth Prime, HSN Secondary Claims:  For the lines paid by MassHealth because…..
• Community Health Center Covered Codes:  Covered Codes download…
• HSN Helpdesk requests for “Claim Status”:  HSN will no longer supply “Claim Status”….
• HSN Interim Payments:  Providers are reminded HSN will…
  (Important:  HSN Payment (Remits) and denials (Validation Reports)
• FY 2016 Closing:  FY16 will be closing September 30, 2018….
• HSN Secondary Claims: Providers are reminded HSN process payment….

Last updated on May 23rd, 2018 at 04:50 pm CT

[05.23.2018]  Now In-Process
The New Medicare Beneficiary Identifier (MBI) project is now in process.   Please feel free to reach out and voice your concerns to CMS (below) or if you have specific questions, our customer service team.

[04.04.2018]
If you would like to voice your concerns to CMS Regarding the New MBI Project, please click below.
Experian Health – Voice Your Concern to CMS About New MBIs – 04.04.2018

[March 29, 2018]
April 2018 – New Medicare Beneficiary Identifier (MBI) – Update, 03.29.2018  
As the April, 2018 approaches, please click this headline and review the information posted on our product dashboard under the New Medicare Beneficiary Identifier (MBI) April 2018.   Experian Health is ready to accept both the HICN and MBI in the X12 270/271 Transactions (Eligibility Inquiry/Eligibility Response).  A new “My Response” coverage banner will also be added to within OneSource and eCareNEXT,   Within the returned 271 Eligibility Response, we will return the message segment:

“CMS mailed a Medicare Card with a new Medicare Beneficiary Identifier (MBI) to the Member”

For Premium EDI clients, we have created an Epic EDI alert that will return the same message. (Similar to when a patient has limited coverage, or a Medicare Advantage/Medicaid MCO.)
Please Note:  CMS will only return that message for beneficiaries that have traditional Medicare. If they’re enrolled in a Medicare Advantage plan, Medicare will not return this information.

(Previous Post - Reference)
Last and Previous Posts: March 22, 2018 - Reminder – New Medicare Beneficiary Identifier (MBI), April 2018 – Update 
Last and Previous Posts: March 9, 2018 - New Medicare Beneficiary Identifier (MBI), April 2018 – Update

[March 22, 2018]
Reminder, Soon Approaching – Medicare Beneficiary Identifier (MBI) Deadline, April 2018
As the April, 2018 Deadline approaches, please review this information we have posted.

Experian Health is ready to accept both the HICN and MBI in the X12 270/271 Transactions (Eligibility Inquiry/Eligibility Response).  Within the returned 271 Eligibility Response, we will also return the message segment:

“CMS mailed a Medicare Card with a new Medicare Beneficiary Identifier (MBI) to the Member”.

[March 9, 2018]
As we prepare for the upcoming changes in the Medicare Beneficiary Identifier we wanted to share some additional information.

If an HICN is sent in the 270, and the HICN is returned in the 271, and the Medicare Beneficiary’s new ID card has been mailed, then CMS will return in the 271 message segment, “CMS mailed a Medicare card with a new Medicare Beneficiary Identifier (MBI) to this beneficiary.  Medicare providers, please get the new MBI from your patient and save it in your system(s).”

This response will only be returned if :

• The beneficiaries is enrolled in traditional Medicare. Beneficiary’s ENROLLED IN A MEDICARE ADVANTAGE PLAN will not have this message as they will receive all identification information from the Medicare Advantage plan’s ID cards.
• The beneficiary does not have a date of death on file.

As a reminder the MBI will be included in the 835.

Experian Health is working with CMS on some modifications to help you with these changes and will share details in the next 5-10 business days.

[January, 26, 2018]
We wanted to provide a brief update on the changes that Medicare will be making in April as it relates to the new Medicare Beneficiary Identification (MBI). Experian Health is working closely with Medicare on this change and how electronic data exchange, 270/271 will work. Our Clearinghouse and products will be ready to support both the existing HICN and new MBI by the April 1 2018 go live date.  Important items to know:

• CMS has stated that there will be no testing of the new MBI format.
• For 18 months you will be able to send either HICN or MBI. Whichever number you send we will pass to Medicare. Medicare will only respond with the number that was sent. Medicare will not respond with both numbers.

We will continue to provide additional status updates.

[August 17, 2017]
Coming in April 2018: New Medicare Card – New Number
Background:
Medicare is taking steps to remove Social Security numbers from Medicare cards. In April 2018, people with Medicare will begin receiving new Medicare cards, replacing all cards by April 2019. These cards will have a Medicare Beneficiary Identifier (MBI) number that is randomly generated with “non-intelligent” characters. Once this change is effective, scheduled for April 2018, we will modify search criteria to support the new MBI. The transition period where both MBI’s and HICN numbers will both be available is now schedule to be for a 21-month period

New Information:
Beginning April 2018, and throughout the 21-month transition period Experian will be supporting both the current HICN and the new MBI formats. Search options will allow for both ID’s. CMS advised us that if you use the HICN number the HICN number will be returned. If you use the MBI the MBI will be returned. They will not be returning both numbers in one transaction/response.

Railroad Retirement Board (RRB) Medicare claims to the RRB Specialty Medicare Administrative Contractor, Palmetto GBA, will notice a change with the new cards:

• Providers will no longer be able to distinguish people with Railroad Medicare by the number on the card.
• The RRB will continue to send cards with the RRB logo to people with Railroad Medicare.
• CMS will return a message on the eligibility transaction response for a Railroad Medicare patient. The message will say, “Railroad Retirement Medicare Beneficiary” in  271 Loop 2110C, Segment MSG.

[May 31, 2017]
Below is an announcement that CMS released today. In order to provide you the most current information on the MBI change we will continue to update this post as we receive more information from CMS. Once this change if effective, scheduled for April 2018, we will modify search criteria to support the new MBI. The transition period where both MBI’s and HICN numbers will both be available is now schedule to be for a 21 month period.

New Medicare cards offer greater protection to more than 57.7 million Americans
New cards will no longer contain Social Security numbers, to combat fraud and illegal use  

The Centers for Medicare & Medicaid Services (CMS) is readying a fraud prevention initiative that removes Social Security numbers from Medicare cards to help combat identity theft, and safeguard taxpayer dollars. The new cards will use a unique, randomly-assigned number called a Medicare Beneficiary Identifier (MBI), to replace the Social Security-based Health Insurance Claim Number (HICN) currently used on the Medicare card. CMS will begin mailing new cards in April 2018 and will meet the congressional deadline for replacing all Medicare cards by April 2019. Today, CMS kicks-off a multi-faceted outreach campaign to help providers get ready for the new MBI.

“We’re taking this step to protect our seniors from fraudulent use of Social Security numbers which can lead to identity theft and illegal use of Medicare benefits,” said CMS Administrator Seema Verma. “We want to be sure that Medicare beneficiaries and healthcare providers know about these changes well in advance and have the information they need to make a seamless transition.”

Providers and beneficiaries will both be able to use secure look up tools that will support quick access to MBIs when they need them. There will also be a 21-month transition period where providers will be able to use either the MBI or the HICN further easing the transition

CMS testified on Tuesday, May 23^rd before the U.S. House Committee on Ways & Means Subcommittee on Social Security and U.S. House Committee on Oversight & Government Reform Subcommittee on Information Technology, addressing CMS’s comprehensive plan for the removal of Social Security numbers and transition to MBIs.

Personal identity theft affects a large and growing number of seniors. People age 65 or older are increasingly the victims of this type of crime. Incidents among seniors increased to 2.6 million from 2.1 million between 2012 and 2014, according to the most current statistics from the Department of Justice. Identity theft can take not only an emotional toll on those who experience it, but also a financial one: two-thirds of all identity theft victims reported a direct financial loss. It can also disrupt lives, damage credit ratings and result in inaccuracies in medical records and costly false claims.

Work on this important initiative began many years ago, and was accelerated following passage of the Medicare Access and CHIP Reauthorization Act of 2015 (MACRA). CMS will assign all Medicare beneficiaries a new, unique MBI number which will contain a combination of numbers and uppercase letters. Beneficiaries will be instructed to safely and securely destroy their current Medicare cards and keep the new MBI confidential. Issuance of the new MBI will not change the benefits a Medicare beneficiary receives.

CMS is committed to a successful transition to the MBI for people with Medicare and for the health care provider community. CMS has a website dedicated to the Social Security Removal Initiative (SSNRI) where providers can find the latest information and sign-up for newsletters. CMS is also planning regular calls as a way to share updates and answer provider questions before and after new cards are mailed beginning in April 2018.

Last updated on March 27th, 2018 at 09:00 am CT

Dear Trading Partners,

Federal regulation CMS-6010-F and 42 CFR Parts 424 and 431, Section 2 requires all providers providing services to Ohio Medicaid consumers be reported on the claim(s).  Beginning on July 1, 2018,  all Clinic and Freestanding Birthing Center (FBC) claims will be required to include the individual Rendering provider NPI.

If your company represents the following provider types: FQHCs (PT 12), RHCs (PT 5) , OHFs (PT 4), AHCCs (PT 50), and FBCs (PT 11)  please take the necessary steps to begin including the individual rendering provider NPI on these claims at your earliest convenience.  All individual providers MUST be enrolled with Ohio Medicaid for claims to be adjudicated and paid appropriately.

If your providers have questions about their provider type, please have them call provider enrollment at 1-800-686-1516.

Last updated on May 22nd, 2018 at 10:05 am CT

[05.22.2018]  This issue has been resolved.

[05.18.2018]
We are currently experiencing a downtime with United Healthcare impacting Notice of Admission. We are working towards a resolution and will update this posting as an ETA becomes available. We apologize for any inconvenience.

Last updated on May 21st, 2018 at 02:47 pm CT

[05.21.2018]
Cigna has indicated that all impacted remits have been resolved.

[05.17.2018]
Cigna has found a solution to better replay the impacted remit volume more efficiently.  Check date 5/7 has been completed. Cigna continues to work through the remaining backlog for check dates 5/1 – 5/5 and will provide an update when completed.

[05.10.2018]
CIGNA has advised that the delayed ERAs are specific to check dates beginning 5/1/18 to present.
They’re working now on getting these regenerated and delivered.

[05.09.2018]
Please be aware Cigna is experiencing a delay in some 835 remittance advice transactions. Cigna is aware of the issue and will provide updates when available.