A hospital discharge notification hits your practice inbox at 4:52 p.m. on a Friday. Your patient went home from observation that afternoon. If nobody in your office reaches that patient or their caregiver by close of business Tuesday, the transitional care management CPT codes are off the table for that episode — and the coordination work your nurse does next week gets billed as a plain office visit or not at all.

This guide is written for the administrator, billing lead, or privacy officer who has to build that workflow and then defend it. It covers the operational mechanics of transitional care management, then makes explicit what the workflow does to your records handling, your vendor list, and your risk analysis. It does not tell you which code fits which patient. That is a documentation-driven determination your clinicians and coders make.

What the Transitional Care Management CPT Codes Cover

The transitional care management CPT codes are 99495 and 99496. Both describe a 30-day service period that begins on the date a patient is discharged from an inpatient, observation, partial hospitalization, or skilled nursing setting back to a community setting — home, domiciliary, rest home, or assisted living.

Three elements define both codes:

  • Interactive contact with the patient or caregiver within two business days of discharge, by phone, secure electronic means, or in person.
  • A face-to-face visit within a defined window — 14 calendar days for 99495, 7 calendar days for 99496.
  • Medical decision making of a specified complexity — moderate for 99495, high for 99496 — documented during the service period.

Medication reconciliation and management must occur no later than the date of the face-to-face visit. Only one practitioner may report a transitional care management service per patient per 30-day period. CMS publishes the operative details in its Medicare Learning Network booklet on Transitional Care Management Services, and you should re-read it against each year's Physician Fee Schedule final rule, because concurrent-billing restrictions with other care management codes have shifted more than once.

The Three Clocks Your Front Desk Is Actually Running

Everything that goes wrong with these codes goes wrong on a calendar. Build the workflow around the clocks, not the codes.

Clock one: two business days to interactive contact

Business days, not calendar days — which means a Friday discharge gives you through Tuesday, and a holiday shifts it. Contact must be interactive. A voicemail is an attempt, not contact. An automated outreach text that nobody answers is an attempt.

CMS guidance has allowed reporting when two or more separate, timely attempts are made and documented but unsuccessful, provided all other requirements are met. Your policy should define what an attempt looks like: date, time, staff initials, method, and outcome, logged in the chart rather than in a nurse's notebook.

Clock two: 7 or 14 calendar days to the face-to-face

This is a scheduling problem before it is a billing problem. If your next available slot with the discharging patient's usual clinician is 19 days out, the transitional care management CPT codes are unavailable regardless of how good the coordination was.

Practices that succeed here hold protected same-week slots and give the care coordinator authority to book into them without a scheduler handoff. Name the person who holds that authority in writing.

Clock three: the 30-day service period

The service period runs 30 days from the date of discharge, and it includes non-face-to-face work performed by clinical staff under the billing practitioner's supervision — reviewing the discharge summary, arranging community services, educating the patient and caregiver, coordinating with home health.

CMS has permitted submission of the claim after the required face-to-face visit occurs rather than requiring practices to wait out the full 30 days. Confirm your clearinghouse edits and your MAC's current instruction before you change your drop-date, and document the version of guidance your policy relies on.

Role Assignments That Survive an Audit

Write the workflow as a named-role document, not a narrative. A reviewer asking about a 2027 claim should be able to see who owned each step in May 2026.

  1. Discharge intake. Who monitors the admit/discharge/transfer feed, the hospital portal, and the fax line? Assign a primary and a backup, and define the check frequency — including weekends, because clock one does not care about your staffing model.
  2. Interactive contact. Who calls, from what number, with what script, and where does the log live?
  3. Records retrieval. Who requests the discharge summary, and by what channel?
  4. Scheduling. Who books the visit and who escalates when no slot exists?
  5. Medication reconciliation. Who performs it and where is it documented so a coder can find it without hunting?
  6. Claim assembly. Who verifies the dates line up before the claim goes out?

Give the billing lead a pre-submission checklist that confirms four dates: discharge date, contact date, face-to-face date, and medication reconciliation date. Most denials and most refund obligations trace back to one of those four being wrong or unfindable.

How Practices Determine and Document Code Selection

Code selection between 99495 and 99496 turns on documented medical decision making complexity and the date of the face-to-face visit. Your job as an administrator is to make sure the documentation supports whatever the clinician determined — not to determine it.

Practical controls that hold up:

  • A note template that captures the discharge date as a discrete field rather than free text, so it can be audited without chart review.
  • A coder query pathway used when the visit date and the documented complexity appear inconsistent, with the query and the response retained.
  • A quarterly internal audit sampling 10 to 20 transitional care management claims against the four dates and the supervision requirements.
  • A written escalation rule: when documentation does not support the elements, the service is reported as whatever the record supports, and the decision is logged.

Do not let a template auto-populate anything about complexity. A template that pre-selects a code and asks the clinician to un-select it is a finding waiting to happen.

The Privacy Exposure: You Are Handling Records You Did Not Generate

Transitional care management pulls protected health information into your practice from outside it, at speed, often through channels your privacy policies were not written for. That is the part nobody budgets for.

Discharge summaries, ADT feeds, and hospital portals

Obtaining discharge information for a patient you are treating is a treatment disclosure. It does not require authorization. What it does require is that the intake channel be a channel you have inventoried.

If a hospital sends event notifications through a health information exchange or an intermediary, confirm in writing how that intermediary is characterized and whether your practice has an agreement in place. If discharge summaries arrive by fax to a machine in a hallway, that is a physical safeguard problem you now touch every week instead of occasionally. If a coordinator uses a personal login to a hospital portal and downloads PDFs to a laptop, you have created a new PHI repository outside your EHR.

Voicemail, text, and unencrypted email

Clock one pushes staff toward whatever channel is fastest. Write the script before that happens.

A voicemail left for an unconfirmed number should contain the practice name, a callback number, and nothing about the hospitalization. Text outreach needs a documented consent trail and a defined content limit. Patients may request communication by unencrypted email, and you may honor that request after advising them of the risk — but that request needs to be recorded in the chart, not remembered by the coordinator. Apply the minimum necessary standard to every one of these channels, and audit a sample of call logs annually.

Vendors in the TCM Workflow That Need a BAA

Run your vendor list against the workflow you just wrote. The transitional care management CPT codes typically drag in several relationships that were never on the list:

  • Care management or population health platforms that ingest discharge feeds and generate task queues.
  • Answering services and after-hours call centers making or receiving the two-business-day contact.
  • Contracted care coordination companies supplying nurses who perform non-face-to-face services.
  • Outbound messaging vendors handling appointment texts tied to the 7- or 14-day visit.
  • Health information exchanges and notification intermediaries routing ADT data.

One distinction matters for the contracted coordinators. Staff you lease and directly control day to day may be workforce members under your policies; an independent firm running its own supervision and systems is a business associate and needs an executed agreement. Decide which model you are using, write it down, and paper it accordingly. If you need a defensible agreement quickly, you can generate a signature-ready Business Associate Agreement and compare it against the sample provisions HHS publishes.

Documentation, Retention, and the Records Request You Will Get

The transitional care management record is not just the office note. It is the contact log, the medication reconciliation, the discharge summary you obtained, and any coordination notes your clinical staff wrote.

When a patient requests their record, all of that is in scope if it sits in the designated record set. Your practice generally has 30 days to respond, with one 30-day extension available, under the HHS right of access guidance. A coordination log living in a spreadsheet on a shared drive is still a record. Decide now whether that spreadsheet is part of the designated record set, or eliminate the spreadsheet and put the log in the chart.

A Worked Timeline

Patient discharged from observation on Thursday, May 7. Notification reaches the practice Thursday evening.

  • Friday, May 8: Coordinator calls at 9:15 a.m., reaches the patient's daughter, who is the documented personal representative. Contact logged in the chart with date, time, method, and who was reached.
  • Friday, May 8: Discharge summary requested through the hospital's provider portal; retrieval logged.
  • Monday, May 11: Visit scheduled into a held slot for Wednesday.
  • Wednesday, May 13: Face-to-face visit occurs. Medication reconciliation completed and documented that day. Clinician documents medical decision making complexity.
  • Thursday, May 14: Billing lead runs the four-date checklist, confirms supervision requirements for the non-face-to-face work, and routes the claim.
  • Through June 5: Remaining 30-day-period coordination documented in the same chart location.

Notice what is auditable here: every step has a date, an actor, and a location in the record. That is the whole game.

Update Your Risk Analysis Before the First Call

Standing up transitional care management changes your risk profile in ways your last analysis did not contemplate: new external data feeds, staff calling patients from outside the office, a new vendor or two, and a coordination log that may live outside the EHR. A risk analysis that predates the workflow does not cover the workflow.

If your documentation set is stale or scattered across old Word files, this is the moment to fix it. Tools that automate HIPAA risk analysis reports and the supporting policy set let you re-run the analysis when you add a workflow instead of once a year when someone remembers. Update the asset inventory, the vendor list, and the communications policy in the same pass.

Do this in order: write the workflow, name the roles, list the vendors, paper the agreements, then re-run the risk analysis against the workflow you actually built. The transitional care management CPT codes will pay for the coordination work your practice is already doing — but only if the dates, the documentation, and the vendor paperwork all line up when someone asks.