Do you need a DSCSA-specific compliance service if you use RxRescue?

It depends on whether the pharmacy needs full DSCSA T3/EPCIS document handling and trading-partner license monitoring. Wholesaler portals already store T3 transaction documents for the required 6-year window, and a dedicated DSCSA service adds automated trading-partner license verification. RxRescue handles the dispenser-side obligations — package-level capture, audit-pack export, recall match history, and FEFO inventory tracking — which is the gap pharmacy management systems don't fill.

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:

Which specific bottles are on the shelf right now, with which expiration dates.
Which lot numbers are present, at the bottle level, for DSCSA serial tracking.
Whether a recalled lot number matches anything in your current physical stock.
Which bottles are expiring in the next 30, 60, or 90 days and should be pulled for wholesaler credit.
What the physical count actually is at any given moment — not the theoretical perpetual count, but the real count after short shipments, breakage, misplaced stock, and partial bottles.

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.

Your wholesaler's portal. It holds the transaction records that arrive with each order, for the retention window. It's a passive archive: it stores the paperwork, but it doesn't tell you what's on your shelf or which lot is expiring.
A DSCSA compliance service, if your pharmacy pays for one. A third party manages DSCSA paperwork in the background. Hands-off by design — which also means it runs out of sight, and you tend to learn whether it's current the week an inspector asks.

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:

Scan-in at receiving. Every bottle is scanned as it arrives, capturing GTIN, lot, serial number, and expiration date from the GS1 DataMatrix barcode. Those four fields are stored as distinct, queryable values — not concatenated text, not a PDF invoice to search later.
FEFO expiration visibility. The dashboard sorts active inventory by expiration date ascending — the bottles expiring soonest are at the top, color-coded by urgency. You see what needs action without walking every shelf.
Daily FDA recall matching. Every morning the app checks the openFDA enforcement feed against your actual scanned inventory. If a recalled lot number matches something on your shelf, it surfaces on the dashboard with a timestamp — proof the check happened.
One-tap DSCSA audit pack. Six CSVs with a shared timestamp: FEFO inventory snapshot, full audit log, bottle-level transaction records (GTIN, lot, serial, expiry), FDA recall match history, return manifest, and quarantine log. An inspector asks for records; you tap one button.
Receiving reconciliation. Import your supplier's shipment manifest (CSV, Excel, or EPCIS XML/JSON) and reconcile it against physically scanned bottles at the point of receipt. Short shipments, over-shipments, unexpected items, and suspect product surface by category; each discrepancy requires a documented resolution before the receiving record is finalized and included in the DSCSA audit pack.
Wholesaler return workflow. Mark bottles pulled, generate the return manifest CSV in the format Cardinal, McKesson, and Cencora (formerly AmerisourceBergen) accept, and send it before the credit window closes.

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:

Your dispensing system continues to handle every fill, every claim, every patient interaction. Nothing about that workflow changes.
RxRescue runs on a Windows tablet or Android phone at the receiving station and on the shelf. Staff scan bottles in as they arrive; the dashboard updates immediately.
For independent pharmacies already scanning at receiving with their PMS, RxRescue can also ingest a periodic inventory export via CSV — so you're not scanning twice. Your dispensing scans stay in your current system; RxRescue gets a snapshot and runs the expiration, recall, and audit layer on top.

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:

Independent pharmacies that already have a PMS and are looking specifically for the DSCSA compliance gap, expiration management, and FDA recall monitoring that their current system doesn't cover. See the independent pharmacy walkthrough →
Correctional and institutional pharmacies whose EHR or contractor-mandated system handles clinical records but leaves physical inventory management to spreadsheets or manual logs. See the correctional pharmacy walkthrough →
Multi-site healthcare contractors rolling out a focused, auditable inventory layer across facilities without replacing the clinical system at each site. Ask about a managed pilot →

Start a 30-day free trial →

Frequently asked questions

Does RxRescue replace my pharmacy management system?

No. RxRescue runs alongside your pharmacy management system. The PMS handles prescription entry, billing, patient records, and dispensing. RxRescue handles the physical-shelf layer the PMS doesn't — expiration tracking by bottle, scan-verified physical counts, daily FDA recall matching against your inventory, DSCSA package-level capture (GTIN, lot, serial, expiration), and one-tap audit pack export. The two systems don't share data; they cover different layers of the pharmacy's operation.

Do I need to integrate RxRescue with my PMS?

No integration is required to use RxRescue. Most pharmacies start with the CSV importer — it ingests the standard inventory exports from Liberty, Rx30, ComputerRx, and similar systems to seed RxRescue's starting inventory, then each bottle is scanned once at receiving to capture the serialized GS1 barcode (lot, serial, expiration). After that, the two systems run in parallel.

Do you need a separate DSCSA T3/EPCIS compliance service if you use RxRescue?

It depends on whether the pharmacy needs full DSCSA T3/EPCIS document handling and trading-partner license monitoring. Your wholesaler's portal (Cardinal, McKesson, Cencora) already stores T3 transaction documents for the required 6-year window, and a dedicated DSCSA compliance service adds automated trading-partner license verification on top of that. RxRescue handles the dispenser-side obligations — package-level capture, audit-pack export, recall match history, and FEFO inventory tracking — which is the gap pharmacy management systems don't fill. For a head-to-head look at how RxRescue compares to the upstream DSCSA platforms, see DSCSA software alternatives.

Does RxRescue collect PHI?

No. RxRescue is designed not to collect PHI. The import path actively rejects patient-shaped columns. The data model stores only stock data: GTIN, lot, serial, expiration, drug name, quantity, and operational fields like timestamps and operator name. Free-text fields are screened at capture, restore, and over-the-wire to reject patient-identifying content. This intentional boundary is designed to keep RxRescue outside HIPAA scope (your compliance officer makes the final determination) and simplifies vendor security review.

Will using RxRescue change anything about how my pharmacy management system works?

No. The PMS continues to operate exactly as before — same dispensing workflow, same billing flow, same staff routines. RxRescue is additive: staff scan bottles at receiving and during cycle audits, but the PMS-side workflow is unchanged. Most pharmacies are productive with RxRescue within a single shift.

Published May 17, 2026.