Live demos: no login required HIPAA-aligned · BAA on every account Austin, TX · Built for skilled nursing operators
(405) 383-5214

Q&A: Common Questions About Tracking PDPM Revenue per Day

Administrators and CFOs often ask how to track PDPM revenue per day. Here are straightforward answers on definitions, trends and what to do with them.

3 min readBy CarePulse Analytics Team

Revenue per patient day is one of the most watched numbers in skilled nursing finance. Under PDPM, it reflects both the characteristics of your residents and how those characteristics are captured and billed. Leaders ask many questions about how to track it sensibly. Here are answers to several of the most common ones.

What exactly is revenue per patient day?

It is revenue for a period divided by the number of resident days in that period. You can calculate it for the whole building, for a payer group such as Medicare Part A, or for a PDPM component. The key is to be consistent about what goes into the numerator and denominator, such as whether you include ancillary revenue, and to document it.

Should we track it overall or by payer?

By payer, at minimum. Medicare Part A, Medicare Advantage, Medicaid, and private pay have different payment structures. A blended figure can move because your mix of payers changed, even if rates for each did not. Tracking by payer, then looking at mix separately, gives a clearer picture.

How often should we look at it?

Weekly for trend awareness and monthly for formal review. Weekly numbers can be noisy, especially in smaller buildings, so use rolling averages. The goal of the weekly look is to notice direction early, not to react to every wiggle.

What drives changes in it?

Several things can move the number.

  • Resident mix: the conditions and needs of those you admit
  • Length of stay: which affects how payment varies over a stay
  • Documentation and assessment timing: how completely and promptly assessments are completed
  • Payer mix: shifts among payer types
  • Census: which affects the denominator and fixed-cost coverage

Separating these drivers is more useful than staring at the total.

How do we know if a change is real or just documentation?

This is a thoughtful question. A change may reflect a true shift in the residents you serve, or it may reflect a change in how assessments are completed, such as new staff or timing. Review both. Compare resident mix by diagnosis group and admission source, and review assessment completion practices. Where documentation is the cause, the aim is accuracy: assessments should reflect each resident's true condition, supported by the clinical record.

Should we set a revenue-per-day target?

Targets can be useful as reference points, but treat them carefully. A target that pushes staff to maximize revenue can create pressure that is inconsistent with accurate documentation and resident-centered care. Many operators prefer to monitor trends and investigate variations instead of chasing a number. If you do use targets, set them with clinical leaders involved.

How does length of stay fit in?

Length of stay shapes revenue because payment patterns change over the course of a stay, and because shorter or longer stays change census flow. Track average length of stay by admission source and diagnosis group so you understand what is driving volume. Connect it to admissions strategy.

What about costs?

Revenue per day is only half the story. Pair it with cost per patient day, particularly nursing and therapy costs, to see whether margin is moving. A rising revenue number paired with rising cost may not improve the bottom line. Looking at both helps leaders see operating health.

Who should review it?

Include finance, the administrator, the DON, the MDS coordinator, therapy, and admissions. Each sees a different piece. A short monthly meeting with these roles helps everyone understand how decisions in their department connect to revenue.

A hypothetical example

Imagine a hypothetical building where revenue per day for Medicare Part A softens for two months. On review, the team finds that admissions from one hospital shifted toward shorter, lower-acuity stays, while an MDS vacancy delayed some assessments. They respond by filling the MDS role and by discussing referral mix with admissions. Looking at the drivers separately led to two distinct actions.

What are common mistakes?

  • Using one blended number. It hides what is moving.
  • Chasing the number. Pressure for revenue can distort priorities.
  • Ignoring cost. Margin matters, not revenue alone.
  • Reviewing too rarely. Monthly closing is late for course correction.
  • Keeping the data in finance. Operational teams can help explain changes.

What is the best first step?

Pick a consistent definition, build a view by payer and component, and review it monthly with a cross-functional group. Add detail as you learn what questions come up.

CarePulse Analytics connects to billing and EHR data to track revenue per day by payer and component, alongside census and cost context. If you would like to see how yours looks, a demo with your building's numbers is a good place to start.