RAAPID raises Series A funding with a Strategic “Industry Trifecta”. Read More

Neuro-Symbolic AI Powered

RAAPID’s
Prospective Risk Adjustment Solution

Reads clinical indicators in claims, labs, and charts to flag emerging suspects so physicians can act.

Prospective Risk Adjustment

Surface Emerging Suspects No Chart or Claim Shows Yet

RAAPID reads clinical indicators in claims, labs, and charts to flag emerging suspects so physicians can act.

Prospective LP a 4
1

Platform
(prospective to RADV)

6

Integration paths
(FHIR, HL7, APIs, SFTP)

5

Output categories
(emerging suspects to deletes)

EHR Integration

Works with any EHR. Connect through FHIR, HL7, or a simple file transfer.

b 72
What Sets RAAPID Apart: Emerging Suspects

From a Flag in the Chart to Action at the Visit

RAAPID connects labs, symptoms, and medications across the chart to flag conditions never documented or claimed.

Illustrative

Before the visit · RAAPID

Step 1

In the record

Hypertension, two eGFR results below 60, no kidney diagnosis.

Step 2

RAAPID flags

Suspected CKD stage 3, linked to both labs.

Illustrative

At the visit · Physician acts

Step 3

At the visit

The physician walks the patient through the lab trend and asks about swelling, fatigue, or changes in urination.
Step 4

Next step

The physician orders a repeat eGFR and urine albumin test, then documents CKD if confirmed or rules it out.

Built for Risk-Bearing Organizations

Provider-Sponsored Health Plans

Health Systems

ACOs and Physician Groups

Health Plans with Provider Networks

Why Prospective Risk Adjustment Stalls

One gap in the record, felt three ways: at the visit, in the IT stack, and on the P&L.

Alert Fatigue

Physicians override more than half of EHR alerts. Suspect prompts land in the same inbox, and the undiagnosed condition sitting in the labs never reaches the visit.

Point-Solution Sprawl

Every vendor wants its own portal, its own feed, and its own integration project. Physicians will not leave the EHR, and security will not approve another unmanaged tool.

Unlinked Chart Review Exclusion

From CY 2027, CMS excludes diagnoses from unlinked chart review records. A condition not confirmed in a visit will not move your risk score.

How Suspects Reach the Visit

Why Most Suspect Lists Never Become Diagnoses

Claims-Based Suspecting

Built from what was already billed
  • ✕Misses conditions never claimed
  • ✕ No clinical indicators behind the prompt
  • ✕ Long lists physicians learn to ignore

Chart-Reading NLP

Reads the chart, still probabilistic
  • – Text matches, not clinical reasoning
  • – Thin explanation per suggestion
  • – Every item needs manual validation

RAAPID's Neuro-Symbolic AI

Finds the undiagnosed from clinical indicators, in the visit
  • ✓ Emerging suspects from labs, symptoms, and medications
  • ✓ Every suspect tied to its clinical indicators
  • ✓ Suspecting based on a clinical knowledge graph
  • ✓ One reviewed list per visit, inside the EHR

Built Around the Visit

Confirmed at the Visit. Every Time.

Confirmed During the Visit

A short, curated list per visit, each suspect with the labs, symptoms, and medications behind it. The physician confirms or rejects with a reason. Nothing is coded without a face-to-face encounter.

Inside the EHR, Not Another Portal

Suspects appear in the chart physicians already work in, and accepted conditions write back. Standards your team already supports, and no rip-and-replace.

Counts Under the 2027 Rules

A diagnosis confirmed in the encounter is linked by design, so it moves the risk score when unlinked chart review no longer does. Targeting puts review effort where findings are likely.

Prospective Risk Adjustment Solutions

Member Targeting and Pre-Visit Review

  • Prioritize members by probability of a finding across 100% of the MA and ACA population
  • Read about two and a half years of charts, claims, labs, and pharmacy data
  • Classify every condition: emerging, code gap, or recaptured
  • Curate the list, batched to each physician’s schedule, before the visit

Point of Care and Post-Visit Reconciliation

  • Deliver the reviewed list inside the EHR, clinical indicators one click away
  • Accept and document, or reject with a reason; unaddressed items carry forward
  • Reconcile the finalized chart against the claim before submission
  • Report acceptance, rejection reasons, and RAF accuracy by physician

RAAPID Prospective Workflow: One Platform, Three Layers

Data comes in from the systems you already run, the platform suspects from clinical indicators, and the
results land where physicians and leaders act.

1. Data Origination

Provider EMRs

Charts, notes, labs, medications

Claims and CMS

Encounter and eligibility data

Your data store

Cloud storage, warehouse, or file transfer. Bidirectional.

→
→

2. RAAPID AI Platform

AI Suspecting Engine

Reads the full chart; every suspect backed by clinical indicators

Targeting

Member prioritization across the MA and ACA population

→
→

3. Action Layer

Provider Insights

EHR integration and PDFs; accept or reject at the visit

Analytics and Dashboard

Campaigns, drill-downs, adoption by practice

Available as a SaaS application or API

The Same Visit, With and Without RAAPID

What changes when suspects come with clinical indicators

Typical suspect list
RAAPID Prospective
Data read
Typical suspect list
Claims only
RAAPID Prospective
Claims, charts, labs, pharmacy, radiology
Conditions found
Typical suspect list
Already claimed before
RAAPID Prospective
Emerging, never documented or claimed
Clinical indicators
Typical suspect list
None shown
RAAPID Prospective
Labs, symptoms, and medications with every suspect
Where physicians see it
Typical suspect list
Separate portal
RAAPID Prospective
Inside the EHR, during the visit, with write-back to the chart
Validation
Typical suspect list
Raw engine output
RAAPID Prospective
Curated by your reviewers or ours
After the visit
Typical suspect list
Nothing
RAAPID Prospective
Chart reconciled against the claim

~90K suspects across 257K members, surfaced in under two weeks at one regional provider-owned health plan.

Why Prospective Programs Stall

The Condition Is in the Chart. The Physician Never Sees It.

No Time to Dig Before the Visit

Physicians can't scan years of labs, notes, and medications for every patient. Conditions hiding in the data go unaddressed.

Every January, the Slate Resets

Chronic conditions must be documented again each year. The ones not revisited quietly drop off, and so does the accuracy of your risk scores.

Lists Without Evidence

Lists arrive from every health plan and EHR prompt, most without evidence. Physicians need one list they can act on, with the proof attached.

RAAPID brings one reviewed list to each visit, with the evidence behind every suspect.

Member Targeting and Pre-Visit+

Prepare Every Visit Before the Patient Arrives

Charts, claims, labs, and pharmacy data come in; your reviewers curate what reaches each physician.

Charts pulled only where findings are likely

Each condition shown once, hierarchies applied

Review rules and coding guidelines set per program

Batched to each physician's schedule, curated first

Illustrative

Tuesday schedule, reviewed

Ready

9:00
Patient A
Annual wellness visit

1 suspect

2 gaps

9:30
Patient B
Follow-up

1 gap

10:15
Patient C
Chronic care visit

1 suspect

1 add

11:00
Patient D
New patient

No findings

Point of Care

Give Physicians Answers Inside the EHR

Findings appear in the workflow physicians already use, with one click to the evidence behind each.

Accept and document, or reject with a reason

Anything not addressed carries to the next visit

Nothing coded without a face-to-face visit, per RADV

Rejection reasons improve each physician's list

Illustrative

Pre-visit findings

In your EHR

Suspected COPD

True suspect

View evidence: inhaler fills, 2 progress notes
Accept and document
Reject with reason
Type 2 diabetes with complications

Historical

View evidence: documented last year
Accept and document
Reject with reason
Post-Visit and Reporting

Close the Loop Before Claims Go Out

RAAPID checks the finalized chart against the claim and the physician’s decisions, before the claim goes out.

Unclaimed and unsupported codes flagged

Missing MEAT routed to CDI

Accepted at the visit but never documented, caught

Acceptance, rejections, and RAF accuracy by physician

Encounter reconciliation

Before submission

Captured
Accepted at the visit and documented

Ready

Missed
Accepted at the visit, not documented

Review

Unclaimed
Documented, missing from the claim

Add

Over-claimed
On the claim, no chart support

Remove

Missing MEAT
Monitoring or treatment evidence absent

To CDI

WHAT OUR CUSTOMERS SAY

"

RAAPID gave our organization a clear view of code gaps across our entire population, including conditions no one had documented before. Our physicians now go into each visit with a reviewed list of suspects and the chart evidence behind each one, and nothing is coded unless they confirm it. Closing code gaps is now part of the visit, not a year-end chase.

VP, Provider-Owned Health Plan

Explore the Latest From RAAPID

PH Case Study v7 Generalize version
Case Study

~90K Suspects Across 257K Members in Under Two Weeks

How a regional provider-owned health plan surfaced evidence-linked suspects from ~40M chart pages.
v28 beyond
Webinar

V28 Beyond the 2026 Transition: What Does It Means for Your Risk Adjustment Program?

V28 is fully live and locked in through 2027. Wynda Clayton explains what it means for your program.
v28
Guide

The Essential Guide to CMS-HCC Model V28

Access the full list of chronic conditions and key updates.

resolve hcc
Blog

How to Resolve HCC Gaps: Best Practices for Healthcare Providers

Strategies to close HCC gaps, keep coding accurate, and protect reimbursement.

Frequently Asked Questions 

Code gaps, unclaimed conditions, unsupported codes, and emerging suspects. You choose what reaches physicians.

A chronic condition never documented or claimed, inferred from labs, symptoms, and medications. Only the physician can confirm it.

No. Start with the step you’re missing and add the rest later.

Charts, claims, labs, pharmacy, and radiology from the last two years plus the current year, via EHR integration or file transfer.

Under two weeks for 257K members at one health plan.

Your pre-care nurses or coders, or RAAPID’s experienced coders. Your choice. Physicians only see the validated list.

Start with one practice of employed providers. Watch the acceptance dashboard, then extend to independent groups with your own adoption data in hand.

See What Your Next Visits Could Look Like

A walkthrough on sample charts, set up your way.

Members reviewed
0 K
Chart pages
0 M
Members with suspect conditions
0 K
Missed HCCs/RxHCCs
~ 0 K
~$ 0 M

Potential value

Results from one regional provider-owned health plan, in under two weeks. Potential revenue at 50% provider confirmation.

Prospective Risk Adjustment Solution Page

"*" indicates required fields

This field is for validation purposes and should be left unchanged.
Full Name*

What Our Customers Say

Talk to Our Customers

Have a candid conversation with a risk adjustment leader whose physicians now close suspect conditions in the visit, not at year-end.

Success Stories

Real results from real customers

Case Studies Banner Thumb 1

~90K Suspects Across 257K Members in Under Two Weeks

By a Regional Provider-Owned Health Plan

Transform Your Prospective Risk Adjustment Program

Frequently Asked Questions (FAQs)

Neural models read the full chart; a clinical knowledge graph applies coding and customer rules on top, so every suspect comes with its clinical indicators and the output follows your guidelines rather than a probability.
Claims-only lists cannot see a condition that was never claimed, and text matching alone produces prompts physicians ignore. Connecting labs, symptoms, and medications across the chart is what surfaces emerging suspects, each with the clinical indicators behind it.
No. RAAPID is EMR-agnostic: Epic, Oracle Health, athenahealth, eClinicalWorks, Allscripts and others, through FHIR R4, SMART on FHIR, HL7 v2, CDS Hooks, REST APIs, or SFTP. Pre-Visit can begin on the file transfer you already use while integration work is scheduled; once connected, Point of Care runs inside the EHR’s native workflow and accepted conditions write back to the chart.
You choose. Each output category can be switched on or off, so a team can start with emerging suspects only and let code gaps and recaptures flow to physicians for visibility. RAAPID surfaces the suspect with its clinical indicators, the physician decides, and the decision drives the chart and the claim.
Practice-level dashboards show acceptance, rejection reasons, and what each physician was shown, so support goes where it is needed instead of to every group equally.
Start with one practice of employed providers. Your pre-care nurses or coders, or RAAPID’s coders, curate the list. Watch the acceptance dashboard, then extend to independent groups with your own adoption data in hand.