Day 1 | Start Before the Start Time
Yesterday, we began this week’s conversation with one question, What story is the anesthesia record telling you? Today, we’re starting at the beginning, but not where you might think. When reviewing an anesthesia record, it’s easy to go directly to anesthesia start time. After all, anesthesia time is an important part of the claim but, the patient’s anesthesia story actually begins before the start time. It begins with understanding the patient, the procedure, and the anesthesia plan.
Think of the pre-anesthesia evaluation as the opening chapter of the anesthesia record. It gives us clinical context for what happens next. Before focusing on the clock or searching for an anesthesia code, take a moment to understand:
- Who is the patient?
- What procedure is planned?
- What anatomy is involved?
- What anesthesia technique is planned?
- What medical conditions may affect anesthesia care?
- What is the documented ASA physical status?
- Are there anticipated risks or special considerations?
- Is additional monitoring or another service anticipated?
None of these questions alone determines the final claim but together, they begin telling us what kind of case we’re reviewing.
Suppose the pre-anesthesia evaluation documents General anesthesia planned. That gives us useful information, but does it prove that general anesthesia was ultimately provided? No. It tells us what was planned. The rest of the anesthesia record tells us what actually happened and those two things are not always the same.
Anyone who works with anesthesia records knows that the scheduled case is not always the case that is ultimately performed. A procedure may be changed, expanded, converted, modified, and/or aborted. The anesthesia plan can change as well. Patient condition may change. The surgical procedure may change. Clinical circumstances may require a different anesthesia technique or additional services. That’s why we don’t stop after reading the opening chapter. We keep reading.
As you move through the record, compare the pre-anesthesia plan with the care that was actually documented and ask: Did the planned procedure occur? Was the planned anesthesia technique used? Did anything change during the case? Did the patient’s condition require additional intervention or monitoring? Does the final documentation make sense when compared with what was anticipated before the case began? When the plan and the final record agree, the story flows naturally. When they don’t, that’s your signal to look closer.
The surgical schedule may say one thing. The pre-anesthesia evaluation may repeat it, but the operative documentation may show that something different actually occurred. That matters. The scheduled procedure is helpful for understanding what was expected. It should not automatically become the basis of the final anesthesia coding decision when the completed documentation tells a different story. Code the care that was actually provided and supported by the record—not simply what was scheduled to happen.
The pre-anesthesia evaluation also provides important information about the patient’s condition. When reviewing the documented ASA physical status, don’t look only at the number. Look at the clinical picture surrounding it. What conditions are documented? What is the patient’s overall status? Does the documentation provide context for the assigned physical status? The coder’s role is not to independently diagnose the patient or create a physical status classification that was not documented, but understanding the patient’s condition helps us understand the anesthesia story.
🚩 Audit Red Flag
Watch for coding decisions based entirely on the scheduled procedure or preoperative plan without confirming what actually occurred. If the schedule + pre-anesthesia evaluation + anesthesia record + operative documentation do not tell the same story, don’t simply choose the version that makes the coding easiest. Investigate the difference. There may be a perfectly reasonable explanation, but we need the complete record to understand it.
💡 Coder’s Corner
Use the pre-anesthesia evaluation for context—not conclusion. It tells you what was expected to happen. The completed anesthesia and operative documentation tell you what actually happened. Both matter, but they serve different purposes in your review.
🔎 What Should You Verify?
As you begin reviewing the record, verify the information that will eventually affect your coding decision using the appropriate documentation and authoritative resources. Depending on the case, this may include:
- The procedure actually performed
- Anatomical site
- ASA physical status documentation
- Anesthesia technique
- Applicable qualifying circumstances
- Provider participation
- Applicable CPT® and ASA guidance
- Medicare or payer-specific requirements
Don’t make the final coding decision from the opening chapter. Use it to understand what you should be looking for as the story unfolds.
🧠 Check Yourself
The pre-anesthesia evaluation states “Plan: General anesthesia.” As you continue reviewing the record, the intraoperative documentation shows that a different anesthesia technique was ultimately provided.
Question:
Should the coder base the claim solely on the anesthesia technique documented in the original preoperative plan?
Answer: No.
The pre-anesthesia evaluation documents what was planned. The coder should review the complete record and base the coding decision on the anesthesia care that was actually provided and supported by the final documentation.
Today’s Takeaway
Before you look at the clock; understand the patient, procedure, and plan, then keep reading, because the pre-anesthesia evaluation gives you the opening chapter. It doesn’t tell you how the story ends.
Coming Tomorrow
Day 2 | Follow the Anesthesia Timeline
Tomorrow, we’ll move into the anesthesia record itself and look at why anesthesia time should be reviewed as more than simply Start time + stop time. We’ll follow the events between those two points and ask does the timeline tell a logical story of anesthesia care?
Chart Talk ~ Anesthesia Coding Conversations ~
Lead. Educate. Comply. Excel.
For educational purposes only. Always verify coding decisions using current CPT®, ASA, CMS, NCCI, payer-specific guidance, and other applicable authoritative resources.
Leave a comment