Intake gets stuck
Referrals sit before they become scheduled visits, and intake teams chase missing information manually.
FDE application · Allied health operations systems
Turn referral-to-first-visit friction into a working operating system.
HONONOH helps growing pediatric therapy and allied-health teams map the real intake, authorization, scheduling, documentation, and handoff workflow, then build the operating layer that makes the next action clear.
Forward-Deployed Engineering: enter the real workflow, reconstruct the operating truth, build the minimum useful system, and verify adoption.
Hidden capacity leak
Demand is not the only bottleneck.
Many allied-health platforms already have referrals, waitlists, and families trying to access care. The expensive leak happens between referral, readiness, first visit, documentation, billing, and follow-up.
Status is unclear
Authorization, readiness, family updates, and clinician handoffs move through scattered tools and staff memory.
Growth gets expensive
Acquired clinics operate differently, leadership sees lagging reports, and scale requires more coordinators.
Start here
Start where leakage is closest to revenue and care access.
HONONOH starts with one workflow: referral to first visit. It is specific enough to fix and important enough to justify executive attention.
Referral
Intake
Eligibility/auth
Scheduling
First visit
Parent/client follow-up
Admin/clinical handoff
Operating layer
We build around the tools you already use.
HONONOH does not replace your EHR, RCM, scheduling, or practice-management system. We build the operating layer between systems and people so the next action is visible, assignable, and measurable.
- referral intake queue
- missing-information detection
- eligibility and authorization checklist
- parent/client status flow
- appointment-readiness tracker
- staff task dashboard
- AI-assisted summaries and handoff notes
- waitlist and capacity visibility
Referral-to-first-visit system
Multi-location view
Referral queue
Missing info
Insurance
Parent consent
Referral note
Family status
Ready for scheduling after auth check.
Staff next action
Assign
Call
Escalate
Readiness board
Bottleneck view
Location B: auth review delay.
Engagements
Make the first decision low-risk. Build only when the workflow justifies it.
Operations System Review
A focused review of one workflow where intake, scheduling, auth, documentation, or handoff friction is leaking revenue and capacity.
$15k-$35k
- current-state workflow map
- leakage and bottleneck analysis
- measurable capacity / revenue case
- recommended operating layer
- sprint scope and build/no-build decision packet
Workflow System Sprint
If the review supports a build, the sprint turns one real workflow into a working operating layer.
$75k-$150k
- intake, handoff, dashboard, checklist, or assistant layer
- staff operating path
- missing-info and readiness logic
- QA, launch support, and handoff documentation
- leadership visibility
Best fit
Built for growing care-delivery operators.
This is for pediatric therapy, autism services, speech therapy, occupational therapy, pediatric mental health, developmental therapy, and mixed allied-health groups where growth is running into operational friction.
5-30 locations
Or active acquisition/de novo growth where each location cannot keep inventing its own intake path.
Fragmented workflow
Referral, auth, scheduling, first-visit readiness, and follow-up work across too many tools and handoffs.
Executive pressure
Leadership needs better throughput, visibility, and standardization without simply adding coordinators.
Practical boundaries
The work is not just software. It is operational translation.
Do you replace our EHR or practice-management system?
No. HONONOH builds around existing systems. The goal is to make the workflow between systems and people clearer, more assignable, and more measurable.
Is this clinical decision-making?
No. The focus is operational workflow: intake, readiness, scheduling, documentation support, handoffs, and visibility. AI should assist with routing, summaries, checklists, and flags under human review.
Can this work across multiple locations?
Yes, if the workflow can be mapped into a repeatable operating pattern. The first step is usually one workflow and a small number of representative locations.
What do we need before starting?
Access to the real workflow: forms, queues, handoff notes, scheduling/auth steps, staff roles, status definitions, and the metrics leadership currently uses or wishes it had.
Sensitive workflows should be designed with human review, data minimization, and system-specific controls. Compliance claims require architecture, hosting, data-handling, and legal review before publication.
FDE application · Start with one workflow
Give us the referral-to-first-visit path.
Use the shared HONONOH qualification gate. We will map the workflow, find the leakage, and determine whether the first mandate is a Decision Record or an Operating System Sprint.