Journeys overview and concepts
What a journey is in LeapHealthOS, how drafts, versions and patients on a journey relate, and the terms used across the Journeys pages.
A journey is an automated care pathway that LeapHealthOS runs for each patient who enters it. You draw it once as a set of connected steps: send a message, wait three days, raise a call task for a nurse, book a follow-up, ask for a consent signature. LeapHealthOS then carries out those steps for every enrolled patient, at the right time, and records what happened. This page introduces the ideas behind journeys and points you to the pages that cover each part. It is for administrators and implementation staff who design journeys, and for anyone who needs to understand what a journey is doing for a patient.
Journey is not a treatment plan
In LeapHealthOS, "journey" always means this automation. It is not a patient's multi-visit treatment plan.
Where to find Journeys
Select Journeys in the sidebar. You see it if your role has the Read permission on Journeys (see Who can do what in Journeys). The Journeys area has five tabs:
Tab | What it is for | Read more |
|---|---|---|
Journeys | The list of journeys. Create, open and archive them here. | |
Entry rules | Rules that enrol patients automatically when something happens, such as a booking or a payment. | |
Patients | Every patient on a journey, with their progress and staff actions. | |
Health | Journeys that are stuck or need attention. | |
Insights | How patients move through each journey, where they drop off and how they finish. |
On screens narrower than 1024 pixels the tabs become buttons. The builder itself needs a desktop-sized screen.
Key ideas
Term | Meaning |
|---|---|
Journey | The design: a named set of steps and connections. Each journey belongs to your whole organisation. |
Draft | The version you are editing. There is always exactly one draft, and it saves itself as you work. Changing the draft never affects patients. |
Version | A frozen copy of the draft, made each time you publish (v1, v2, …). Versions never change. |
Patient on a journey | One patient's run through one version of a journey. The Patients tab lists them. A patient stays on the version they started with, even after you publish a newer one. |
Step (node) | One box on the canvas. There are 15 types, such as Pause, Engage, Reach and Close. See the Node reference overview. |
Connection (edge) | An arrow from one step to the next. It decides where the patient goes when a step finishes. |
Outcome | The result a step finishes with, for example met on a Gather or Nobody answered in time on an Engage. Connections can route on outcomes. |
Track (branch) | One line of steps being worked through. A patient can be on several tracks at once when a step starts parallel paths. |
Default connection | The connection followed when none of a step's conditions matched. |
Gather | The step that brings parallel tracks back together. |
Close | The step that ends a track, or the whole journey, with an outcome of success, failure or neutral. |
Entry rule | A rule that enrols a patient when a matching event happens. |
Initiation fields | Values a patient is enrolled with (for example, which doctor referred them). Steps and conditions can read them. |
Review findings | Problems LeapHealthOS finds in a journey before it is published, at three levels: blocking, risk and warning. |
Simulate | A dry walk through the journey on screen. Nothing is sent or saved. |
The life of a journey
- Create a journey and give it a name. It starts with an empty draft and the status Draft.
- Build the draft on the canvas: add steps, configure them and connect them. See The builder canvas and how connections work.
- Check it. Fix the review findings, and walk through it with Simulate. See Publishing and validation rules and Versions, drafts and simulate.
- Publish it. This makes version v1 and the status becomes Published.
- Enrol patients with entry rules or by hand. Each patient runs on the latest published version at the moment they enter.
- Keep improving the draft and publish again. New patients get the new version; patients already on the journey continue on theirs.
How patients enter a journey
A patient can only enter a published journey. There are three ways in:
- Entry rules: an event, such as an appointment being booked or a package being bought, enrols the patient automatically.
- By hand: staff with the right permission use Enrol patients to add one or more patients.
- From another journey: a Connect step hands the patient over to this journey, or an Involve step starts this journey for a related person.
Before a patient is admitted, LeapHealthOS runs admission checks, for example that they are not already on the same journey. See Why a patient was not enrolled.
How a journey moves
When a step finishes, the journey follows its connections:
- Every plain connection fires, so several steps can start at once.
- A connection with a condition or an outcome fires only when it matches.
- A default connection fires when no conditioned connection matched.
- If no connection fires, that track ends.
Steps that wait for people (tasks, forms, signatures) take a time limit, so the journey moves on even if nobody acts. The builder tells you when a waiting step has no limit. The full rules are on The builder canvas and how connections work and Waiting, time limits and reminders.
What patients and staff see
Patients receive messages, forms, booking links and signing requests from the journey's steps. See What patients receive. Staff receive tasks from Engage, Capture and Sign steps on their worklist. See Where tasks come from.
Related pages
Last updated on