FQHC Braided Funding: When Section 330, Ryan White, and SAMHSA BHI Overlap

Federally Qualified Health Centers are, by design, braided-funded organizations. The FQHC model assumes multiple revenue streams — HRSA Section 330 as the base, Medicaid as the primary payer, and supplemental grants to expand scope and serve specific populations. A well-functioning FQHC braids these streams so seamlessly that patients experience a single integrated health center, regardless of which funding stream pays for their visit.

The compliance side is less seamless.

A small FQHC — single site, $8-15 million budget, 50-120 staff — commonly manages five to eight concurrent funding streams: HRSA Section 330 (the core federal grant), Medicaid (fee-for-service or PPS), Ryan White (if HIV services), SAMHSA Behavioral Health Integration (if BHI), state contracts (maternal health, family planning, immunization), CDC cooperative agreements, and foundation grants. Each stream has its own compliance framework, reporting schedule, cost allocation requirements, and audit expectations.

The approximately 1,400 FQHCs in the United States share this operational reality. They also share something else: a remarkably consistent set of compliance pain points that stem not from any single grant being unreasonable, but from the interactions between grants when managed simultaneously.

This guide covers the FQHC braided funding stack — what each stream requires, where the frameworks conflict, and what it takes to manage them as an integrated compliance operation.

---

The FQHC Funding Stack

HRSA Section 330: The Base Layer

Every FQHC receives a Section 330 grant from HRSA's Bureau of Primary Health Care (BPHC). This is the foundational funding that defines the FQHC — without it, the organization is a community health center but not a Federally Qualified one.

Award range: $500,000 to $10M+ (varies by scope, sites, and patient volume) Framework: 2 CFR 200 Fiscal year: Federal (October-September), though budget periods may differ Key compliance requirements:

• 19 HRSA program requirements (governance, scope of services, staffing, sliding fee discount, quality improvement, and more)
• UDS (Uniform Data System) annual reporting — comprehensive clinical, financial, and operational data due in February for the prior calendar year
• HRSA Operational Site Visit (OSV) — periodic comprehensive review of compliance with all 19 program requirements
• SF-425 federal financial reporting
• Single Audit (virtually all FQHCs exceed the $750,000 threshold)

The 330 compliance nuance: Section 330 compliance is ongoing, not periodic. The 19 program requirements must be met continuously — not just at renewal or site visit. An FQHC found non-compliant during an OSV may face conditions on its grant, progressive action, or in extreme cases, loss of FQHC status. This makes Section 330 compliance the highest-stakes element of FQHC operations.

Medicaid: The Revenue Engine

For most FQHCs, Medicaid is the largest revenue stream — often 40-60% of total revenue. FQHCs receive either a Prospective Payment System (PPS) rate or a fee-for-service rate, depending on the state's payment methodology.

Framework: CMS cost principles Fiscal year: Calendar (January-December) for cost reports Key compliance requirements:

• Medicaid cost report (annual, calendar year)
• PPS rate reconciliation (for PPS states)
• Encounter data submission
• Conditions of participation
• State Medicaid-specific requirements

The Medicaid compliance nuance: The PPS rate is calculated from the FQHC's costs. This means cost allocation directly affects future revenue — if costs are underallocated to Medicaid, the PPS rate will be lower than it should be, reducing reimbursement for every Medicaid visit going forward. Getting the allocation right isn't just a compliance requirement; it's a revenue determination.

Ryan White HIV/AIDS Program

FQHCs providing HIV services often receive Ryan White funding (Part C for early intervention or Part A/B through regional planning bodies).

Framework: 2 CFR 200 + Ryan White-specific requirements (HRSA HIV/AIDS Bureau) Fiscal year: Federal (October-September) Key compliance requirements:

• Ryan White Services Report (RSR) — client-level data
• SF-425 federal financial reporting
• Program-specific quality measures
• Payer of last resort requirement (Ryan White pays only when no other payer covers the service)

The Ryan White compliance nuance: The "payer of last resort" requirement creates a direct interaction with every other funding stream. Ryan White cannot pay for a service that Medicaid, a state contract, or any other source covers. This means the cost allocation must route costs to Ryan White only when no other stream is eligible — a funding routing logic that most allocation spreadsheets handle poorly.

SAMHSA Behavioral Health Integration

Many FQHCs receive SAMHSA grants to integrate behavioral health services into primary care settings — typically through the Primary and Behavioral Health Care Integration (PBHCI) program or the CCBHC model.

Framework: 2 CFR 200 Fiscal year: Federal (October-September) Key compliance requirements:

• SPARS/GPRA data
• Quality measures (CCBHC measures if certified)
• SF-425 federal financial reporting
• Program-specific deliverables

The SAMHSA BHI compliance nuance: Behavioral health integration means that the same visit may involve both primary care (Section 330) and behavioral health (SAMHSA) services. When a patient sees a PCP and a behavioral health consultant on the same day — an integrated care model — the cost allocation must determine which funding stream covers which component of the visit. The clinical integration that SAMHSA is paying for creates compliance complexity in how costs are attributed.

State Contracts

FQHCs commonly hold state contracts for specific programs: maternal and child health, family planning (Title X), immunizations, STI screening, and state-funded behavioral health.

Framework: State-specific terms Fiscal year: State (July-June, typically) Indirect cost cap: Commonly 10-15%

CDC Cooperative Agreements

Some FQHCs receive CDC funding for specific public health activities — cancer screening, diabetes prevention, HIV prevention, immunization.

Framework: 2 CFR 200 Fiscal year: Federal Often smaller awards with specific deliverables.

Foundation Grants

Community foundations, health conversion foundations, and national funders provide supplemental funding — typically for workforce development, technology, patient navigation, or facility improvements.

---

Where the FQHC Frameworks Collide

Collision 1: Section 330 + Medicaid Cost Allocation

This is the most consequential allocation decision for any FQHC. Section 330 covers the costs of operating the health center that aren't covered by patient revenue (Medicaid, Medicare, private insurance, sliding fee). Medicaid cost reports must accurately reflect the costs of providing Medicaid-covered services.

If too much cost is allocated to Section 330, the Medicaid cost report understates costs, the PPS rate is too low, and the FQHC loses revenue on every Medicaid visit. If too much cost is allocated to Medicaid, the Section 330 grant may appear to be underspent, potentially affecting future award levels.

The allocation between Section 330 and Medicaid is not arbitrary — it must reflect actual service delivery. But the boundary is fuzzy: enabling services (care coordination, outreach, transportation) funded by Section 330 support Medicaid patients. Quality improvement activities funded by Section 330 improve Medicaid outcomes. Administrative staff support both. Getting this allocation right requires a clear methodology and consistent application.

Collision 2: Ryan White Payer of Last Resort

Ryan White's payer-of-last-resort requirement means costs can only be charged to Ryan White if no other funding stream covers the service. In practice, this creates a funding routing decision for every HIV-related service:

1. Is the patient Medicaid-eligible? → Bill Medicaid first
2. Is the service covered by a state contract? → Charge the state contract
3. Is the service covered by Section 330? → Charge Section 330
4. Only if no other payer covers the service → Charge Ryan White

This routing logic must be applied consistently, documented for each patient encounter, and reconciled with the cost allocation. An HIV-positive patient who is also Medicaid-eligible and receives behavioral health services funded by SAMHSA touches four funding streams in a single visit — and the allocation must follow the payer-of-last-resort hierarchy.

Collision 3: Multiple Federal Grants with Different Indirect Cost Treatments

An FQHC with Section 330, Ryan White, and SAMHSA grants has three federal awards under 2 CFR 200 — all eligible for the organization's full negotiated indirect cost rate. But each grant has its own budget with its own indirect cost line. The total indirect costs recovered across all three grants cannot exceed actual indirect costs.

Additionally, the state contracts typically cap indirect costs at 10-15%, creating a structural underrecovery. The FQHC must track:

• Full indirect rate applied to federal grants
• Capped rate applied to state contracts
• Indirect costs embedded in the Medicaid PPS rate
• Total recovery across all mechanisms ≤ actual indirect costs

Collision 4: UDS + SAMHSA + Medicaid Data Alignment

The HRSA Uniform Data System requires comprehensive clinical and operational data for the calendar year. SAMHSA requires GPRA and quality measures data for the federal fiscal year. Medicaid requires encounter data for the calendar year.

These three data sets overlap substantially — the same patients, the same visits, the same clinical outcomes. But the reporting periods differ (UDS = CY, SAMHSA = FFY, Medicaid = CY), the measure definitions differ, and the data aggregation differs. An FQHC must ensure that the clinical data reported to HRSA, SAMHSA, and Medicaid is consistent — because auditors and program officers will compare.

Collision 5: HRSA Operational Site Visit Readiness

HRSA OSVs review compliance with all 19 program requirements — including financial management, governance, and scope of services. The financial management review examines the FQHC's cost allocation methodology, internal controls, and compliance with 2 CFR 200.

An OSV finding on cost allocation doesn't just affect the Section 330 grant — it raises questions about every other funding stream that shares the same allocation methodology. If HRSA determines that the FQHC's allocation methodology is deficient, the same deficiency applies to Ryan White, SAMHSA, and Medicaid allocations.

This means OSV preparation is not a Section 330 exercise — it's an enterprise compliance exercise that tests the entire braided funding infrastructure.

---

The FQHC Cost Allocation Methodology

The Standard Approach

Most FQHCs use a cost allocation methodology that follows this structure:

Step 1: Direct assignment. Costs that benefit a single funding stream are charged directly (e.g., HIV test kits → Ryan White; dental equipment → Section 330 dental expansion).

Step 2: Clinical cost allocation. Shared clinical costs (clinician salaries, clinical supplies, EHR) are allocated based on encounters, patient visits, or clinical FTEs by program area.

Step 3: Enabling services allocation. Enabling services (care coordination, transportation, outreach, translation) are allocated based on the populations served — often by patient count or visit count per funding stream.

Step 4: Administrative allocation. Administrative costs (finance, HR, IT, executive leadership) are allocated through the indirect cost pool using MTDC, FTEs, or direct costs as the base.

Step 5: Facility allocation. Facility costs are allocated by square footage, adjusted for program-specific space.

The Section 330 Scope Question

A recurring challenge: which costs are "Section 330 costs" versus "general FQHC operating costs"?

Section 330 funds the health center's required scope of services — primary care, preventive care, enabling services — for patients regardless of ability to pay. But the health center also provides services funded by other streams (HIV care, behavioral health, specific state programs). The cost allocation must separate Section 330-funded activities from activities funded by other streams.

In practice, this separation is imperfect because the FQHC model is integrated — a primary care visit may involve Section 330-funded screening, SAMHSA-funded behavioral health assessment, and Medicaid-billable medical treatment, all in a single encounter. The allocation methodology must handle these blended visits systematically, not on a case-by-case basis.

The UDS Alignment Imperative

UDS data drives FQHC policy, funding, and evaluation at the national level. HRSA uses UDS to assess health center performance, allocate supplemental funding, and evaluate the program. The financial data in the UDS must align with the FQHC's audited financial statements and cost allocation methodology.

When UDS financial data contradicts the Section 330 SF-425 or the Medicaid cost report, it raises questions during OSVs and audits. The three data sets must tell a consistent story about the FQHC's costs, revenues, and service delivery — even though they're reported to different agencies on different schedules using different formats.

---

Practical Guidance for FQHC Braided Compliance

Build the Methodology Around Encounters

For FQHCs, the encounter is the unit of service delivery — and it should be the primary allocation base for clinical costs. Every visit is documented in the EHR with patient demographics, services provided, diagnoses, and payer. This encounter data is the most defensible basis for allocating clinical costs across funding streams.

Map each encounter type to its primary funding stream:

• Primary care visit, Medicaid-eligible patient → Medicaid
• Behavioral health visit, SAMHSA-funded program → SAMHSA
• HIV care visit, uninsured patient → Ryan White (payer of last resort)
• Preventive visit, sliding fee patient → Section 330

Use encounter volume (or clinical hours by program) to allocate shared clinical costs — clinician supervision, clinical supplies, EHR costs.

Separate the Section 330 "Wrap-Around"

Section 330 doesn't pay for specific services — it pays for the infrastructure that makes services available regardless of ability to pay. The sliding fee discount program, enabling services, and unfunded clinical capacity are Section 330's domain.

In the cost allocation, Section 330 absorbs:

• The sliding fee discount (difference between charges and collections for low-income patients)
• Enabling services costs not attributable to other grants
• Clinical costs for uninsured/underinsured patients not covered by other streams
• Infrastructure costs not recovered through Medicaid, grants, or patient revenue

This "wrap-around" function means Section 330 is the residual funder — it covers what's left after other streams cover their share. The allocation methodology should reflect this by allocating other streams first (Medicaid, Ryan White, SAMHSA, state contracts), then assigning remaining costs to Section 330.

Negotiate Your Indirect Cost Rate Strategically

FQHCs with significant state contracts face the indirect cost cap problem — state contracts pay 10-15% while actual overhead may be 20-30%. The federally negotiated rate should reflect true overhead costs, even if some streams cap recovery.

When negotiating or renewing your NICRA:

• Include all legitimate indirect costs in the pool
• Use MTDC as the base (standard for HRSA-funded organizations)
• Document the rate calculation thoroughly — it will be reviewed during OSVs
• Understand that the rate applies to all 2 CFR 200 awards (Section 330, Ryan White, SAMHSA, CDC) but not to state contracts or Medicaid

The indirect cost underrecovery on state contracts is a structural cost of doing business. Budget for it explicitly rather than discovering it at year-end.

Prepare for the OSV Continuously

HRSA OSVs are not scheduled predictably — an FQHC may be reviewed every 3-5 years. But the 19 program requirements must be met continuously. The organizations that perform well on OSVs are the ones that treat compliance as an ongoing operational discipline, not a review preparation exercise.

For braided funding compliance specifically, OSV readiness means:

• Cost allocation methodology is documented, current, and consistently applied
• Financial data in the most recent UDS aligns with audited financial statements
• Indirect cost rate documentation is current and available
• Personnel effort is documented and matches financial allocations
• Ryan White payer-of-last-resort documentation is maintained per patient
• Board governance (a Section 330 requirement) includes financial oversight of the full braided portfolio, not just the 330 grant

---

The FQHC Compliance Stack

Function	Common Tool	Gap
EHR	eClinicalWorks, Athena, NextGen, Epic Community	Good encounter data, limited financial reporting
Accounting	Sage Intacct (dominant), QBO (smaller FQHCs)	Tracks transactions, doesn't allocate or validate
Practice Management / Billing	EHR-integrated or separate	Claims processing, not grant compliance
UDS Reporting	EHR-based extraction + manual compilation	Annual exercise, not integrated with ongoing compliance
Grant Compliance	Spreadsheets + consultants	No cross-framework allocation, no automated validation

The gap remains the same as in other braided-funded organizations: no operational layer between service delivery (EHR) and financial recording (accounting) that models funding rules, allocates costs across frameworks, and produces framework-specific outputs.

For FQHCs, the gap is amplified by the volume of encounters (thousands per month), the number of funding streams (5-8), and the stakes of getting the allocation right (PPS rate accuracy directly affects revenue).

---

This guide is part of GrantBridges's braided funding compliance series. See also: Braided Funding Is an Operations Problem, the Cost Allocation Methodology Guide, and the Compliance Framework Comparison Chart.