The platform

Connect360 is how we actually build a Community Information Exchange.

Purpose-built for government agencies, community networks, and coordinated care — not another platform primarily serving hospitals and health plans. Connect360 sits above your existing systems and connects them, rather than replacing them. IBM builds the platform; the community runs the network.

Capabilities

Eight capabilities. One coordinated platform.

Each one is configurable per deployment. Each one is built to meet the compliance bar that government and healthcare buyers expect.

01 Public portal Community-facing directory, eligibility screening, resource discovery — with anonymous access where it matters for trust.
02 Client portal Authenticated residents see their shared record, manage consent, and engage directly with the organizations in their care team.
03 Provider portal The daily-use surface for caseworkers, navigators, and intake staff across the network. Fast, searchable, configured per organization.
04 Closed-loop referrals The core of the platform. Every referral tracked from creation through delivery to documented outcome, with configurable workflows per domain.
05 Assessments & screening Social needs assessments, eligibility screens, outcome follow-ups — with per-community governance over what gets asked and who sees the answers.
06 Person-centered record One unified view across providers, under the person's consent control. Built on FHIR, extendable to the domains a community prioritizes.
07 Analytics & AI Population-level outcomes at the network level. AI-assisted care navigation where it helps front-line workers, never in place of them.
08 Compliance & security HIPAA, HITRUST, 42 CFR Part 2-capable, FedRAMP-aligned infrastructure. The posture agencies and health plans require.
Architecture

Connect360 doesn't replace your systems. It connects them.

A coordination layer above what you already run — integrating with EHRs, case management platforms, 211 services, and state-agency systems through open standards (FHIR, HSDS, HL7).

Residents · Providers
Public portal Client portal Provider portal
Connect360 platform
Closed-loop referrals Person-centered record Assessments & outcomes Analytics & AI
Integration & standards
FHIR HSDS HL7 Open APIs
Your existing systems
EHRs Case management 211 platforms State HHS systems Medicaid data
Where Connect360 fits

Different category. Different buyer. Different build.

Connect360 is built for a different primary audience than the category's best-known platforms. Not better or worse — different in how it's designed and who it's designed for.

 
Connect360
FindHelp
Unite Us
Primary buyer
Government agencies, community networks, coordinated-care convening bodies
Health plans, health systems, with community surface
Health plans, payers, value-based care networks
Governance model
Community-governed network; IBM operates the platform
Vendor-operated SaaS
Vendor-operated network with health plan anchors
Standards posture
FHIR-native, HSDS-exportable, HL7-integrated
HSDS directory-focused
Integration available, varies by deployment
Federal compliance
HIPAA · HITRUST · 42 CFR Part 2-capable · FedRAMP-aligned
HIPAA · HITRUST
HIPAA · SOC 2
Best for
State deployments, SDOH infrastructure grants, community-led CIEs, workforce and re-entry coordination
Broad resource directory at scale; single-health-plan implementations
Payer-anchored networks tied to clinical workflows
Where it's going

The public roadmap. Honestly labeled.

What's live today, what's in flight for 2026, and what's on the longer horizon. A detailed internal roadmap with release dates, feature prioritization, and customer-specific commitments is available to IBM partners and sellers with access.

Live · Production
The core platform
  • Closed-loop referral workflows
  • Provider & client portals
  • Assessment engine
  • FHIR person record
  • Network analytics
  • HIPAA + HITRUST compliant
2026 · In flight
Interoperability + AI
  • Expanded FHIR resource coverage
  • Federated cross-CIE exchange
  • AI-assisted care navigation
  • 42 CFR Part 2 enablement
  • HSDS v3 export
  • Advanced outcome measurement
Gated · Roadmap
Detailed internal roadmap
  • Release dates by feature
  • Customer-specific commitments
  • Feature prioritization rationale
  • Integration partner pipeline
  • Research previews
  • Access via roadmap.building-cies.com
Compliance & trust

Built to the bar agencies require.

Every deployment of Connect360 carries the compliance posture that state and federal buyers expect. Data remains under the community's governance; the platform meets the technical standards that make those governance decisions enforceable.

HIPAAHITRUST42 CFR Part 2FedRAMP-alignedFHIRHSDSSOC 2 Type II
What's next

See Connect360 in the communities actually running it.

The platform is easier to evaluate when you see it operating. TogetherNow has been running Connect360 in Monroe County for years. ReCity Network is deploying it in Durham now. Both are honest about what's worked, what's harder, and what the next phase looks like.

See the deployments Read the case