A denial lands on your work queue: claim rejected, invalid procedure code, date of service February 2026, code billed 99441. Your biller pulls the encounter and finds a five-minute phone call documented by a clinician who used the same superbill template she has used since 2021. Nobody updated it. The 99441 cpt code description you are searching for describes a service that CPT deleted on January 1, 2025 — and if that code is still sitting in your charge master, your EHR favorites list, or a paper encounter form at the front desk, you have a cleanup project and a vendor review waiting for you.

This guide covers what 99441 described, what took its place, how practices document and select codes for phone-based encounters now, and the privacy, records, and business associate obligations that attach to every one of those calls.

What the 99441 CPT code description actually said

99441 was the first code in a three-code family for telephone evaluation and management services provided by a physician or other qualified health professional who may report E/M services. The distinguishing element across the family was time spent in medical discussion:

  • 99441 — 5 to 10 minutes of medical discussion
  • 99442 — 11 to 20 minutes
  • 99443 — 21 to 30 minutes

The code descriptors also carried conditions your billers should recognize, because the same logic survives in current guidance. The service had to be initiated by an established patient or the patient's guardian, it could not be reported if it occurred within a defined window after a related E/M service, and it could not be reported separately if it led to an E/M service within the next 24 hours or at the next available appointment. Time had to be documented.

Those conditions are why the 99441 cpt code description generated so many takebacks during the public health emergency years. Practices billed the code for calls that were really follow-up on a visit three days earlier, or for calls that turned into an office visit the following morning. The clinical note said "phone call, patient doing well." No time, no initiation, no assessment. That is a refund waiting to happen.

Is 99441 still a valid CPT code in 2026?

No. CPT deleted 99441, 99442, and 99443 effective January 1, 2025. For dates of service on or after that date, the code is invalid and payers will reject it. CPT replaced the telephone E/M family with a broader set of telemedicine E/M codes covering both audio-video and audio-only encounters, split by new versus established patient, plus a code for brief communication technology-based check-ins.

Two practical consequences. First, claims with 2024 dates of service that are still in appeal may legitimately carry 99441 — do not "correct" them to a current code. Second, coverage of the replacement audio-only codes is not uniform. Medicare's approach in the Physician Fee Schedule differed from CPT's structure, with instruction to continue reporting office/outpatient E/M codes and to identify audio-only delivery through modifier 93, alongside place-of-service coding. Commercial and Medicaid policies vary further. Your billing lead needs a payer-by-payer grid, not a single rule.

Where the payer grid actually lives

Build it as a one-page table your billers can see without opening three portals: payer, audio-only covered yes/no, code set accepted, modifier required, place of service, patient consent documentation required, and effective date of the policy you read. Put a review date on it. Recheck it every January and whenever a payer bulletin lands, because these rules have changed at least once a year since 2020. CMS maintains its current telehealth coverage material on the Medicare telehealth page, and the statutory flexibilities have been extended in short increments through a series of appropriations measures — confirm the live expiration date before you build a workflow that depends on it.

The five documentation elements your billers need to see

Regardless of which code set a payer accepts, the elements a reviewer looks for in a phone-based encounter note have stayed remarkably stable since the 99441 cpt code description was in force. Coding decisions belong to your clinicians and certified coders; your job as administrator is to make sure the note contains what a code selection has to be supported by.

  1. Who initiated the contact. Patient-initiated versus practice-initiated changes what can be reported. "Patient called reporting..." is a different note than "Nurse called to check in."
  2. Total time in medical discussion, stated in minutes, with start and stop or a total. Not "brief call."
  3. Modality. Telephone, audio-only, no video available or video declined. This drives modifier and place-of-service selection.
  4. Consent. Verbal consent to a telehealth encounter, obtained and documented, including any patient cost-sharing discussion your state or payer requires.
  5. Clinical content and disposition. Assessment, plan, and whether the encounter resulted in a scheduled visit — because a same-day or next-available visit may fold the call into that visit.

Turn those five into a note template block and a five-item pre-bill check. Your coder should be able to clear or query an encounter in under a minute.

Role assignments: who owns each step of a phone encounter

Front desk / phone triage. Captures who initiated the call, verifies identity against at least two chart identifiers, confirms the callback number on file, and routes the request. If your staff take clinical questions on a personal cell phone, that stops now — it creates PHI on a device your practice cannot inventory or wipe.

Clinical support. Confirms whether the patient had a related E/M service inside the lookback window and flags it in the encounter. This single check prevents most audio-only denials.

Clinician. Documents time, modality, consent, assessment, plan, and disposition contemporaneously. Selects the code, or defers to your coder with sufficient documentation to support selection.

Billing lead. Applies the payer grid, appends modifiers, monitors denial codes weekly, and owns the charge master. The charge master is where retired codes hide — 99441 should not be selectable for a 2026 date of service in any system you operate.

Privacy officer. Owns the platform inventory, the business associate agreements, the audio-only risk assessment, and the record-request workflow described below.

Every platform touching that call is a business associate

Here is where administrators get caught. OCR's Notification of Enforcement Discretion for telehealth ended in 2023, and with it the grace period for non-compliant consumer video and messaging tools. There is no lingering allowance for a personal video account or a consumer chat app used for patient care.

Walk the actual path of one phone encounter and count the vendors. The VoIP or cloud phone provider that carries and often records the call. The voicemail transcription service. The scheduling and reminder platform that texted the patient beforehand. The EHR or documentation tool holding the note. The ambient documentation or transcription assistant, if a clinician uses one. The clearinghouse that transmits the claim. The answering service that took the after-hours call in the first place. Each of those is a business associate if it creates, receives, maintains, or transmits PHI on your behalf, and each needs a signed agreement on file before it handles a patient call.

OCR's guidance on audio-only telehealth and HIPAA is explicit that a covered entity using a telecommunication service provider that creates, receives, maintains, or transmits PHI beyond mere conduit transmission needs a business associate agreement in place. A traditional landline carrier is generally treated as a conduit. A cloud platform that stores recordings, transcribes voicemail, or logs call content is not.

If your audit turns up a vendor with no agreement — and the answering service, the transcription add-on, and the reminder tool are the usual offenders — you can generate a signature-ready Business Associate Agreement through a six-step wizard with PDF and DOCX export, one-time purchase, and send it the same afternoon. That is faster than waiting for a vendor's legal team to surface a template, and it gives you a consistent document across your whole vendor list instead of eight different vendor-drafted agreements with eight different breach-notification clocks.

Audio-only is not HIPAA-free

Staff assume phone calls are exempt because there is no screen. Wrong instinct. The Security Rule applies to electronic PHI in any transmission, and a cloud-based phone system is electronic. Your risk analysis needs to address call recording retention, who can replay recordings, whether transcripts land in a searchable inbox, and how a lost cell phone with a softphone app gets remotely wiped. Verify patient identity before discussing PHI, and document that you did — a wrong-number disclosure is a reportable event.

Phone-visit notes are part of the designated record set

When a patient requests their record, the phone encounter note goes with it. So does the billing record showing what you charged. If a call recording is maintained in your designated record set — and if you store recordings tied to the chart, it likely is — treat it as accessible. The 30-day clock under the HIPAA right of access runs from the request, and OCR's enforcement history on access is long and unforgiving.

Two specific traps. First, records stored only inside a phone vendor's portal, where your release-of-information staff have no login and never think to look. Second, transcriptions that live in an email inbox rather than the chart. Both mean an incomplete production and a defensible-sounding excuse that will not hold up.

A 30-day cleanup checklist

  1. Days 1–3: Search every charge master, superbill, encounter form, and EHR favorites list for 99441, 99442, and 99443. Deactivate them for current dates of service. Keep them selectable for historical corrections only if your system supports date-bounded codes.
  2. Days 4–10: Build or refresh the payer grid for audio-only and telemedicine E/M. Circulate it to clinicians with a one-paragraph plain-language summary.
  3. Days 11–15: Update note templates to prompt for the five documentation elements. Test with one clinician before rolling out.
  4. Days 16–22: Inventory every vendor in the phone-encounter path. Match each to a signed, current business associate agreement. Chase the gaps.
  5. Days 23–27: Update your risk analysis to address call recording, transcription, and softphone devices. Document the decisions, not just the findings.
  6. Days 28–30: Brief your release-of-information staff on where phone-encounter documentation lives, and run one test request end to end.

Pull a denial report by code for the last twelve months while you are in there. If retired telephone E/M codes are still generating rejections, that is a measurable dollar figure to attach to this project when you take it to your physician owners.

What to do this week

Searching for the 99441 cpt code description usually means a claim already failed or an auditor already asked. Handle the code table first because it is fast, then handle the vendor list because it is the part that carries breach exposure. If your business associate agreements are incomplete, build the missing agreements from a guided six-step wizard and get signatures moving. If your broader documentation set — risk analysis, policies, workflows — has not been touched since the telehealth scramble of 2020, automating the risk analysis and policy set is a reasonable way to close that gap without a six-week consulting engagement.