Centricity Common Event Model (CEM) returning 500 internal server error

Question

The call to the Common Event Model (CEM) is returning a "500 Internal Server" error. What is the cause and how can I resolve this.

Answer 1

The "500 Internal server" error can mean several things. Here is a list of the common issues and what to check.

 

1. If the user configured on the webservice in Qvera (default user is "qieuser") does not exist.
2. The password configured on the webservice in Qvera (default user is "qieuser") is incorrect. 
3. The subscription name is wrong or missing:
   • CQR name is "Clinical Quality Measures Reporting"
   • Immunization name is "Immunization Registry"

 

To test scenario 1 and 2 from above: Ask the customer to log on to the CPS application using that user.  You may get a security challenge that the user does not have access to the main menu but that tells you that the username and password is correct.

To verify the subscription: Verify the subscription is imported into EMR or Centricity. See below for the location for each.

• EMR: Setup -> Settings -> Interoperability -> Configuration
• CPS: Administration -> System -> Interoperability -> Configuration

 

Answer 2

If the issue is the user and password you will get a "Fault String: User account is locked"

In this case you will need to stop any channel that is running and that uses that user and password in QIE. Then you can unlock the user in Centricity. Now that you can log into Centricity with that user you should start up the channels in QIE.

If the QIE channels are not stopped before you change the password then the user will get locked again because the channels are continuously trying to connect to Centricity.