Purposeful routing
Define a pathway around service requirements, provider participation and agreed eligibility rules.
Provider orchestration
Bring order to the steps between services. Define how requests reach participating providers, how handovers happen and what your team does when a journey needs attention.

Built around your experience
Define a pathway around service requirements, provider participation and agreed eligibility rules.
Specify the information and responsibility that move with each request.
Plan for declined requests, missing information and a person who needs another route.
From request to follow-through
An orchestration model should describe what happens at each stage, not just where a request is sent. Work through acceptance, status changes, escalation and follow-up with the providers involved.
How the pieces connect
Capture the agreed information and service context.
Route through agreed operational steps and provider acceptance.
Communicate the next step or refer an exception to the right team.
Good to know
A few details about provider orchestration and working with our platform team.
No. Operational routing does not replace clinical assessment. The responsible practitioner determines suitability, treatment and any clinical next step.
A cross-provider handover can be scoped where providers agree the requirements, permissions and responsibilities. It should not be assumed to happen automatically.
We define an appropriate fallback or support process during planning. It may involve another pathway, additional information or direct follow-up.
Build with Health Platform Group
Tell us about your platform and the experience you want to create. We’ll work through the right approach together.