The Preferral platform
Care is a journey. The experience should feel like one.
We’re bringing patient conversations, referral coordination, and scheduling into a more connected path. So useful context travels, responsibility stays clear, and the next step has somewhere to go.
Explore what fits your organizationListen & understand
Review & guide
Route & accept
Book & follow through
Patient conversations
Help a patient express what they need before deciding what should happen next. Bring useful context to the people responsible for the decision.
Discovery & referral coordination
Connect the reason for care to an appropriate receiving team. Make the request, its relevant information, and the path to acceptance clear.
Scheduling & follow-through
Bring the path to booking into the care journey, with the receiving practice’s rules and the patient’s next action clearly understood.
One illustrative journey
Follow a patient’s question through the decisions and handoffs that make a next step possible.
A question between visits should have somewhere to go. Help a patient explain what they need, with context for the people who can help.
Platform vision · Illustrative experience
The foundation matters
A shared platform should clarify the boundaries between people and practices.
Read our security overviewOne person’s experience can span multiple practice relationships, with access defined for each relationship.
Relevant context belongs in an intentional handoff. A connected practice does not need access to every private conversation.
AI can help organize information and support a next step. Clinical decisions and responsibility stay with the appropriate care team.
Begin with the actual work
Bring one workflow. We’ll map the people, systems, and decisions it needs.
We are developing the next chapter of Preferral with healthcare organizations. The platform illustrations show the experience we are working toward. A scoping conversation establishes current availability, deployment scope, and the roadmap for your needs.
Start by identifying your source records, identity provider, scheduling systems, and team responsibilities. We assess integration requirements for the proposed workflow rather than assume every system connects out of the box.
A clinical or operations owner who knows the workflow is a useful starting point. Bring care coordinators, access staff, and security or IT reviewers into the discussion as the scope becomes concrete.
A defined population or referral pathway, named participating teams, an agreed definition of completion, and a small set of operational measures. Scope and commercial terms are discussed directly with our team.
A better next step
Let’s find the place where a clearer next step can make a meaningful difference.
