It's 7:40 a.m. and there are four faxes in the tray, all from the same orthopedic group, all saying some version of "Please clear patient for total knee, surgery date 2/3." No history. No problem list. No indication of what the surgeon is worried about. Your scheduler has to put these somewhere, your clinician has to see them, and your biller has to code them — and the way your team handles icd 10 preoperative clearance encounters determines whether you get paid, whether the surgical practice gets what it needs on time, and whether protected health information leaves your building through a channel you can actually account for.

This guide covers the operational mechanics: which code subcategory applies, how sequencing works, who owns each handoff, and where the records exchange with the requesting practice creates privacy and vendor exposure your risk analysis probably hasn't documented.

Short Answer: How ICD-10 Preoperative Clearance Encounters Are Coded

The ICD-10-CM Official Guidelines for Coding and Reporting address preoperative examinations directly. Encounters for preprocedural evaluation are reported from subcategory Z01.81, and the guidelines direct a three-part sequence:

  1. First-listed: a code from subcategory Z01.81 describing the type of preprocedural examination documented — cardiovascular (Z01.810), respiratory (Z01.811), laboratory (Z01.812), or other (Z01.818).
  2. Second: a code for the condition that is the reason for the planned surgery.
  3. Additional: any findings identified during the preoperative evaluation.

Your coder selects the specific Z01.81 code from what the clinician documented as the focus of the evaluation, not from what the fax cover sheet requested. If the note documents a cardiovascular assessment, the cardiovascular code is supported; if it documents only labs, the labs code is what the record supports. The current guidelines are published alongside the code set on CMS's ICD-10 page, and your coding lead should be pulling the fiscal-year update every October rather than relying on a cheat sheet taped to a monitor.

Why "Clearance" Is the Wrong Word on Your Intake Form

Surgeons say "clearance." Payers and coders recognize a preprocedural evaluation. That gap causes real operational problems.

When your front desk books the visit as "clearance," the clinician often receives no indication of what question is being asked. The note then reads as a generic physical, and the coder is left guessing which Z01.81 code the documentation supports. Denials follow, and so do rework loops with the surgical practice.

Rename the appointment type in your scheduling system to something like Preprocedural Evaluation — Requested, and require two fields at booking: the planned procedure and the specific concern prompting the request. That single change moves the coding decision out of guesswork and into documentation.

Consultation Versus Transfer of Care

The evaluation-and-management code family your billers apply depends on payer policy and on whether the encounter meets the requesting-provider criteria your payers use. Medicare stopped recognizing consultation codes years ago; many commercial payers still do. Your billing lead should maintain a payer-by-payer grid rather than letting each biller decide. Document the grid, date it, and review it when payer policy bulletins land.

The same discipline applies to modifiers. Staff sometimes reach for a mandated-services modifier because a third party "required" the visit. Whether that modifier fits a surgeon-requested preoperative evaluation is a payer-policy question, and your compliance lead should get a written answer from each major payer before it becomes a habit across thousands of claims.

The Documentation Packet You Should Demand Before the Visit

Your practice is not obligated to accept a one-line fax. Build an intake standard and give it to every surgical group that sends you volume:

  • Planned procedure and anticipated date
  • The specific clinical question being asked
  • Anesthesia type, if known
  • Any prior workup the surgical practice already holds
  • A named contact and a verified return fax number or Direct address

Send it as a one-page form. Practices that do this cut their inbound clarification calls sharply, and the resulting note almost always contains what the coder needs to support the icd 10 preoperative clearance selection.

Role Assignments: Who Owns Each Step

Front Desk

Verifies the request is complete against the intake standard. Confirms the return contact by calling a number from your own directory — not the number printed on the incoming fax. Logs the request in a tracking sheet with a due date tied to the surgery date, not to the request date.

Clinical Support

Pulls prior records, reconciles medications, and attaches the surgical practice's request to the encounter so the reason for the evaluation is visible in the chart, not just in a fax folder.

Clinician

Documents the focus of the evaluation explicitly. A note that names what was assessed and why is the difference between a clean claim and a records request from a payer six months later.

Coder or Biller

Applies the Z01.81 sequencing, verifies the reason-for-surgery code is present, and confirms findings are captured. Flags any note where the documented focus and the requested focus diverge — that discrepancy is a documentation problem, not a coding problem, and it goes back to the clinician.

Records or Release-of-Information Staff

Sends the completed evaluation back through an approved channel and logs the disclosure. This is the step most practices treat as clerical, and it is the step that produces breaches.

The Records Move Both Ways — That's Where Privacy Breaks

A preoperative evaluation generates a two-way exchange: records in from the surgical practice, a completed evaluation out. Both directions are treatment disclosures under the Privacy Rule, which means you do not need patient authorization to send the evaluation back to the requesting surgeon. That is settled, and staff should stop chasing signatures for it.

Two things get missed. First, the minimum necessary standard does not apply to disclosures for treatment — but that is not a license to dump an entire longitudinal chart into a fax queue. Sending 340 pages when the surgeon asked about cardiovascular status increases your exposure with no operational benefit, and it buries the answer the surgical team actually needs.

Second, the return path is where misdirected faxes happen. A transposed digit on a cover sheet sends a full evaluation to a car dealership. Your staff will not catch it, because the fax confirmation page prints "OK." Verify destination numbers against your own contact directory at intake, store verified numbers as scheduling contacts, and prohibit staff from keying numbers off incoming cover sheets.

Rank Your Return Channels

In order of preference: Direct secure messaging or an interoperability exchange your EHR already participates in; a portal-to-portal transfer where both practices hold accounts; encrypted email with a verified address; fax as the fallback. If fax is still your default in 2026, write down why, and put a date on revisiting it.

Log every outbound disclosure with date, recipient, channel, and what was sent. When a patient exercises their right to an accounting of disclosures — or when you're reconstructing an incident — a tracking log is the difference between a two-hour answer and a two-week one.

Every Vendor That Touches a Preop Packet Needs a BAA

Walk the path of one preoperative evaluation and count the outside parties. A cloud fax service. A transcription vendor. An outsourced coding partner. A clearinghouse. A release-of-information company. A document-scanning service handling the inbound paper. A patient-communication platform sending appointment reminders for the preop visit.

Each of those is creating, receiving, maintaining, or transmitting PHI on your behalf. Each requires a business associate agreement before the first record moves. HHS publishes sample BAA provisions as a baseline, but the sample is provisions — not a finished, signable contract with your entity names, breach notification timelines, subcontractor flow-down, and termination terms filled in.

If you're onboarding a coding vendor to handle preoperative volume next month and legal review is a six-week queue, you can generate a signature-ready Business Associate Agreement through a six-step wizard with PDF and DOCX export — one-time purchase, no subscription — and have the executed document in the vendor file before the first chart is transmitted. Attach it to your vendor inventory the same day.

A practical rule: if a vendor appears in your accounts payable and could plausibly see a patient name, it belongs on your BAA tracking list with an execution date and a renewal reminder.

Information Blocking and the Same-Day Result Problem

Preoperative evaluations generate labs, ECGs, and imaging that post to the patient portal on release. Patients frequently see abnormal findings before the surgical practice does, and before your clinician has called.

You cannot solve this by delaying release as a matter of routine. The information blocking rules constrain practices that withhold electronic health information without an applicable exception, and ONC maintains current guidance on what the rules require and which exceptions exist. What you can do is operational: set an internal standard for how quickly a clinician reviews preop results, script the front-desk response for the patient who calls about a portal result before anyone has reached them, and tell patients at the preop visit that results post automatically.

Denials, Audits, and the Documentation That Survives Both

Preprocedural evaluation claims draw scrutiny because they can look like routine physicals with a different label. The record that survives an audit shows three things: a documented request from the surgical practice, a documented clinical question, and a note whose content matches the Z01.81 code reported.

Run a quarterly sample. Pull twenty preoperative encounters and check whether the requesting document is in the chart, whether the reason-for-surgery code is present as a secondary diagnosis, and whether findings were coded. Track the failure rate by clinician and by coder. If the same gap appears twice in a row, it's a workflow defect, not a training gap.

A 10-Minute Self-Audit

  1. Is there a distinct appointment type for preprocedural evaluations, separate from annual exams?
  2. Does your intake form require the planned procedure and the specific clinical question?
  3. Are return fax numbers and Direct addresses verified against your own directory, not the incoming cover sheet?
  4. Is every outbound preop disclosure logged with recipient, channel, and content?
  5. Do you have an executed BAA for your fax service, transcription vendor, coding partner, and clearinghouse?
  6. Does your quarterly coding sample specifically include preprocedural encounters?
  7. Have you documented these workflows in your risk analysis, including the fax channel?

Any "no" on that list is an assignment with a name and a date attached, not a nice-to-have.

Next Step

Start with the vendor list, because it's the item most likely to be incomplete and the one that costs the most when it's wrong. Walk one preoperative packet end to end this week, write down every outside party that touches it, and confirm you hold a signed agreement for each. Where you don't, build the BAA and get it executed before the next chart moves. If your broader risk analysis and policy set haven't been refreshed since these workflows changed, automating the document set is the faster path to a file you can hand an auditor without apologizing for it.