A surgical scheduler faxes your front desk at 4:15 on a Thursday: the patient is on Monday's OR board, the ASC needs "clearance," and they want the last two years of records attached. Your medical assistant has forty minutes before close, a fax cover sheet, and no written policy telling her what to send. That single moment contains a coding decision, a minimum-necessary decision, and at least three vendor relationships.

This guide covers how practices handle the preoperative exam ICD 10 code family operationally — what documentation your coders need, who owns each step, and where the records and vendor exposure sits. It is administrative guidance for administrators, billers, and privacy officers. It is not clinical guidance, and it does not tell you which code fits a given patient.

Which ICD-10-CM Codes Cover a Preoperative Exam?

Preprocedural examinations are classified under the Z01.81- subcategory, "Encounter for pre-procedural examinations." The descriptors distinguish the type of evaluation performed:

  • 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

Your coder selects among these by matching the descriptor to what the documentation actually says was evaluated and why. The current code set, addenda, and the ICD-10-CM Official Guidelines for Coding and Reporting are published by CMS on its ICD-10 code files page, and your coding staff should be working from the fiscal-year file in force on the date of service — not a cached PDF from three Octobers ago.

The Three-Layer Sequence Coders Expect on a Preop Encounter

The Official Guidelines address preoperative evaluations directly, and the structure they describe is what your billing staff should recognize on a clean claim:

  1. A code from Z01.81- sequenced first, describing the preprocedural examination itself.
  2. A code for the condition that is the reason for the planned surgery, reported additionally.
  3. Codes for any findings related to the preoperative evaluation.

Operationally, that means a preop claim rarely carries one diagnosis. If your scrubber is kicking back single-code preop claims, or your coders are dropping the surgical indication because "we're not doing the surgery," you have a training issue, not a payer issue.

Who assigns what

The clinician documents the request, the evaluation performed, and any findings. The coder maps that documentation to descriptors. Nobody in the billing office should be choosing a preoperative exam ICD 10 code from the schedule alone, from the surgeon's fax, or from a habit of "we always use the same one." Write that separation into your coding policy and hold it in your annual training file.

When the code changes after the visit

Findings identified during the evaluation frequently change the diagnosis picture after the encounter closes. Decide now who has authority to amend a submitted claim, how the amendment is documented in the chart, and how a corrected claim is tracked. Practices that leave this informal end up with coders editing notes — a records-integrity problem that shows up badly in any audit.

The Five Documentation Elements That Prevent Preop Denials

Payers, including Medicare, do not recognize a generic benefit called "surgical clearance." The encounter is payable as an evaluation and management service when it is medically necessary and documented as such. Denials in this category are almost always documentation failures, and they are fixable at the front desk.

Build a five-field intake block into your preop template:

  • Who requested the evaluation — named provider, practice, and date of request.
  • The planned procedure and its scheduled date.
  • The specific question asked — what the requesting provider wants evaluated.
  • The evaluation performed and the clinical reasoning documented by the treating clinician.
  • The findings and disposition, including anything newly identified.

Missing the first element is the single most common cause of a preop denial in practices I have reviewed. A faxed one-line request from a scheduler is not the same as a documented request from the operating provider, and your MA should be trained to capture the difference.

A Preop Clearance Workflow With Named Owners and Clocks

Assign the steps or they will not happen consistently.

Day 0 — referral intake (front desk)

Log the request in one place, not in a fax tray. Capture requesting provider, procedure, surgery date, and the ASC or hospital involved. Flag anything scheduled inside seven days for same-day scheduling escalation.

Day 0–1 — scheduling (front desk lead)

Book the encounter with enough lead time that results can be returned before the OR date. Note in the appointment record which facility will receive the report — that determines the disclosure route later.

Day of visit — documentation (clinician and MA)

The five-field intake block gets completed before the clinician closes the note. The MA confirms which outside records, if any, were requested and received.

Within 24–48 hours — coding and release (coder, then records staff)

Coding happens first; the release of information happens second. Reversing that order is how partially coded charts get faxed to surgical centers and then amended, leaving two versions of the truth in two organizations.

Weekly — reconciliation (billing lead)

Run a report of preop encounters with no corresponding claim, and preop claims denied in the prior week. Ten minutes weekly beats a quarterly cleanup project.

Minimum Necessary When the ASC Asks for "the Whole Chart"

Here is the point that trips up well-meaning staff. Disclosures to another provider for the treatment of the patient are permitted without patient authorization, and the minimum necessary standard does not apply to disclosures made to a health care provider for treatment purposes. HHS states this explicitly in its minimum necessary guidance.

So sending the surgeon what the surgeon needs to operate safely is lawful, and your staff should not be paralyzed by it. But two operational cautions apply.

First, the exception covers treatment disclosures. A scheduler collecting records for the facility's billing department, a pre-admission testing vendor, or a third-party clearance platform is a different analysis. Train your records staff to ask what the request is for and who is asking.

Second, HIPAA sets a floor, not your policy ceiling. Many practices adopt an internal standard of sending the preop report, the relevant diagnostics, and the medication list rather than a full chart dump — because a 200-page fax to the wrong number is a bigger breach than a four-page one. Whatever you choose, write it down and make it the default in your release template.

The fax number problem

Misdirected faxes remain one of the most ordinary breach causes in outpatient practices. Verify surgical-facility fax numbers against a maintained directory rather than the number printed on an inbound request, use a confirmation page, and document the verification step in your release log. This is unglamorous and it works.

Every Vendor a Single Preop Clearance Touches

Walk one clearance visit end to end and count the outside parties handling protected health information:

  • Cloud fax or secure-messaging service transmitting the report — business associate.
  • Referral or care-coordination platform the hospital asked you to log into — read the terms; if it stores your PHI, it is a business associate of somebody, and you need to know whose.
  • Transcription or remote scribe service documenting the encounter — business associate.
  • Billing or RCM company coding and submitting the claim — business associate.
  • Clearinghouse routing the claim — business associate.
  • Diagnostic overread or interpretation service under contract to your practice — analyze carefully; some arrangements are treatment relationships between providers, others are vendor services requiring an agreement.
  • Records-retrieval or courier vendor moving paper — business associate, and frequently the one nobody papered.
  • Reference laboratory — generally a covered entity in its own right, receiving the order as a treatment disclosure, not a business associate.

That is six or seven agreements riding on one Z01.81- encounter. If you cannot produce a signed, current agreement for each of those vendors within ten minutes, that gap is your real preop exposure — not the code selection. Practices closing that gap quickly can generate a signature-ready Business Associate Agreement through a six-step wizard, exported as PDF or DOCX, as a one-time purchase rather than another subscription line item.

Keep the agreements in the same folder as your vendor inventory, with a renewal date on each. A BAA that no one can locate is functionally the same as no BAA.

When Surgery Is Cancelled and the Patient Asks for the File

Cancelled procedures generate records requests. The patient wants to know what the evaluation found, or wants the file sent to a second surgeon, or is disputing a bill for a visit that led to no operation.

Your obligation is the individual right of access: generally act on the request within 30 days, with one 30-day extension available if you notify the individual in writing of the reason and the expected date. HHS maintains detailed right-of-access guidance, including limits on fees and the requirement to provide records in the form and format requested when readily producible.

Two operational notes specific to preop encounters. First, if a coding amendment happened after the initial report went out, the chart the patient receives should reflect the amendment history clearly. Second, a request to send records to the new surgeon is a patient-directed transmission, and your staff should log it as such rather than treating it as a routine provider-to-provider fax.

A 20-Minute Quarterly Check for Preop Encounters

Pull five preop charts at random each quarter and confirm:

  1. The requesting provider and the clinical question are documented in the note, not just the fax.
  2. The claim carries the preprocedural code plus the surgical indication plus any findings.
  3. The release log shows what was sent, to whom, on what date, and who verified the destination.
  4. Every vendor that touched the encounter appears on your inventory with a current agreement.
  5. Coding preceded release, and any post-release amendment is documented.

Five charts, twenty minutes, one dated memo in your compliance file. That memo is what you hand an auditor who asks how you supervise preoperative exam ICD 10 reporting and the disclosures that follow it.

If your broader documentation set is thinner than that — no current risk analysis, policies written by a previous administrator, no vendor inventory at all — build the foundation first. You can automate the risk analysis and policy set, and paper your vendors with a Business Associate Agreement you can sign this week. Start with the preop workflow, because it touches coding, records, and vendors in a single visit — and fixing it fixes three problems at once.