A hospital discharges your patient at 4:40 p.m. on a Friday. Your two-business-day interactive contact clock is already running, nobody in your office has seen the discharge summary, and the ADT notification landed in an inbox your care coordinator checks on Mondays. That single gap is the most common reason practices lose transitional care management revenue — and the most common reason a payer takes it back on audit.

This is an operations guide to transition of care CPT billing for practice administrators, billing leads, and privacy officers. It covers the timing rules, who owns each step, how practices document code selection defensibly, and — the part that usually gets skipped — the vendor relationships and PHI flows this service line creates. It is administrative guidance, not clinical guidance.

What Transition of Care CPT Codes Actually Require

Transitional care management is a 30-day bundled service reported after a patient moves from an inpatient or equivalent setting back to a community setting. The CPT code set contains two codes for it, distinguished by the complexity of medical decision making and how quickly the face-to-face visit occurs.

Three elements must all be satisfied and documented:

  • Interactive contact with the patient or caregiver within two business days of discharge, by phone, in person, or electronically.
  • A face-to-face visit within 7 or 14 calendar days of discharge, depending on which code applies. The visit is part of the bundle and is not separately reported.
  • Non-face-to-face services across the 30-day period beginning on the discharge date — reviewing discharge information, following up on pending diagnostics, medication reconciliation no later than the date of the face-to-face visit, education, referrals, and scheduling.

One practitioner reports the service per patient per 30-day period. The billing practitioner — not the coder, not the care coordinator — determines the level of medical decision making, and that determination drives which of the two codes is reported. Your job as an administrator is to make sure the record supports whatever the practitioner selected.

The Two-Business-Day Clock and Who Owns It

Assign this clock to a named role, not to a team. "The care coordinators" owns nothing. "The RN care coordinator on the discharge queue, backed up by the front-desk lead" owns something.

Business days exclude weekends and holidays, which means a Friday evening discharge gives you until end of day Tuesday. That sounds generous until you account for the fact that most practices do not learn about the discharge on Friday at all.

Building the discharge intake queue

Your queue should have exactly one entry point. Feed it from every source you actually have: electronic patient event notifications from hospitals, your health information exchange, faxed discharge summaries, hospitalist calls, and patient-initiated calls. Deduplicate at intake, timestamp every entry, and record the discharge date separately from the notification date. Auditors care about the discharge date; your staffing model cares about the gap between the two.

Under the CMS Interoperability and Patient Access rules, many hospitals are required to send electronic patient event notifications at admission, discharge, and transfer to established outpatient providers. If you are not receiving them, that is a conversation with your hospital partners and your HIE — not a reason to run this service line off fax alone. CMS summarizes the notification requirements in its Interoperability and Patient Access fact sheet.

Documenting failed attempts

Contact attempts fail constantly. Wrong number, no voicemail box, caregiver unreachable. CMS guidance permits reporting the service when timely attempts were made and documented but unsuccessful, provided the other requirements are met. Your telephone note template needs date, time, method, staff initials, and outcome for each attempt. A note that says "called patient, no answer" with no timestamp is worth nothing in an audit.

The Face-to-Face Window and the 30-Day Service Period

Two different clocks run simultaneously and staff confuse them weekly.

The face-to-face visit window is 7 or 14 calendar days from discharge, depending on the code. Calendar days, not business days. The 30-day service period begins on the date of discharge and runs through the following 29 days; that is the window during which the non-face-to-face work counts.

Build the scheduling rule into your template, not into tribal knowledge. When a discharge hits the queue, the scheduler should be offered slots inside the 7-day window first. If the practice cannot make 7 days, the schedule should still target 14 — but nobody in scheduling should be inferring which code will be reported from the slot they booked. That inference runs backward and is exactly how upcoding allegations start.

CMS permits reporting the service on the date of the face-to-face visit rather than waiting for the 30-day period to close. Confirm current billing mechanics, concurrent-billing allowances with other care management services, and place-of-service rules against the annual Physician Fee Schedule materials on the CMS fee schedule site before you finalize a charge-capture rule. These rules have changed more than once since the codes were introduced.

How Your Practice Documents Code Selection Without Practicing Medicine

Administrators get in trouble here in two directions. Some practices let coders pick the higher-complexity code because the visit happened inside 7 days. Others default every case to the lower-complexity code to avoid scrutiny, which is its own form of inaccuracy.

The defensible process looks like this:

  1. The clinical record documents the discharge date, the date and method of interactive contact, the date of medication reconciliation, and the date of the face-to-face visit.
  2. The billing practitioner attests to the level of medical decision making in the note, in their own words, not through a checkbox your billing team added.
  3. Coding staff verify that the documented dates satisfy the timing element for the code the practitioner selected, and that the 30-day period contains no duplicate report for the same patient.
  4. If the dates and the selected code conflict, coding queries the practitioner. Coding does not change the code and does not change the note.

Write that four-step sequence into your charge-capture policy and audit ten charts a quarter against it. Track two metrics: percentage of discharges with documented contact inside two business days, and percentage of reported services where the timing element is fully documented. Those two numbers predict your audit outcome better than anything else you can measure.

Where the PHI Comes From — and Why That Matters

Transitional care management is unusual among billable services because most of the underlying PHI originates outside your walls. Discharge summaries, medication lists, pending lab and imaging results, ADT feeds, and skilled nursing facility notes all arrive from other covered entities.

Requesting and receiving that information for treatment is permitted without patient authorization. The minimum necessary standard does not apply to disclosures for treatment purposes, but it does apply when your staff pull records for billing or care coordination functions that are not treatment. HHS explains the boundary in its minimum necessary guidance. In practice, the risk is not the request — it is what happens after.

Hospital portal credentials are an access-control problem

Your care coordinators almost certainly hold logins to two or three hospital portals and an HIE interface. Ask your privacy officer three questions today:

  • Are those credentials individually assigned, or does the team share one?
  • When the coordinator who left in January was offboarded, did anyone notify the hospital's access administrator?
  • Does anyone review the portal audit logs, or do you assume the hospital does it?

Shared portal credentials are the single most common finding I see in transitional care workflows. They defeat audit logging on both ends and they make an internal snooping investigation nearly impossible to close.

Information blocking cuts both ways

You are usually the requester. Sometimes you are the source — a specialist asks for your notes to support their own transitional care work. Unreasonably delaying that release can implicate the information blocking rules; the ONC/ASTP overview of information blocking and its exceptions is worth reading with your records clerk, not just your attorney.

The Vendor List This Service Line Creates

Stand up a transitional care program and you will typically add three to six vendors that touch PHI:

  • An after-hours or overflow call service making the two-business-day contact when your staff cannot reach the patient before the deadline.
  • A care management or population health platform holding the discharge queue and task list.
  • A patient texting or secure messaging vendor used for the electronic form of interactive contact.
  • An HIE or ADT notification intermediary, if you are not receiving feeds directly.
  • A transcription or scribe service capturing the face-to-face visit.
  • A billing company or outsourced coder reviewing timing elements.

Every one of these is a business associate. Every one needs a signed agreement in place before PHI moves, and the call service is the one practices forget, because it feels like a staffing arrangement rather than a data arrangement. It is a data arrangement. That vendor receives name, discharge date, discharge facility, and often the reason for admission.

If you are onboarding a call service or a messaging vendor this quarter and the contract is stalled because nobody wants to draft the agreement, you can generate a signature-ready Business Associate Agreement through a six-step wizard and export it as PDF or DOCX. One-time purchase, no subscription — useful when the holdup is a document rather than a negotiation. Compare the output against the sample BAA provisions HHS publishes so you know what each clause is doing.

Also check whether the platform vendor is subcontracting. Many care management tools route text messages through a third-party carrier gateway. That subcontractor relationship should be covered downstream, and your agreement should say so.

What a Payer Reviewer and an Investigator Each Ask For

A payer reviewer requesting records for transition of care CPT services will ask for the discharge documentation, the contact attempt log, the medication reconciliation entry, and the visit note — for a named date range. Your release process needs to produce exactly that and nothing more. Pulling the entire longitudinal chart because it is easier is an over-disclosure, and it is avoidable.

A privacy investigation asks different questions: who accessed this record, from where, under whose credentials, and was that access job-related. If your discharge queue lives in a vendor platform, you need to know whether that platform logs individual user access and whether you can export those logs on demand. Ask during procurement. Asking after an incident is too late.

Retain the supporting documentation on the longer of your payer contract requirement or the six-year HIPAA documentation retention period for policies and required records. Keep the contact attempt logs with the chart, not in a separate spreadsheet on a shared drive that nobody backs up.

A 30-Day Timeline to Hand to Staff

  1. Day 0 (discharge): Notification hits the single intake queue. Coordinator timestamps entry, records discharge date and facility.
  2. Day 0–2 business days: Interactive contact attempted and documented with date, time, method, and outcome. Every attempt logged.
  3. Day 0–3: Discharge summary and medication list obtained. Pending results identified and tracked.
  4. By day 7 or 14: Face-to-face visit occurs. Medication reconciliation documented no later than this date.
  5. Day 7–29: Remaining non-face-to-face work — referrals, result follow-up, education, community resource coordination — documented contemporaneously.
  6. At charge capture: Coding verifies timing elements against the practitioner's selected code. Conflicts generate a query, not an edit.

Five Failure Points Worth Auditing This Month

  • Notifications arriving in an inbox nobody monitors on weekends.
  • Contact attempts documented without timestamps.
  • Shared hospital portal credentials across the care coordination team.
  • A call service or texting vendor operating without an executed business associate agreement.
  • Coders adjusting the reported code based on visit timing rather than querying the practitioner.

Fix the last two first. They carry regulatory exposure on top of revenue exposure.

Your Next Step

Pull your vendor inventory and mark every party that touches discharge data — including the answering service and the messaging gateway. For anything missing paperwork, draft the business associate agreement before the next discharge hits the queue. If the broader documentation set behind it is thin, automated risk analysis and policy generation will get your program to a defensible baseline faster than rebuilding templates from scratch.