💡 Response Needed- Epic EHR fix to eliminate sending resolved problems in case reports
CSTE is requesting Public Health Agencies (PHAs) indicate their preference for a solution to the issue of sending historical data from EPIC EHRs. Epic has identified a potential solution that could be implemented nationally which would address the presence of historical data in Electronic Initial Case Reports (eICR).
Summary of issue:
- Epic EHRs use “resolved” problems to trigger eICRs but this results in the loading of “resolved” problems not relevant to current encounters in EHRs. This means: (1) an eICR may be triggered by a resolved problem to be sent to RCKMS decision support, or (2) the presence of resolved/ historical problems in the eICR problem list
- Epic has developed a solution that will only trigger and load active problems in the EHR; Epic instructed Healthcare Organizations (HCO) clients to ask PHAs if they want this solution implemented, and each HCO client may implement this solution individually, which is inefficient and slow
Epic may potentially apply this solution across all HCO implementations nationwide if PHAs collectively request the Epic solution to only trigger and load active problems in EHRs.
CSTE is requesting one response per PHA to the questions below about preferences to implement the Epic solution:
- Does your PHA want to receive information about resolved problems in eICR problem list entries? Yes/ No
- Does your PHA agree that the Epic solution to trigger and load only active problems in the EHR should be implemented broadly across all Epic HCO implementations nationwide? Yes/ No
- Note: If the solution is implemented, resolved problems in EHRs will not trigger eICRs and will not be present in eICR problem list entries
Note: Resolved problems are not used in RCKMS rules or decision support for reportability determination. However the upcoming timeboxing functionality will enable filtering of eICRs sent to PHAs based on active problem list entries within a specific date range. Timeboxing will not eliminate “resolved” problem list entries from eICRs.
Please reply to this thread with your responses to Questions 1 & 2 (above) by Wednesday, March 8, 2023.
Please reply to this thread with your responses to Questions 1 & 2 (above) by Wednesday, March 8, 2023.
1. No
2. Yes
1. No. CDPH does NOT want to receive information about resolved problems in eICR problem list entries.
2. Yes. CDPH agrees that the Epic solution to trigger and load only active problems in the EHR should be implemented broadly across all Epic HCO implementations nationwide.
For WI DHS:
1. No
2. Yes please.
1. No, Kentucky does not want to receive information about resolved problems in eICR problem list entries.
2. Yes, solution should be implemented broadly across all EPIC HCO implementations.
No – don’t want to receive information about resolved problems
Yes – agree to having solution implemented broadly
Deb
NO. AKDOP does NOT want to receive information about resolved problems in eICR problem list entries.
YES. AKDOP agrees that the Epic solution to trigger and load only active problems in the EHR should be implemented broadly across all Epic HCO implementations nationwide.
James Howard III
Program Coordinator I
Alaska Department of Health (AKDOH)
Division of Public Health – Epidemiology
I will admit that I/we have not thought this through completely for some diseases of long duration (TB...) but feel that the answer is likely to be true for those diseases as well.
Karla
1) No, we would not like to receive resolved problems
2) Yes, we would agree to a nationwide implementation
Thank you,
Sue
Indiana is in agreement with the comments in this thread.
1) No, we do not want to receive information about resolved problems
2)Yes, nationwide implementation would be preferable
Thank you,
Darren
1. No to receiving resolved problems.
2. Yes to nationwide implementation.
Thank you,
Lori
1. No
2. Yes
1. No
2. Yes
1. No, we do not want resolved problems in the eICR.
2. Yes, nationwide.
thank you,
Brenda Ryals
Programmer Analyst Senior
Bureau of Information Technology
Alabama Department of Public Health
1. No
2. Yes
1. No
2. Yes
1. No
2. Yes
1. No
2. Yes
1. No
2. Yes
[cid:image001.png@01D8E3C2.903395D0]
Angie McKee | Data Systems Manager
Missouri Department of Health and Senior Services
Division of Community and Public Health
Bureau of Data Modernization and Interoperability
P.O. Box 570, Jefferson City, MO 65102-0570
573-751-6146 | Angela.McKee@health.mo.gov<mailto:Angela.McKee@health.mo.gov>
Health.Mo.Gov
Working remotely each Monday, Wednesday, and Thursday
CONFIDENTIAL:
This electronic communication is from the Missouri Department of Health and Senior Services and is confidential, privileged and intended only for the use of the recipient named above. If you are not the intended recipient or the employee or agent responsible for delivering this information to the intended recipient, unauthorized disclosure, copying, distribution, or use of the contents of this transmission is strictly prohibited. If you have received this message in error, please notify the sender immediately at the following email address angela.mckee@health.mo.gov<mailto:angela.mckee@health.mo.gov> or by calling 573-751-6146. Thank you.
1. No
2. Yes
The Illinois Department of Public Health agrees with the rest:
1. Does your PHA want to receive information about resolved problems in eICR problem list entries? No
2. Does your PHA agree that the Epic solution to trigger and load only active problems in the EHR should be implemented broadly across all Epic HCO implementations nationwide? Yes
Thanks,
Matt
Matthew Leslie DVM, PhD
Statistical Research Specialist II
Office of Disease Control
Division of Infectious Disease
Illinois Department of Public Health
2121 W. Taylor St. #508
Chicago, Illinois 60612
Direct: 312-793-9062
Main: 217-782-2016
1) No, we would not like to receive resolved problems
2) Yes, we would agree to a nationwide implementation
Thank You,
Charleen
1) No.
2) Yes please.
1. No
2. Yes