Quick take: One API call, the whole RAF story
Hot take for the risk-adjustment nerds:
A single member can carry a RAF of 0.9 or 2.4 depending on whether their chronic conditions ever made it from the chart into a coded, model-mapped HCC. Same person. Same care. Wildly different score.
That gap is almost never clinical. It's plumbing.
The teams that close it stopped doing RAF math in spreadsheets and put the logic behind one deterministic endpoint — an ApiKey-authenticated REST endpoint where you send the model, segment factor, demographics, and ICD-10 codes, and get back an itemized HCC + Total breakdown (Grand Total, MA-adjusted, normalized), not just a number. That's the whole pitch behind the VBC Risk Analytics RAF Score API: same inputs, same explainable output, every time.
Want the use cases (real-time scoring, batch rescoring after a model change, gap suspecting, audit reconciliation)? The full rundown lives here: RAF Score API use cases.
VBC Risk Analytics. Educational only — not coding, billing, or clinical advice; verify against the current CMS Rate Announcement. Synthetic data only.
