Your Network Is Already Running.
It Just Can't See Itself.
Trellis is the intelligence layer that makes referral networks observable, measurable, and continuously improving — without replacing your EHR, CLR, or case management system.
Not a directory. Not a platform. The layer that makes both work.
Built for real-world referral networks — from county systems to managed care.
Every system has a directory. None of them are good enough.
Listings go stale
Community resource data has a short half-life. Most directories are updated quarterly at best. By the time a care worker searches, the listing may be months out of date.
No outcome visibility
A referral is sent. Then what? Most systems have no visibility into whether the referral was accepted, the client received a service, or the CBO is even functional.
Generic results
Search returns everything that matches a category in a ZIP code — no ranking by eligibility fit, no awareness of language or insurance, no signal about which CBOs actually accept clients like this one.
Workflow friction
Care workers leave their system to search a separate tool, copy information back, and manually initiate a referral. Each step is an opportunity for the loop to break.
"Building and maintaining a live, intelligent resource directory is a distinct engineering problem — one that no CLR vendor, EHR, or case management system has made their core competency."
One API call. Ranked results. No workflow change.
Your system owns the workflow. Trellis owns the intelligence. The care worker never leaves their screen.
Three data inputs. No external directory can replicate all three.
211 Foundation
What
Structured, validated resource listings via OpenReferral HSDS 3.0
Why it matters
Thousands of vetted CBOs from day one — no cold start, no scraping
Network Intelligence
What
Live CLR acceptance rates, loop closure data, and capacity signals from participating referral networks
Why it matters
Which CBOs actually perform, right now — data no external directory possesses
Client Context
What
SDOH flags, language, insurance, ECM enrollment, and location — already in the referral workflow
Why it matters
Personalized matching — the right resource for this specific person, not a generic list
Intelligence that compounds with every closed loop.
More connected networks → more signal → better matches → more referrals → more signal. Trellis improves with every participating network, regardless of which CLR platform they use.
What Trellis is. What it isn't.
| Trellis IS | Trellis IS NOT |
|---|---|
| Network-agnostic middleware any CCH, plan, or county can connect to | A competing referral network |
| Standards-based: FHIR R4, HSDS 3.0, 360X, SDOH IG | A replacement for 211 systems or their directories |
| An intelligence layer that makes 211 systems more actionable | Locked to any single EHR, CLR vendor, or network operator |
| A closed-loop accountability tool for CalAIM ECM/CS programs | A case management system or care management platform |
| Public infrastructure — not a proprietary network | A subscription directory (CBOs don't pay to be listed) |
| Embeddable: "Powered by Trellis" inside any referral workflow | A workflow product — it's the intelligence layer under one |
Four audiences. One infrastructure.
Counties and public sector
An open, standards-based intelligence layer that satisfies procurement requirements and CalAIM reporting obligations — without vendor lock-in.
Managed care plans
Closed-loop referral accountability and SDOH quality measure data for ECM/CS oversight, member attribution, and encounter reporting.
Community-based organizations
A lightweight portal to maintain listings, receive referrals at any technical tier, and build a performance record that increases visibility to referrers.
Technical / developer
FHIR R4, HSDS 3.0, 360X, REST + GraphQL APIs, webhook events. Embeds cleanly into any referral workflow as an intelligence service.
Where Trellis fits.
| Platform | Primary model | Directory intelligence | Network lock-in |
|---|---|---|---|
| Trellis | Standards middleware layer | HSDS + live CLR signal + AI matching | None — open API, any network |
| Findhelp (Aunt Bertha) | Consumer-facing resource directory | Large but static; no CLR signal | Medium — proprietary listings |
| Unite Us | Enterprise CLR network | Network-only signal; closed | Very high — network-centric |
| 211 Systems | Community resource directory | Deep listings; no outcome data | None — but no CLR layer |
Making 211 smarter, not replacing it.
211 System gives
Structured, maintained resource listings via HSDS export or live API. Thousands of validated CBOs, taxonomy-classified and geographically scoped.
211 System receives
Anonymized referral outcome signals — which resources accept, which close loops, which are capacity-constrained. Data 211 has never been able to generate on its own.
Proof of concept: 211 San Diego. Replication model: every county Trellis operates in.
A static directory is a feature. A referral intelligence layer — grounded in 211 data, enriched by live network signal, embedded in the clinical workflow — is infrastructure.