eCR/RCKMS Community of Practice

The purpose of the eCR/RCKMS Community of Practice Basecamp is to provide staff from state, local, territorial, and tribal public health agencies with a venue to participate in peer-to-peer discussions pertaining to using RCKMS. This Basecamp is not intended for formal communications about RCKMS or eCR and will not be moderated by CSTE staff. For technical issues or assistance with RCKMS, please visit www.rckms.org to submit a ticket. Disclaimer: The statements and responses posted on the eCR/RCKMS Community of Practice are solely the views of the authors and do not necessarily represent the official views of CDC or CSTE.

Have any PHAs requested the Epic fix to be implemented for eCRs?

Virginia would like to know if any PHA has requested any Epic facility to implement the Epic fix to only trigger eCRs based on active problems. If yes, would you be able to provide a high-level recap of what you have noticed? We would appreciate any feedback, as we are preparing to make the request to our HCO's. Thank you.

Comments & Events

Shaily Krishan, Program Manager at CSTE
Hi Steve, 

CSTE/ CDC/ APHL have also communicated with both Epic & Oracle Cerner to implement solutions to address the issues with loading & triggering eICRs using resolved problem list entries. 

We are following up with Epic again on the status of the solution, but would also be interested to hear if any PHAs have made the request & the response received.

As FYI:

Oracle Cerner has informed us that they have blocked resolved problems from triggering & loading eICRs, so hopefully jurisdictions are not seeing the issue in Cerner EHRs.
Ann Kayser
Hey Steve! This seems like a great question to have on CSTE Connect. Do you mind if I also post your question there?

In Minnesota we did have a few sites implement the Epic fix - one actually reached out to ask if we would like this implemented! It's harder to tell from the receiving side how successful the change went, but I did have a nice conversation with someone who monitors the eCR feeds that go through AIMS and they were able to indicate they could see a decrease in eICRs triggered to AIMS from that particular HCO.
James Howard, eCR Program Coordinator at Alaska Department of Health and Social Services
Alaska did an Epic Go-Live 11/2022. I had heard a setting existed to limit eICR generated from the Problem List and inquired with the Regional Providence team. This was their response:

"I think you are talking about this setting: 'Set profile variable CDA_SEND_FULL_PROBLEM_LIST (6339) to 0-False to prevent extraneous problems from being sent.'  If so, we already have this SU and set it to false in production on 10-31-22.  Please let us know if you have any questions."

We were then able to contact other HCOs using Epic and have them confirm this setting was set to False. We had 2 additional Epic Go-Lives in 2022. Our Go Live experiences were similar to the 1st Go Live. No issues to report.

I can't say how much this setting change reduced extra eICR numbers because I didn't have legacy data to compare it to. The Epic setting change was so close to the Go-Live date (2 days before) we just proceeded to our data validation process & never looked back. 
Steve Barber, eCR Coordinator
Ann,

Please feel free to post the question on CSTE Connect.

Kind regards,


Steve Barber
eCR Coordinator
Division of Informatics and Information Systems (DIIS)

Mobile (804) 584-8413
S.Barber@vdh.virginia.gov

Facebook<http://www.facebook.com/VDHgov> | Twitter<https://twitter.com/vdhgov> | YouTube<https://www.youtube.com/channel/UCKhLlujgbrx7hsyH5cXTnKQ> | LinkedIn<https://www.linkedin.com/company/virginia-department-of-health>

Virginia Department of Health
109 Governor Street
Richmond, VA 23219

[VDH logo 36px]<https://www.vdh.virginia.gov/>

Please do not reply to this email with any protected health information or patient identifying information. This includes: name, phone number, date of birth, address, and medical record number. Please call my confidential line at (804) 584-8413 to coordinate this exchange. Thank you.