Zero-Drift OOS Management

A Scalable Solution for Pharmacy Operations

Executive Summary

The Problem in Plain Terms

Every day, pharmacy staff across the organization perform a task that should not exist: manually transcribing data that already lives in our systems.

When a medication fails to arrive from a supplier, an invoice is generated. That invoice contains everything needed to resolve the exception—NDC numbers, quantities, expected delivery dates. Meanwhile, the Out-of-Stock queue in Intercom Plus contains the same information from the pharmacy's perspective. These two data sets should talk to each other. They do not. Instead, a human being prints a PDF, logs into a legacy system, and manually cross-references line by line, clearing exceptions one at a time, waiting for each claim to adjudicate before moving to the next.

This is not a minor inefficiency. It is a structural flaw that scales across every location, every day, consuming hours of skilled labor on pure data transcription—time that could be spent with patients.

Why This Matters Beyond Efficiency

The obvious cost is time. The less obvious cost is data integrity.

The current system architecture lacks safeguards against inventory drift. When exceptions are processed through fragmented workflows—jumping between Intercom Plus, RXI, supplier websites, and email—there are multiple points where inventory counts can become disconnected from reality. On-hand quantities become unreliable. Automatic reordering algorithms, which depend on accurate counts, begin to fail. The system loses its ability to self-correct, and staff must compensate with additional manual checks and workarounds.

This creates a compounding problem: the more the system drifts, the more manual intervention it requires, which introduces more opportunities for drift.

The Solution Concept

The fix is not a wholesale replacement of existing systems. It is an integration layer—a bridge that allows the data already flowing through our operations to connect where it currently cannot.

Core Automation: Invoice data is parsed automatically and cross-referenced against the OOS queue. Matches are validated and cleared without manual transcription. Only true exceptions—items requiring human judgment—surface for staff review.

Interface Modernization: The OOS queue becomes sortable, filterable, and actionable. Staff can select multiple items, view invoices alongside the queue, and process exceptions in batches rather than one painful click at a time.

System Integration: Intercom Plus, RXI, and supplier availability data connect through a unified layer. Staff no longer context-switch between five disconnected systems to complete a single task.

This approach is modular. Each component delivers value independently, but together they transform a fragmented workflow into a coherent operation.

The Opportunity

This is not a complaint about how things are. It is a recognition that we have the data, the technology exists, and the path forward is clear. The gap between our current state and a dramatically better one is not a moonshot—it is an engineering problem with known solutions.

Pharmacy staff are capable of far more than data transcription. The systems they depend on should reflect that.

The Ask

I am requesting a conversation.

This document represents significant thought about a real operational problem, grounded in daily experience with the workflows in question. I am not asking for immediate approval or resources. I am asking for the opportunity to discuss this further—to pressure-test the ideas, identify obstacles I may not see from my vantage point, and explore whether there is a path to pilot this approach.

If this resonates, I would welcome thirty minutes to walk through the details and answer questions.

Technical Proposal: Detailed Analysis and Architecture

1.1 The OOS Exception Process — Step by Step

The following represents the standard workflow for processing Out-of-Stock exceptions when a supplier invoice arrives. This occurs multiple times daily at each pharmacy location.

1.2 System Fragmentation Visualization

The current workflow requires navigation across five disconnected systems:

┌─────────────────────────────────────────────────────────────────────────────┐
│                           CURRENT STATE                                      │
│                                                                              │
│    ┌──────────┐     ┌──────────────┐     ┌─────────┐     ┌──────────────┐   │
│    │  Email   │     │ Intercom Plus│     │   RXI   │     │   Supplier   │   │
│    │  System  │     │   (Legacy)   │     │         │     │   Portals    │   │
│    └────┬─────┘     └──────┬───────┘     └────┬────┘     └──────┬───────┘   │
│         │                  │                  │                  │          │
│         │                  │                  │                  │          │
│         ▼                  ▼                  ▼                  ▼          │
│    ┌─────────────────────────────────────────────────────────────────────┐  │
│    │                                                                     │  │
│    │                      HUMAN "MIDDLEWARE"                             │  │
│    │                                                                     │  │
│    │   • Prints PDF invoices                                             │  │
│    │   • Manually transcribes data between systems                       │  │
│    │   • Maintains context across disconnected interfaces                │  │
│    │   • Compensates for lack of integration                             │  │
│    │                                                                     │  │
│    └─────────────────────────────────────────────────────────────────────┘  │
│                                                                              │
│                    ┌───────────────┐                                         │
│                    │  RXassembly   │                                         │
│                    │  (Monitors)   │                                         │
│                    │               │                                         │
│                    │  Displays OOS │                                         │
│                    │  data but     │                                         │
│                    │  READ-ONLY    │                                         │
│                    └───────────────┘                                         │
│                                                                              │
└─────────────────────────────────────────────────────────────────────────────┘

Critical Observation: The filling station monitors (RXassembly) represent newer infrastructure that displays OOS queue information—but allows zero user input. Staff can see the exceptions but cannot act on them, forcing a return to the main terminal and the Intercom Plus workflow. This is a missed opportunity: the hardware and data connection exist, but the interface does not permit interaction.

Expected Outcomes

Time Reclamation: The current workflow requires skilled staff to perform data transcription that could be automated. By eliminating manual cross-referencing and enabling batch operations, the time required for OOS exception processing is dramatically reduced. This time returns to the available capacity pool for patient-facing activities.

Error Reduction: Manual transcription between systems introduces error opportunities at each step. Automated matching eliminates transcription errors entirely for matched items. Confidence scoring catches ambiguous cases before they result in incorrect actions.

Data Integrity: Unified data flow between systems reduces drift between inventory counts and reality. Automated reconciliation checks catch discrepancies earlier. Audit trails enable root cause analysis when issues occur.

Patient Outcomes

Faster Resolution: Exceptions processed more quickly mean medications arrive in patient hands sooner. Automated processing reduces the time from invoice receipt to prescription fill.

Proactive Communication: With supplier availability and shortage data integrated, staff can proactively contact patients about delays or alternatives rather than waiting for patients to inquire.

Adherence Support: Time reclaimed from administrative tasks can be directed toward medication therapy management, adherence counseling, and other interventions that directly impact patient health.

Closing Perspective

This proposal addresses a specific operational problem—OOS exception management—but it represents something larger: the recognition that our systems contain untapped potential.

The data already exists. The technology to connect it is not exotic. The people doing the work understand the friction better than anyone. What has been missing is the architectural bridge that transforms fragmented workflows into coherent operations.

This is not about replacing human judgment with automation. It is about reserving human judgment for decisions that require it, and automating the mechanical transcription that currently consumes skilled capacity.

The path forward is clear. The question is whether we walk it.