A surgical office faxes your clinic a one-page form at 4:40 p.m. on a Tuesday. It says "pre-op clearance, surgery 5/28" and nothing else. Your front desk books the patient for Thursday, the provider documents a visit, and eleven days later the claim comes back denied for medical necessity. That single fax is where every presurgical evaluation ICD 10 problem starts — and it is also an unlogged inbound disclosure of protected health information that nobody on your team assessed.

This guide is for the administrator, biller, or privacy officer who owns both halves of that visit: the coding and documentation mechanics that get the claim paid, and the records-handling and vendor obligations that come with shuttling charts between a primary care clinic, a surgeon, an anesthesia group, a hospital or ASC, and a lab. Nothing here is clinical guidance. It is workflow.

Which ICD-10 code applies to a pre-op visit?

Pre-procedural examination encounters are reported from subcategory Z01.81- in ICD-10-CM. The official ICD-10-CM Guidelines for Coding and Reporting (Section I.C.21) instruct that for a patient receiving preoperative evaluations only, you sequence a code from Z01.81- first to describe the pre-procedural encounter, then assign a code for the condition that is the reason for the planned surgery, and then code any findings related to the evaluation.

The subcategory includes:

  • Z01.810 — encounter for pre-procedural cardiovascular examination
  • Z01.811 — encounter for pre-procedural respiratory examination
  • Z01.812 — encounter for pre-procedural laboratory examination
  • Z01.818 — encounter for other pre-procedural examination

Which one applies is a documentation-driven determination made by your coder or provider from the actual note and the actual request — not something an administrator assigns from the appointment type. Your job is to make sure the record contains enough detail that the determination is defensible, and that the encounter is genuinely a pre-procedural evaluation rather than routine chronic disease management that happens to fall before a surgery date. Verify current codes and effective dates against the CMS ICD-10 code set files each October.

The Six Intake Fields That Decide Whether the Claim Survives

Most denials on these visits trace back to intake, not coding. Build these fields into your scheduling template and make them required before the appointment is confirmed:

  1. Requesting provider name and NPI. Several payers want the request documented in the note.
  2. Planned procedure and scheduled date. Vague requests produce vague notes.
  3. Surgical facility. Determines where results go and under what agreement.
  4. What was specifically requested. Cardiovascular evaluation? Labs? A general assessment? This is the single most useful field on the form.
  5. Whether the surgeon is requesting a consultation or transferring management of a condition. Different documentation expectations, different code family on the CPT side.
  6. Coverage and any prior authorization already obtained by the surgical office.

Assign ownership explicitly. Scheduler captures fields 1–4. Referral coordinator confirms 5–6 by phone if the fax is incomplete — and documents the call. If your front desk cannot get a complete request, the visit does not get booked as a pre-op evaluation; it gets booked as whatever it actually is.

Build a one-page return request form

Send incomplete faxes back with your own template rather than chasing details verbally. Practices that do this cut their pre-op denial volume noticeably within a quarter, and they end up with a written record of what the requesting provider asked for — useful in both an appeal and an audit.

Documentation That Supports Presurgical Evaluation ICD 10 Selection

Coders cannot invent specificity. Three elements need to be present in the encounter record for the presurgical evaluation ICD 10 assignment to hold up:

1. The request itself, in the chart

The inbound fax, portal message, or referral record belongs in the encounter, not in a shared drive folder. If the request lives outside the legal medical record, it disappears the moment a payer asks why the visit happened.

2. The reason for the planned surgery

The guideline directs a code for the condition prompting surgery as an additional diagnosis. That condition has to be documented in your note, sourced from records you actually received — which means the referral packet matters operationally, not just clinically.

3. Findings, if any

Anything identified during the evaluation gets coded in addition. Your provider documents it; your coder decides sequencing. Administrators should not be nudging either direction.

On the CPT side, keep in mind that Medicare has not recognized the consultation code family since 2010, so "clearance" visits are typically reported using standard office visit codes for Medicare patients while some commercial payers still accept consultation codes. Your billing lead should maintain a payer-by-payer grid rather than relying on habit.

The Disclosure Map: Four Organizations, One Visit

Now the part that most coding guides skip. A single pre-op evaluation typically involves PHI moving among:

  • The requesting surgical practice (inbound request, outbound report)
  • Your clinic (the evaluation, the note, the claim)
  • An anesthesia group, hospital pre-admission unit, or ASC (results, medication list, testing)
  • A reference lab or imaging center (orders and results)
  • The payer (claim, and later the appeal or audit response)

Disclosures among these providers for treatment purposes are permitted without patient authorization under the Privacy Rule's treatment, payment, and health care operations provisions. That is the easy part. The operational failures happen in how much gets sent and where it lands.

Minimum necessary applies unevenly — know which side you are on

The minimum necessary standard does not apply to disclosures to another provider for treatment. It does apply to disclosures for payment and health care operations. So when your biller sends a records packet to a payer supporting a pre-op claim appeal, sending the entire chart because it was easier to print is a minimum necessary problem. HHS guidance on the minimum necessary requirement is worth putting in front of your billing team once a year.

The fax number nobody re-verified

Pre-op workflows run on standing fax numbers stored in a scheduling macro from 2021. When a surgical practice moves offices or changes numbers, results go somewhere unintended. Add a quarterly verification task: every recurring outbound destination for pre-op reports gets confirmed against the receiving organization's current listing, and the confirmation is documented with a date and initials. Misdirected faxes are one of the more common small breaches practices self-report, and they are almost always preventable at the address-book level.

Where Your Vendor List Gets Exposed

Trace the pre-op encounter end to end and count the outside companies that touch it. In a typical mid-sized practice:

  • A revenue cycle or billing company submits and works the claim
  • A contract coder or coding review service reviews diagnosis assignment
  • A clearinghouse transmits the claim
  • An electronic fax or secure-messaging service moves the report
  • A transcription or ambient documentation tool creates part of the note
  • A patient reminder or texting platform confirms the appointment
  • An IT managed service provider has administrative access to all of it

Every one of those is a business associate. Each needs a current, signed business associate agreement, and each should appear in your risk analysis with a note on what data it touches. When a practice discovers a gap here, it is usually the contract coding service or the fax vendor — the two that got added mid-year without going through contracting. If you need to close a gap quickly, you can generate a signature-ready business associate agreement and get it out the same day rather than waiting on a vendor's legal cycle.

Pre-op workflows also tend to create informal data paths: a coordinator's personal cloud drive holding scanned referral packets, a shared inbox nobody audits, a spreadsheet tracking surgery dates with names and diagnoses. Those are not vendor problems. They are documentation problems, and they belong in your risk analysis with a remediation date.

The Records Request That Follows Six Months Later

Pre-op documentation shows up in access requests more often than administrators expect — disability filings, second opinions, and litigation over surgical outcomes all pull the pre-procedural evaluation into scope. Your obligation runs on a 30-day clock from receipt, with one possible 30-day extension and written notice of the delay. Review the HHS right of access guidance against your actual turnaround times, not your policy's stated turnaround times.

Two practical traps:

Split records. If part of the pre-op evaluation lives in your EHR and part lives as a scanned PDF in a referral folder, a fulfillment clerk will send one and miss the other. Designate a single location for inbound surgical requests and outbound reports.

Non-treatment recipients. A request from an employer, an attorney, or a disability insurer is not a treatment disclosure. That needs a valid authorization, and your staff needs to recognize the difference at intake rather than after the packet is in the mail.

A Worked Example, End to End

Consider a hypothetical: a surgical office requests an evaluation ahead of an elective orthopedic procedure and asks specifically about a cardiac history. Your coordinator confirms the requesting provider, procedure, date, facility, and the specific request, then files the fax into the encounter. The provider documents the evaluation, the reason for surgery, and any findings. Your coder reviews the note and assigns the presurgical evaluation ICD 10 code from Z01.81- supported by that documentation, sequences the surgical indication next, and adds findings.

On the privacy side: the report goes to the surgeon and the anesthesia group as a treatment disclosure, logged in the outbound record. The claim goes through your clearinghouse under a current BAA. When the payer requests documentation two months later, your biller sends the pre-op encounter and supporting results — not the full chart. If your coding is handled by an outside firm, that firm's access is scoped to what it needs and documented.

That is what a clean pre-op workflow looks like. Notice how much of it is assignment of responsibility rather than coding knowledge.

Five Tasks to Assign This Month

  1. Privacy officer: list every outside organization that touches pre-op documentation and confirm a signed BAA exists for each.
  2. Billing lead: build the payer-by-payer grid for pre-op visit reporting rules and appeal documentation expectations.
  3. Front desk supervisor: add the six required intake fields to the scheduling template and the return-request form to the fax queue.
  4. Records custodian: designate one storage location for inbound surgical requests and re-verify every recurring outbound fax destination.
  5. Practice administrator: confirm your risk analysis reflects the current vendor list and the informal data paths, and set a review date.

If item five stalls because your last risk analysis is a two-year-old spreadsheet, that is the usual bottleneck. Tools that automate HIPAA risk analysis reports and the supporting policy set get you from "we know we should" to a documented, dated assessment you can hand to an auditor — including the vendor inventory that pre-op workflows quietly expand every quarter.

Start with the disclosure map. Once you can draw where a single pre-op evaluation's data travels, the coding discipline, the BAA gaps, and the records-request exposure all become visible on the same page — and fixable in the same afternoon.