But Connect programs are not without their challenges. IT staffing within the host organization can be particularly difficult to estimate and manage. Sales pipelines are inconsistent, so the analyst work effort needed for an affiliate implementation wave can vary wildly. Each new site that partners with the host organization requires support, which can feel negligible for individual sites or provider, but adds up with each wave that goes live. Connect sites require daily attention for break-fix issues and small requests, and they also need to be accounted for in change management and education as the EHR and related systems evolve via projects, new applications, new features, and upgrades.
We’re proposing an alternative approach to Community Connect support: partnering with a managed services provider. Managed services providers can function as an extension of the host organization and provide high-quality, cost-effective, and scalable support for Connect programs. This approach isn’t limited to post-live support — managed services teams can manage Connect projects and enhancements, new affiliate site implementations, and data & analytics services. Daily Connect maintenance and support is typically the foundation that other engagements are built on, so we’ll start with that approach and tackle additional Connect program scope areas in future articles.
Managed services engagements are based on a scope of work and service level agreements (SLAs) that measure the quality of the work performed. The fee is usually fixed, not hourly. These engagements provide clear, known value for the spend compared to hourly-rate, staff augmentation approaches. The baseline managed services scope for a Connect program is post-live Tier 2 EHR site support. Affiliate organizations still contact the host organization via a service desk or other portal to report incidents and submit requests (Tier 1 support), and issues that can’t be resolved by the service desk are routed to the managed services provider. SLAs are based on ticket resolution, and customer-service metrics derived from surveys sent to a percentage of end users after issues are closed.
Every healthcare IT team is challenged by an overwhelming and growing set of priorities to balance, and Connect program add to the list. Connect support grows incrementally over time as waves of new sites go live, so it’s hard to estimate when the incremental growth creates enough demand to increase the team size, which results in fractional staffing challenges in the interim. This also complicates how host organizations calculate the financial performance of their Connect program.
A managed services approach to Connect support can be liberating for the host organization in many ways:
The best managed services providers offer these services as an extension of the host organization. They onboard their team to the host’s change control processes and provide affiliate support within the host’s build guidelines and change management. The host organization has visibility into the quality of support via SLAs, ticket metrics, and collaborative change control, but without having to manage staffing challenges or provide day-to-day oversight. This leads to a solid support foundation for affiliates, which results in better retention as contracts come up for renewal. And with the solid support foundation in place, conversations with affiliate sites can focus on end user adoption, optimization, and improvements, not concerns about support quality.