Coding Coach: Follow These HPI Tips For Bulletproof E/M Coding

Why This Topic Matters

Accurate HPI documentation can affect the supported level of history in E/M coding and influence whether a visit is defensible under audit. The article also highlights the importance of choosing one documentation guideline set consistently and aligning note content with medical necessity and payor expectations.

Article Sections

1. HPI documentation and chronic conditions

   Introduces how chronic or inactive conditions may be referenced in the history portion of a visit note and why separate documentation locations can matter. Discusses general documentation considerations for assessment and history.

2. Comparing the 1995 and 1997 guidelines

   Reviews the two documentation guideline versions used for E/M services and explains why coders need to understand the differences. Covers the general advantages and limitations associated with each approach.

3. Know your carriers

   Describes the role of payors and audit tools in reviewing documentation and the need to stay current with carrier expectations. Emphasizes that review practices may vary across payors.

4. Example scenario

   Presents a sample established-patient follow-up scenario involving multiple chronic conditions and documentation status. Uses the example to illustrate how guideline selection and visit documentation can affect the supported service level.

5. Alternate scenario and documentation reminder

   Addresses how the visit level may still depend on the other key components when history detail is limited. Ends with a reminder that medical necessity drives the documentation.