Software for specialty pharmacies

A specialty pharmacy dispensing manufactured products is a dispenser under the Drug Supply Chain Security Act, licensed in its home state and as a nonresident pharmacy in each state it ships to, and — to be in payer and manufacturer networks — accredited by URAC, ACHC or both. Accreditation standards ask for documented processes and evidence: a dispensing process with pharmacist verification, a cold-chain shipping procedure with validation, a recall procedure, a system for tracking shipments and patient outcomes, and records that show the procedures are followed. Where a specialty pharmacy also compounds — sterile or nonsterile — USP <795>, <797> and <800> apply and the 503A rules govern the compounded portion.

Every order follows one lifecycle — Received, Eligibility, Clinical Review, In Production or line fill, Packed, Shipped, Delivered, with On Hold and Cancelled reachable from the working states — and the allowed transitions are a table in Postgres guarded by a trigger. Two interlocks are checked by the database itself: an order cannot be Packed without a finished lot, and cannot be Shipped without a recorded pack verification. An order tied to a prescription cannot be Packed or Shipped unless that prescription is Filled. Status changes go through functions that check the caller's permission, and each writes a history row with actor and time. That history is what turns turnaround time and hold reasons into reports rather than estimates.

Before verification the pharmacist sees a prospective DUR screen built only from data the pharmacy holds: duplicate therapy against the patient's active prescriptions, therapeutic duplication within the GLP-1 class, a controlled-substance-with-refills alert, a quantity-versus-days-supply check, a GLP-1 counselling reminder, and an explicit note that no allergies are on file so they are confirmed at counselling. Verification is recorded as a signed approval.

Cold-chain failures are usually process failures: a refrigerated order packed at an ambient station, or shipped on a slow service into a heatwave. In Pharmacy Flow packout is a field on the order — standard, cold-chain (insulated with gel packs), frozen (dry ice) or hazardous (segregated) — set from the product's storage requirement, and the cold-chain flag is carried on the parcel through to the carton and the carrier record. Materials with refrigerated or frozen storage conditions are routed by the putaway rule to cold or frozen locations on receipt, with the reason recorded. Returns carry "cold-chain breach" as a reason code, and a temperature excursion is a deviation category with its own investigation and CAPA path. Validation of packout configurations for your lanes and seasons is your procedure; the cold-chain guide walks it.

Subscriptions generate orders on a 28-, 30- or 90-day cadence, and each generated order runs the same eligibility, licence and refill checks as a new one. A refill that would breach a Schedule II prohibition or a Schedule III–V five-refill, six-month limit is refused with the reason; a controlled material without a parseable schedule holds the refill for manual verification. The partner portal shows a referring practice its patients' subscriptions and next fills. Adherence programmes and outreach live in your clinical team's hands; the platform's contribution is that the fill goes out on the day and the record shows it did.

Referring practices, infusion centres and payer programmes each get a partner-portal login: submit an order against a patient reference and prescriber, see order status and carrier scans, manage subscriptions, and view and print invoices. Integrations use the ordering API, which authenticates on an API key, is idempotent on a client order id so retries never duplicate, and checks the ship-to state licence before accepting the order. Orders into states where the pharmacy holds no licence, or where the licence is expired, are held at eligibility with the reason shown. The partners page and the ordering API page cover both.

Each dispensed unit carries a serial on a GS1 DataMatrix label with GTIN, lot and serial; parcels aggregate into cartons and pallets with an SSCC. Each fill, pack, verify and ship step writes an EPCIS-style event, so a unit's journey is a query on its serial. Carrier scans arrive by webhook and are stored one row per carrier event, de-duplicated on the carrier's event id, so a retry never fabricates a second delivery; delivery cascades to the order but honours a QA hold. A recall is initiated from a lot's trace: the platform lists every shipment and unit of the lot, creates a recall record with a 21 CFR 7 classification, marks each unit Recalled and tracks per-unit disposition until effectiveness is reconciled. A recalled unit fails the fill interlock if scanned again. The serialization and DSCSA explainer covers the standards; security and compliance covers the audit trail behind the events.

Manufactured product is received against a purchase order into quarantine with the supplier lot number, expiry, quantity, temperature check and certificate or transaction document attached, and released to Available only after QA release; the putaway rule assigns cold, frozen, vault, hazmat or general locations from the material's requirements. Lots follow a fixed lifecycle with history, and inventory is listed by expiry band. Electronic exchange of DSCSA transaction data with trading partners — EPCIS messaging with wholesalers — is on the roadmap rather than in the product today; if that is a current requirement for you, say so on the demo call and we will tell you the plan plainly. The inventory module page has the receiving detail; the supplier directory and RFQ marketplace cover sourcing.

Finance and analytics — receivables, product and geographic analytics, growth and retention — are part of the same platform; see the platform overview and pricing. Related reading: GLP-1 pharmacy operations and the GLP-1 fulfilment page.