Use Cases
See Trellis in Action
Four real-world workflows showing how Trellis connects systems, ranks resources, and improves outcomes in real time.
Workflow 01
Healthcare systems · Hospitals
Housing Referral at Hospital Discharge
Epic → Trellis → Ranked Housing Matches
Scenario
A patient being discharged needs stable housing. The care coordinator is inside Epic.
What happens
Trellis receives a CDS Hook at discharge planning. It returns a ranked, eligibility-filtered list of housing programs in the patient's ZIP code — currently accepting referrals, matching insurance, with successful loop closures in the past 90 days. The coordinator selects and refers without leaving Epic.
Outcome
The care team avoids manual searching, reduces discharge delays, and selects programs with a higher likelihood of acceptance — improving patient stability post-discharge.
How Trellis operates in a workflow
Workflow 02
Community Care Hubs · Managed care plans
CalAIM ECM Care Planning
Case Mgmt → Trellis → ECM Service Matching
Scenario
A CHW builds a care plan for a new ECM member with housing instability, food insecurity, and a pending Community Supports authorization.
What happens
The case management system calls Trellis. Trellis surfaces CS-eligible services with authorization status visible, ranked by acceptance rate and proximity. Referrals are tracked through the FHIR Task lifecycle for DHCS reporting.
Outcome
The CHW builds a compliant care plan faster, reduces denied referrals, and ensures services align with both eligibility and performance.
Workflow 03
CCH administrators · Directory managers
211 Directory Integrity Review
HSDS Feed → Trellis → Validated Directory
Scenario
A quarterly 211 data feed arrives with 2,400 updated records.
What happens
The HSDS pipeline stages changes as a diff report. The admin reviews adds, updates, and deletes before anything touches the live directory. Freshness scoring flags stale listings for manual review. Import commits only after approval.
Outcome
Directory accuracy improves, stale records are reduced, and downstream referrals are more likely to succeed.
Workflow 04
Regional networks · Counties
Multi-Network Resource Discovery
Multiple Networks → Trellis → Unified Ranking
Scenario
A regional network spans three counties, each running a different referral platform.
What happens
A single Trellis instance aggregates signal from all three networks. Rankings reflect performance across the entire region — not one vendor's closed platform. High-performing CBOs surface regardless of which system sent the referral.
Outcome
High-performing providers surface across network boundaries, reducing fragmentation and improving referral success rates region-wide.
See how Trellis fits your workflow
Every network is different. Trellis adapts to yours — and improves it over time.