A History Of Present Illness

The section everyone rushes through is the one that saves your ass later

Most people treat the A History Of Present Illness like a checkbox. They type it fast, copy-paste from yesterday's note, and move on to billing. That approach works until a reviewer asks you to justify a high-complexity E/M code or a colleague needs to understand what actually happened to the patient over the last six months. The HPI is a chronological narrative of the patient's current problem. It is not a symptom list. It is not a template. It is a story with dates, timelines, and clinical reasoning attached to each event. The difference matters more than you think.

A History Of Present Illness: how to actually write one that holds up

I used to write HPIs that were paragraphs of symptoms grouped by system. That was before I had a prior authorization denied for a spine MRI because the HPI didn't clearly establish the failure of first-line conservative treatment. The reviewer literally said "insufficient HPI to justify imaging." My note had listed back pain, radiating leg pain, numbness, and weaknees. It did not have a timeline showing three months of physical therapy, two trials of NSAIDs, one course of muscle relaxants, and the point at which symptoms progressed despite compliance. That single addition fixed the denial, but it took me forty-five minutes to reconstruct from clinic records. So here is the structure I use now, and the one I recommend: Start with the chief complaint in the patient's own words, with a date of onset. Then move forward chronologically. For each intervention or change in status, include the date, what was done, and the result. If the patient is being evaluated for a chronic issue that is currently stable, state that explicitly with the duration of stability and the most recent relevant negative findings. Never skip the negatives that matter for the differential.

The trick nobody teaches you is that the HPI should answer the question a peer would ask after reading it: what are you still worried about? If you don't have that answer in your note, you haven't written a sufficient HPI. You've written a laundry list. I track four elements in every HPI: onset, location, character, and temporal pattern. Those are the old mnemonics, yes, but they are useful because they force specificity. " abdominal pain since Tuesday" is not enough. "Cramp epigastric pain starting 3 days ago, worsening 12 hours ago, worse with eating, partially relieved by antacids" tells someone exactly where the patient sits on the diagnostic spectrum. That second version cuts the time my team spends deciding on the next workup step because the differential is already half-written. There is a common pitfall with HPIs that catches people who use EMR macros heavily. Macros make it easy to generate a note that looks complete but actually contains placeholder data. I once pulled a note where the HPI read "pain radiating to bilateral upper extremities" for a patient who was clearly describing lower back symptoms. The macro had been reused from a cardiology admission. The rest of the note was correct. Only the HPI was wrong. It happened because nobody reads the HPI carefully when they are generating it. They trust the template.

Another pitfall is the tendency to write HPIs backward. Clinicians often start with the current status and then append earlier events like an afterthought. That makes the timeline hard to follow and creates gaps that reviewers exploit. Write it forward. Onset first. Current status last. Keep the progression visible. For chronic conditions being re-evaluated, include the baseline status and any deviations from it. If a diabetic patient presents for a routine visit and their HPI simply states "diabetes, follows up regularly," you have not documented anything useful. Note the last HbA1c, the trend over the past year, any medication changes, and any symptoms that deviate from their usual pattern. The absence of change is itself data, but you have to state what the usual pattern is before you can prove nothing changed. One counter-intuitive thing about HPIs: the longer they are, the less useful they often become. A dense paragraph of twenty sentences where everything is equally weighted forces the reader to extract the signal themselves. Four or five tight sentences with clear chronology and specific modifiers carry more weight. I keep mine to roughly one paragraph per problem. If a patient has three active issues, that is three paragraphs. Anything longer and I am padding.

When documenting a symptom, always include the associated signs and symptoms, the modifying factors, and the severity in the patient's functional terms. "Severe" is meaningless to a reviewer. "Could not walk more than two blocks without stopping" is not. Functional limitation is what drives decision-making in most chronic pain and musculoskeletal cases, so documenting it explicitly inside the HPI rather than burying it in the review of systems makes the clinical argument stronger. There are scenarios where the HPI approach breaks down. In emergency presentations where the timeline is unclear because the patient is confused, intoxicated, or has amnesia, you cannot construct a reliable chronology. In those cases, state the limitation plainly: "timeline unreliable secondary to altered mental status on presentation." Then document what you do have from collateral sources. Faking a timeline in that situation is worse than admitting the gap, and auditors notice the difference. If you are doing this for a specific EMR system or need a template file, most major platforms have built-in HPI builders that enforce the timeline structure. Epic's smart phrases and Cerner's problem-oriented templates both have options that prevent the copy-paste drift I described. I don't have a direct download link to share since these are platform-specific and tied to institutional licenses, but searching your EMR's documentation library for "HPI template chronological" will surface the official versions. Third-party templates exist online, but I caution against using them without verifying they match your current coding requirements, since those change annually.

The A History Of Present Illness is the single most impactful section of a clinical note for external reviewers, peer consultations, and your own follow-up planning. Treat it like the narrative backbone of the encounter rather than the first box you check. Write it in order. Include the negatives that matter. Keep it tight. And for god's sake, read it back before you sign.