People ask why there's both a RAF score calculator and a RAF score API when they both run the same math.They don't do the same job.
The calculator is for the moment a coder is looking at one chart. Pick the model — V28, V24, RxHCC, ESRD, CMMI-HCC — pick the risk factor, drop in up to 20 ICD-10 codes, and out comes a revenue impact report with V24 and V28 side by side and the MA payment spelled out. PDF it, attach it to the query, move on.
It answers: what is this patient worth, and what did documentation miss?
The API is for the moment nobody is looking at anything. It sits inside the EMR, the population health platform, the risk capture tool, and scores the whole panel while everyone sleeps. Potential, cumulative, delta.
It answers: which 1,000 of these 40,000 patients should a human open tomorrow?
The failure mode that shows up most often: a team buys the second problem's solution for the first problem, or spends a year doing the API's job by hand in the calculator.
One chart at a time is a coder's tool. Forty thousand charts is an integration.
Figure out which question is actually being asked. Then pick the door.
🔗 Full breakdown of when each one wins → RAF Score Calculator vs API
🔗 If the interactive route is the one → the RAF score calculator decomposes a member's score on the spot.
Free tier on the calculator, free trial on the API.












