A clearer handoff
Give prospective patients a purpose-built referral path and give the clinic a shared way to review how that path is being used.
Founding Three-Clinic Pilot
Test a clearer referral path before building a bigger clinic platform.
We are manually onboarding three clinics to test the referral → OfRoot Health signup → activation → doctor-ready report flow and learn where staff and patients encounter friction.
This is a Technology service for clinic growth, referral links, and aggregate operations. It does not provide automatic access to Health patient data.
The plain-language answer
A manual pilot for three clinics—not a broad software rollout.
Each clinic gets one focused referral path, a staff workflow interview, and a review of agreed aggregate signals. We use the repeated friction to decide what deserves to be built. The pilot is not a replacement for clinical judgment, care delivery, or a Health patient-record system.
Operational visibility
Use aggregate counts and trend signals to understand referral activity and follow-up operations without creating a patient-record dashboard in Technology.
A three-clinic learning loop
Manually onboard the first three clinics, interview staff, observe referral friction, and build only around repeated needs.
Referral flow
Every handoff has a clear home.
The pilot keeps clinic-growth activity legible. Technology manages the referral-link layer and aggregate operations view. Health remains the system for patient information and care.
- 01
Referral link
Technology creates a clinic-approved referral path.
- 02
Clinic handoff
The clinic defines how the referral is handled in its own workflow.
- 03
Aggregate operations
Technology reports agreed aggregate activity, not patient records.
- 04
Clinic review
The team reviews the signal and agrees the next operational step.
Data boundary
Operations visibility without automatic patient-data access.
Technology owns
- Clinic-growth work and referral links
- Aggregate operations views and reporting
- The agreed implementation and service cadence
Health owns
- Patient data and patient records
- Clinical workflows and care decisions
- Approval for any proposed Health-data access
Technology does not receive Health patient data through this pilot by default. If a future workflow needs Health-data access, it begins as a separate, documented approval and architecture conversation.
Implementation and learning
Start with three clinics. Review real usage. Continue deliberately.
The pilot stays manual so we can learn which intake, appointment-preparation, and admin problems actually repeat before we invest in broader software.
01
Choose three clinics
Confirm one accountable staff owner, one referral use case, and the privacy boundary for each clinic.
02
Onboard manually
Set up one clinic-approved referral path and walk staff through the handoff without an EHR integration or outreach automation.
03
Observe the flow
Review aggregate referral, signup, activation, and report signals, then interview staff about intake, preparation, and admin friction.
04
Build only the repeat
Continue only with problems that recur across clinics; any Health-data access remains a separate approval and architecture decision.
Founding clinic conversation
See whether one of the three pilot spots fits your clinic's referral and appointment-preparation workflow.
We will start with the clinic's operating question, existing referral path, and the boundary the pilot must respect.