How Health Plans Are Using RAF Score APIs to Power Care Gap Closure

The Care Gap Problem

Care gap closure in risk adjustment refers to the process of identifying and resolving discrepancies between a Medicare Advantage member's true clinical complexity and the HCC conditions reflected in their current RAF score — using API-driven real-time intelligence to close documentation and coding gaps at the point of care.

A RAF score API embeds real-time risk intelligence directly into clinical and administrative workflows. Care gaps in risk adjustment represent the difference between a member's true clinical complexity and what is reflected in their current RAF score. Every unclosed gap means two things simultaneously: the plan is not being paid accurately for the risk it carries, and the member's medical record does not fully reflect their health status.

The scale of the problem is significant. Industry analyses consistently show that 20-35% of chronic HCC conditions fail to recapture annually, and an additional 10-15% of clinically present conditions are never identified through standard coding workflows. For a typical 100,000-member MA plan, this translates to tens of thousands of open care gaps at any point during the year.

• Revenue Impact: Each unclosed HCC gap represents approximately $500-$3,000 in annual revenue depending on the condition's coefficient value under V28. Aggregate gap-related revenue loss can reach 8-15% of total plan risk-adjusted revenue
• Clinical Impact: Gaps in condition documentation often correspond to gaps in care management — conditions not documented are frequently conditions not actively managed
• Compliance Exposure: Both undercoding (missed gaps) and overcoding (closing gaps without proper documentation) create regulatory risk, making accurate gap identification and closure essential
• Operational Challenge: Traditional gap closure relies on manual chart review and periodic provider outreach, creating bottlenecks that prevent timely resolution

The fundamental limitation of traditional gap closure programs is speed. By the time gaps are identified through quarterly claims analysis, distributed to providers through static reports, and addressed during scheduled encounters, months have passed and the payment year window has narrowed.

How RAF APIs Enable Gap Identification

RAF Score APIs transform gap identification from a batch analytics exercise into a real-time capability. By calculating risk scores programmatically and comparing them against expected values, APIs can identify gaps the moment sufficient data is available.

• Current vs Expected Score Comparison: The API calculates a member's current RAF score based on documented diagnoses and compares it against an expected score derived from prior-year HCCs, pharmacy signals, and clinical indicators. The delta identifies the gap magnitude and likely condition sources
• HCC-Level Gap Detail: Beyond aggregate score differences, APIs return condition-level detail showing which specific HCCs from prior years have not been recaptured and which suspected conditions have supporting evidence but no current-year documentation
• Coefficient-Weighted Prioritization: Each identified gap is weighted by its RAF coefficient value, enabling automated prioritization that focuses resources on the highest-value closure opportunities
• Real-Time Updates: As new claims and encounter data flow in, the API recalculates scores and updates gap status automatically. A gap closed by a provider encounter today is reflected in the system today — not in next quarter's report
• Multi-Model Support: APIs supporting V28, V24, ESRD, and RxHCC models simultaneously enable plans to track gaps across all relevant risk models without separate analytical processes

The automation of RAF scoring through APIs eliminates the manual analytical bottleneck that limits traditional gap programs. What previously required analyst teams running quarterly queries now happens continuously and programmatically.

Real-Time Scoring at Point of Care

The most impactful use of RAF Score APIs is embedding risk intelligence directly into the clinical encounter. When providers can see a member's care gaps during the visit, gap closure becomes part of routine care rather than a separate administrative process.

• Pre-Visit Score Display: When a member checks in, the API calculates their current RAF score and surfaces open gaps in the provider's EHR view. The provider sees both the documented conditions and the suspected gaps before entering the exam room
• Encounter-Triggered Recalculation: As the provider adds diagnosis codes during the encounter, the API recalculates the RAF score in real time, showing the incremental impact of each documented condition. This immediate feedback loop reinforces comprehensive documentation
• Gap Closure Confirmation: When a provider evaluates and documents a suspected condition, the API confirms gap closure immediately, removing it from the open gap list and updating the member's projected RAF score
• Missing Documentation Alerts: If the provider's coded diagnoses do not include conditions flagged as high-probability gaps, the system can generate a non-intrusive alert suggesting clinical evaluation of those conditions
• Post-Visit Summary: After the encounter, the API generates a summary showing gaps addressed, gaps remaining, and the net RAF score impact of the visit — providing data that supports both provider performance tracking and plan revenue forecasting

Point-of-care integration requires careful design to avoid disrupting clinical workflows. The API approach offers flexibility that standalone calculators cannot match, enabling customized presentation of gap data tailored to each provider's preferred workflow.

Population-Level Gap Analysis

While point-of-care scoring addresses individual encounters, population-level gap analysis reveals systemic patterns that require strategic intervention.

• Condition Category Heat Maps: Aggregate API data across the full member population to identify which HCC categories have the lowest recapture rates. If diabetes HCCs recapture at 90% but behavioral health HCCs recapture at only 55%, the investment priority is clear
• Provider Network Analysis: Compare gap closure rates across providers to identify documentation champions and providers needing additional support. API data enables weekly rather than quarterly provider scorecards
• Geographic Clustering: Identify geographic areas where gap density is highest, potentially indicating access barriers, provider shortages, or member populations that are harder to engage
• Revenue Forecasting: Use aggregate gap data to project the revenue impact of planned closure activities. If 10,000 open gaps carry an average coefficient of 0.25, the plan can project approximately $26 million in addressable revenue and track closure progress against that target
• Trend Analysis: Track gap density over time to measure program effectiveness. Declining gap rates indicate improving capture; stable or increasing gaps despite intervention signal process failures that need diagnosis

Population-level analysis using HCC recapture data from the API creates the strategic intelligence layer that guides resource allocation across the plan's risk adjustment program.

Workflow Integration Patterns

Health plans deploying RAF Score APIs for gap closure follow several proven integration patterns, each suited to different organizational structures and technology capabilities.

• EHR-Embedded Integration: The API is called from within the EHR application, displaying gap data in the provider's native workflow. This pattern has the highest adoption rates but requires EHR vendor cooperation or custom development using API use case patterns
• Care Management Platform Integration: Gap data from the API feeds care management systems, enabling care coordinators to prioritize outreach, schedule appointments, and track closure activities for high-gap members
• Provider Portal Integration: Plans surface gap data through provider-facing portals where practices can view their panel's open gaps, download pre-visit summaries, and track their closure performance metrics
• Member Outreach Automation: API-identified gaps trigger automated member communications — appointment reminders, health assessment invitations, or condition-specific educational materials designed to prompt care-seeking behavior
• Analytics Dashboard Integration: API data feeds executive dashboards showing real-time gap status across the entire plan population, enabling leadership to monitor gap closure as a key operational metric

The most effective implementations layer multiple integration patterns. A single API-powered gap identification engine feeds the EHR for point-of-care use, the care management platform for outreach, and the analytics dashboard for oversight — all from the same real-time data source.

Measuring Gap Closure Impact

Measuring the impact of API-powered gap closure requires both financial and operational metrics that connect technology investment to outcomes.

• Gap Closure Rate: The percentage of identified gaps resolved within defined time windows — 30 days, 90 days, and year-to-date. Target: 75-85% closure by end of Q3. Track separately for recapture gaps (prior-year conditions) and new suspect gaps
• Revenue per Closed Gap: Calculate the actual RAF coefficient value generated by each closed gap to validate revenue projections and optimize condition prioritization algorithms
• Time-to-Closure: Measure the elapsed time from gap identification to documented closure. API-enabled programs typically achieve 50-70% shorter time-to-closure compared to quarterly report-based programs
• Provider Adoption Metrics: Track how many providers actively use point-of-care gap data, how often gap alerts result in clinical evaluation, and what percentage of evaluations confirm the suspected condition
• RAF Score Trajectory: Monitor the plan's aggregate RAF score trajectory against prior-year baselines. Effective gap closure programs should produce stable or improving RAF scores for clinically stable populations
• API Utilization: Track API call volumes, response times, and error rates to ensure the technical infrastructure supports the operational program without bottlenecks

Report gap closure metrics alongside financial performance metrics at the same cadence. When leadership sees the direct connection between gap closure rates and revenue outcomes, investment in API-enabled workflows becomes self-justifying.