The most critical prerequisite to the successful delivery of great care via telehealth are well-designed, well-deployed workflows. The delivery of excellent telehealth that provides a great experience for patients and clinicians alike, depends on a multitude of care team members doing their job well. Which they can only do, if the steps they need to perform are well understood.
For telehealth to work well, there are 7 workflows that must be designed, developed, and deployed:
- Telehealth Scheduling
- Telehealth Onboarding
- Telehealth Rooming
- Telehealth Visit
- Telehealth Post-Visit
- Telehealth Follow-Up
- Telehealth Billing
Recipe for Telehealth Workflows
To define, develop & deploy each of the seven workflows here are the ingredients and techniques:
Actors & Users: Define for each workflow the individuals contributing (“actors”) and benefitting (“users”) from the workflow.
Objective: Clearly define the outcome of each workflow. What state is the workflow trying to accomplish? What is the experience like?
Trigger: Identify what event starts the workflow? How does the first actor know when to act?
Scenarios (see below): First define the Happy Day Scenario without getting distracted by what could also happen. Next, systematically develop the Alternate Scenarios or Exception Scenarios by exploring for each step of the Happy Day Scenario what variations could occur in each step.
Exit/Handoff: Finally, clearly define when each workflow ends and/or where the workflow is handed off to.
Training: Next you need to define the optimal training. This typically includes walking people through the workflow and providing written instructions, e.g., in the form of “cheat sheets” that remind people of the various steps.
Critical Tool: Workflow Scenarios
Using a scenario-based mindset is absolutely critical when designing workflows. Too many workflow designs are done badly, because the design team gets lost in the various exceptions to the rules and things that could go wrong.
The key is to start with the Happy Day Scenario first: defining what you expect to happen 80%, 90% of the time; the typical, normal, every-day scenario. This will require a disciplined leader to keep the workflow design team focused on the Happy Day Scenario as many of us are excellent at pointing out flaws or identifying things that can go wrong. But it is important to first optimize the workflow for the conditions that are usually occurring.
Alternate Scenarios: The next step is to systematically go through each step of the Happy Day Scenario and identify what could happen differently. These are the known or anticipated variations, but instead of designing the whole workflow around those exceptions, you typically only have to define a few steps that are different.
Exception Scenarios deal with the unexpected or rarely anticipated. If it is unlikely to occur regularly, some thought must be given to a backup plan, but since those situations rarely emerge, not much time has to be spent on defining the details.