Cardiology Coding Alert

Evade E/M Mishaps by Homing In on History Levels

Warning: Not all payers accept 'all other systems reviewed and negative'

If you're squeaking by without learning E/M history levels' laundry list of requirements, help is here. Break down your documentation one step at a time, and then use our handy history chart to choose the right level for your patient.

You have four levels to choose from:

• problem-focused

• expanded problem-focused

• detailed

• comprehensive.

When determining the appropriate history level for your E/M codes, consider the following elements.

CC: Clarify Your Medical Necessity

Every E/M history level requires a chief complaint (CC). According to CPT, this is a concise statement, usually in the patient's words, explaining the main reason for the appointment. Look for a symptom, problem, condition, diagnosis, or physician-recommended return.

Documentation should note specific problems to support medical necessity for the visit. Even if your office asked the patient to return, look for the complaint that prompted the visit or the condition that brought the patient for a follow-up.

Example: A patient presents for a coronary artery disease follow-up assessment, and the provider documents coronary artery disease (CAD) as her chief complaint.

Bottom line: Look for a complete CC. Payers sometimes won't find "Here for follow-up" an acceptable chief complaint. Best advice: Your physician should specify the condition or complaint the patient is following up.

HPI: Look for These Factors in Patient Timeline

The second E/M history element, history of present illness (HPI), should be an actual chronological description of the patient's current illness, says Bill Dacey, MHA, MBA, CPC, in his presentation "E/M Auditing: Regulations vs. Reality" at the 2007 national American Academy of Professional Coders conference in Seattle.

Check your documentation for location (e.g., chest), quality (e.g., dull pain), severity (e.g., her pain is 7 on a scale of 1-10), duration (e.g., CAD diagnosed in 1999), timing (e.g., mid-day her symptoms peak), context (e.g., while walking quickly), modifying factors (e.g., alleviated with nitroglycerine), and associated signs and symptoms (e.g., dizziness).

If you have documentation of one to three of these categories, consider this a brief HPI. Four or more equals an extended HPI.

ROS: Count Systems to Determine Proper Level

For the third E/M history element, review of systems (ROS), the provider either analyzes a questionnaire filled out by the patient or support staff or directly asks the patient questions (or both). Keep in mind, however, that this section does not involve examining or touching the patient.

Red flag: Payers and auditors who smell cloned documentation may hit your practice with fines and refund requests. Patient-completed ROS templates may be OK, but ask providers to make their documentation specific to each patient.

The main purpose of the ROS is to be sure no important symptoms have been missed, especially in areas not already covered in the HPI, says Rebecca Parker, MD, FACEP, president of Team Parker LLC, a coding, billing and compliance consulting firm in Lakewood, Ill.

CPT E/M guidelines list 14 different systems:

• constitutional symptoms (e.g., weight loss)

• eyes (e.g., blurred vision)

• ears, nose, mouth, throat (e.g., trouble swallowing)

• cardiovascular (e.g., chest pain)

• respiratory (e.g., shortness of breath)

• gastrointestinal (e.g., nausea)

• genitourinary (e.g., urine incontinence)

• musculoskeletal (e.g., joint pain)

• integumentary (e.g., skin and/or breast; example: discolored skin)

• neurological (e.g., numbness)

• psychiatric (e.g., depression)

• endocrine (e.g., taking synthetic hormones)

• hematologic/lymphatic (e.g., anemia)

• allergic/immunologic (e.g., asthma/immunodeficiency).

Note: "In cardiology, a physician should touch on constitutional, respiratory, integumentary, hematologic/lymphatic, allergy/immunology, because these are all very important in diagnosing a patient with a cardiac problem," says Sarah Tupper, CMC, coder for Central New York Cardiology in Utica.

What to do: If documentation covers only the system directly related to the present illness, this is a problem-pertinent ROS.

Inquiring about the most directly related system as well as a limited number of others (for a total of two to nine) is an extended ROS.

A complete ROS requires documenting your review of 10 to 14 of the body systems. If the provider asks about all the systems and only one is showing problems, documenting the problem, the pertinent negatives, and stating, "All other systems reviewed and negative" satisfies the complete ROS requirements -- unless your payer instructs you otherwise. For example, TrailBlazer (a Medicare carrier) does not except this AMA/CMS guideline.

PFSH: Decide Scope With These Tips

The final element for you to consider is past, family and social history (PFSH).

Past history refers to the patient's own medical history, such as previous surgeries. Family history includes medical events in the patient's family line, such as hereditary diseases that put the patient at risk. Social history reviews the individual's past and current activities (for example, occupational history or tobacco use).

If the provider asks only about one history element related to the main problem, this is a pertinent PFSH.

Depending on the type of E/M service you're billing, a complete PFSH may require your physician to document reviewing two or three of the history areas. In particular, higher levels of new patient office visits and consultations require all three areas (past, family and social) for a complete PFSH. If you're reporting for a higher-level E/M, definitely make sure you've covered all three history areas.

Tabulate Your History Level

Decide which history level to choose based on how you fulfilled the requirements in the chart on page 5.

Example: You have a CC, brief HPI, and problem-pertinent ROS. Consider this an expanded problem-focused history level.

Other Articles in this issue of

Cardiology Coding Alert

View All