A surgical scheduler faxes your front desk at 7:40 a.m. The sheet says "pre-op clearance needed, surgery 6/9, please advise." No diagnosis, no requesting physician signature, no phone number that reaches a human. Your medical assistant slots the patient for Thursday, your physician sees them, and three weeks later the claim denies. Somewhere in that chain, a decision about the CPT code for pre op clearance got made by default instead of by documentation — and a set of records left your building without anyone logging where they went.

This guide is for the person who owns both problems: the administrator, biller, or privacy officer who has to make the coding defensible and the disclosure trail auditable. It covers the operational mechanics, then the records-handling and vendor consequences that ride along with them.

Is There a CPT Code for Pre Op Clearance?

No. There is no CPT code that means "pre-operative clearance." The CPT code set does not contain a service defined that way, and no payer publishes one.

What practices actually report is an evaluation and management service — an office or other outpatient visit code, or an office consultation code where the payer recognizes and reimburses consultations. Which family applies depends on the relationship between the requesting surgeon and your physician, whether a written request exists, whether a report goes back, and the payer's own policy. The diagnosis coding, not the CPT code, is what identifies the encounter as pre-procedural.

So when someone in your office asks "what's the CPT code for pre op clearance," the correct internal answer is: we select an E/M level based on documented medical decision making or total time, and we sequence the pre-procedural examination diagnosis according to payer policy. That sentence belongs in your billing desk reference.

Consultation Codes vs. Office Visit Codes

Consultation codes exist in CPT, but Medicare stopped separately recognizing them for payment in 2010, and many commercial plans followed. Others still pay them. Your practice needs a payer-by-payer matrix, maintained by your billing lead, that says which plans accept consultation reporting and which require an office visit code instead.

Where consultation reporting is accepted, the documentation burden is specific and non-negotiable: a request from another provider, the reason for the request, and a written report communicated back to the requester. If your physician's note doesn't name the requesting surgeon and state the question being asked, your coder cannot support a consultation. That is a documentation problem, not a coding problem, and it gets solved in the template — not at the claim scrubber.

Level Selection Is a Documentation Output, Not a Front-Desk Input

Since the 2021 and 2023 revisions to the office and outpatient E/M guidelines, level selection for these visits rests on medical decision making or total time on the date of the encounter. Your schedulers should never pre-assign a level. Your coders should never assume that every pre-op encounter lands on the same level because the visits "feel similar."

Build an internal audit sample: pull ten pre-procedural encounters a quarter, have your coder and a second reviewer level them independently, and reconcile. Document the reconciliation. That file is what you hand an auditor who asks how your practice arrives at code selection.

The Diagnosis Sequencing Question

ICD-10-CM contains codes for encounters for pre-procedural examinations. Payer policies differ on whether that code is sequenced first, followed by the condition prompting surgery and the comorbidity driving the evaluation. Some plans deny when the pre-procedural code leads; others deny when it doesn't appear at all.

Keep the sequencing rules in the same payer matrix as the consultation rules. Assign one person to update it, review it twice a year, and date-stamp every change. When a denial pattern appears, you want to know exactly which policy version your claims went out under. CMS publishes its coverage and claims processing instructions through the Internet-Only Manuals, which is where your biller should start rather than a third-party summary.

The Four Documentation Elements That Decide the Claim

Whatever the payer, these four items determine whether a pre-procedural encounter survives review:

  • The request. Who asked, in writing, and when. A fax cover sheet counts if it names the requesting provider and the reason.
  • The clinical question. Not "clearance" — the specific issue. Vague requests produce vague notes, which produce indefensible levels.
  • The evaluation itself. Documented in the physician's own words, supporting the medical decision making or the time attested.
  • The report back. Sent, dated, and filed in the chart with proof of transmission.

Your front desk controls element one. If a request arrives without a named requesting provider or a stated reason, your policy should be to call the surgical office and get it before the visit — not after the denial. Give that task to a specific role, not to "whoever's up front."

The Disclosure Is Treatment — And That Changes What Paperwork You Need

Here is where administrators most often over-engineer or under-engineer the privacy side.

When your physician sends a pre-op report to the requesting surgeon, that is a disclosure for treatment purposes. Under the Privacy Rule, treatment disclosures between covered health care providers do not require patient authorization, and the minimum necessary standard does not apply to disclosures to a provider for treatment. HHS explains the permitted uses framework in its privacy guidance for professionals.

Who Needs a BAA and Who Doesn't

The surgeon's office is not your business associate. You do not need a BAA with a referring or receiving provider to exchange treatment information. Practices that demand one before releasing a clearance letter delay surgeries for no legal reason.

The vendors in the middle are a different story. Every entity that touches the transmission or storage of that report on your behalf is a business associate:

  • Your electronic fax service
  • Your referral management or care-coordination platform
  • Your transcription or scribe service
  • Your document scanning and release-of-information vendor
  • Your secure messaging or portal provider, if separate from your EHR
  • Any offsite storage or shredding company handling paper clearance requests

Pull your vendor list and check each of those against a signed, current agreement. Pre-op workflows are notorious for running through a fax service someone signed up for years ago with a personal credit card and no contract. If you find a gap, close it in writing before the next request cycle — you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX, one-time purchase, which is faster than routing a redline through counsel for a fax vendor you're about to replace anyway.

Where Pre-Op Clearance Records Actually Leak

Misdirected fax remains one of the most common small-practice disclosure incidents, and pre-op traffic is high-volume, deadline-driven, and manually addressed. That combination is exactly how a clearance letter with a full medication list ends up at a hardware store's fax line.

Three controls cut most of that risk:

  1. Verified destination list. Maintain surgical office fax numbers in a controlled directory. Staff select from the list; they do not type numbers from a cover sheet.
  2. Confirmation filing. The transmission confirmation goes in the chart alongside the report. This does double duty — it proves the report-back element for coding and it proves the destination for privacy.
  3. Same-day misdirect protocol. One named person handles wrong-number callbacks, requests destruction confirmation, and logs the event for the annual risk assessment review.

If a misdirected disclosure meets the breach definition, your notification obligations follow the Breach Notification Rule timelines. The public record of reported incidents is searchable on the HHS breach reporting portal, and the volume of small-provider incidents there is a useful reality check for staff who think this only happens to hospitals.

A Pre-Op Workflow You Can Assign Names To

Day 0 — request arrives. Front desk logs it in the referral tracker: requesting provider, surgery date, stated reason. Missing fields trigger a callback the same day. Owner: front desk lead.

Day 0–1 — scheduling. Visit scheduled with enough runway before the surgery date. The tracker flags anything scheduled inside five business days of surgery for supervisor review. Owner: scheduler.

Day of visit — documentation. Physician documents the request, the question, the evaluation, and the plan. Template prompts for the requesting provider's name. Owner: clinician.

Within 24 hours — report back. Report transmitted to the verified destination; confirmation filed. Owner: clinical support staff.

Within 48 hours — coding. Coder selects the E/M level from the documentation and applies the payer's diagnosis sequencing rule. Anything unclear goes back to the clinician as a query, documented. Owner: billing.

Monthly — reconciliation. Compare the referral tracker against billed encounters. Every logged request should map to a claim, a documented cancellation, or a no-show. Gaps are revenue leakage and records-handling gaps at the same time. Owner: practice manager.

The 30-Day Clock When the Patient Asks for the Clearance Letter

Patients ask for these constantly — surgical centers tell them to "bring your clearance," and they call your office for a copy. That is a right-of-access request, and it runs on the access timeline: generally 30 days, with one 30-day extension available if you notify the patient in writing of the reason and the new date.

You cannot condition release on payment of an outstanding balance. You cannot require the patient to explain why they want it. Fees, where charged, must fit within the permitted cost-based limits. HHS maintains detailed individual right of access guidance that your release-of-information staff should have bookmarked.

Practically: most clearance letters can go out same-day through the portal. Set that as the standing expectation, and reserve the 30-day framework for the unusual case. Train front desk to recognize that "can I get a copy of my clearance?" is an access request, not a favor.

Denials, Appeals, and the Records That Travel With Them

When a pre-procedural claim denies, your appeal packet typically includes the office note, the request document, and the report back. That packet is a disclosure for payment purposes — permitted without authorization, but subject to minimum necessary. Send the records that support the specific denial reason, not the entire chart.

Track appeal outcomes by payer and denial reason. Within two quarters you will know whether your problem is diagnosis sequencing, consultation reporting, or documentation of the request — and each of those has a different fix and a different owner.

What to Do This Quarter

Three concrete tasks. First, write the one-page payer matrix covering consultation recognition and diagnosis sequencing, and assign an owner with a review date. Second, audit ten pre-procedural encounters for the four documentation elements and report the results to your clinicians. Third, reconcile every vendor in the pre-op path against your executed agreements.

If that third task turns up gaps — and it usually does — produce the missing Business Associate Agreements before the next batch of requests hits the fax line. If your broader policy set and risk analysis haven't been refreshed alongside it, automating the full compliance document set is the cheaper path than rebuilding it under audit pressure. The coding question and the privacy question arrive in the same envelope; handle them in the same workflow.