A continuaciónSiguiente guía
Riesgos de cumplimiento de codificación y actualización de IA
sociedad
GUÍA de industrias
AI in HCC risk adjustment coding scans medical records for documented chronic conditions that map to Hierarchical Condition Categories, which CMS uses to calculate risk scores and payments for Medicare Advantage enrollees.
Escuche esta guíaNarrado por IA · ~3 min
Each supported diagnosis can change what a plan is paid, so accuracy matters in both directions. Missing a real condition means underpayment. Adding a diagnosis the record does not support creates overpayment, audit liability and possible False Claims Act exposure.
The CMS-HCC model predicts each Medicare Advantage enrollee's expected cost from demographic factors and from diagnosis codes grouped into Hierarchical Condition Categories. The result is a risk adjustment factor (RAF) that scales payment to the plan. Hierarchies mean that when related conditions of different severity are coded, only the most severe category in that family counts. Diagnoses reset every calendar year, so a chronic condition must be documented again each year. It must also come from a face-to-face encounter with an acceptable provider type. Diagnostic radiology reports, for example, do not qualify. CMS phased in a revised model, known as V28, over 2024 through 2026. It restructured the categories and removed many diagnosis codes from payment, which changed which findings matter. AI tools read clinical notes, find mentions of conditions, check whether each one is current, negated or historical, map them to ICD-10-CM codes and then to HCCs, and link each finding to supporting text. Coders review the suggestions. That review matters because the most common AI error is to treat a mention as a diagnosis. Problem lists, medication lists, family history and phrases like "history of" do not show that a condition was evaluated or treated at the visit. Audit risk is real. CMS conducts Risk Adjustment Data Validation (RADV) audits, and a 2023 rule allowed extrapolating audit findings across a contract starting with payment year 2018. OIG reports have questioned diagnoses reported only through chart reviews or in-home health risk assessments. The Justice Department has brought False Claims Act cases alleging that plans used chart reviews only to add codes, without deleting unsupported ones. A frequent misconception is that MEAT (Monitor, Evaluate, Assess or Address, Treat) is a CMS regulation. It is an industry convention for auditing. The actual requirement is documentation that supports the code under ICD-10-CM guidelines.
A retrospective review finds type 2 diabetes with neuropathy documented in a clinic note, with an assessment and plan, but the diagnosis never reached a claim. The coder confirms the documentation and submits E11.40 for that date of service.
An AI running a two-way review flags an office visit coded with an acute stroke code for a patient whose stroke happened years earlier. It recommends deleting that code and replacing it with a code for stroke history or for its lasting effects, as documented.
Notes mention dialysis three times a week, but no provider has documented end-stage renal disease. The tool does not code ESRD. It sends a documentation query so the treating clinician can address it at the next visit.
Before an annual wellness visit, the system lists conditions that were documented last year but not yet this year. The clinician must actually evaluate each one during the visit. A checkbox confirmation is not enough.
Pressure on risk adjustment is rising from several directions: the V28 transition, expanded RADV audits with extrapolation, and continued federal enforcement. Tools marketed only on how many new codes they find are a growing liability. Tools that combine finding missed conditions with deleting unsupported codes, and that keep an evidence trail, fit where regulators appear to be heading. Using AI before visits, to prompt clinicians to evaluate conditions at the visit rather than hunting for codes afterward, is a more defensible pattern. Specific future changes to the payment model should be taken from CMS announcements, not from predictions.
Boletín gratuito
Tres noticias verificadas sobre IA cada mañana de lunes a viernes, explicadas con claridad. Gratis para siempre y sin anuncios.
Un correo cada día laborable. Date de baja con un clic. Nunca vendemos ni compartimos tu dirección.
Ponte a prueba
Corrección inmediata en cada respuesta y un certificado para compartir, con un ID verificable, cuando apruebas un curso.
Apoya la educación gratuita sobre IA. AI Understanding es una organización sin fines de lucro 501(c)(3): sin anuncios ni muros de pago, nunca. Hacer una donación
AI in HCC risk adjustment coding scans medical records for documented chronic conditions that map to Hierarchical Condition Categories, which CMS uses to calculate risk scores and payments for Medicare Advantage enrollees. Each supported diagnosis can change what a plan is paid, so accuracy matters in both directions. Missing a real condition means underpayment. Adding a diagnosis the record does not support creates overpayment, audit liability and possible False Claims Act exposure.
Las jerarquías evitan la doble contabilización dentro de una familia de condiciones. Sólo la categoría más grave cuenta para la puntuación de riesgo.
Las puntuaciones de riesgo se reconstruyen cada año a partir de los encuentros calificados de ese año, por lo que cada año se debe respaldar nuevamente una condición de por vida.
Los codificadores no pueden asignar un diagnóstico que el proveedor no documentó. El paso correcto es una consulta para que el médico tratante pueda abordar la afección.
La revisión bidireccional corrige errores en ambas direcciones. Los casos de la Ley de Reclamaciones Falsas se han dirigido a revisiones de gráficos que supuestamente solo agregan códigos.
MEAT es una forma ampliamente utilizada de organizar la revisión, pero el estándar real de CMS es la documentación que respalda el diagnóstico según las pautas de la CIE-10-CM.
sigue aprendiendo
Más guías seleccionadas para este tema.
A continuaciónSiguiente guía
Riesgos de cumplimiento de codificación y actualización de IA
sociedad