Your physician rounds at two skilled nursing facilities on Tuesday and comes back with 19 encounters scribbled on a folded census printout, three of them on residents who were discharged Monday afternoon. Your biller has to turn that into clean claims, and your privacy officer has to explain why a paper list of 40 resident names spent the night in a car. This guide covers the operational mechanics of nursing home CPT codes — how the visit families are structured, how charge capture actually breaks, how place of service drives payment — and then the records-handling and vendor questions that facility rounding creates for every practice that does it.

Which CPT code families cover nursing facility visits?

Nursing facility evaluation and management services sit in a small, well-defined block of the CPT E/M section. Your coders work from these families:

  • Initial nursing facility care — the 99304–99306 range, three levels.
  • Subsequent nursing facility care — the 99307–99310 range, four levels.
  • Nursing facility discharge day management — 99315 and 99316, split by total discharge-day time.
  • Prolonged service and care management add-ons — reported only when the base service and the payer's rules support them.

Two structural changes from the 2023 CPT revision still trip up practices that rebuilt their fee schedules and never revisited them. The annual nursing facility assessment code was deleted, and the separate domiciliary/rest home family was folded into the home or residence services range. If your charge tickets or superbill templates still list retired codes, they are generating denials every week.

Since 2023, level selection for these services rests on medical decision making or total time on the date of the encounter, not on history and exam bullet counts. History and exam are performed as clinically appropriate; they no longer set the level. CMS maintains current guidance on the revised framework in its Evaluation and Management Services materials, and your coding lead should be re-reading it annually, not once.

How your practice determines and documents code selection

Administrators do not pick codes. Providers do. Your job is to build the documentation pathway that makes the provider's selection defensible, and to make sure nobody in billing is upcoding by pattern or downcoding out of fear.

Give the provider a structured choice at the point of documentation

The cleanest workflows force an explicit answer: was this level selected on medical decision making, or on total time? If time, the note needs the total time on the date of service and enough description of what was done to support it. If MDM, the note needs the elements — problems addressed, data reviewed, risk — visible without a coder guessing.

Build that as a required field in the note template. When it is optional, it disappears in month two.

Run a quarterly distribution review, not a monthly one

Pull each provider's distribution across the subsequent nursing facility range and compare it to the group and to their own prior quarters. You are looking for a flat line — a provider reporting the same level on 90% of encounters is either seeing a very uniform panel or not documenting differentiation. Both are worth a conversation. Document the review; the file note is your evidence of an active compliance program.

Keep coding education separate from productivity coaching

If your coder's feedback arrives in the same meeting as RVU targets, you have built an incentive problem into your audit function. Split them. Different meeting, different person, written summary.

Place of service, consolidated billing, and the two-building problem

Nursing facility claims fail on logistics more often than on clinical content. Three recurring causes:

Place of service mismatch. Skilled nursing facility and nursing facility carry different POS values, and a resident's status can change mid-stay while the building never changes. Your billers need a reliable source for status on the date of service, not a guess based on the facility name. CMS publishes the authoritative place of service code set; print it, post it, and stop relying on institutional memory.

Consolidated billing confusion. Under Medicare, certain services furnished during a covered Part A stay are bundled to the facility rather than billed separately. Physician professional services are treated differently from the bundled ancillaries. When your practice also supplies items or ancillary services, that distinction determines whether you bill the payer or invoice the facility — and that invoice relationship has its own contract implications, discussed below.

Census drift. Residents transfer, expire, or go to the hospital between the rounding list and the claim. Every day of lag between the encounter and charge entry increases the chance of a claim for a resident who was not there.

A workable reconciliation loop

  1. Day of rounds: provider closes notes and submits charges before leaving the building, or within the same business day.
  2. Next morning: billing pulls the facility census for the prior day and matches it line by line against submitted charges.
  3. Exceptions: unmatched encounters and unbilled residents go on a single worklist owned by one named person, not "the billing team."
  4. Weekly: the practice administrator reviews the aging of that worklist. Anything past seven days gets a reason code.

Also confirm which regulatory visit obligations apply to each resident. Federal participation requirements set minimum physician visit intervals for nursing facility residents and place limits on which visits may be delegated to non-physician practitioners. Those are the facility's compliance obligations as much as yours, and the scheduling coordination is a shared operational task. Put it in writing with the facility so nobody assumes the other side is tracking it.

The privacy problem hiding in your rounding list

The billing side of nursing home CPT codes is well documented. The records-handling side rarely is, because rounding workflows evolved organically and nobody wrote them down.

Inventory what actually moves. A typical rounding day involves a printed census with 30–60 resident names and room numbers, photographs of paper MAR pages taken on a personal phone, a face sheet faxed from the facility to your front desk, notes dictated into a mobile app on the drive back, and a text message to the office manager listing three residents who need follow-up. Every one of those is protected health information in motion, and most practices have never mapped them.

Minimum necessary applies to your census printout

A full-building census handed to a provider who is seeing eight residents exceeds what the encounter requires. Ask the facility for a filtered list. Where the facility cannot filter, set a rule: the list stays in a closed folder, never leaves the provider's person, and goes into cross-cut shredding the same day. HHS guidance on the minimum necessary standard is short and worth circulating verbatim to clinical staff.

Photographs, texts, and personal devices

If providers photograph facility documents, those images live in a personal camera roll and often sync to a consumer cloud account. That is a disclosure to a service provider with no agreement in place. Either supply a practice-managed device with a controlled documentation app, or prohibit photography and require transcription into the chart. Half-measures — "delete it when you're done" — fail on the first audit and on the first lost phone.

Fax cover sheets still matter

Facilities fax. A misdirected face sheet is one of the most common small breaches in this workflow. Verify stored fax numbers quarterly, use a cover sheet with a misdirection notice, and log every inbound fax that arrives without a matching resident on your panel.

Which nursing facility relationships need a BAA — and which do not

This is the question that generates the most confusion, so be precise about it.

A nursing facility is itself a covered entity. When your practice and the facility exchange PHI for treatment of a shared resident, that is a permitted covered-entity-to-covered-entity disclosure. No business associate agreement is required for that flow.

The relationship changes when your practice performs a function on behalf of the facility. Medical directorship, utilization review, quality assurance support, staff training built on resident data, or administrative services delivered to the facility can put you in a business associate role — and the facility's counsel will usually ask for an agreement. Read what they send. Facility-drafted BAAs frequently include indemnification and breach-notification timelines far more aggressive than the regulation requires. HHS explains the underlying framework in its business associate guidance.

If you need your own paper rather than signing whatever arrives by email, 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 a facility relationship starts on a Friday and the first data exchange is Monday.

The vendor list a nursing-home-heavy practice forgets to update

Rounding practices accumulate business associates faster than office-only practices, because the work happens outside your walls. Check whether you hold a current, signed agreement with each of these:

  • The billing company or coding contractor touching nursing facility claims
  • Any mobile charge-capture or dictation application on provider devices
  • Transcription services, including overnight offshore vendors
  • Your clearinghouse and any denial-management contractor
  • Answering services taking after-hours calls from facility nursing staff
  • Document shredding and secure-disposal vendors
  • Cloud storage or file transfer used to move census files
  • Any scribe supplied through a staffing agency rather than employed directly

Verify the signature dates. An agreement executed before your last EHR migration may name a system you no longer run. Re-paper it.

Records requests when the chart lives in two buildings

A resident's family requests records. Your practice holds visit notes and claims data; the facility holds the MAR, nursing notes, and care plan. You owe the requester your designated record set, and the individual right of access clock — generally 30 days, with one 30-day extension available — runs against you, not against the facility.

Two operational rules keep this clean. First, do not forward requests to the facility and call it handled; respond to what you hold and tell the requester in writing which records they must obtain from the facility. Second, confirm personal representative status before releasing anything. Nursing facility requests arrive disproportionately from adult children, powers of attorney, and guardians, and the documentation supporting that authority varies by state. Your front desk needs a written checklist, not judgment calls at the counter. HHS maintains detailed right of access guidance that covers timelines and permissible fees.

A 60-day cleanup for practices already rounding

Days 1–15. Pull your charge tickets and note templates. Remove retired codes. Confirm the MDM-or-time field is required. Verify POS mapping for every facility you serve.

Days 16–30. Map the PHI flow for one rounding day, end to end. Name every device, paper artifact, fax, and app. Circle the ones with no agreement behind them.

Days 31–45. Close the agreement gaps. Where you sit in a business associate role for a facility, get that on paper too. If your broader documentation set — risk analysis, policies, workforce training records — has not been refreshed since the rounding program started, automating the risk analysis and policy set is faster than rebuilding it in a word processor.

Days 46–60. Run the census reconciliation loop daily and measure the exception rate. Train the front desk on the records-request checklist. Schedule the first quarterly coding distribution review and put it on the calendar for the next four quarters.

Handled well, nursing home cpt codes are just a workflow: a defensible level selection, a matched census, a clean claim. Handled poorly, they are a denial pattern and a paper trail of PHI you cannot account for. The difference is whether someone owns the loop.

If your facility relationships are outrunning your paperwork, start with the agreements — build a signature-ready BAA before the next data exchange, then work backward through the vendor list.