Help Pathways
5
food · maternal · chronic · mental · substance
Campus Trails
2
expecting-parent · older-adult (8 stops each)
QR Codes
22
6 active for demo · 16 draft until sign-off
Resources Verified
20
14 high · 6 medium · 0 unverified
Go-Live Gates
5
all on Banner's side — small & concrete
The one thing to remember
Banner puts a QR sticker anywhere a member might need help — a clinic wall, an ER waiting room, a food bank, a community center. A person scans it with their phone and lands on a warm, plain-language page that connects them to verified, nearby help: food, prenatal care, chronic-disease support, mental health, and substance use. Plus two guided "campus walking tours" of a Banner facility.
- It's built FFH-quality and Banner-branded — Banner's name on the front, the Force for Health engine underneath.
- It's safe enough for a hospital to deploy — crisis lines first, no medical advice, no personal data, verify-before-publish.
- It's Tucson-specific — real Pima County resources, a UMC Tucson campus tour. Proof FFH did the local homework on Banner's home turf.
📱 Scan sticker
→
theforce.health/t/<code>
→
🔀 Router
→
🍎 Right help page
Why it's clever: the printed sticker holds a code, never a web address. If a food bank moves, you change one line centrally — the sticker never gets reprinted.
What's actually in the module
Three working parts, plus the admin and data files that make it real and safe.
| Part | What it is | State |
|---|
| Pathways page (patient-facing) | The main tool — 5 help pathways, each with a warm intro, verified local resources, and a "request a callback" option. | Demo-ready |
| Campus Trail #1 | Expecting-Parent walking tour of UMC Tucson — 8 stops (prenatal clinic → lab → L&D → ER → rehab…). | Draft |
| Campus Trail #2 | Older-Adult & Caregiver walking tour — 8 stops. | Draft |
| QR "Force Fields" system | Token Resolver (router) + a non-technical Token Manager dashboard to repoint, add, and export codes with one click. | Built |
| Data & safety records | Verification log (20 resources), no-PII analytics spec, source-of-truth token registry. | Built |
The five help pathways (verified Tucson resources)
Every pathway leads with crisis lines, then routes to confirmed local organizations. 20 resources verified — none unverified.
🍎 Food Security
Community Food Bank of S. Arizona, Interfaith Community Services, SNAP/Nutrition (AZ DES), WIC (Pima County).
🤰 Maternal & Prenatal
El Rio Health Prenatal, MHC Healthcare, Nurse-Family Partnership, WIC.
❤️ Chronic Disease
Pima County Self-Management, El Rio Diabetes, TMC Diabetes Education, Healthy Heart Program.
🧠 Mental Health
Crisis Response Center (walk-in), HOPE Warm Line, NAMI Southern AZ, Emerge Center.
💊 Substance Use
CODAC, SAMHSA National Helpline, free Naloxone (Pima County), Community-Wide Crisis Line.
Safety, built in: 911 · 988 (call/text) · local Tucson crisis line 520-622-6000 lead every page and every pathway — before any other content. No medical advice, no diagnosis, no eligibility gatekeeping, no personal data in any code, URL, or analytics event.
Why it matters for the Banner opportunity
This is the piece that makes FFH look like an operating partner, not a vendor — and it does it in Banner University Family Care's own backyard.
- It maps to managed-care priorities. Food, maternal, chronic, behavioral, and substance-use navigation are exactly the social-needs and health-equity levers an AHCCCS plan is measured on.
- It's white-labeled. The model for how every future FFH build looks to Banner's members.
- It's a deployable asset, not a slide. Already staged in Deploy Ready with a deploy script — demo to live in days once Banner signs off.
The Friday hook: open the page on a phone and scan the Food Security QR live. It routes in seconds. That single demo lands the whole concept with the CEO and the 10 around the table.
The ask, made concrete: "Give us sign-off on the resources, an intake destination, and the in-building locations — and we flip it live."
Where it fits in our Banner materials
A new, distinct pillar — community navigation — that complements the existing stack.
| Existing material | What it covers | How Pathways fits |
|---|
| Friday Deck (v5/v6) + Master Briefing | The pitch & the 4-Pillar Play | Add Pathways as the "we're already in Tucson" live proof point / demo. |
| Prepared Patient demo bundle | Clinical condition journeys (asthma, HTN, sickle cell) | Pathways is the front door — connects people to help before/around the clinical content. |
| Workforce Development hub | Careers, phlebotomy, ecosystem | Same engine, different audience — shows platform breadth. |
| Sponsorship Proposal + ROI tools | The commercial ask | Pathways' no-PII analytics spec feeds the ROI / engagement story. |
What's still needed before go-live (the 5 gates)
All on Banner's side — small, and they put the next step in the client's hands. Be honest about these Friday.
- Banner signs off on every resource and on the callback/intake destination.
- Fill in-building locations for the trail stops marked "[Banner to confirm]" (clinic floor, ER door, L&D entrance, pharmacy, rehab). We never invent hospital directions.
- Assign a named owner to keep resources and the QR registry current.
- Flip tokens to active once approved — today 6 are active for demo, 16 trail codes are held as "coming soon."
- Stand up the
/t/ resolver on theforce.health (one Vercel rewrite — Pace's 3-step deploy).
Bottom line
Dr. Rob handed Lucy a finished, safe, Tucson-specific demo of a tool that connects Banner's members to real local help via a QR code. It's not another thing to build — it's a ready-to-show proof point for Friday and a deployable asset for the contract. The only work before go-live is getting five small confirmations from Banner.
How this explainer was built. Summarized directly from the banner-pathways-tucson-complete module delivered by Dr. Rob (PACKAGE-MANIFEST, START-HERE guide, pathways JSON, verification log, and analytics spec). Resource counts and confidence flags are read from the module's own verification log (20 resources · 14 high · 6 medium · 0 unverified, packaged & verified 2026-06-06). Status, gates, and safety rules are quoted from the module manifest. Internal leadership view — not the public tool.
Source: banner-pathways-tucson-complete module · Dr Rob Input → Ready to Test for Lucy → Direct from Rob's Claude Output · packaged 2026-06-06. Companion Word version: Banner-Pathways-Tucson-Executive-Explainer.docx in the Banner Gameplan folder.