Your hospitalist group's April denial report shows nine claims kicked back with the same message: documentation does not support a consultation service. All nine were billed as 99253. The clinical notes were thorough. What was missing were two lines of administrative text — the name of the requesting physician and the question they asked. If you run a practice that sends physicians to bedside consults, the 99253 CPT code description is not a coding curiosity. It drives your chart-completion checklist, your payer expectations, and the paper trail that leaves your building every time a consult report goes back to a referring doctor.

This guide walks through what the descriptor covers, how practices build workflows to determine and document code selection, and the privacy and vendor exposure that consultation traffic creates — outsourced coders, transcription services, fax platforms, release-of-information contractors, and the agreements you may not have on file.

What the 99253 CPT Code Description Covers

CPT 99253 sits in the middle of the inpatient or observation consultation family, 99252 through 99255. The descriptor describes a consultation for a new or established patient that requires a medically appropriate history and/or examination and a low level of medical decision making. When total time on the date of the encounter is used for code selection instead of medical decision making, the descriptor sets a threshold of 45 minutes, which must be met or exceeded.

Two structural facts your billing staff should have memorized:

  • 99251 no longer exists. It was deleted effective January 1, 2023. The inpatient/observation consultation family now begins at 99252.
  • History and exam no longer set the level. Since the 2023 evaluation and management revisions, level selection rests on either medical decision making or total time. History and examination are performed as medically appropriate but do not drive code choice.

Verify descriptors, time thresholds, and setting applicability against your current-year CPT manual and each payer's policy before you build them into a template. Nothing in this article tells you which code fits a given patient — that determination belongs to the treating physician and your certified coders, working from the documentation in front of them.

The Request-and-Report Rule That Kills More 99253 Claims Than Anything Else

A consultation is a distinct service because someone asked for it. CPT guidance requires that the request come from another physician or appropriate source, that the request and the reason for it be documented in the patient's record, and that the consultant's findings and opinion be communicated back in a written report.

Denials in this family rarely turn on the physician's clinical reasoning. They turn on the absence of the request, the absence of a stated question, or a note that reads like a transfer of care rather than an opinion rendered at someone else's request. If your physician assumed full management of the problem from the outset, the consultation family is generally the wrong place to look — and your coders need documentation clear enough to tell the difference.

Three fields to add to your consult intake form

  1. Requesting provider, with credential and service line. "Requested by hospitalist" is not a name.
  2. The specific question asked. One sentence, in the requester's words where possible.
  3. Date, time, and channel of the request. Secure message, hospital order, phone call logged by your answering service, or fax.

Assign this to whoever takes the consult call — usually a scheduler or clinical coordinator, not the physician. If it lives on a paper triage slip that never reaches the chart, your coder has nothing to work with and your appeals team has nothing to attach.

Proving the report went back

Build a closing step that produces evidence: a transmission confirmation, a portal delivery receipt, or a note in the chart identifying who the report was sent to and when. When a payer audits a batch of consultation claims eighteen months later, that evidence is the difference between a five-minute response and a write-off.

Why Your Medicare Line Never Shows 99253

Medicare stopped recognizing CPT consultation codes for payment in 2010. Physicians billing Medicare report the appropriate evaluation and management visit code for the setting instead — initial or subsequent hospital inpatient and observation care codes, for example. That policy has held for well over a decade, so the consultation family in practice belongs to commercial payers and to whichever Medicaid programs and secondary carriers recognize it.

The operational consequence: you cannot run one code map across all payers. If your charge entry template defaults every bedside consult to the consultation family, your Medicare claims will bounce and your staff will spend the month rebilling. Set payer-specific logic in the charge scrubber, and review it whenever a payer publishes a policy update. CMS maintains its current evaluation and management policy references on the Evaluation and Management Visits page.

Time or Medical Decision Making: What Your Coders Actually Need in the Note

Because the 99253 CPT code description allows either path, your documentation policy has to support both without encouraging shortcuts.

If the physician uses total time

Total time counts the reporting physician's or qualified health professional's own time on the date of the encounter — face-to-face and non-face-to-face — and excludes time for services reported separately. Clinical staff time does not count. The number in the note needs to reflect actual time spent, recorded by the person who spent it.

Here is the audit pattern to watch for: a template phrase such as "45 minutes spent in consultation" appearing on essentially every note from the same clinician. That uniformity is what draws payer attention. Flag it internally before someone else does, and address it as a documentation-behavior issue with the physician and your coding lead.

If the physician uses medical decision making

Your coders will look for what the note establishes about the problems addressed, the data reviewed and analyzed, and the risk of complications from management decisions. Give them a query workflow with a service-level target — for example, coder query out within one business day, physician response within three — and track queries that age past that window. Unanswered queries are how claims sit unbilled for a quarter.

Keep the internal boundary clean. Coders identify documentation gaps and ask questions. They do not select a level of service the record does not support, and they do not tell physicians what to write. Put that in your coding policy in writing.

Where the Consult Note Travels — and Which Vendors Need a BAA

Now the part that gets skipped. A consultation service is, by design, a disclosure. Your physician produces a report and sends it to another practice, often in another organization. Under the Privacy Rule, disclosures for treatment purposes to another provider are permitted without patient authorization, and the minimum necessary standard does not apply to treatment disclosures. HHS explains the boundaries of that standard in its minimum necessary guidance.

The exposure is not the disclosure. It is the infrastructure carrying it. Walk the path of a single consult note and list every outside party that touches it:

  • Cloud fax or secure messaging platform transmitting the report to the requesting practice
  • Transcription or ambient documentation service producing the note
  • Outsourced coding vendor assigning and auditing the level
  • Billing or revenue cycle company submitting the claim and handling denials
  • Denial-appeal or audit-defense consultant receiving copies of contested notes
  • Document storage, shredding, and archive vendors

Every one of those is a business associate, and every one needs an executed agreement on file before protected health information moves. HHS sets out what those agreements must contain in its business associate guidance. If you added a fax platform or an offshore coding partner in the last two years and cannot put your hands on the signed agreement in under ten minutes, you have a gap. You can produce a signature-ready contract for that vendor using a six-step business associate agreement generator that exports to PDF and DOCX — one-time purchase, no subscription — which is faster than waiting three weeks for the vendor's legal team to send you their version.

The hospital EHR is a different question

When your credentialed physician documents a consult in the hospital's system, the hospital is not your business associate and you are not theirs. That is provider-to-provider treatment activity, and in many facilities it is structured as an organized health care arrangement. What you do owe: a clear internal record of which of your clinicians hold access to which facility systems, and a termination checklist that removes that access the day someone leaves. Orphaned hospital logins belonging to a departed physician on your roster are your problem, not the hospital's.

When the Payer Requests the Note: A 14-Day Workflow

Disclosures to a health plan for payment purposes are permitted, but minimum necessary does apply here. A request for documentation supporting a consultation claim is not an invitation to send the entire chart.

  1. Day 1. Billing logs the request: payer, member, dates of service, claim numbers, response deadline, and the mailing or portal address.
  2. Days 2–4. Records staff pull only the encounters at issue — consult report, documented request and reason, and any separately identified supporting documents for those dates.
  3. Days 5–7. Compliance or the coding lead reviews the packet against the request. Nothing extra goes out.
  4. Days 8–10. Transmit through a channel covered by a signed agreement. Save the confirmation.
  5. Days 11–14. Close the log entry with what was sent, by whom, and to whom.

Treatment, payment, and operations disclosures are excluded from the patient-facing accounting of disclosures, so this log is for your own defense rather than a regulatory report. It is still the fastest way to answer "what did we send that payer in 2025?"

The Patient Asks for the Consult Note. Which Chart Do You Produce?

Patients often assume the consulting group holds the whole hospital record. It does not, and that confusion generates avoidable complaints.

You must provide access to protected health information in the designated record set you maintain, generally within 30 days, with one 30-day extension available if you notify the patient in writing of the reason and the new date. If your group keeps its own copy of the consult report, that copy is yours to produce. For the facility's full inpatient chart, direct the patient to the hospital's health information management department — in writing, with a name and phone number, not a shrug. The HHS right of access guidance covers timelines and permissible fees.

Script this at the front desk. "We have Dr. Reyes's consultation note from March 3. The rest of your hospital stay is held by the hospital — here is who to call." Two sentences prevent a records complaint.

A Seven-Line Audit You Can Run This Week

  1. Pull 20 recent consultation claims. Does each note name the requesting provider and the question asked?
  2. Of those 20, how many carry evidence that the written report went back?
  3. Does any single clinician document an identical total time on more than 80 percent of notes?
  4. Does your charge scrubber block consultation codes on Medicare claims?
  5. List every vendor that touches a consult note. Do you hold a signed agreement for each?
  6. Can records staff describe, from memory, the 30-day access timeline and the extension requirement?
  7. When did you last update your risk analysis to reflect the vendors added since?

If lines five and seven are where you stalled, start there. Contracts and a current risk analysis are the two artifacts an investigator asks for first, and both are documentation problems rather than clinical ones — which means you can close them without waiting on a physician's schedule. Tools that automate risk analysis reports and the supporting policy set shorten that work considerably, and getting the missing business associate agreements executed is a one-afternoon project rather than a quarter-long one. Put both on this month's list, before the next denial batch or records request forces the issue.