Allscripts Credentials

2020-09-04

Background

The Allscripts-Cardio EMR interface makes calls into Allscripts webservices. For that to work, the interface app has credentials (a username and password) that need to be valid. These credentials expire, normally every 6 months.

As of 1/1/2020, Allscripts has new security requirements that made it necessary to modify the interface application. To enforce those new security rules, Allscripts has blocked the ability to create new app credentials. From Allscripts’ perspective, that is a good way to ensure that apps that don’t get updated will automatically stop working.

A new revision of the Allscripts-Cardio interface was developed, version 1.4.0.1, that implements the new security requirements. The changes are mostly invisible to the user, except that the “Test” button on the configuration UI now requires the user to input an Allscripts user account and password. Note that this is separate from the interface app credentials which are invisible to the user.

Issues (may apply to CardioPerfect, CC, or DCS)

On Wednesday 2020-09-02 early AM, the new Allscripts-Cardio interface version 1.4.0.1 was pushed out through PartnerConnect. We have received several calls since then about the Allscripts interface not working.

1.       Invalid Credentials

The push out through PartnerConnect will have updated the interface apps on the customer’s machines. That should have left the interface app credentials intact. Yet, some customers are reporting issues with the crendentials. Most likely, the credentials were somehow wiped out from the registry.
If you encounter this, please take a screenshot of the allscripts interface app settings in the registry and attach to the service notification:

HKEY_LOCAL_MACHINE\\SOFTWARE\\Welch Allyn\\Allscripts Unity\\CardioPerfect

Or

HKEY_LOCAL_MACHINE\\SOFTWARE\\WOW6432Node\\Welch Allyn\\Allscripts Unity\\CardioPerfect

Then to correct the credentials, follow the “Manual Credential Delivery” section of TSB 20014495, page 17.

NOTE: The part of the TSB that describes how to obtain the credentials is broken. Obtain the CPWS.reg file from here instead. Carefully read the TSB instructions – simply double-clicking the .reg file will not be good enough on an x64 machine!

2.       Error when launching the interface from within the EMR: there is no endpoint listening.

This means that the URL that is set up in the interface app to talks with Allscripts is incorrect.  
It is not expected that installation of the interface app will modify the URL setting. One example from an account that was escalated, had what appears to be an extra “/unityservice” at the end of the URL. These URLs normally end in “UnityService.svc”.
It is unlikely that our installation process would have added “/unityservice” to the existing URL.

3.       Error when launching the interface from within the EMR: several other causes.

Contact Frits Kroon on TEAMS, if available, for assistance troubleshooting while you’re in the customer’s system

In all cases, create an escalation in TFS so we can properly track this issue and have R&D engaged.

Note that only the Allscripts-Cardio interface app was pushed out; no new credentials were pushed out yet. That will likely happen within a few weeks. The current credentials expire on 9/15, but will be extended for some additional amount of time in the next few days so we have a chance to stabilize the situation.