Culbert Healthcare – CHS Culbert Healthcare – CHS
  • SERVICES
    • CLINICAL OPERATIONS
    • MANAGEMENT CONSULTING
    • HEALTH IT
      • EPIC CONSULTING
      • ATHENAHEALTH & ATHENAIDX
      • ALLSCRIPTS CONSULTING
      • CERNER CONSULTING
  • MEDIA & EVENTS
    • CONFERENCES
    • WEBINARS
    • CASE STUDIES
    • NEWSLETTERS
  • CAREERS
    • AVAILABLE POSITIONS
    • BENEFITS
    • STAFF TESTIMONIALS
  • ABOUT
    • MANAGEMENT TEAM
    • COMPANY MEETING & PRESIDENTS CLUB
  • BLOG
  • CONTACT
Culbert Healthcare – CHS Culbert Healthcare – CHS
  • SERVICES
    • CLINICAL OPERATIONS
    • MANAGEMENT CONSULTING
    • HEALTH IT
      • EPIC CONSULTING
      • ATHENAHEALTH & ATHENAIDX
      • ALLSCRIPTS CONSULTING
      • CERNER CONSULTING
  • MEDIA & EVENTS
    • CONFERENCES
    • WEBINARS
    • CASE STUDIES
    • NEWSLETTERS
  • CAREERS
    • AVAILABLE POSITIONS
    • BENEFITS
    • STAFF TESTIMONIALS
  • ABOUT
    • MANAGEMENT TEAM
    • COMPANY MEETING & PRESIDENTS CLUB
  • BLOG
  • CONTACT
Mar 30

Non-technical Considerations Before Beginning an Epic Connect Project

  • March 30, 2017
  • Michelle Taylor
  • Epic, Epic Connect

An organization’s decision to extend their instance of Epic to outside practices and/or facilities, known as Connect, offers many advantages to patients, providers and organizations. Used appropriately, the functionalities extended enhance the providers’ understanding of a patient’s clinical results, history and charts. In turn, this enhances the patient experience with an overall better, more comprehensive treatment and understanding of that patient’s particular problems.  A goal of ‘one patient, one medical record’ is more attainable and sustainable and should lead to better outcomes.  Additionally, communication and relationships between organizations and their medical community providers is improved.  It is not difficult to understand why an organization may decide to offer a Connect product to their community.

On the surface, the implementation planning sounds easy. After all, the organization offering their EHR has already done the ‘heavy lifting’ of building workflows and determining best practices.  Oftentimes, the overall mindset in these projects initially is to treat an implementation the same way the project team would treat an internal implementation (e.g., a new department or service line).

As with any implementation, there will always be lessons learned. There are some key areas of potential risk to your ‘customers’ overall satisfaction with a Connect implementation. These items can be easily addressed prior to contracting and can ultimately alleviate or bypass future pain points for both your customers and your project team.  Although not comprehensive, below are some recurring challenges that can be experienced in Connect projects.  Organizations should ensure they have a clearly defined and communicated strategy around them.

 

  • Everyone is special – Determine your customization thresholds. Just as your organization is different than another in your city or region, your Connect partner is likely different from you. When extending your instance of the EHR, you need to clearly and frequently communicate to your recipients what, if any, customization you will support in their EHR with you. Customization in build is not just limited to clinical workflows but can include interfaces, third party vendor relationships, user security templates, billing/claims workflows and clearinghouses, scheduling templates and reports/reporting, among other items. Any items or areas in which your organization is willing to step away from in an established build and workflow, needs to be clearly defined for all so your Connect partner is aware of what is or isn’t possible and your project team has set parameters. Keep in mind that the more customization of the build you allow (vs. standardization), the more complex and costly your maintenance of that build will be long-term. 
  • No one likes to be ignored – Determine what level of participation your Connect partners will have in your governance and/or clinical content decisions. The quickest way to antagonize your Connect partners is to make them feel ignored. Clinicians, particularly specialty clinicians, will have preferences and suggestions to the clinical content and workflows you have extended to them. Your organization should strongly consider inviting representation of these partners into your governance and/or clinical content infrastructures. Such a strategy not only leverages additional resources to enable better patient care, it also serves to start shifting your organization’s internal culture to include consideration of outside providers and facilities in their deliberations.
  • You may need a culture shift. When you sign on your first Connect partner, your organization is no longer just “your” organization. From that moment forward, everyone from your leadership down needs to be aware that changes to workflows and content in Epic build could now impact your partners, and therefore those entities need to be included in any consideration of such changes. This is particularly important for the Epic team, as they are the ones responsible for your build, as well as any system upgrades and updates. You also may need to incorporate your Connect partners into any communication and/or training protocols you currently use around changes and upgrades in your system.
  • What are your long-term strategies around your Connect partners? How will problems be reported and resolved with your partners? We have seen a variety of solutions to these questions with our clients. Many organizations use their normal help desk operating procedures (call in a ticket, ticket is reviewed & prioritized using organization standards, ticket is assigned and worked by Epic team), but some organizations utilize a dedicated team and phone number for their Connect partners’ requests and problems. Another long-term consideration is new employee on-boarding at your Connect partners since your organization remains subject to your Epic agreement, which includes training requirements prior to access. You should review who/how that training is to be provided and how a partner communicates the need for training. As a corollary, how is your organization to be told of employee terminations for security inactivation?
  • What is the exit strategy? Unfortunately, Connect partnerships do not always work out. This may be due to practice closure or provider dissatisfaction. To protect both your organization and any of your potential Connect partners, it is strongly recommended to ensure you have an off-boarding protocol clearly laid out and communicated prior to contracting. This protocol should include the steps of how a partner initiates off-boarding activities, what the reasonable expectation of deliverables after off-boarding will be (i.e., how does the partner access the patient medical record once they are off-boarded?) and the projected timeline of an off-boarding.

Each of these items is underscored by the underlying theme of communication.  Wherever you land on decision points in your Connect implementations means little if these decisions are not shared clearly and frequently with your partners, your organization and your project team.

Connect projects are exciting opportunities for any organization to better care for patients, both in-house and in the community. Just be sure to look at the entire picture before beginning these partnerships so you can ensure your partners will be  successful using your EHR.

 

  • Facebook
  • Twitter
  • Tumblr
  • Pinterest
  • Google+
  • LinkedIn
  • E-Mail

About The Author

Comments are closed.

Recent Posts

  • 21st Century Cures Act Requirements for Providers – Revised Compliance Dates and Why This Matters
  • Information Blocking Delay-We Can Help you Prepare for April 2021
  • Improve Revenue by Optimizing Coding Performance
  • Work Claim Denials More Efficiently Using Owning Areas: Epic Resolute Hospital Billing
  • Why Now is a Good Time to Shift Your Focus

Recent Comments

    Archives

    • November 2020
    • October 2020
    • September 2020
    • June 2020
    • May 2020
    • April 2020
    • March 2020
    • September 2019
    • August 2019
    • July 2019
    • June 2019
    • May 2019
    • March 2019
    • January 2019
    • December 2018
    • November 2018
    • October 2018
    • September 2018
    • August 2018
    • July 2018
    • June 2018
    • May 2018
    • April 2018
    • March 2018
    • February 2018
    • November 2017
    • October 2017
    • September 2017
    • August 2017
    • June 2017
    • May 2017
    • April 2017
    • March 2017
    • February 2017
    • January 2017
    • December 2016
    • November 2016
    • October 2016
    • September 2016
    • August 2016
    • July 2016
    • June 2016
    • May 2016
    • April 2016
    • March 2016
    • February 2016
    • January 2016
    • December 2015
    • November 2015
    • October 2015
    • September 2015
    • August 2015
    • July 2015
    • June 2015
    • May 2015
    • April 2015
    • March 2015
    • February 2015
    • January 2015
    • December 2014
    • November 2014
    • October 2014
    • September 2014
    • August 2014
    • July 2014
    • June 2014
    • May 2014
    • April 2014
    • March 2014
    • February 2014
    • January 2014
    • December 2013
    • November 2013
    • October 2013
    • September 2013
    • July 2013
    • June 2013
    • May 2013
    • April 2013
    • March 2013
    • February 2013
    • January 2013
    • December 2012
    • November 2012
    • October 2012

    Categories

    • 21st Century Cures Act
    • Allscripts
    • athenahealth
    • Clinical Operations
    • CMS Quality Payment Program-MIPS Path
    • Coding
    • Consumerism
    • COVID-19 Resources
    • EHR
    • EHR Integration
    • EHR Optimization
    • Epic
    • Epic Connect
    • Epic Reporting
    • Epic Security
    • GE
    • GE Centricity
    • ICD-10
    • Information Blocking
    • IT
    • MACRA
    • Management Consulting
    • Meaningful Use
    • Patient Access
    • patient experience
    • patient satisfaction
    • process improvement
    • Revenue Cycle
    • Strategy & Executive Leadership
    • Telehealth
    • Tom Dubeck-Stuff You Wish You Had Learned in Epic Certification
    • Training
    • Uncategorized

    Meta

    • Log in
    • Entries feed
    • Comments feed
    • WordPress.org
    Connect with Culbert
    call us at 781.935.1002 info@culberthealth.com
    800 West Cummings Park Suite 6000 Woburn, MA 01801
    2020 Culbert Healthcare Solutions