CRC Medical Record Documentation & Abstraction 1 — Questions and Answers

Question 1: Why is accurate medical record documentation essential in risk adjustment coding?

To speed up coding reviews
To fill out claim forms
To support diagnoses and coding validity (Correct answer)
To avoid follow-up care

Correct answer: To support diagnoses and coding validity

Accurate and thorough medical record documentation is the cornerstone of valid risk adjustment coding. It provides the essential clinical evidence needed to justify the reported diagnoses and procedures. Without clear, comprehensive documentation, the validity of coded information cannot be supported, which can lead to compliance issues and inaccurate risk scores.

Question 2: Which part of the record is most often used for abstracting diagnoses?

Patient demographics
Lab requisition forms
Assessment and plan notes (Correct answer)
Billing summary

Correct answer: Assessment and plan notes

The assessment and plan sections of a provider's note are typically the most reliable sources for abstracting diagnoses, especially for risk adjustment. These sections contain the provider's professional judgment regarding the patient's current health conditions and the proposed management strategy. This clearly indicates which diagnoses are active and being addressed during that specific encounter.

Question 3: What is the MEAT criteria used for?

To calculate a patient’s BMI
To define disease stages
To justify diagnosis coding (Correct answer)
To identify billing errors

Correct answer: To justify diagnosis coding

The MEAT criteria (Monitored, Evaluated, Assessed, Treated) are essential guidelines used to justify the reporting of a diagnosis, particularly for risk adjustment. These criteria ensure that the medical record documentation demonstrates that a chronic condition was actively managed by the provider during the encounter. This validation confirms the ongoing impact of the condition on the patient's health and the resources required for their care.

Question 4: When abstracting data, which type of documentation should be avoided?

Physician progress notes
Problem list without documentation (Correct answer)
Hospital discharge summaries
Specialist consultation notes

Correct answer: Problem list without documentation

While a problem list provides a summary of a patient's conditions, coding directly from it without supporting documentation in the current encounter is generally avoided. For a diagnosis to be coded and submitted, especially for risk adjustment, the medical record must clearly show that the condition was addressed, assessed, or managed during that specific visit. A problem list alone does not provide this necessary validation.

Question 5: How should a coder handle an unsigned provider note?

Code it as usual
Sign it for the provider
Wait for the provider's signature (Correct answer)
Use it for internal training only

Correct answer: Wait for the provider's signature

An unsigned provider note is considered incomplete and lacks legal validity for coding and billing purposes. All medical documentation must be authenticated by the provider's signature to confirm its accuracy and authorship. Therefore, a coder must wait for the provider to sign the note before it can be used to abstract diagnoses and submit claims.

Question 6: What is abstraction in the context of medical coding?

Drawing lab samples
Summarizing patient preferences
Extracting relevant data from records (Correct answer)
Filing insurance claims

Correct answer: Extracting relevant data from records

Abstraction in medical coding is the crucial process of carefully reviewing a patient's medical record to identify and extract all pertinent clinical information. This includes diagnoses, procedures, and services rendered, which are then translated into standardized codes. This meticulous extraction ensures that all relevant data is captured accurately for billing, data analysis, and risk adjustment.

CRC Medical Record Documentation & Abstraction 1

Why is accurate medical record documentation essential in risk adjustment coding?