Skilled nursing product in development

Ease currently serves behavioral health organizations and is planning a skilled nursing product. Discuss planned scope and availability.

CFO and executive sponsor

Switch SNF EHRs Now or Wait? A Timing Model for the CFO

Compare switching now with a deliberate six-month delay, including recurring costs, evidence-gathering time, implementation capacity and delayed benefits.

Quick answer

Compare an immediate EHR transition and a delayed transition over the same calendar horizon. Include costs that change with timing, benefits that start only after demonstrated adoption, overlap expenses and any new information the delay can produce. Keep sunk costs out of the forward decision and distinguish a cash forecast from a valuation of staff capacity. Waiting is useful only when its purpose and decision date are explicit.

Compare dates on one calendar

A five-year ownership model answers what a platform may cost. It does not automatically answer whether to start a replacement this quarter. Timing changes legacy payments, implementation capacity, overlapping systems and the first month in which an improvement can be used.

The GAO Cost Estimating and Assessment Guide emphasizes explicit assumptions and sensitivity analysis. This article applies those principles to a fictional nursing-facility decision. All dollar amounts are invented for arithmetic; they are not SNF software benchmarks or an estimate of Ease pricing.

Use a fixed evaluation window. Comparing twelve months of one system with eighteen months of another can make a delay look cheaper simply because fewer months were counted. State whether the model is cash-based, discounted, or includes an assigned value for staff capacity. The example below is an undiscounted, incremental cash comparison over eighteen months.

Build two schedules before assigning savings

Assume implementation takes three months after its start. Option A begins in month one and operates the replacement in months four through eighteen. Option B begins in month seven and operates it in months ten through eighteen. Both retain the current system during implementation. No additional archival or cancellation costs are assumed in this simplified example; actual proposals must supply them.

Invented input Switch now Start six months later
Implementation payment $60,000 $60,000
Current system at $5,000/month 3 months = $15,000 9 months = $45,000
Replacement at $6,000/month after implementation 15 months = $90,000 9 months = $54,000
Additional internal coverage $12,000 $4,000
Total cash outflow $177,000 $163,000

Waiting reduces modeled outflow by $14,000. That result includes an assumed $8,000 reduction in replacement coverage because a later period has better staffing availability. If that coverage difference cannot be supported, remove it. Do not hide the assumption inside an unexplained implementation estimate.

Now suppose a separately validated operational change avoids $4,000 of actual monthly expense, beginning only after go-live. Option A avoids $60,000 over fifteen operating months; Option B avoids $36,000 over nine. Net modeled outflow becomes $117,000 versus $127,000. Under those assumptions, starting now is better by $10,000.

Find the assumption that reverses the decision

The earlier start buys six additional operating months at an extra $14,000 of modeled outflow. Its simple break-even benefit is $14,000 divided by six, or approximately $2,333 per additional month. This is a decision boundary within this example, not a target a sales team should promise.

If the benefit is only $1,500 per month, earlier operation produces $9,000 rather than $24,000 of additional benefit. Waiting is then better by $5,000. If the improvement merely releases fragmented staff minutes without reducing expenditure, show that capacity separately instead of inserting it into the cash-benefit row.

Change assumptions one at a time before building combined scenarios. Useful questions include whether implementation slips, whether subscription begins at signing rather than go-live, and whether a legacy renewal creates an additional contractual payment. A six-month delay can cross a renewal deadline; a three-month project can also become six months. Neither outcome should be silently treated as impossible.

Price the information a delay can produce

A deliberate delay can fund useful learning: a verified interface connection, a representative workflow trial, confirmed data exports or a more complete statement of work. Specify the evidence expected and its owner. “Wait until things are clearer” provides no mechanism for making the next decision better.

Suppose the facility spends $3,000 during the waiting period on a defined evaluation. Add that cost to Option B. Record which uncertainty it could resolve and how the result affects the go/no-go decision. Do not claim the evaluation creates a guaranteed dollar return. It may instead reveal that the proposed transition should never occur.

The GAO Schedule Assessment Guide supports connecting activities and dependencies rather than treating dates as isolated promises. In a facility's schedule, an interface approval or qualified reviewer's availability may determine when a task can finish. Put those dependencies beside the financial assumptions.

Give the board a decision, a boundary and a revisit date

Present the two calendar schedules, the incremental cash bridge and the assumption that changes the result. Show unresolved safety or operational requirements separately; a favorable cash result cannot waive them. Record who can approve the transition and which evidence remains necessary.

For a group, repeat the timing analysis by rollout wave rather than pretending every site receives benefits on the first launch date. For a single facility, protect the availability of the people who must validate records while continuing daily operations.

Use the ownership-cost guide for the broader long-term budget. This timing model earns its place when it makes a near-term choice transparent: start, defer for a defined reason, or stop the replacement proposal.

Questions & answers

Is every month spent on the current system a lost savings opportunity?

Only benefits that are achievable, incremental and available in that month belong in the comparison. A proposed benefit that depends on unbuilt functionality or unfinished integration is not an established monthly loss.

Should implementation spending already paid affect the switch decision?

Historical spending is relevant background but is normally sunk for a forward choice. Future cancellation payments, remaining obligations and reusable work can differ between options and should be included explicitly.

Primary sources

Use the cited source and its applicable version when making a facility-specific decision. These guides explain operational evaluation methods; they are not individualized clinical, coding, or legal advice.