E/M Coding Alert - 2001 Issue 12
Reader Question: Coding Unfound Conditions
Subscribe or sign in to view the full article.
Article Overview
This reader Q&A explains how to think about coding an encounter when a reported problem is investigated and no condition is ultimately found. It is aimed at coders and billing staff working with ICD-9-CM diagnosis coding, especially in emergency or evaluation settings where the visit is prompted by suspicion rather than a confirmed diagnosis. The article discusses the broad use of observation/status-style diagnosis categories, when a symptom may also be reported, and why the encounter should not be treated as routine well-child care.
Why This Topic Matters
These situations are common in real-world chart review and can affect diagnosis selection, claim accuracy, and payer expectations. Understanding the general coding approach helps avoid misclassifying an evaluation for a suspected condition.
What You Will Learn
- How encounters for suspected but unconfirmed conditions are discussed in diagnosis coding context.
- Why the encounter type matters when a condition is not ultimately identified.
- When a symptom may be associated with the suspected problem in the coding discussion.
- How the article frames the distinction between routine care and evaluation for suspicion-based visits.
Who Should Read This
- Medical coders
- Billing staff
- Practice managers
- Emergency department coding staff
- Pediatric coding staff
Codes Discussed
Code Ranges Discussed
Subscribe or sign in to view the full article.
Quick, Current, Complete - www.findacode.com