A 42-page fax lands in your referral queue at 7:40 a.m. It contains a cardiology office's request for an endocrine opinion, six months of labs, and a scanned insurance card. Your intake coordinator scans it into the chart, schedules the visit for Thursday, and moves on. Three weeks later a payer asks you to substantiate the consultation you billed, and the only proof that a request ever existed is a fax header nobody indexed.

That is the operational reality behind the 99244 CPT code. This guide is for practice administrators, billing leads, and privacy officers who have to make consultation billing defensible — and who own the records and vendor consequences that follow every consult report out the door.

What the 99244 CPT Code Represents on a Claim

99244 sits in the office or other outpatient consultation family, which after the 2023 CPT revisions runs 99242 through 99245. The old 99241 was deleted effective January 1, 2023, so a four-code ladder is what your fee schedule should reflect.

Two structural facts drive everything downstream. First, the consultation codes apply to either a new or an established patient — there is no separate new-patient row, which is a common source of crosswalk errors when practices migrate a charge master. Second, since the 2023 alignment with the rest of office E/M, level selection rests on medical decision making or on total time on the date of the encounter. History and exam are performed as medically appropriate but no longer set the level.

For 99244, CPT associates the code with a moderate level of medical decision making, or with 40 minutes or more of total time on the encounter date. Which of those two paths a clinician uses is a documentation choice your billing team needs to see reflected in the note — not inferred.

Administrative guidance, not clinical guidance

Nothing here tells you which code fits a given patient. Your job as an administrator is to make sure the record supports whatever the treating clinician selected, that the selection method is visible, and that the supporting elements are captured before the claim goes out. Code selection belongs to the rendering provider; the audit trail belongs to you.

What Are the Requirements to Bill the 99244 CPT Code?

Four conditions have to hold before a consultation code is on the table at all:

  1. A documented request. Another physician, qualified health care professional, or other appropriate source asked for the opinion or advice, and the request plus the reason for it appear in the patient's record.
  2. An opinion rendered. Your clinician evaluated the patient and formed an opinion. Initiating diagnostic or therapeutic services during the same encounter does not disqualify a consultation.
  3. A written report back. Your clinician communicated findings and recommendations to the requesting party in writing.
  4. Level support. Documentation supports moderate medical decision making, or total time on the date of the encounter meets or exceeds 40 minutes for the 99244 CPT code.

If the referring provider transferred care outright rather than asking for an opinion, the encounter is not a consultation and your team should be selecting from the standard office visit family instead.

Building the Request-Render-Report Trail Your Auditor Will Ask For

The failure mode is almost never the clinical note. It is the request and the report — the two pieces that live at the front desk and in the outbound queue.

Capture the request as a chart artifact, not a fax pile

Assign one person per site to index inbound referrals the day they arrive. The minimum fields: requesting practice, requesting clinician's name, date received, stated reason for the request, and the document ID where the original request lives in the chart. If your intake team retypes the reason into a scheduling field and discards the source document, you have created a summary with no provenance.

Verbal requests happen. A cardiologist calls your physician at the hospital and asks for an opinion. That request is billable-supporting only if someone writes it into the record contemporaneously, with who asked, when, and why. Build a template. Do not rely on memory at claim-scrub time.

Close the loop on the written report

The report back is the element practices most often assume happened. Put a work queue on it. A consultation charge should not drop until the report has a transmission record — sent date, recipient, and channel. Many practices set a rule that the charge holds for a fixed window, commonly the same business day the note is signed, and escalates if the report is unsent after that.

Medicare Doesn't Recognize Consultation Codes — Your Payer Matrix Has To

CMS stopped recognizing the office and inpatient consultation codes for Medicare payment effective January 1, 2010. Medicare claims use the appropriate office visit or hospital care code instead. That policy is long-settled and still in force, and your fee schedule and edits should enforce it automatically rather than depending on a biller remembering.

Commercial plans and Medicaid programs vary. Some pay consultation codes; some mirror Medicare; some pay them only for specific specialties or only with a documented referral in the claim record. Maintain a payer-by-payer grid with three columns: recognizes consults yes/no, effective date of the policy you verified, and the source document. Review it twice a year and after every contract renewal. Verify current Medicare payment policy through the CMS Physician Fee Schedule resources rather than a secondhand summary.

Practical consequence: the same encounter can produce a 99244 claim for one plan and an office visit code for another. That is a configuration problem, not a coding judgment call, and it belongs in your claim edits.

The Consultation Report Is a PHI Disclosure — the Channel Is Where Practices Slip

Sending your report back to the requesting clinician is a disclosure for treatment purposes. It is permitted without patient authorization, it does not require an accounting of disclosures, and the minimum necessary standard does not apply to disclosures to a provider for treatment. HHS states the treatment exception plainly in its minimum necessary guidance.

What HIPAA does not excuse is the transport. Every channel your practice uses to return a consult report is a Security Rule question:

  • Cloud fax. Your fax provider stores and transmits PHI. That is a business associate relationship, and "we've always used them" is not a signed agreement.
  • Direct secure messaging. Usually flows through your EHR or a HISP. Confirm which entity holds the contract and whether the agreement covers message retention.
  • Portal-to-portal or HIE delivery. Check what the receiving organization can see beyond the report itself.
  • Paper mail. Still common for out-of-network referrers. Log it the same way you log electronic sends.
  • Plain email. If a referring office asks you to email the report to a general inbox, that request goes to your privacy officer, not to a medical assistant.

Wrong-number faxes and misaddressed reports remain among the most ordinary breach triggers in ambulatory practices. A verified recipient directory, reviewed quarterly, prevents more incidents than any policy document.

Records That Arrive Before the Visit Become Yours

Those 42 pages the cardiologist sent? Once your clinician uses them to make decisions about the patient, they sit inside your designated record set. That has three concrete effects.

First, a patient can request them from you and you owe a response within 30 days, with one 30-day extension available if you notify the patient in writing. HHS's right of access guidance is the operative reference, and "go ask the referring office" is not a compliant answer for records you hold and used.

Second, amendment requests can reach outside records in your chart. You are not obligated to amend another provider's document, but you must process the request, respond in writing, and document the outcome.

Third, your retention schedule now covers material you did not create. Make sure your records policy says so explicitly, and that your ROI staff know inbound referral packets are in scope for a standard release.

Every Vendor That Touches a 99244 Claim Needs a Signed BAA

Walk the claim from encounter to payment and list who handles PHI along the way. For a typical specialty practice billing consultations, that list looks like this:

  • EHR and practice management host
  • Clearinghouse
  • Cloud fax or secure messaging provider
  • Transcription or ambient documentation service
  • Outsourced coding or billing company
  • External coding auditor reviewing your consultation documentation
  • Denials management or A/R follow-up firm
  • Release-of-information vendor
  • Offsite scanning or shredding contractor
  • Backup and archive provider

The external coding auditor is the one practices forget. When you hire a firm to sample consultation charts and tell you whether the request-render-report trail holds up, that firm reads full clinical notes. It is a business associate on day one, before the first chart is pulled.

If a name on that list has no executed agreement, close it now. HHS publishes sample business associate agreement provisions, and if you would rather not assemble one from scratch, you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX — a one-time purchase, no subscription, which matters when you need three agreements this week and none next quarter.

Time-Based Selection Creates an Audit Trail You Should Test

When a clinician selects a consultation level by total time, the number in the note is the claim's foundation. Total time on the date of the encounter includes qualifying non-face-to-face work by the reporting clinician — record review, ordering, documentation, care coordination — performed that day.

Two administrative controls are worth building. Require the note to state the actual total time rather than a canned phrase. And run a periodic distribution check: if a single clinician's time-based consultations cluster tightly at exactly the 40-minute threshold, that pattern is what an outside reviewer will notice first. Address it internally with education before a payer addresses it for you.

Keep in mind that your EHR's own metadata — open/close timestamps, signature times — may be pulled in an audit. That is another reason your EHR agreement and your understanding of what the vendor retains should be current.

A Payer Audit Is a Payment Disclosure — Know Who Answers

When a plan requests documentation for a consultation claim, releasing the records is a disclosure for payment purposes. Permitted, no authorization needed. But minimum necessary does apply here, unlike the report back to the referring clinician.

Name a single owner for audit responses. Log what was sent, to whom, on what date, and under which request number. Send the encounter documentation the payer asked for — not the entire chart because exporting the whole thing was faster. Over-disclosure in response to a payer request is a genuine and avoidable exposure.

Six Checks to Run This Quarter

  1. Pull 20 consultation claims from the last 90 days. Confirm each has an indexed request document and a logged outbound report.
  2. Verify your fee schedule reflects the four-code family and that 99241 is retired everywhere, including paper superbills.
  3. Re-verify consultation policy for your top five payers and date-stamp the grid.
  4. Reconcile your vendor inventory against executed BAAs. Flag anything unsigned or older than your current template.
  5. Review the fax and Direct recipient directory for stale entries.
  6. Confirm your risk analysis covers the referral intake and report-out workflow, not just the EHR. If yours has not been refreshed since your last system change, automated risk analysis and policy generation will get you to a current document faster than a spreadsheet rebuild.

Consultation billing rewards boring discipline. The request gets indexed, the report gets sent and logged, the payer grid stays current, and every vendor in the path has a signed agreement on file. Start with the BAA gap — it is the fastest one to close, and the BAA generator will hand you an executable document before your next referral batch arrives.