Clinical Documentation Review & Medical Coding Services

Documentation: The Foundation of Reimbursement

Every claim you submit must be supported by clinical documentation that justifies the diagnosis, medical necessity, services rendered, and the provider's decision-making. Payers are increasingly sophisticated at identifying documentation deficiencies — and they use them to deny, downcode, or recoup previously paid claims during audits.

BlueBird Medserv's documentation review team includes certified clinical documentation improvement (CDI) specialists and certified professional coders (CPC) who audit your records against current payer guidelines, CMS documentation requirements, and specialty-specific clinical criteria.

Our Documentation Review Process

• Pre-bill documentation audit against payer-specific coverage policies
• E/M level of service optimization for office and hospital visits
• HCC risk adjustment documentation review for value-based care contracts
• Procedure documentation completeness checks for surgical and procedural services
• Medical necessity language review and strengthening recommendations
• RAC and payer audit preparation and defense support
• Provider education and feedback on recurring documentation gaps
• Query process management to resolve documentation ambiguities with physicians

Key Benefits

The Revenue Hidden in Your Clinical Notes

Most physicians and practice administrators are surprised to learn how much revenue is hiding in their existing clinical documentation — not as fraud or overbilling, but as legitimate services rendered that are either undercoded due to insufficient documentation, missed entirely because a secondary diagnosis was not captured, or denied because medical necessity language did not meet the payer's specific criteria. Conservative industry estimates suggest that documentation-related revenue loss affects 10–20% of billable encounters in the average practice.

Our documentation review process is not about billing more aggressively — it is about billing accurately. When a provider spends 30 minutes with a complex patient managing multiple chronic conditions, the documentation should reflect that complexity, and the claim should be coded at the appropriate E/M level. When a procedure requires a modifier to distinguish it from a bundled service, that modifier needs to appear in the documentation before it appears on the claim. BlueBird Medserv's CDI specialists are trained to identify these gaps and resolve them before they cost your practice revenue.

Protecting Against RAC and Payer Audits

Recovery Audit Contractors (RACs), Medicare Administrative Contractors (MACs), and commercial payer Special Investigations Units are increasingly sophisticated at identifying documentation deficiencies in submitted claims — and they use these deficiencies to recoup previously paid revenue, sometimes years after the service was rendered. Practices without a consistent documentation review program are significantly more vulnerable to these retrospective audits and the substantial financial and reputational damage they can cause.

BlueBird Medserv builds audit-readiness into the documentation review process from day one. Every review we conduct is designed to ensure that your clinical records would withstand scrutiny from any payer or government contractor — not just today's claim, but in any future audit. This proactive approach dramatically reduces your exposure and gives you confidence that your billing practices are built on a foundation of thorough, compliant documentation.

Specialties with the Highest Documentation Risk

Certain specialties face heightened scrutiny from payers due to their complexity, claim volume, or historical patterns of documentation deficiency. Our CDI specialists have deep experience in the highest-risk specialty categories:

Office E/M Leveling Since 2021: Medical Decision Making or Time

Since January 1, 2021, office and other outpatient E/M visits (new patient 99202 to 99205, established patient 99211 to 99215) are leveled on either medical decision making (MDM) or total time on the date of the encounter. History and physical examination are still required to be medically appropriate, but they no longer determine the level. The same MDM framework was extended to hospital inpatient and observation, consultations, emergency department, nursing facility, and home or residence services in later CPT revisions. Level 99211 is the exception, because it is reported without a requirement for MDM or time.

Option 1: Level by medical decision making

MDM has three elements, and the level is the one met or exceeded by at least two of the three.

The table is a summary of the AMA CPT framework. The full definitions of terms such as "stable," "independent historian," "unique test," and "addressed" control the final result, and coders apply them to the note itself. Two points commonly cause a downcode on audit: a problem that is listed in the note but not evaluated or managed that day does not count as "addressed," and a test that is ordered and later reviewed counts as one item, not two.

Option 2: Level by total time

Total time is the time personally spent by the physician or other qualified health care professional on the date of the encounter, including face-to-face and non-face-to-face work such as reviewing records, ordering, documenting, counseling, and care coordination. It excludes time spent by clinical staff, travel, teaching that is not tied to the patient's care, and time for separately reported services. Current CPT thresholds are stated as minimums to be met or exceeded.

When time is used, the note states the total time and describes the activities included, for example "total time on the date of the encounter was 42 minutes, including record review, history, counseling, order entry, and documentation." A generic statement of time without any description of the activities is weaker on audit. Prolonged services use CPT 99417 under AMA rules and HCPCS G2212 under Medicare rules, and the time thresholds differ, so the payer's rule is checked first. Do not count the same minutes toward both a visit level and a separately reported service.

Medical Necessity: Linking the Diagnosis to the Service

For most payers, a service is paid only if it is covered, reasonable, and necessary for the patient's condition. Medical necessity is shown by the link between the clinical picture in the note, the diagnosis code, and the service billed. It is tested by coverage policy and checked by the claim edit, then by the auditor.

• Start with the reason for the encounter. The first-listed diagnosis is the condition chiefly responsible for the service. Signs and symptoms are coded when no definitive diagnosis has been made, and not "probable" or "rule out" conditions in the outpatient setting.
• Document the clinical rationale. The note says why the test, procedure, or referral was ordered, referring to findings, failed conservative treatment, or risk. A bare "knee pain" with a request for an MRI does not give a reviewer enough to approve the study.
• Match to LCD and NCD policy. Medicare coverage policies state which indications and diagnosis codes support a service, how often it is covered, and what documentation is expected. Commercial policies work in a similar way, but vary by payer.
• Document that the service was performed and by whom. The date, provider credentials, signature, and any supervision or incident-to elements are part of the record. A signature log or attestation statement addresses a missing or illegible signature where the payer allows it.
• Document the plan. The assessment and plan should show how each diagnosis was addressed, including monitoring, evaluation, assessment, or treatment (often shortened to MEAT). This is also the standard used for risk adjustment diagnoses.

A denial for medical necessity is commonly reported with CARC 50, and an additional documentation request may appear as CARC 252 with a RARC giving the requirement. The response is based on the record, and a late addendum written solely to support a denied claim is not a safe substitute for contemporaneous documentation.

ICD-10-CM Specificity: Where Documentation Drives the Code

The ICD-10-CM code can be only as specific as the note. Unspecified codes are valid but are more likely to fail medical necessity edits and risk adjustment, and are less able to describe severity. Coders cannot add detail that the provider did not document, so specificity is a documentation task first.

For risk adjustment, chronic conditions are reported at least once during the calendar year from a face-to-face or qualifying telehealth encounter with an acceptable provider type, and each reported condition is supported in the note. The CMS-HCC model version and the payer program dictate which diagnoses map to risk categories, so the reviewer works from the current model and not from memory.

The Provider Query Process

When a note is unclear, conflicting, incomplete, or does not support a diagnosis that appears to be present, the coder or CDI specialist sends a query to the provider. A compliant query follows the principles in the ACDIS and AHIMA guidance on compliant query practice.

1. Identify the triggerExamples are a diagnosis with no clinical support, a documented treatment with no associated diagnosis, conflicting statements within a note, an unclear relationship between conditions, or a procedure note missing a required element such as laterality, approach, or time.
2. Present clinical indicatorsThe query cites the specific findings in the record, such as lab values, medications, vital signs, imaging, and the provider's own statements, without emphasizing a preferred answer.
3. Ask a non-leading questionOptions include all clinically reasonable answers, plus "other" and "unable to determine." A query never states or implies the effect of the answer on payment or quality scores, and never asks the provider to document something unsupported by the clinical picture.
4. Record the response in the legal recordThe provider answers by addendum or note in the EHR, signed and dated at the time of the response, and any change is a labeled late entry. Original documentation is never erased or replaced.
5. Hold the claim, then release or correctThe charge stays on hold until the query is answered or the practice policy sets a limit. If the provider does not respond, the code is based only on what is documented.
6. Track and trendQuery volume, response time, agreement rate, and topics are reviewed with the provider group, and recurring topics become education items.

Common documentation shortcuts that raise audit risk include cloned or copied-forward notes that do not reflect the actual visit, templated text that populates elements which were not performed, unsigned notes, and conclusions without supporting findings. Electronic signatures are acceptable if they are secure and attributable, while stamped or typed names alone generally are not.

Audit Sampling and Review Methodology

Documentation review is most useful when it is planned. There are two basic types: prospective review of encounters before a claim is released, and retrospective review of paid claims. The first prevents errors, and the second measures them and finds trends.

• Sample selection. Random samples are drawn by provider so that results are comparable. Sample size varies by practice size and risk, and a common approach is a fixed number of encounters per provider per review period, with a larger sample for providers with higher error rates, new providers, and high-risk codes.
• Targeted reviews. Focused samples are drawn for codes that payers watch closely, including high-level E/M visits (99215, 99205), modifier 25 claims, prolonged services, critical care, high-cost drugs, and any code that is an outlier compared with the specialty's national utilization.
• Scoring. Each encounter is scored for code accuracy, diagnosis accuracy, modifier accuracy, and documentation elements. Findings are recorded as accurate, undercoded, overcoded, or not supported. Many compliance programs set an accuracy goal in the 90 to 95 percent range, and providers below the goal are re-reviewed.
• Overpayments. When review finds that payment was received in error, the practice follows its compliance policy and the applicable rule. For Medicare, overpayments generally must be reported and returned within 60 days after they are identified, under current CMS rules, so findings are escalated to the compliance officer promptly.
• Extrapolation. Government contractors can estimate overpayments across a universe of claims from a statistically valid sample, which is why consistent errors on one code can turn into a large demand.
• Feedback and education. Results go to each provider with examples from their own notes. Education is repeated and followed by a re-audit, so improvement is measured rather than assumed.