Reporting Under a 638 Contract: The Negotiated Framework
Unlike competitive federal grants — where reporting requirements are standardized in the Notice of Award and largely non-negotiable — reporting under a 638 contract is defined by the Annual Funding Agreement (AFA). This means that reporting frequency, format, scope, and deadlines are all subject to negotiation between the tribe and IHS.
This is a significant advantage of 638 contracting, but it also means that reporting obligations vary across contracts, IHS Areas, and contractor maturity levels. There is no single “638 reporting manual.” What follows is a comprehensive guide to the reporting types that most tribal health 638 contractors will encounter, with practical guidance on how to manage each one effectively.
GPRA Reporting
The Government Performance and Results Act (GPRA) of 1993 (P.L. 103-62), as updated by the GPRA Modernization Act of 2010, requires federal agencies to establish performance goals and report on their achievement. IHS has developed a comprehensive set of GPRA clinical measures that apply to all IHS-funded health programs — including those operated by tribes under 638 contracts.
IHS GPRA Clinical Measures
IHS GPRA measures cover key areas of clinical performance. The specific measures and targets are updated annually through the IHS GPRA process. As of the most recent reporting cycle, core GPRA measure categories include:
| Category | Example Measures | Reporting Basis |
|---|---|---|
| Diabetes | HbA1c testing, ideal glycemic control, LDL assessment, blood pressure control | Annual; based on patient population data |
| Behavioral health | Depression screening, suicide risk assessment, substance use screening | Annual; encounter-based |
| Immunizations | Childhood immunization rates, influenza vaccination, adult immunizations | Annual; age cohort-based |
| Maternal & child health | Prenatal care in first trimester, well-child visits, developmental screening | Annual; event-based |
| Cancer screening | Cervical cancer screening, breast cancer screening, colorectal cancer screening | Annual; age/sex cohort-based |
| Access to care | Patient wait times, appointment availability, after-hours access | Varies; often quarterly |
GPRA Data Sources and Extraction
GPRA data is typically extracted from the clinical health information system used by the tribal health program. Most tribal 638 programs use one of two systems:
- RPMS (Resource and Patient Management System). The IHS-developed electronic health record system. RPMS includes built-in GPRA reporting packages (the “CRS” — Clinical Reporting System) that extract measure data directly from patient records. Many tribal 638 programs continue using RPMS under a separate IT support agreement with IHS.
- Commercial EHR systems. Some tribal programs have transitioned to commercial EHR systems (NextGen, athenahealth, Cerner, Epic). When using a commercial system, the tribe is responsible for developing GPRA-equivalent reports or mapping their data to the IHS GPRA specifications. This is a significant technical undertaking and should be planned for during EHR transition.
GPRA data is submitted to IHS through the IHS Data Mart or directly to the IHS Area Office. The reporting period typically aligns with the federal fiscal year (October 1 – September 30), with final data due within 30–60 days after the period ends.
IHS Reporting Portals and Systems
Tribal 638 contractors interact with several IHS data systems for reporting purposes:
- IHS Data Mart / National Data Warehouse. The central repository for IHS clinical and administrative data. GPRA data, workload statistics, and demographic data are uploaded here. Access requires an IHS user account and appropriate permissions.
- Payment Management System (PMS). The HHS payment system where tribal contractors draw down funds from their 638 contract. PMS also serves as the submission point for SF-425 Federal Financial Reports.
- Federal Audit Clearinghouse (FAC). Where Single Audit reports are submitted. Not IHS-specific, but IHS monitors FAC submissions for all 638 contractors.
- Behavioral Health Information System (BHIS). For programs contracting behavioral health or substance abuse PFSAs, BHIS captures encounter and outcome data specific to behavioral health services.
- National Diabetes Prevention Program (NDPP) Portal. For diabetes prevention and treatment programs, specific reporting through the NDPP data collection system.
Annual Report Requirements
Most AFAs require an annual report that provides a comprehensive summary of the contract period. While format varies, a strong annual report typically includes:
- Executive summary. High-level overview of program accomplishments, service volume, and key outcomes for the contract period.
- Service delivery summary. Patient/client counts, encounters by type, geographic coverage, and any expansion or contraction of services during the period. Compare against AFA targets.
- GPRA performance. Summary of GPRA measure results with trend analysis (comparison to prior years). Identify measures where the program met, exceeded, or fell short of targets, and explain variances.
- Financial summary. Total expenditures against the contract amount, breakdown by major budget category, CSC utilization, and any carryover amounts.
- Staffing summary. Current staffing levels compared to plan, key vacancies and recruitment efforts, and staff development activities.
- Challenges and plans. Significant challenges encountered during the period and strategies for the coming year, including any proposed modifications to the AFA.
The annual report is both a compliance document and a negotiation tool. A well-prepared annual report demonstrates program quality and positions the tribe for favorable AFA renewal terms, including potential reductions in reporting burden as the tribe progresses toward mature contractor status.
SF-425 Federal Financial Reports
The SF-425 (Federal Financial Report) is the standard form for reporting financial status on federal awards, including 638 contracts. While 638 contractors have more flexibility than grant recipients in how they manage funds, the SF-425 reporting requirement ensures transparency in federal fund utilization.
SF-425 Key Fields for 638 Contractors
| Field | What to Report |
|---|---|
| Total federal funds authorized | The full contract amount (Secretarial amount + CSC) from the AFA |
| Federal share of expenditures | Total expenditures charged to the 638 contract during the reporting period. Separate Secretarial amount expenditures from CSC expenditures. |
| Federal share of unliquidated obligations | Committed but not yet expended amounts (purchase orders, contracts in progress) |
| Total federal share | Sum of expenditures + unliquidated obligations |
| Unobligated balance | Authorized amount minus total federal share. For 638 contracts, a carryover balance is generally permissible without prior approval. |
| Program income | Third-party collections (Medicaid, Medicare, private insurance) earned through the contracted programs. Report gross collections. |
SF-425 filing frequency is specified in the AFA — typically quarterly or semi-annually. Most tribes submit SF-425s through the Payment Management System (PMS). Ensure your accounting system can generate the data needed for SF-425 fields at the required frequency.
Categorical Reporting
Depending on the specific PFSAs contracted, tribal programs may have additional categorical reporting obligations tied to specific program areas:
Behavioral Health Reporting
Programs contracting behavioral health or substance abuse treatment PFSAs typically report to IHS through the Behavioral Health Information System (BHIS). Required data elements include patient demographics, diagnoses, treatment episodes, and outcomes (treatment completion, relapse rates, functional improvement). Some IHS Areas also require reporting through the Substance Abuse and Mental Health Services Administration (SAMHSA) Treatment Episode Data Set (TEDS) for substance abuse programs.
Diabetes Program Reporting
Tribal diabetes programs funded through the Special Diabetes Program for Indians (SDPI) — whether through a 638 contract or a separate SDPI grant — report through the SDPI data system. This includes patient registry data, clinical outcomes (HbA1c, blood pressure, lipids, kidney function), and program activity data (diabetes education sessions, community wellness events). SDPI reporting is annual, with data typically due by January 31 for the prior calendar year.
Community Health Representative (CHR) Reporting
CHR programs have their own reporting framework, including activity logs, home visit records, patient education contacts, and referral tracking. IHS Area Offices typically require quarterly CHR activity reports showing the volume and type of services provided.
Environmental Health Reporting
Contracted environmental health programs report on facility inspections, injury investigations, food safety surveys, and institutional environmental health services. Data is submitted through the IHS Environmental Health Reporting System.
Mature vs. Non-Mature Contractor Reporting
One of the most practical benefits of mature contractor status is the ability to negotiate reduced reporting requirements. The differences can be significant:
| Report Type | Non-Mature Contractor | Mature Contractor |
|---|---|---|
| Program reports | Quarterly narrative and statistical reports | Annual narrative report only |
| SF-425 financial | Quarterly | Semi-annual or annual |
| IHS monitoring visits | Annual or semi-annual site visits | Biennial or as-needed; more consultative |
| GPRA data | Annual (same for all contractors) | Annual (same for all contractors) |
| Corrective action plans | May be required for any identified deficiency | Typically addressed through mutual consultation |
Even mature contractors must submit GPRA data annually and comply with Single Audit requirements. The reduced reporting applies primarily to AFA-negotiated program and financial reports. See the eligibility guide for how mature contractor status is assessed.
Building a Reporting Calendar
With multiple reporting streams operating on different schedules, a consolidated reporting calendar is essential. Here is a typical annual reporting timeline for a tribal 638 health contractor:
| Month | Typical Reporting Activities |
|---|---|
| October | New fiscal year begins. Finalize prior-year GPRA data extraction. Begin AFA renegotiation for current year. |
| November–December | Submit Q4 (July–September) SF-425 if quarterly. Submit final GPRA data to IHS Data Mart. |
| January | Q1 (October–December) program report due (if quarterly). SDPI annual data due (January 31). Begin Single Audit preparation. |
| February–March | Q1 SF-425 due. Annual report for prior fiscal year due (typically by March 31). Single Audit fieldwork. |
| April | Q2 (January–March) program report due. Finalize AFA for current year. |
| May–June | Q2 SF-425 due. Single Audit report finalized and submitted to FAC (due within 9 months of fiscal year end — June 30 for September year-end). |
| July | Q3 (April–June) program report due. Mid-year financial review with IHS Area Office (if applicable). |
| August–September | Q3 SF-425 due. Close-out procedures for fiscal year. Prepare for GPRA data extraction. Begin next-year AFA planning. |
This calendar assumes a federal fiscal year (October–September) contract period and quarterly reporting. Adjust based on your specific AFA terms. If your organization also manages competitive grants on different fiscal years, the reporting calendar becomes significantly more complex — the Tribal Healthcare Funding Guide discusses managing multi-stream reporting schedules.
Reporting Best Practices
Effective reporting is not just about meeting deadlines — it is a tool for demonstrating program quality, supporting AFA negotiations, and progressing toward mature contractor status. Practical recommendations:
- Automate GPRA extraction. If using RPMS, configure the CRS (Clinical Reporting System) to run GPRA reports monthly, not just at year-end. Monthly monitoring allows early identification of measures falling below targets, giving clinical staff time to intervene.
- Maintain data quality. GPRA measures are only as good as the underlying clinical data. Invest in data entry training, regular data quality audits, and clinical coding accuracy. A strong GPRA performance starts with clean data, not last-minute report manipulation.
- Use reporting to tell your story. Annual and program reports should highlight successes, contextualize challenges, and demonstrate the impact of tribal self-determination on community health outcomes. These reports are read by IHS Area Office staff who influence mature contractor designations and AFA terms.
- Reconcile financials monthly. Do not wait until the SF-425 is due to reconcile your 638 contract expenditures. Monthly reconciliation catches miscodings, missed allocations, and cash flow issues early.
- Negotiate reporting reductions proactively. If you have a strong compliance track record, do not wait for IHS to offer reduced reporting. In your next AFA negotiation, propose a transition from quarterly to semi-annual or annual reporting, citing your compliance history.
Reporting gaps are one of the most common compliance issues affecting 638 contractors. The common mistakes guide covers how reporting failures can affect contract renewals and what to do when you fall behind.