Audit
Specificity Upgrade
Replacing an unspecified ICD-10-CM code with a more specific one supported by the documentation.
Definition
A specificity upgrade is the act of replacing a less specific (often "unspecified") ICD-10-CM code with a more specific code that is fully supported by the available clinical documentation. Common examples: I50.9 (Heart failure, unspecified) upgraded to I50.32 (chronic diastolic heart failure) when ejection fraction is documented; N18.9 (CKD, unspecified) upgraded to N18.31 (stage 3a) when GFR or stage is recorded.
Specificity matters for three independent reasons. First, payers scrutinize unspecified codes (especially in inpatient DRG groupers, where they may not group to a CC or MCC). Second, risk adjustment models often reward specific codes over unspecified ones (e.g., diabetes with complications maps to a higher-weighted HCC than diabetes without complications). Third, downstream analytics (population health, quality measures) work better with specific codes.
AutoICD's specificity capability inspects each submitted code, finds candidate upgrade targets in the same hierarchy, and verifies via an LLM that the chart documentation supports the more specific code.
When to use
- •You're seeing a high rate of unspecified codes (X9 endings, *.9 codes) in submitted claims.
- •You're preparing inpatient claims and want to verify whether specificity changes the DRG.
- •You're optimizing risk capture without adding net-new diagnoses.
Try it in AutoICD API
Find unspecified codes that can be upgraded
curl -X POST https://autoicdapi.com/v1/audit \
-H "Authorization: Bearer $AUTOICD_API_KEY" \
-H "Content-Type: application/json" \
-d '{
"text": "70M chronic systolic heart failure, EF 28%. CKD stage 3b, GFR 35.",
"submitted_codes": ["I50.9", "N18.9"],
"capabilities": ["specificity"]
}'Language: bash. View full API docs · Get an API key.