AI Documentation for Surgical Pre-Op Clearance: The 2026 Playbook for Reducing Same-Day Cancellations

AI documentation reduces same-day surgical cancellations by capturing anticoagulant hold dates, glycemic values, blood pressure, GLP-1 and SGLT2 instructions, and cardiac risk scores as structured fields. A complete record must reach the surgical team at least 72 hours before incision, coded with Z01.810 or Z01.818 and attested by the clearing physician.

Same-day cancellations usually begin with incomplete preoperative documentation

CLINICAL UPDATE 2026: Revised for 2026 CMS CPT G2211 attestation rules, California SB 1120 compliance, and NCCI Modifier 25 bundling criteria.

Most avoidable day-of-surgery cancellations come from information failures rather than new clinical events. A patient arrives having taken apixaban that morning. A hemoglobin A1c was drawn but never reached the anesthesia record. A weekly semaglutide injection was continued with no documented aspiration risk assessment. The anesthesiologist cannot proceed, and the operating room block goes unused.

The clearance note is where these failures either get caught or get passed along. A narrative that ends with "patient is cleared for surgery" gives anesthesia nothing it can act on. Current guidance, including the 2024 ACC/AHA perioperative cardiovascular guideline, frames the primary care evaluation as risk stratification and optimization. It is not meant to grant permission.

For a clinic medical director, the operational question is narrow. Does every preoperative note your clinicians sign contain the discrete data elements anesthesia needs, in a format the surgical scheduler can verify before the patient arrives? Ambient AI documentation answers that question at the point of care, while the patient is still in the room.

Six cancellation drivers each require a discrete documented data element

Cancellation audits tend to show the same small set of causes. Each one maps to a specific value, date, or instruction that should be documented in the clearance note. If any element is missing, the clinic is relying on the patient's memory on the morning of surgery.

Anticoagulant and antiplatelet hold dates

Direct oral anticoagulant interruption depends on two variables: procedural bleeding risk and renal function. The PAUSE trial protocol supports holding apixaban or rivaroxaban for one day before low bleed risk procedures and two days before high bleed risk procedures. Dabigatran needs longer interruption when creatinine clearance falls below 50 mL/min. The note should state the drug, dose, last dose date, resumption date, and the creatinine clearance used to decide.

Warfarin requires a five-day hold and a documented plan for checking INR before surgery. For most patients with atrial fibrillation, the BRIDGE trial supports withholding heparin bridging. If bridging is chosen, the indication must be recorded. For antiplatelet therapy in patients with coronary stents, document the stent type, implant date, and coordination with cardiology. Never let the AI infer a hold date from a medication list alone.

Glycemic control values

Hemoglobin A1c thresholds for elective surgery vary by institution. Many surgical programs postpone elective joint replacement or spine fusion above a set cutoff, commonly in the range of 7.5 to 8.0 percent. The clearance note should carry the most recent A1c value with its collection date, the surgical program's threshold, and the day-of-surgery insulin dosing instruction. That instruction typically reduces basal insulin and holds prandial insulin.

Blood pressure and the postponement threshold

Severe uncontrolled hypertension remains a common reason for day-of-surgery postponement. Many anesthesia departments use a threshold near 180/110 mmHg. Document at least two in-office readings, the patient's home blood pressure trend, any medication changes made at the visit, and which agents to hold. ACE inhibitors and ARBs are often held the morning of surgery to reduce intraoperative hypotension, but the decision should follow the anesthesia protocol.

GLP-1 receptor agonists and SGLT2 inhibitors

GLP-1 receptor agonist guidance changed between 2023 and 2024. The original ASA consensus recommended holding weekly agents for one week. The 2024 multisociety guidance shifted toward continuing therapy in most patients, with individualized assessment for gastrointestinal symptoms and dose escalation phase, and consideration of a liquid diet for 24 hours before the procedure in higher risk patients. Your note must state which approach applies and why.

SGLT2 inhibitors carry a labeled hold of three days before scheduled surgery for canagliflozin, dapagliflozin, and empagliflozin, and four days for ertugliflozin. Missing this hold creates euglycemic ketoacidosis risk and is a frequent and avoidable cause of cancellation. The AI should flag any SGLT2 inhibitor on the reconciled medication list and require an explicit hold date before the note can be finalized.

Cardiac risk stratification and functional capacity

The Revised Cardiac Risk Index and functional capacity in metabolic equivalents determine whether further testing is warranted. A patient who can reach 4 METs or more (for example, climbing two flights of stairs without symptoms) generally needs no stress testing before elevated risk surgery. Document the RCRI score, each contributing factor, the METs estimate with the activity the patient described, and the rationale for ordering or skipping an ECG, echocardiogram, or BNP.

Airway and obstructive sleep apnea screening

Undiagnosed obstructive sleep apnea changes anesthetic planning, postoperative monitoring, and sometimes the surgical setting itself. A STOP-Bang score of 5 or higher should appear in the clearance note along with CPAP status and adherence. For ambulatory surgery centers, this single data point can decide whether the case stays on schedule or moves to a hospital-based facility.

Structured risk statements replace the ambiguous word "cleared"

The word "cleared" creates liability without creating clarity. It suggests the primary care clinician has guaranteed a safe surgical outcome, which no internist can do. It also gives anesthesia no information to act on. The 2024 ACC/AHA guideline language favors describing perioperative risk and stating whether the patient is optimized, which is more defensible.

A compliant risk statement reads like this: "Patient has elevated perioperative cardiovascular risk (RCRI 2: insulin-treated diabetes, creatinine 2.1). Functional capacity exceeds 4 METs. No further cardiac testing indicated. Medically optimized for planned procedure with hold instructions below." That sentence is quotable, auditable, and actionable by anesthesia.

Scribing.io enforces this structure through specialty templates. When clinicians use the Specialty Clinical Documentation Library, preoperative encounters generate a risk statement block in place of a free-text conclusion. Clinicians can edit the language, but the template keeps the required components in the note: risk tier, contributing factors, functional capacity, testing rationale, and optimization status.

Each clinical parameter carries a specific audit vulnerability

The table below maps each cancellation driver to its documentation standard, the risk that appears during payer audit or peer review, and the Scribing.io mechanism that addresses it. Medical directors can use it as a chart audit checklist.

Correct ICD-10 sequencing places Z01.810 or Z01.818 first

Preoperative evaluations should be coded with a Z01.81x encounter code in the first position, followed by the condition that requires surgery, then the comorbidities that drove the evaluation. Use Z01.810 (ICD-10-CM) when the encounter is primarily a preprocedural cardiovascular examination. Use Z01.818 (ICD-10-CM) for general preprocedural examinations that do not fit the cardiovascular, respiratory, or laboratory subcategories.

Secondary diagnosis sequencing supports medical necessity. A Medicare beneficiary undergoing total knee arthroplasty with type 2 diabetes on insulin, chronic kidney disease stage 3b, and atrial fibrillation on apixaban needs all three conditions coded, with the knee osteoarthritis diagnosis included. Without the comorbidities, the visit looks like a routine screening exam, which Medicare does not cover.

Scribing.io validates condition linkage before claim submission. If the note discusses apixaban interruption but the diagnosis list omits atrial fibrillation or the relevant thromboembolic history, the system flags the gap. The clinician then either adds the diagnosis or removes the unsupported discussion, so the documentation and the claim stay consistent.

G2211 applies only when the clearing clinician owns longitudinal care

The G2211 visit complexity add-on recognizes the work of being the continuing focal point for a patient's care, or of providing ongoing care for a single serious or complex condition. A primary care physician who manages the patient's diabetes, hypertension, and anticoagulation and then performs the preoperative evaluation can generally report G2211 with the office E/M code, as long as the longitudinal relationship is documented.

A dedicated preoperative clinic usually cannot report G2211. If a hospitalist-run perioperative clinic sees the patient once, completes the clearance, and returns care to the PCP, no longitudinal relationship exists. Billing G2211 in that setting is a predictable audit finding. Medical directors overseeing both models should set separate billing rules for each.

Attestation language should be explicit. A defensible statement reads: "I serve as this patient's continuing focal point for all needed health care services, including longitudinal management of diabetes and anticoagulation." Scribing.io inserts this attestation only when the encounter history shows an established longitudinal relationship. It suppresses the add-on suggestion when the encounter is a one-time preoperative consultation.

Modifier 25 interacts with G2211 under a narrow rule. CMS permits payment of G2211 when the associated E/M carries modifier 25 only if the same-day service is an annual wellness visit, vaccine administration, or a Medicare Part B preventive service. If the preoperative evaluation happens on the same day as a minor procedure, such as a skin biopsy or joint injection, G2211 is not payable on that E/M.

Modifier 25 and global surgery rules determine who gets paid

Medicare does not recognize consultation codes 99242 through 99245. Preoperative evaluations requested by a surgeon are reported with office E/M codes 99202 through 99215, with level selection based on medical decision making or total time. A complex preoperative evaluation involving anticoagulation management, multiple chronic conditions, and independent review of an ECG often supports moderate complexity MDM.

When a significant, separately identifiable E/M occurs on the same day as a minor procedure, modifier 25 is required. NCCI bundling edits assume the E/M is part of the procedure unless the documentation shows otherwise. The preoperative evaluation must stand on its own: separate history elements, separate assessment, and a plan that goes beyond the decision to perform the minor procedure. Review Managing Modifier 25 Clinical Revenue Integrity for the full documentation separation framework.

Surgeons face a different constraint. For major procedures with a 90-day global period, the surgeon's E/M on the day before or the day of surgery falls inside the global package. If that visit is where the decision for surgery is made, modifier 57 applies. Primary care preoperative evaluations are outside the surgeon's global package and are billed separately by the evaluating clinician.

California SB 1120 keeps physicians accountable for AI-supported determinations

California SB 1120, effective January 2025, requires health plans and disability insurers that use artificial intelligence in utilization review to base determinations on the individual patient's clinical history and circumstances. A licensed physician or qualified health professional must make medical necessity decisions. AI tools cannot deny, delay, or modify care on their own authority.

This law affects preoperative documentation in two ways. First, prior authorization for elective surgery depends on clinical evidence that a payer's reviewing physician can evaluate individually. Structured clearance notes with explicit risk factors give that reviewer something concrete. Second, when payers use AI-assisted review, a well-structured record lowers the chance of a pattern-based denial that the treating physician then has to appeal.

The same principle governs clinical AI documentation. Scribing.io drafts the note, calculates scores, and flags missing elements. The signing physician confirms every risk determination, hold instruction, and optimization statement. The audit trail records which elements the AI generated and which the clinician confirmed or changed, which is the accountability structure SB 1120 expects across the care continuum.

A four-stage workflow closes the gap between clinic and OR

Effective preoperative programs treat clearance as a timed handoff with defined checkpoints. The workflow below assumes the surgical date is known when the evaluation is scheduled. It is designed for clinics that receive clearance requests from multiple surgical groups.

Stage one: Intake at least 14 days out

The scheduling team captures procedure type, surgical date, facility type (hospital or ambulatory surgery center), anesthesia type, and the surgeon's specific requests. Scribing.io uses these fields to preload the right specialty template. A hip arthroplasty at an ASC triggers OSA screening and glycemic threshold fields automatically.

Stage two: The evaluation visit

During the encounter, ambient capture records history, medication review, functional capacity discussion, and examination findings. The clinician speaks naturally. The AI organizes the content into structured fields, calculates RCRI and STOP-Bang, and pulls recent labs with their collection dates. Clinicians can add procedure-specific elements using the 1,000+ Specialty Clinical Macros library, which includes bariatric, orthopedic, ophthalmic, and endoscopic preoperative variants.

Stage three: Pre-signature validation

Before the note can be signed, the system runs a completeness check against the cancellation driver list. Any missing anticoagulant hold date, SGLT2 stop date, stale A1c, or absent risk statement creates a hard stop. The clinician resolves each flag or documents a clinical reason for the exception. This step is where cancellations are actually prevented.

Stage four: Transmission at least 72 hours out

The signed note and a patient-facing medication instruction sheet go to the surgical team and the patient. The instruction sheet lists each medication with its last dose date in plain language. Front desk staff confirm receipt with the surgical scheduler. Any request for additional testing then has enough lead time for completion before the surgical date.

Operational rule: No signed clearance means no confirmed OR slot.

Medical directors should track five cancellation metrics monthly

Measurement turns documentation standards into accountable operations. These five metrics show whether the clearance program is preventing cancellations or just producing paperwork. Each can be pulled from the Scribing.io reporting dashboard or your EHR with modest configuration.

• Same-day cancellation rate by cause: Categorize each cancellation by driver (anticoagulant, glycemic, blood pressure, GLP-1, SGLT2, cardiac, airway, administrative). Report the percentage attributable to documentation gaps.

• Clearance transmission lead time: Measure hours between note signature and scheduled incision. The target is 72 hours or more for at least 95 percent of cases.

• Hard-stop override frequency: Track how often clinicians override completeness flags. High rates point to template problems or training needs.

• G2211 appropriateness rate: Audit a sample of G2211 claims for documented longitudinal relationship. Any G2211 billed by a one-time preoperative clinic is a compliance finding.

• Z01.81x denial rate: Monitor payer denials on preoperative evaluations. Denials usually reflect missing secondary diagnosis linkage.

Share cause-specific cancellation data with surgical partners each quarter. When a surgical group sees that SGLT2 hold failures dropped after template enforcement began, the clinic gains credibility as a reliable clearance partner. That relationship affects referral volume and gives you leverage in conversations about scheduling lead times.

Specialty-specific templates prevent the most common procedure-level failures

Different procedures carry different cancellation profiles. Orthopedic joint replacement programs enforce strict A1c and BMI thresholds. Endoscopy suites focus on GLP-1 gastric retention and bowel preparation. Cataract surgery rarely requires routine preoperative testing at all, and the documentation should say so explicitly so redundant labs are not ordered.

Bariatric surgery evaluations require additional elements, including nutrition and psychological evaluation status, sleep study results, and documented weight trajectory. Cardiac electrophysiology procedures need anticoagulant management notes that align with the electrophysiologist's protocol, since some ablations proceed on uninterrupted anticoagulation. A generic preoperative template cannot handle these differences.

The Scribing.io template architecture separates universal elements (medication reconciliation, risk statement, functional capacity) from procedure-specific modules. Clinicians choose the procedure category at intake, and the matching module loads. Medical directors can lock required fields for each procedure category based on agreements with specific surgical partners.

Clinician adoption depends on reducing documentation time

Preoperative evaluations are documentation-heavy encounters. Medication reconciliation alone can take a substantial share of the visit for a patient on twelve or more medications. When structured requirements add work without saving time elsewhere, clinicians find workarounds, and those workarounds bring the cancellation drivers back.

Ambient capture shifts the burden away from manual entry. The clinician talks through the medication plan with the patient ("Stop your apixaban after Tuesday morning's dose, restart Friday evening if the surgeon agrees"), and the AI converts that conversation into a structured hold instruction with dates. The clinician reviews and signs instead of typing. Explore the full workflow through the Scribing.io Clinical Interface.

Track documentation time per preoperative encounter before and after deployment. If structured completeness rises while time per note holds steady or falls, adoption will last. If time per note rises, look at template configuration before blaming clinician behavior.

The clearance note functions as a handoff contract

Every preoperative evaluation makes an implicit promise to the surgical team: this patient has been assessed, their risks are stated, and their medications are managed. When the note breaks that promise through a missing hold date or a stale lab, the cost shows up in an empty operating room, a frustrated patient, and a surgical partner who starts sending clearances elsewhere.

AI documentation reinforces the contract by making the required elements hard to skip, the codes hard to mis-sequence, and the attestations hard to misapply. The clinical judgment still belongs to the physician. The system makes sure that judgment is fully recorded and delivered in time for anesthesia to act on it.

Medical directors who implement structured preoperative documentation, enforce 72-hour transmission, and track cancellations by cause gain a measurable operational advantage. These three steps turn the clearance note from an administrative formality into a working part of surgical safety and revenue integrity.