Recovery Point Objectives: How Much Charting Could You Re-Enter?

A server fails at 3 p.m., and the IT person restores the system from last night's backup. Everything entered since then is gone. Aides who charted during the afternoon, the nurse who documented a fall, the business office clerk who posted payments: all of it has to be redone from memory and scraps of paper.

How much is lost in a moment like this depends on a number most facilities never chose on purpose. It is called the recovery point objective, or RPO, and it is the amount of recent data you are willing to lose, measured in time. It is a question directors of nursing and business office managers can answer better than IT can.

RPO in plain terms

If you back up once a night, your RPO is effectively up to a day, because a failure just before the next backup loses everything since the last one. If a system saves a copy every few minutes, the RPO is a few minutes. Shorter is safer, and it usually costs more or takes more tooling.

The key question is not "how often do we back up," but "how much could the people who use this system realistically re-enter?"

How to ask the right people

Sit down with the person who does the work in each system. Ask them to picture losing the last few hours, and answer concretely:

What would you have to re-enter, and where would you get the information?

Is there a paper source, such as a signed sheet, a note, or a phone message?

Which entries could not be recreated at all, because nobody else saw them?

How long would reconstruction take, and who else would be pulled away from their work?

An aide who charts at the bedside in real time has a very different answer from a billing clerk who posts payments in batches.

Patterns you will likely find

Every facility differs, but common patterns look like this:

Clinical documentation. Entries about falls, changes of condition, medication administration and vital signs are hard to rebuild because they depend on memory. Many facilities want a very short RPO here.

Business office entries. Payments, claims and posted charges can often be reconstructed from bank records, remittance advice and batch reports, so a longer RPO may be tolerable.

Scheduling and payroll. Timekeeping edits can usually be redone if supervisors have their own records, but errors affect paychecks.

Documents and scans. If originals are kept on paper, scans can be redone. If paper is destroyed after scanning, the stakes rise.

Write the answer for each system in hours, such as "no more than an hour" or "a day is acceptable."

Test the number against reality

A target means nothing if your backups do not match it. Ask IT or your vendor:

How often does each system actually get backed up or copied?

Where are the backups stored, and are they separate from the live system?

Have restores been tested, and how much data did the test show would be lost?

For hosted systems, what does the vendor say about frequency and the data you could lose?

If the real interval is longer than your tolerance, you have two choices: tighten the backups or build a paper habit that covers the gap.

Habits that shrink the gap

Even without new technology, you can reduce what a loss would cost:

Keep paper sources, such as signed sheets and shift reports, until the data is safely backed up.

Print key reports, such as the census and medication list, at a set time each day.

Have staff note times on paper during downtime, so entries can be made in order afterward.

Do not discard source documents on the same day they are entered.

Review it regularly

Your answers will change when you add a system, change a workflow or switch vendors. Put the RPO for each system in a table with an owner, and review it each year. Also revisit it after any real outage, when you will have learned what re-entry actually took.

Who decides, and who signs off

The tolerance for lost data is not purely technical. It affects patient care and money, so a director of nursing and an administrator should agree on the clinical answers, while the business office manager signs off on financial ones. Write down the decision, the date and who made it. That way, when IT or a vendor asks what the facility expects, there is a clear answer rather than a guess.

How we can help

UnityCare IT helps administrators and business office managers match backup frequency to the RPO they choose, test restores, and ask hosted vendors how much data could be lost. We provide backups, cloud and EMR support, and a 24/7 after-hours help desk, with signed Business Associate Agreements where protected health information is involved. Setting the tolerance itself is a decision for your clinical and financial leaders.

Related service

Security monitoring, HIPAA safeguards, backups and staff training for healthcare and small businesses.

Related articles

Keep reading

Contact UnityCare Technologies

Call or text: 405-285-3845

New customers: start@unitycareit.com

Existing customers: support@unitycareit.com

Service area: based in Edmond, Oklahoma, serving Oklahoma, Texas and Kansas

Hours: Mon–Fri 8 AM–5 PM CT; 24/7 after-hours support