Integrations

Connect what already exists.

Integrates with everything. Owns nothing.

Trellis sits above EHRs, case management platforms, referral networks, 211 systems, and legacy environments — turning disconnected activity into a coordinated intelligence layer.

Open standards where possible. Practical adapters where necessary.

No rip-and-replace. No vendor lock-in. No dead-end architecture.

EHR (FHIR R4) Case Mgmt (REST) CLR (360X) 211 (HSDS bulk) Legacy (HL7 v2) CBO (Email/SMS) TRELLIS API gateway + adapters Ranked Matches contextual shortlist Network Signal capacity + outcomes Loop Closure 360X events

Interoperability is table stakes. Learning is the difference.

Most integration pages stop at compatibility.

Trellis goes further.

It does not just connect systems. It turns the activity flowing through them into signal — so every referral, response, and outcome improves the network over time.


Built on open standards

Trellis uses the standards already adopted across healthcare, community systems, and public-sector infrastructure — which makes it easier to embed, govern, and scale across real environments.

Standard Version Trellis Role
OpenReferral HSDS 3.0 Canonical import/export format for 211 systems nationally.
FHIR R4 / US Core 4.0.1 EHR integration surface. SMART on FHIR and CDS Hooks.
360X 1.0 Closed-loop referral transaction protocol. Bidirectional outcome signal.
SDOH Clinical Care IG HL7 ballot SDOH screening result ingestion. Gravity Project Z-code mappings.
IHE PIXm / PDQm ITI-83/84 Patient identity cross-referencing. MPI layer.
AIRS Taxonomy 2024 ed. Canonical human services classification vocabulary.

Standards make Trellis portable. What Trellis learns from the network is what makes it valuable.

Built for real-world interoperability

FHIR R4 HSDS 3.0 360X SMART on FHIR HL7 v2 REST / GraphQL SFTP
Epic-compatible Cerner-compatible Athena-compatible OCHIN-compatible HSDS-compatible

Compatible systems

Trellis does not ask organizations to standardize on one stack. It meets systems where they already are.

EHRs

Epic, Cerner, Athena, OCHIN — clinical workflow context via SMART on FHIR and CDS Hooks

Case Management

Eccovia, Apricot, Clarity HMIS, Netsmart — care coordination context via REST and GraphQL surfaces

211 / CIE Systems

Directory source of truth — any HSDS-compatible system nationally via bulk import and delta feeds

Referral Networks

Transactional coordination and outcome signal via 360X-connected platforms


Where Trellis sits

Trellis does not replace the systems above it. It connects them into a learning layer below.

EXISTING SYSTEMS EHR Case Mgmt Referral Network 211 / Directory Legacy Systems TRELLIS intelligence layer Ranked Matches contextual shortlist Network Signal capacity + outcomes Loop Closure 360X events Analytics dashboards + reporting INTELLIGENT OUTPUTS

Not just integration. Intelligence.

Traditional integrations move data. Trellis understands it.

Normalize

Unifies inconsistent formats, naming conventions, and data structures across systems automatically.

Enrich

Adds metadata like capacity status, closure rates, acceptance history, and network performance signal.

Monitor

Continuously evaluates system behavior, referral outcomes, and network health in real time.


Three ways to connect

Not every system is equally modern. Trellis is designed for that reality.

API call

Best for systems that want Trellis intelligence embedded directly into existing workflows. POST /v1/match returns a ranked shortlist in a single call.

REST · GraphQL · OAuth 2.0

Embedded widget

Best for clinical environments that need context-aware matching without forcing users into a separate tool. Reads context directly from the EHR encounter.

SMART on FHIR · CDS Hooks

Data feed / import

Best for 211 systems, regional data partners, and organizations managing resource catalogs at scale. Staged diff review before any changes go live.

HSDS 3.0 · bulk ZIP · SFTP

For systems without APIs, Trellis provides HL7 v2 adapters and flat-file / SFTP pipelines. No organization should be excluded because its systems are old.

What each system sends and receives

Different systems contribute different context. Trellis accepts what each one knows and returns the intelligence needed for the next decision.

Caller type Method Sends Receives
EHR systemSMART on FHIR / CDS HooksFHIR Patient + SDOH ConditionsRanked matches surfaced inline
Case managementREST / GraphQLClient profile: SDOH flags, demographics, enrollmentRanked shortlist with eligibility pre-check
CLR platformREST + 360X outcomesClient SDOH at initiation; outcome events after referralRanked shortlist; enriched matching from signal
CHW portalAuthenticated REST (OAuth 2.0)Manual context: need toggles, location, languageRanked shortlist with full detail + refer payload
211 data partnerHSDS bulk import / deltaHSDS ZIP package (org, location, service CSVs)Staged diff report; anonymized outcome feed
Public / patient appPublic read API (rate-limited)ZIP, service category, languagePublished listings; no network signals

Multi-speed connectivity for the real world

Networks are uneven by nature. Some organizations have APIs. Others have email and a shared inbox. Trellis is designed for both.

Tier 1

Full API / FHIR

For large CBOs with technical infrastructure. Direct FHIR/REST integration, full bidirectional data flow.

Tier 2

Hosted portal

For mid-size organizations. Web portal for listing management, referral receipt, and status updates. No developer required.

Tier 3

Email/SMS bridge

For small CBOs and volunteer-run organizations. Referrals delivered as structured emails with a one-click response form. No login, no account, no portal.


Every connection makes the network smarter.

Integration is not a one-time event. Once a system connects to Trellis, every referral it sends and every outcome it reports strengthens the intelligence layer for the whole network.

More connected systems means better matching, better visibility, and better routing for everyone — regardless of which EHR, referral platform, or case management system they use.

The network gets smarter every time it runs.

Systemsends request Trellismatches CBOresponds Loopcloses outcome signal feeds future rankings

Every system can connect.
The network gets smarter when they do.

Ready to connect the systems you already have?

Whether your environment speaks FHIR, REST, HSDS, HL7, or nothing modern at all, Trellis provides a path to integration — without replacing what already works.

You don't need a new stack. You need a better layer.