Build the MAV Network
Build mobile access—not a giant specialty fleet.
The implementation problem is not “how many vans should Arkansas buy?” It is how to give ANCHOR dependable field capacity across the state using a practical mix of Regional Docks, core public staff, Access Vans, higher-capability MAVs, partner sites, pop-up kits, telehealth and targeted specialist support.
Implementation has to fit Arkansas systems
Build agreements and operating lanes before buying the fleet.
ARDOT + mobility
Map rural transit and 5310/5311 coordination opportunities; define the Mobility Desk and passenger-transport boundary.
DHS + Medicaid
Define NET/NEMT handoff, Medicaid-provider boundaries, waiver/benefit navigation and what ANCHOR can assist with without becoming the eligibility authority.
ADH / health systems / UAMS
Coordinate clinical partner days, telehealth, mobile-health best practices, public-health links and referral continuity rather than duplicating existing capacity.
Regional Docks + local hosts
Use libraries, colleges, health units, clinics, schools and community buildings as recurring access sites where appropriate instead of leasing mobile-only square footage everywhere.
Data + privacy
One consent model, minimum necessary records, no uncontrolled device storage, role-based access, secure referral status and deidentified gap reporting.
Procurement
Issue functional specifications for each vehicle tier, accessibility, power, climate, network, secure storage, maintenance, warranties and lifecycle cost. Do not lock the program to one vendor concept.
Interactive deployment planner
Build the visit before you choose the vehicle.
Use the operating model as a decision system. Pick the setting, the main access job and the expected scale. The planner shows a proposed starting configuration—not a procurement order or a fixed staffing rule.
Costing framework
Cost the operating system, not only the vehicle.
Final dollar figures require Arkansas procurement, salary/benefit assumptions, insurance, fuel/maintenance, IT/security, partner contracts and route-mile modeling. This site therefore defines the cost centers and expansion gates instead of inventing a precise appropriation.
Core field staff, Mobility Desk, supervision, rotating specialist contracts, training, leave coverage.
Acquisition/lease, upfit, accessibility, registration, insurance, maintenance, tires, fuel, replacement reserve.
Host-site, Sensory Haven, AAC, technology library, signage, privacy, sanitation, replacement inventory.
Secure devices, scheduling, referral tracker, consent, hotspot/connectivity, telehealth, cybersecurity, offline fallback.
Clinical service agreements, host support, interpretation, transportation purchases where lawful, local coordination.
Route data, quality review, public dashboard, service-gap analysis, user feedback and independent review.
Proposed funding architecture
Use different money for different functions.
No single grant or billing stream should be expected to fund the whole MAV Network. The public access spine, transportation coordination, vehicles, licensed services and local partnerships have different legal and fiscal characteristics.
Appropriation / operating base
Core navigators, peers, Mobility Desk, statewide standards, secure data/referral infrastructure, minimum fleet, equipment replacement, insurance and administration.
Reason:These are public-access functions that should not disappear when a grant ends or when no billable clinical event occurs.
ARDOT + FTA coordination
Evaluate 5310, 5311, mobility-management, accessible-vehicle and coordinated-transportation eligibility with ARDOT and transit partners. ARDOT's current state-program page also lists a revolving account that provides vans to 5310/5311 agencies through an interest-free loan structure.
Boundary:Eligibility, recipient status, coordinated plans and match requirements must be confirmed before budgeting any federal transit dollar.
Billable partner services
When a licensed provider delivers a covered service through a lawful mobile/telehealth arrangement, reimbursement belongs to that clinical service lane.
Boundary:Do not call general navigation, peer support or public outreach “clinical” merely to generate reimbursement.
HRSA/FORHP and program grants
Use competitive rural-health, workforce, telehealth, care-coordination or demonstration funds for launch, evidence development and defined service expansions when an opportunity matches the scope.
Boundary:Grant funding should add capability; it should not be the only way the statewide access spine survives.
Host + service agreements
Libraries, colleges, clinics, health units, community organizations and other hosts can contribute rooms, utilities, outreach, staff time or scheduled specialist capacity under clear agreements.
Reason:Existing public/community infrastructure can reduce capital cost and improve local trust.
Equipment + innovation
Private grants and donations can support Sensory Haven kits, technology library equipment, vehicle enhancements, public education and local experiments.
Boundary:Do not make core statewide access dependent on unpredictable donations.
Operating model
One statewide standard. Regional execution. Local hosts.
Statewide MAV standard
Define visit types, communication/access requirements, privacy, data, staff credentials, safety, equipment, route publishing, host rules and referral-loop closure.
Regional Dock bases
Use Regional Docks or comparable stable hubs for staff supervision, equipment storage, route scheduling, partner coordination and unresolved-case follow-up.
Mixed mobile capacity
Use light Access Vans for general outreach; higher-capability MAVs for private/telehealth/assistive-tech work; host rooms and pop-up kits when a vehicle adds no value.
Core public field staff
Maintain navigators, peer capacity, mobile operations and required supervision as accountable ANCHOR functions. Add clinical/specialist roles only to the visits that need them.
Local and specialist partners
Use libraries, schools, health sites, colleges, transportation, providers and community organizations for defined functions rather than contracting away the whole operating model.
Closed-loop data
Track completed handoffs, waitlists, service deserts, access failures, complaints, travel burden and demand so route capacity grows where evidence supports it.
Fleet logic
Four field configurations cover most use cases.
Access Van
General outreach, public access, Passport help, communication/sensory kits, route navigation and community events.
Higher-capability MAV
Private consultation, telehealth equipment, assistive-tech demos, secure devices, mobile Academy and more complex field support.
Host-site kit
Portable privacy, communication, sensory, technology and signage kit deployed into an existing library, clinic, school, college or community room.
Event / Sensory Haven kit
Pop-up access station, quiet-zone materials, communication board, public education and route navigation for events and public venues.
Regional route design
Predictable routes are more useful than constantly moving vehicles.
Recurring hub day
Same weekday/host location so people and referral partners learn the rhythm.
Rural circuit
Several smaller communities connected to one Regional Dock and one travel day.
Targeted access day
Employment, school transition, health access, adult evaluation preparation, community training or another documented local need.
Event deployment
Temporary high-volume public access and Sensory Haven capability.
Staffing
Keep a core team; rotate specialists.
Resource navigator
System navigation, benefits, scheduling, Passport, warm handoffs and follow-up.
Certified peer specialist
Lived-experience support, education, peer connection and de-escalation within role boundaries.
Driver / mobile operations
Vehicle, site, equipment and route safety. EMT/community-paramedic capability can be added when a specific model requires it.
Licensed clinical lead
Only where clinical triage, risk assessment or licensed service is actually part of the visit; license scope and clinical protocols control.
AAC / SLP consultantOT / sensory consultantAdult autism clinicianGeriatric specialistWaiver / benefits expertBilingual liaison
Funding logic
Pay for the public field spine; use reimbursement only where an actual billable service exists.
Core access infrastructure
- field staff and supervision;
- vehicles, fuel, maintenance and insurance;
- Regional Dock storage/dispatch;
- public navigation and communication access;
- equipment library and consumables;
- route scheduling, resource data and follow-up;
- training, quality, privacy and reporting.
Defined partner / clinical capability
- lawful healthcare reimbursement when a licensed covered service is actually delivered;
- grants for defined access, rural, transportation, technology or training functions;
- interagency agreements for named services;
- partner vehicle/site upfits where cheaper than duplicating infrastructure.
Phased rollout
Prove the network region by region.
- 01
Build the field standard and route tools.
Service definitions, host agreement, privacy/data rules, equipment lists, staff training, route calendar and public information.
- 02
Launch a small number of regional routes.
Tie them to stable Docks/hosts and deliberately test urban, rural and service-desert conditions.
- 03
Measure what people actually ask for.
Service mix, visit duration, travel burden, referral completion, equipment demand, privacy needs, specialist use and local follow-up capacity.
- 04
Add the right capacity.
More route days, another Access Van, a higher-capability MAV, additional host kits, specialist telehealth blocks or a new Regional Dock—whichever solves the documented bottleneck.
- 05
Publish performance and gaps.
Show where routes work, where people remain stuck and why further capacity is or is not justified.
Implementation boundary
Clinical capability is optional. Governance is not.
Every MAV route needs clear ownership, privacy, safety, staff roles, public information and follow-through. Only routes offering clinical care need the additional licensure, clinical records, billing, supervision and medical emergency infrastructure that apply to that service.