Recovery Time Objectives Explained Through a Medication Pass

Picture the 8 a.m. medication pass on a Tuesday. The EHR is down, the nurse cannot see the medication administration record, and thirty residents are waiting for pills, insulin and eye drops. Each minute that passes matters a little more, because some medications are time-sensitive and some are not.

That moment is the easiest way to understand a recovery time objective, or RTO: the longest a system can be unavailable before the harm becomes unacceptable. It is a decision about people, not computers, and directors of nursing and administrators are the ones who can make it.

What an RTO is, and what it is not

An RTO is a target, not a promise. If you decide the medication record must be back within two hours, that tells your IT team and vendors what to design toward, and tells your staff when to switch to paper and when to call for help. It is different from how much data you could lose, which is a separate decision called the recovery point objective.

Be honest about the number. A shorter RTO usually costs more, since it requires redundancy, faster support or backup systems. A longer one is cheaper but means staff operate on downtime procedures for longer.

Walk through the missed medication pass

Use the scenario to ask questions of the clinical team. Take the EHR going down at the start of the morning pass and ask:

In the first 30 minutes, can nurses give medications safely from a printed list? Which ones cannot wait, such as insulin, seizure medication or time-critical antibiotics?

At one hour, how many residents are affected, and what is the worst realistic outcome for each group?

At two to four hours, what happens to the next pass, to documentation, and to the pharmacy's ability to verify orders?

By the end of the shift, what documentation must be reconstructed, and by whom?

Your clinicians already know how to answer. Let them. The answers show where the pain begins, which is where your RTO should fall.

Turn the answers into a number

Often the discussion produces a range like this: a few minutes of disruption is fine with paper lists, a couple of hours becomes risky, and half a day is serious. Pick the point where operations stop being safe with downtime procedures, and set the RTO somewhat before it. Then do the same for each system.

A rough order of urgency often looks like this, though your facility may differ:

The medication record, orders and the nurse call system

Phones and internet for emergencies and pharmacy contact

Care plans, census and admissions information

Dietary, therapy and activities systems

Billing, payroll and accounting

Some of these are more tolerant of delay. Payroll can wait longer than the medication record, though not forever.

Check what your vendors actually deliver

An RTO means little if your vendor cannot meet it. Ask each one how fast it can restore service after a failure, whether support is available overnight, and what the contract says. If the vendor's real recovery is slower than your target, you have a gap to fill with paper procedures, a backup plan or a different product.

Do not assume a hosted system recovers instantly. Ask.

Prepare the downtime procedure

The RTO tells you how long you will live on the fallback, so the fallback must be ready:

Printed medication lists, updated on a schedule

Paper administration forms

A phone tree with the pharmacy, physician and IT support

A named person who decides when to start and stop downtime procedures

A plan for entering paper data later

Practice it once or twice a year, including on a night shift.

Write it down and review it

Record the RTO for each system in one table, with the owner's name and the date. Review it once a year, and whenever you adopt a new system or change vendors.

Include the weekend and night shifts

The 8 a.m. pass is a convenient example, but outages do not follow a schedule. Ask the same questions about the 2 a.m. pass and the Sunday afternoon, when fewer staff are present and your vendor's support may be slower. If your plan only works on a weekday with the administrator in the building, it is not yet a plan. Test it with the people who actually work those shifts.

How we can help

UnityCare IT helps administrators and directors of nursing turn these decisions into technical plans, including backups, failover internet, vendor questions and tested restores. Our help desk offers 24/7 after-hours support, and we offer EMR and EHR support and backups with signed Business Associate Agreements. The clinical call on how long is too long belongs to your team.

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