A community care hub is a centralized organization that manages contracting, data, and quality oversight for a network of community-based organizations, so health systems and payers can work with one accountable entity instead of dozens of disconnected agencies. The ASPE/RAND environmental scan documents this structure across states, and the Administration for Community Living frames it as capacity-building infrastructure. The operational difference that matters: a hub closes the loop on referrals, something a directory of services never does.
TL;DR:
- True community care hubs are responsible for tracking referral outcomes, not just listing service availability, ensuring accountability for client needs.
- Operational success depends on building six core functions: leadership, contracting, network engagement, contract compliance, operations, and IT security, with underinvestment risking failure.
- Contracts with payers usually require standardized service definitions, outcome metrics, HIPAA compliance, and billing codes, which rely on mature data and reporting systems.
- Developing effective data flows involves establishing agreements before sharing data, using limited datasets, and standardizing status definitions among partners.
- Scaling hubs often benefits from specialized platforms like EquiLoop to manage complex referral tracking and outcome reporting at larger networks.
Table of Contents
- What Makes the Community Care Hub Model Different From a CBO Network
- Six Operational Domains Every Mature Hub Must Staff
- Who Hubs Contract With and What Payers Actually Demand
- Building Data Flows That Actually Close the Loop
- How Hubs Pay for Themselves Past the Pilot Grant
- Standing Up a Hub: A 12-Month Implementation Sequence
- What State Pilots and Rural Deployments Teach About This Model
- What WellCheck’s Deployment Data Shows About Closing the Loop
- When a Hub Should Consider a Platform Like EquiLoop
- Where to Go Next for Policy and Contracting Guidance
- Sources
What Makes the Community Care Hub Model Different From a CBO Network
Not every group of collaborating organizations qualifies as a hub. The label gets applied loosely, and that loose usage causes real confusion when a health system tries to figure out who is actually accountable for a referral once it leaves the clinic.
Three structural variants show up repeatedly in practice:
- Hub-and-spoke: one lead organization holds the payer contract, sets the terms, and distributes work and revenue to member CBOs, who act as spokes delivering direct service.
- Umbrella hub: a larger entity, often an FQHC or hospital system, absorbs a coalition of CBOs under its own compliance and billing infrastructure without necessarily branding itself as a hub.
- Network lead model: a designated organization coordinates health-related social needs services on behalf of a state Medicaid pilot, as seen in the North Carolina Healthy Opportunities Pilot and comparable New York efforts.
What separates a true community care hub model from a simple referral directory or an uncoordinated health alliance (UHA) is accountability for outcomes, not just visibility into available services. A directory tells a case manager that a food pantry exists three miles away. A hub tracks whether that referral was accepted, whether the client showed up, and whether the need was resolved, then rolls that data into a report a payer can act on. Hubs also serve as the single point of contact between health care entities and networks of CBOs, which is the specific function that reduces contracting complexity for a health system that doesn’t want to negotiate forty separate agreements.
CCHs show up most often in states running Medicaid Section 1115 waivers targeting health-related social needs, in AHEC-affiliated rural networks, and in county health department coalitions trying to standardize social care referrals across a service region.
Six Operational Domains Every Mature Hub Must Staff
A hub isn’t a concept you can run on goodwill and a shared spreadsheet. The functions model published by Partnership2ASC groups mature hub operations into six domains, and skipping any one of them tends to show up later as a contract you can’t fulfill.
- Leadership and governance. Someone has to set strategic direction, hold decision-making authority across member CBOs, and answer for performance when a payer asks hard questions.
- Strategic business development and contracting. This function negotiates payer agreements, prices services, and structures the terms that determine whether the hub survives past its first grant cycle.
- Network recruitment and engagement. Bringing new CBOs into the network, vetting their capacity, and keeping them engaged requires dedicated staff time, not an occasional email blast.
- Contract administration and compliance. Someone has to manage the paperwork side of every payer relationship, including audits, reporting deadlines, and regulatory filings.
- Operations. Day-to-day referral routing, quality assurance, and training for community health workers and navigators live here.
- Information technology and security. Data infrastructure, security protocols, and interoperability decisions determine whether the other five domains can actually function at scale.
Most hubs that stall out in year two underinvested in one of these six domains, usually IT or contract administration, and tried to compensate with more staff hours in operations. That trade doesn’t work. A hub without contract administration capacity will win a payer agreement and then fail to bill for it correctly.
Who Hubs Contract With and What Payers Actually Demand
Payers don’t sign with a hub because the mission is good. They sign because the hub reduces their own administrative burden and gives them one accountable party instead of a fragmented CBO landscape. Hubs reduce contracting complexity by providing access to a vetted network of CBOs and absorbing reporting and compliance obligations the payer would otherwise carry itself.
Typical partners in a mature hub arrangement include:
- Managed care organizations (MCOs) contracting for health-related social needs services under Medicaid managed care arrangements.
- State Medicaid agencies, often through 1115 waiver authority or targeted pilot programs.
- FQHCs, which frequently convene hubs directly because they already carry clinical trust and billing infrastructure that smaller CBOs lack, a point the AHRQ implementation guide makes directly.
- Hospitals and health systems, usually motivated by readmission penalties and community benefit obligations.
- Rural health networks and AHECs, which often anchor hubs in areas with thin CBO density.
Contracts payers expect to see include specific service definitions, outcome reporting cadences, HIPAA-compliant data handling terms, and billing mechanisms that map back to specific reimbursable codes. A hub that shows up to a payer negotiation without a standardized reporting format loses leverage immediately, because the payer has no way to verify what it’s paying for. Hubs that operationalize contracts well tend to negotiate a pilot period first, prove closed-loop completion rates, then expand scope in a second contract cycle rather than trying to sell a full-scope agreement on day one.
Building Data Flows That Actually Close the Loop
A referral directory tells you where to send someone. A closed-loop referral system tells you what happened after you sent them. That distinction is the entire operational core of the community care hub model, and it’s the piece most new hubs underbuild because it looks like a back-office IT problem instead of the thing payers are actually buying.
The practical build sequence, based on lessons documented in the RAND environmental scan, looks like this:
- Start with business associate agreements (BAAs). Get these signed with every CBO partner before any data moves, not after.
- Use a limited data set for shared reporting rather than pushing full protected health information across every partner, which reduces both risk and integration overhead.
- Begin with a secure portal or fax-to-digital workflow. Full EHR integration is a later milestone, not a starting requirement, and most successful pilots deliberately delayed it.
- Standardize your status taxonomy before you scale. Define what “referred,” “accepted,” “service started,” and “resolved” mean, and map every partner’s internal terms to those categories so payer reports aren’t reconciling five different vocabularies.
Pro Tip: Build your status taxonomy on paper with your three busiest CBO partners before you buy or build any software. If those three organizations can’t agree on what “resolved” means, no platform will fix that gap for you.
Hubs that skip taxonomy standardization discover the problem at the worst possible moment: during a payer audit, when three different partner reports use “closed” to mean three different things. A tool like EquiLoop can enforce a consistent status taxonomy across a partner network once it’s defined, but the definitional work has to happen before any platform decision, not after.
How Hubs Pay for Themselves Past the Pilot Grant
Most community care hubs launch on grant money and either diversify or die when that grant ends. Sustainable hubs braid Medicaid payments, MCO contracts, program fees, and grants rather than depending on any single stream, and that braiding has to start well before the original grant clock runs out.
Realistic revenue sources for a hub include:
- MCO service contracts paying per completed referral or per enrolled member served.
- State Medicaid pilot funding, often time-limited but useful for proving a model before it goes to full contract.
- Program-specific fees, such as bundled pricing for delivering an evidence-based chronic disease program like the National Diabetes Prevention Program through the hub’s CBO network, an approach the Coverage Toolkit documents in detail.
- Foundation and federal grants, useful for capacity building but risky as a sole funding source.
Diversifying revenue matters because a single MCO contract can be renegotiated, delayed, or cancelled, and a hub with no other income has no leverage in that renegotiation. Aggregating outcomes data across a whole CBO network lets a hub produce funder-ready reporting that no individual CBO could produce alone, and that reporting capability is often the specific asset that unlocks a second or third payer contract. Funders increasingly want to see completion rates, time-to-resolution, and demographic breakdowns of served populations, not just a count of referrals sent.
Standing Up a Hub: A 12-Month Implementation Sequence
Building a hub in the right order saves months of rework. Here’s a sequence that reflects what’s actually worked in state pilots and rural deployments.
- Months 0 to 2: Governance and MOUs. Establish the lead organization’s decision-making authority, draft memoranda of understanding with founding CBO partners, and hold at least two community engagement sessions to confirm the hub is solving a need residents actually recognize.
- Months 2 to 4: Staffing and workforce priorities. Hire or designate a contract administrator first, then build out community health worker and navigator capacity. Training curricula for CHWs and navigators, delivered through a program like the Workforce Development Academy, should run in parallel with hiring rather than after.
- Months 4 to 6: Minimum viable tech stack. Sign BAAs, define your status taxonomy, and stand up a secure referral portal. Resist the urge to build a custom EHR integration this early.
- Months 6 to 9: Pilot referral pathways with two or three CBO partners. Test the full loop, referral sent, accepted, service delivered, outcome recorded, before adding more partners.
- Months 9 to 12: Payer conversations and KPI baseline. Bring closed-loop completion data to a first MCO or Medicaid conversation, and set baseline KPIs for referral volume, acceptance rate, and time-to-resolution.
Pro Tip: Don’t onboard your full CBO network before your data flow is proven. A hub that tries to scale partners and technology at the same time usually breaks the technology first.
Community engagement can’t be a single kickoff meeting. Hubs that maintain ongoing resident advisory input tend to catch service gaps, like a transportation barrier that undermines a food referral pathway, months before a payer audit would surface the same problem.
What State Pilots and Rural Deployments Teach About This Model
The North Carolina Healthy Opportunities Pilot and comparable efforts in New York used network-lead organizations to coordinate health-related social needs services under Medicaid, and both surfaced a consistent set of lessons:
- Governance clarity has to come before technology decisions. Pilots that picked software before settling who had final decision-making authority spent months renegotiating both.
- IT integration is almost always harder and slower than partners expect. Pilots that assumed EHR interoperability on day one lost time waiting on vendor timelines.
- Funding models that rely on a single Medicaid waiver cycle create real anxiety for CBO partners, who need revenue certainty to keep staff.
- Community voice, when built into governance rather than added as an advisory afterthought, catches implementation gaps earlier.
For a rural network or a hub with thinner CBO capacity, the adaptation isn’t to skip these steps. It’s to sequence them over a longer runway and lean more heavily on an anchor institution, an AHEC or FQHC, for the compliance backbone smaller partners can’t build alone.
What WellCheck’s Deployment Data Shows About Closing the Loop
Tracking outcomes after a referral is made, not just listing available services, is the operational core of this model. That’s the design principle behind the Workforce Development Academy for training CHWs and navigators, and behind the specific artifacts a hub needs: a defined status taxonomy, an outcomes dashboard with columns for referral date, acceptance date, service delivery date, and resolution, and a reporting cadence payers can rely on.
In one rural health hub deployment built around a multi-partner ecosystem spanning both clinical and social services referrals, the platform recorded 22,682 individuals screened, 45,458 services delivered, and a 93.9% closed-loop completion rate.[^1] That completion rate is the number payers actually care about, because it answers the question a service count never can: did the referral resolve?
[^1]: Rural health hub deployment with a multi-partner ecosystem. Includes both clinical and social services referrals.
When a Hub Should Consider a Platform Like EquiLoop
Some hubs try to build closed-loop tracking with shared spreadsheets and fax logs, and for a two-partner pilot, that can work for a while. The problem shows up at scale: once a hub has a dozen CBO partners and a payer contract demanding monthly outcome reports, manual tracking breaks down fast, and staff start spending more time reconciling spreadsheets than coordinating care.
EquiLoop is built specifically for that gap. It handles SDoH screening and intake, routes referrals to clinical and community partners, tracks follow-up status against a standardized taxonomy, and generates the outcomes dashboards and funder-ready reports hubs need for payer renewals. It’s locally configurable, meaning it sits around the partner network and reporting requirements a hub already has, rather than asking a hub to rebuild its workflows around new software.
The buy-versus-build decision usually comes down to timeline and staff capacity. If a hub has in-house developers and a year to spare, a custom build is possible. Most hubs don’t have either, and the closed-loop referral implementation guide walks through what that build actually requires before a program director commits staff time to it. For hubs ready to see how a platform handles the taxonomy, routing, and reporting work described throughout this article, WellCheck offers a 30-minute demo to walk through specific referral pathways and reporting requirements.
Where to Go Next for Policy and Contracting Guidance
The ASPE/RAND environmental scan remains the most complete case-study reference for how hubs form and operate across different states. The NCBI Bookshelf version of that same research breaks out the contracting and single-point-of-contact functions in more detail. For Medicaid-specific implementation lessons, the CHCS report on New York and North Carolina pilots is the sharpest practitioner resource available. The ACL’s partnership guidance is the best starting point for aging and disability network capacity-building questions, and the Coverage Toolkit from NACDD and CDC offers concrete detail on structuring evidence-based program contracts through a hub.
Sources
- Community Care Hubs: A Promising Model for Health and Social Care Coordination — NCBI Bookshelf
- Building Community Care Hubs to Address Health-Related Social Needs: Lessons from New York and North Carolina Medicaid (CHCS)
- Partnerships to address whole-person health — Administration for Community Living (ACL)
