Positioning

Published May 17, 2026 · By the RxRescue Team

RxRescue alongside your pharmacy system — not instead of it.

The most common question we hear from pharmacists evaluating RxRescue is some version of: "We already have Liberty. Why do we need another system?" It's a fair question, and the answer is straightforward once you understand what pharmacy management systems actually track — and what they don't.

What your pharmacy management system does

Liberty, Rx30, ComputerRx, McKesson Pharmaserv, and similar systems are built around the dispensing workflow: patient records, prescriptions, fills, claims adjudication, and billing. They are very good at that job. Every fill is logged, every claim is submitted, every patient's medication history is tracked at the prescription level.

What they are not designed to do is track what's physically on your shelf. They know what you've dispensed. They do not know:

That gap — between what the dispensing system knows and what's actually on the shelf — is the problem RxRescue is built to fill.

The two systems in between

Most pharmacies also lean on two other systems for compliance, and it's worth being clear about what each one does — because the same gap runs through both.

Both are useful. Neither was built to see the physical shelf — so the picture is four layers, not two: your dispensing system, your wholesaler's portal, a compliance service if you use one, and the physical inventory layer RxRescue provides on top.

What RxRescue adds

RxRescue is a focused physical inventory layer. It handles the shelf side of the equation that dispensing systems leave unaddressed:

How the two systems work together

RxRescue does not replace your dispensing system and does not require integration with it. The two operate independently on the same inventory:

The result is two systems with distinct jobs: your PMS handles the patient-facing dispensing workflow; RxRescue handles the physical shelf. Neither is redundant.

The No-PHI boundary

Because RxRescue is a medication inventory tool — not a dispensing or patient-care system — it is designed not to collect patient health information. The import path explicitly rejects CSV files with patient-shaped column names (DOB, MRN, prescriber, patient name). The audit log records device and operator identifiers, not patient identifiers. Most facilities conclude that no Business Associate Agreement is needed — but whether a specific deployment falls outside HIPAA-covered scope is a determination your privacy officer makes. See the security and compliance posture page for the full breakdown.

Who this matters most for

The "alongside, not instead of" positioning matters most for three groups:

Start a 30-day free trial →

Related

Published May 17, 2026.