Skip to main content

Houston Healthcare Nonprofits: HRSA and FQHC Compliance Software

Published: Last updated: Reviewed: Sources: bphc.hrsa.gov ryanwhite.hrsa.gov houstontx.gov dshs.texas.gov hrsa.gov

TLDR

Houston healthcare nonprofits operating as FQHCs live inside HRSA's program requirements regime, with UDS reporting as the operational backbone and Operational Site Visits as the periodic high-stakes evaluation. Ryan White Part A funding through Houston Health Department layers on its own service category reporting, and Harris County Public Health contracts add categorical reporting on top. The compliance question is not whether to invest in clinical, financial, and governance systems - it is whether those systems produce defensible UDS data and OSV-ready evidence in the formats HRSA requires.

Houston healthcare nonprofits operating as Federally Qualified Health Centers live inside HRSA’s program requirements regime, which is one of the most prescriptive federal compliance environments in the nonprofit world. UDS reporting is the operational backbone - annual, patient-level, and consequential. Operational Site Visits are the periodic high-stakes evaluation against all 19 Health Center Program Requirements. Ryan White Part A funding through Houston Health Department layers on its own service category reporting and the payor of last resort discipline. Harris County Public Health and Texas DSHS contracts blend categorical funding with city, county, and state sources.

This article walks through the HRSA Section 330 framework, the UDS data infrastructure, the OSV evaluation cycle, and the Ryan White Part A overlay specific to Houston, with attention to what a system has to handle for a Houston FQHC to operate without crisis cycles.

HRSA Section 330 and the 19 program requirements

HRSA Section 330 funding under the Public Health Service Act supports FQHCs that provide comprehensive primary health care to medically underserved areas and populations. The 19 Health Center Program Requirements are organized around needs assessment, services, management and finance, and governance. They cover what services must be provided, how services must be provided to all residents regardless of ability to pay, what governance structure must be in place, what financial management systems must support the operation, and what quality improvement infrastructure must be maintained.

The substantive program requirements include provision of comprehensive primary care services across age groups, sliding fee discount schedule with documented methodology and consistent application across all patients, quality improvement and assurance program covering credentialing and privileging of clinical staff, financial management system with required cost accounting capability, and governing board with consumer-majority composition. The board composition rule is one of the more visible - at least 51% of board members must be patients of the health center, demographically representative of the patient population.

FTCA (Federal Tort Claims Act) deeming is an important operational dimension. Health centers that meet HRSA’s deemed status requirements receive medical malpractice coverage through FTCA for covered services delivered by covered providers. Annual deeming applications are required, and deeming status drives risk management documentation, credentialing, and the protocols that must be in place for FTCA-covered care.

UDS: the annual data submission that defines the year

The Uniform Data System (UDS) is HRSA’s annual reporting requirement for Section 330 grantees and FQHC Look-Alikes, due February 15 each year covering the prior calendar year. UDS aggregates patient-level data across demographics, clinical services, clinical quality measures, staffing, and financials.

The demographic tables capture patient counts by age band, race, ethnicity, primary language, income relative to federal poverty level, and insurance status. The visit and service tables capture visits by type and counts of patients receiving specific services. The clinical quality measure tables capture metrics including childhood immunization, cervical cancer screening, depression screening and follow-up, diabetes control, hypertension control, and others. The financial tables capture costs and revenue by service category.

Data quality requirements are stringent. Implausible patient counts (patients counted in multiple age bands, totals that do not reconcile across tables), demographic totals that do not match service totals, and quality measure denominators that do not match clinical service counts produce HRSA-required corrections. UDS data is published on HRSA’s website at the health center level, supports comparative dashboards, and feeds federal funding decisions including HRSA’s Quality Improvement awards.

UDS production is an organizational discipline that runs throughout the year. Data quality work happens monthly, not in February. Health centers that try to produce UDS in the six weeks before submission consistently produce data with rework cycles after submission and weaker quality measure performance than peers.

Operational Site Visits and the evidence file

Operational Site Visits (OSVs) occur on a roughly three-year cycle for most Section 330 grantees. The HRSA-contracted review team spends multiple days on site reviewing compliance with all 19 program requirements. The review covers clinical operations (chart audits, sliding fee application observation, scope of services confirmation), financial systems (cost accounting, audit findings, financial management), governance (board composition, board minutes review, board engagement with operations evidence), and management (credentialing files, quality improvement program documentation, billing and collections).

The evidence file required for an OSV is substantial. Policies and procedures across all 19 program requirements. Board minutes and committee minutes covering at least the most recent two years. Audited financial statements and management letters. UDS submissions and any HRSA correction correspondence. Credentialing files for all licensed clinical staff. Quality improvement plan, QI committee minutes, and evidence of QI cycle completion. Sliding fee discount schedule, methodology documentation, and audit evidence of consistent application. FTCA deeming application materials.

The compliance posture that supports a clean OSV is continuous documentation, organized in a way that survives staff turnover. The compliance posture that produces findings is a frantic three-month evidence assembly cycle before the OSV date. The difference is the system that holds policies, board materials, and evidence year-round versus the absence of one.

Ryan White Part A and Houston Health Department

Houston is a Ryan White Part A Eligible Metropolitan Area and Health Services Delivery Area, with the Houston Health Department serving as the Part A recipient. Healthcare nonprofits delivering HIV-specific services often hold Ryan White Part A subrecipient contracts with the Health Department alongside their HRSA Section 330 grants. Some Houston organizations also hold direct Ryan White Part C or Part D awards from HRSA.

Ryan White service categories include outpatient ambulatory health services, oral health, mental health, substance use treatment, medical case management, and supportive services. Each service category has its own eligibility criteria, allowable cost rules, and reporting requirements. Client-level data is captured in CAREWare or successor systems, with quarterly and annual reporting flowing to the Health Department and ultimately to HRSA HIV/AIDS Bureau.

The payor of last resort rule is the operational discipline that catches the most subrecipients. Ryan White funds may not pay for services covered by other payors. Verification at every encounter, documentation of payor enrollment efforts for eligible clients, and billing protocols that bill other payors first are required. Failures here produce repayment of Ryan White expenditures covering multiple program years.

Texas DSHS, Harris County, and the categorical overlay

Texas DSHS administers Title V Maternal and Child Health Block Grant pass-through funding and a range of categorical health programs. Harris County Public Health contracts blend categorical funding with county sources. These contracts add reporting on top of HRSA and Ryan White obligations, often with overlapping clinical service categories that require source-specific cost allocation. The Uniform Guidance cost principles at 2 CFR 200 Subpart E govern federal sources, and Single Audit obligations under Subpart F cover the federal funding totality.

What a system has to handle

For Houston healthcare nonprofits operating as FQHCs, the practical software requirements break down across three system tiers. The EHR/PM is the system of record for clinical and patient-level data, supporting UDS data extraction and Ryan White CAREWare integration. The financial system is the system of record for GL data, supporting cost reporting, financial statements, and Single Audit. The grants management system is the orchestration layer holding contract terms, deliverable status, match documentation where applicable, and the audit trail from grant draw to specific eligible cost.

Reporting must support UDS submission, Ryan White Part A quarterly and annual reporting through CAREWare and Houston Health Department portals, Texas DSHS contract reporting, Harris County contract reporting, and Single Audit. Compliance overlays must track sliding fee discount methodology and application audit, board composition and consumer-majority requirements, FTCA deeming, and credentialing and privileging. Document management must hold the OSV evidence file year-round in a structure that survives staff turnover.

The HRSA 330 reporting guide walks through UDS production discipline in more detail, and the Houston grant deadline calendar covers the broader public funding calendar that Houston healthcare nonprofits operate inside.

The single thread running through this environment is that HRSA program requirements are continuous, not periodic. UDS data quality, sliding fee application consistency, board engagement, and quality improvement cycle execution are evaluated through ongoing operations and documented through the systems that support those operations. The compliance work is the substantive work of running a federally qualified health center, not an artifact added on top.

HRSA's Health Center Program funds nearly 1,400 health centers nationally serving more than 30 million patients, governed by 19 Health Center Program Requirements covering services, management, finance, and governance

Source: HRSA Bureau of Primary Health Care

Ryan White Part A funds Eligible Metropolitan Areas with high HIV/AIDS prevalence, with Houston serving as one of the EMAs and Houston Health Department serving as the recipient that administers subrecipient contracts to healthcare providers

Source: HRSA HIV/AIDS Bureau

The Uniform Data System (UDS) is HRSA's annual reporting requirement for Section 330 grantees and FQHC Look-Alikes, due February 15 each year and covering patient demographics, clinical services, clinical quality measures, staffing, and financials

Source: HRSA Bureau of Primary Health Care UDS

Houston Healthcare Compliance Cadence
ObligationCadenceWhere it lives
UDS submissionAnnual by February 15EHR + financial system + UDS portal
HRSA Operational Site Visit~Every 3 yearsFull evidence file across 19 PRs
Ryan White Part A reportingQuarterly to Houston Health DeptCAREWare + financial system
Sliding fee applicationContinuous, every patient encounterEHR/PM system
FTCA deeming applicationAnnualRisk management + governance documentation
Single Audit (federal threshold)AnnualAuditor + GL

Q&A

Can a single grants management system handle UDS, Ryan White reporting, and the financial side?

UDS and Ryan White reporting both pull primarily from the EHR and practice management system for clinical and demographic data, and from the financial system for cost and revenue data. A grants management system holds the contract terms, deliverable status, match documentation, and the financial system trail from grant draw to specific eligible cost. The realistic posture is EHR/PM as the system of record for clinical data, financial system as the system of record for GL data, and grants management system as the orchestration layer that holds compliance documentation and reporting bridges. Trying to consolidate clinical data into a grants management system is the wrong direction; trying to consolidate compliance documentation into an EHR is also the wrong direction.

Q&A

What is the realistic financial cost of an OSV finding requiring corrective action?

Significant OSV findings can produce conditions on funding, requiring corrective action plans (CAPs) approved by HRSA before conditions are lifted. Common high-impact findings include sliding fee schedule application inconsistencies, board composition and engagement gaps, financial management system weaknesses, and quality improvement program deficiencies. The remediation cost is typically a combination of consultant time, internal staff time, and operational changes that take months to implement and longer to demonstrate effectiveness. Health centers with multiple conditions on funding face increased HRSA scrutiny and reduced flexibility in subsequent funding cycles.

Q&A

How should sliding fee discount methodology be documented?

HRSA Sliding Fee Discount Program guidance under PAL 2024-01 requires a documented methodology applied consistently across all patient encounters. The schedule must be based on the federal poverty guidelines, must provide nominal fees for patients at or below 100% FPL, must apply to all health center services, and must be applied based on income and family size at every encounter for non-insured and underinsured patients. Documentation of methodology must be maintained, application must be auditable in the EHR/PM system, and inconsistent application across providers or sites is a common OSV finding. The sliding fee schedule is one of the few HRSA program requirements where day-to-day operational practice is reviewed line by line at OSV.

Free resource

Get the Nonprofit Grant Compliance Checklist

A practical checklist for post-award grant compliance: restricted funds, reporting cadence, audit prep, and common failure points. Delivered by email.

We'll email the resource and a short follow-up sequence. Unsubscribe any time.

Email is required because the download link is delivered by email, not on-page.

There are approximately 90 healthcare nonprofits in houston in the United States that could benefit from unified donor and grant management.

Key Pain Points for Healthcare Nonprofits in Houston

  • HRSA Section 330 grantees must submit UDS (Uniform Data System) reporting annually with strict data quality requirements that affect future funding
  • Ryan White Part A funding for Houston HSDA flows through Houston Health Department with separate service category reporting beyond HRSA's HAB requirements
  • Sliding fee discount schedule under HRSA program requirements requires documented methodology and consistent application across patient encounters
  • Harris County Public Health contracts blend with state DSHS pass-through funding, producing source-specific reporting on overlapping clinical programs
  • Operational Site Visits (OSVs) by HRSA evaluate clinical, financial, and governance compliance against 19 program requirements with significant remediation cost

Common Grant Types

  • HRSA Section 330 Health Center Program funding for FQHCs
  • Ryan White HIV/AIDS Program Part A grants administered through Houston Health Department
  • Ryan White Part C and Part D direct HRSA grants
  • Texas Department of State Health Services Title V Maternal and Child Health funding
  • Harris County Public Health categorical contracts
  • Federally Qualified Health Center Look-Alike status (no Section 330 grant but program rules apply)

Compliance Notes

Houston healthcare nonprofits operating as Federally Qualified Health Centers (FQHCs) receive HRSA Section 330 grant funding under the Public Health Service Act, governed by 42 USC 254b and HRSA Bureau of Primary Health Care policies including PIN 2014-01 (governance), PAL 2024-01 (sliding fee), and the 19 Health Center Program Requirements. UDS reporting is the single most consequential annual data submission, required by February 15 each year and aggregating clinical, financial, demographic, and quality measure data at the patient and visit level. Operational Site Visits (OSVs) occur on a multi-year cycle and evaluate compliance with all 19 program requirements. Ryan White HIV/AIDS Program Part A funding for the Houston Eligible Metropolitan Area and Health Services Delivery Area flows through the Houston Health Department under the Ryan White HIV/AIDS Treatment Extension Act and HAB program requirements, with service category reporting for outpatient ambulatory health services, oral health, mental health, substance use treatment, medical case management, and supportive services. Texas DSHS Title V Maternal and Child Health Block Grant pass-through carries its own program rules. Harris County Public Health contracts blend categorical funding with city and county sources. The Uniform Guidance at 2 CFR 200 applies to all federal awards including HRSA Section 330 and Ryan White, with Single Audit triggering at $750,000 in federal awards in a fiscal year.

GrantPipe pricing at a glance

Every plan includes a 1-month free trial, unlimited users, and access to the same source-of-truth feature catalog.

Enterprise

Complex grant-funded teams that need custom terms

$1,329/mo $15,948/yr billed annually
Contact sales

Frequently asked

Frequently Asked Questions

What does HRSA Section 330 actually require for compliance?
HRSA Section 330 grantees must comply with 19 Health Center Program Requirements organized around needs assessment, services, management and finance, and governance. The substantive requirements include: provision of comprehensive primary health care to all residents in the service area regardless of ability to pay; sliding fee discount schedule with documented methodology and consistent application; quality improvement and assurance program with credentialing and privileging; financial management systems with required cost accounting; governing board with consumer-majority composition (at least 51% of members must be patients of the health center); and federal tort claims coverage under FTCA when the health center elects FTCA coverage and meets deemed status requirements. Compliance is evaluated through annual UDS reporting, periodic Operational Site Visits, and ongoing HRSA project officer engagement.
How does UDS reporting actually work?
The Uniform Data System (UDS) is HRSA's annual reporting requirement for Section 330 grantees and FQHC Look-Alikes, due February 15 covering the prior calendar year. UDS aggregates patient-level data on demographics (age, race, ethnicity, primary language, income relative to federal poverty level, insurance status), clinical services (visits by type), clinical quality measures (childhood immunization, cervical cancer screening, depression screening, diabetes control, hypertension control, and others), staffing, and financials (costs and revenue by service category). Data quality requirements are stringent - implausible patient counts, demographic totals that do not reconcile, and quality measure denominators that do not match clinical service counts produce HRSA-required corrections. UDS data is published on HRSA's website at the health center level and feeds federal funding decisions.
What is an Operational Site Visit and what does it evaluate?
An Operational Site Visit (OSV) is HRSA's on-site review of compliance with all 19 Health Center Program Requirements. OSVs occur on a roughly three-year cycle for most Section 330 grantees, conducted by HRSA-contracted teams over multiple days. The team reviews clinical operations (chart audits, sliding fee application, scope of services), financial systems (cost accounting, audit, financial management), governance (board composition, board oversight, board engagement with operations), and management (credentialing and privileging, quality improvement, billing and collections, staffing). Findings are categorized by severity. Conditions on funding can result from significant findings and require corrective action plans with HRSA approval before funding restrictions are removed.
How does Ryan White Part A flow through Houston Health Department?
The Ryan White HIV/AIDS Program Part A funds Eligible Metropolitan Areas and Transitional Grant Areas with high HIV/AIDS prevalence. Houston is a Part A jurisdiction, and the Houston Health Department serves as the recipient for Houston EMA/HSDA Part A funding. The Health Department administers Part A through subrecipient contracts with healthcare nonprofits delivering HIV-specific services. Substantive compliance is governed by HAB (HIV/AIDS Bureau) program requirements covering service categories (outpatient ambulatory health services, oral health, mental health, substance use treatment, medical case management, supportive services, and others), eligibility determination for clients (HIV-positive status documentation and Ryan White financial eligibility), payor of last resort requirement (Ryan White funds may not pay for services covered by other payors), and Aggregate Administrative Costs caps. CAREWare or successor systems are used for client-level data, and quarterly and annual reporting flows to the Health Department and ultimately to HRSA HAB.
What does the payor of last resort rule actually mean operationally?
The Ryan White payor of last resort rule means that Ryan White funds cannot be used to pay for services or items that another payor - Medicaid, Medicare, private insurance, the Texas HIV Medication Program, or another funding source - covers for the eligible client. Operationally, this requires verification at every encounter that no other payor is available, documentation of payor enrollment efforts for clients who appear eligible for other coverage, and billing protocols that bill other payors first and Ryan White only for the residual. Payor of last resort failures are among the most common findings in Ryan White subrecipient monitoring and can produce repayment of Ryan White expenditures covering multiple program years.
What records have to survive after a HRSA grant period?
Federal record retention under 2 CFR 200.334 is generally three years after final expenditure report. Patient medical records carry separate retention obligations under Texas state law (Texas Medical Practice Act and Texas Health and Safety Code) and HIPAA - typically seven years from last patient encounter for adults and longer for minors. Ryan White client records carry retention obligations under HAB program rules. The practical implication is that the medical records side of the retention schedule is longer than the grant records side in most cases, and the systems that hold each must support those different retention windows independently.

Next step

See the workflow in GrantPipe.

Start a 1-month free trial and test donor, grant, restricted-fund, and compliance work in one place.

Start your 1-month free trial