0700-0800 hours CST
|Anupam Goel (corporate)||Sakhie Hussain (Trinity)|
|Chris Jamerson (Children’s)||Kris Kardasis (South Suburban)|
|Sudha Kumien (Advanced Practice Registered Nurse, Cardiology)||Elliot Levine (Illinois Masonic)|
|Shilpan Patel (Good Shepherd)||Natalie Selk (Christ)|
|Suneel Udani (Good Samaritan)|
Migrating from Cerner/Allscripts to Epic
Advocate is currently in contract negotiations with Epic. The contract is expected to be finalized by the end of March. The suggested timeline is:
- Late 2018: ambulatory sites and any other sites using IDX billing
- 2019Q3-2020Q2: hospitals and other sites
We will start the inpatient design sessions sometime in the summer of 2018. Some high-level decisions that need to be made before we start design include:
- Will we continue telephone transcription?
- What orders will be required to be entered by the provider?
- What information is released through the patient portal?
Provider training expectations
Advocate will have specialists train specialists with training times varying by specialty. Since many providers already practice at other locations using Epic, there will be a process to demonstrate competency to exempt out of specific training segments.
Regardless of a provider’s Epic experience, each user will be expected to spend at least an hour configuring their profile within Epic before seeing a patient. In addition, the user will have access to Epic analysts to help further configure their profile after seeing patients for a week or so.
Managing education and support after the go-live
Anupam proposed an education and support model for providers:
- One super-user will be appointed for up to 10 physicians and advanced practice registered nurses within a specialty. The superuser will provide educational updates to the provider group and receive feedback from the group about electronic medical record struggles.
- Superusers of the same specialty will meet on a regular basis to share feedback and consider changes that might benefit the department across the organization. The identified changes will be escalated to Advocate’s relevant system service line, Council or system-wide department meeting for consideration.
- Specialty-specific electronic medical record changes that do not affect other users will be escalated to Advocate’s Clinical Information System Enhancement Committee for review. If approved the change will be forwarded to the electronic medical record build team for implementation. If the suggested changes affect multiple specialties, the change request will be reviewed by the Provider Advisory Group to determine if the change is compatible across the affected departments. After review, the change would also be escalated to the Clinical Information System Enhancement Committee for review.
- Practice locations (e.g., outpatient offices, hospitals) will be assigned configuration analysts who will help providers update their profiles when new content becomes available or new workflows are developed. These analysts may be shifted across the organization to help support groups of new users or provide assistance remotely. The configuration analysts will also be responsible for helping providers update their mobile devices to access all the relevant clinical information systems tools that Advocate provides to its user community.
- A Provider Builder Group will serve as clinicians trained in Epic’s structure and functionality to consider changes for specific Epic modules (e.g., Cardiology, Oncology, Emergency Medicine). These clinicians will work in their specialty 75-80% of the time and 20-25% within Health Informatics and Technology. The group will update educational content, prioritize specialty-specific change requests and help configure solutions to meet software updates and system-generated initiatives. The Group will also interface with Advocate’s system-wide Service Line or Council to help better understand end-user needs. After last month’s meeting, Anupam circulated a draft job description with the group.
- Voice recognition – Advocate expects to complete its negotiations with a voice recognition vendor by the end of March. At that time, we should have access to secure voice recognition technology for our independent ordering providers with mobile device functionality.
- PowerPlan consolidation – Given the recent decision to migrate to Epic, the CareConnection team will only focus on those PowerPlans that have a tight connection with a system KRA (e.g., STAAR) or would address a major safety gap (e.g., DKA). The CareConnection team will be much smaller as the associates are being trained on the new electronic medical record platform.
- Texting policy – Anupam submitted an Advocate-wide policy around secure texting to apply for AMG and Advocate providers to the organization’s Quality Management System. After additional review, the policy will be submitted to Bobbie Byrne for approval. Anupam will be communicating this change (i.e., only use a secure texting platform and do not text orders [CMS stance]) with the physician community after the policy is approved.
- Illinois Prescription Monitoring Program – Advocate’s Health Informatics and Technology team has reached out to the state to connect our electronic medical record platforms with the state controlled substances database.
- Merger update – no new information since the last meeting.
- High-census notification through PerfectServe – Await PerfectServe prioritization.
Clinical Information System enhancements awaiting disposition
All non-essential CareConnection enhancement requests will not be resourced. Clinicians are welcome to suggested build configurations during the Epic design sessions. Approved projects include:
- STAAR PowerPlans
- Adult sepsis, inpatient
- Pediatric sepsis, ED (update) and inpatient