Release Date:
Thursday, December 10, 2015 at 10:00p.m. CT
Change Overview:
eCareNEXT Bar Update
Users will be prompted to download a new version of the NEXT Bar beginning on Friday, December 11, 2015. The new version does not change the functionality or appearance of the NEXT bar. The only noticeable change is to popup a warning message when an IP range is enabled, but is not recognized. This feature will be turned off by default.
Epic Alerts Deployment – This Week, December 10th
This Thursday evening, December 10th, we will be making the following adjustments to NEBO alerts:
- We will be changing the verbiage of NEBO0043 from “IPA/Group Name:{1}” to “Medical Group IPA:{1}” to better reflect the information being returned in the alert.
Current NEBO0043: “IPA/Group Name: {1}”
Future NEBO0043: “Medical Group IPA: {1}”
Epic Alerts Deployment – Next Week, December 17th
Next week, our Epic Alerts Deployment will include:
- We will be adjusting the logic in NEBO0005: Patient Birth Date Does Not Match That for the Patient on the Database to look at the DOB submitted in the request and comparing what is returned in the 271. Additionally the verbiage will be updated to “DOB in Reg does not match DOB in eligibility.” This change is to better reflect the original goal of the alert. Current NEBO0005: “Patient Birth Date Does Not Match That for the Patient on the Database” (Looking for existence of AAA*71) Future NEBO0005 “DOB in REG does not match DOB in ELIG” (Looking at DOB in the request and comparing to DOB in the payer response)
- We will be retiring NEBO0512: DOB in REG does not match DOB in ELIG. This is to reduce redundancy.
- We will be retiring NEBO0004: DOB in REG does not match DOB in ELIG: MM/DD/YYY. This is to reduce redundancy.
- We will be retiring NEBO0122: DOB in REG does not match DOB in ELIG. This alert was specific to IL Medicaid, however NEBO0005 will be bringing forward this information and NEBO0122 will no longer be needed.
If you have an Epic build that depends on these alerts you will need up update that build accordingly.
Reminder – TLS Transaction Encryption
Passport will prohibit access to products using TLS 1.0 as of April 1st, 2016. Vulnerabilities have been identified with TLS 1.0 and we are urging customers to configure their browsers to support TLS 1.1 and/or TLS 1.2 as soon as possible. Internet Explorer 11.0 is preferred as Support for TLS 1.1 and 1.2 is enabled by default, but we will continue to allow IE 8.0 as long as TLS 1.1 and TLS 1.2 are enabled. Please note that IE Versions 8, 9 and 10 do not have TLS 1.1 and 1.2 enabled by default and must be configured. We encourage you to make certain this is communicated to your IT department as soon as possible. Chrome, Firefox, and Safari will run most Passport applications, but not all and therefore not recommended. We apologize for the short notice, but it is in our mutual best interest to eliminate this security weakness as soon as possible. For details about our Passport Products, Browser, Hardware, and Security Requirements hardware requirements, click here.
Special Notes:
Weekly Deployment Schedule:
Passport’s weekly application deployment is between 8:00p.m. and 10:00p.m. CT every Thursday night. However, our deployment process typically results in no customer impact or downtime. If we suspect a change will impact customers, we will communicate forty-eight hours in advance. The hardware and systems maintenance follows the application deployment Thursday nights from 10:00p.m. to 12:00a.m. CT. During this window customers may experience intermittent processing issues.
Previous Deployment Detail:
You may view previous deployment notes on the Passport product dashboard located at http://www.passportproductdashboard.com.
