decisionhealth Newsletters, Coder Pink Sheets - 2002 Issue 1 (January)
Diagnostic test coding tips
Subscribe or sign in to view the full article.
Article Overview
This article explains broad documentation and coding considerations for diagnostic tests, especially in cardiology settings. It discusses how payers evaluate medical necessity, what types of findings and diagnoses may support testing, how clinicians and coders should review procedure notes and carrier guidance, and why advance beneficiary notices and physician clarification processes matter. It also notes a CMS policy change affecting how diagnostic tests may be coded based on results and documentation.
Why This Topic Matters
Diagnostic test claims are often denied when the documentation does not support medical necessity or when the record is incomplete. This article helps readers understand the general documentation themes and workflow issues that affect reimbursement and compliance in cardiology and other procedure-based practices.
Article Sections
-
Key diagnostic test terms
This section highlights broad categories of symptoms, conditions, and risk factors that may appear in diagnostic test reports. It focuses on the kinds of documentation reviewers may look for across common cardiology procedures.
What You Will Learn
- How diagnostic test documentation is reviewed for medical necessity
- What types of report findings and patient conditions are commonly discussed in cardiology coding
- Why carrier guidance and physician clarification processes are important
- How advance beneficiary notices fit into diagnostic testing workflows
- How a CMS policy change affected coding of diagnostic tests
Who Should Read This
- Medical coders
- Cardiology billing staff
- Physician office staff
- Compliance and revenue cycle professionals
Codes Discussed
Code Ranges Discussed
Subscribe or sign in to view the full article.
Quick, Current, Complete - www.findacode.com