PDX Pharmacy API
PDX is a pharmacy technology company whose Enterprise Pharmacy System (EPS) powers prescription filling, central patient records, clinical services, inventory, and third-party billing for nearly 10,000 independent, chain, mail-order, specialty, central-fill, and long-term-care pharmacies. An unofficial API lets you programmatically pull prescriptions, patients, prescribers, inventory, and claim data—and push updates like new fills, refills, and clinical service records back into PDX.
What is PDX?
PDX is a Fort Worth-based healthcare technology company that has provided pharmacy management software and services for over 30 years to nearly 10,000 pharmacies nationwide. Its flagship Enterprise Pharmacy System (EPS) is used across independents, regional and national chains, mail-order facilities, central-fill locations, specialty pharmacies, and pharmacies serving outpatient and long-term-care settings—handling prescription filling, a real-time central patient record, clinical services, inventory, and third-party reconciliation. PDX was acquired by Change Healthcare in 2020.
Core product areas include:
- Enterprise Pharmacy System (EPS) — cloud prescription-filling platform with real-time central patient record, central fill, and LTC support
- Care Rx® — clinical services platform for immunization reporting, medication reconciliation, billing, specialty, MTM, CRM, and lab testing
- Absolute AR® Services — third-party claims submission and reconciliation with claims chasing and account management
- Turn Rx® — predictive-analytics-driven automated inventory management, integrated with EPS
- PDX Manufacturer Services (PDX-MS™) — manufacturer-facing data and program services
Common data entities:
- Prescriptions, Fills, Refills, Central-Fill Orders
- Patients, Central Patient Records, Allergies, Medication History
- Prescribers, Pharmacies, Stores, Locations
- Drugs, NDCs, Inventory, Reorder Points (Turn Rx)
- Third-Party Claims, Adjudications, AR Records (Absolute AR)
- Clinical Services, Immunizations, MTM Cases (Care Rx)
The PDX Integration Challenge
Pharmacies run mission-critical dispensing workflows on PDX every day, but turning a workstation- and portal-driven system into API-driven automation is non-trivial:
- No public developer API: EPS is delivered as an enterprise pharmacy platform, so most data access runs through authenticated application surfaces rather than open documented endpoints
- Partnership and vendor gates: Integrations to EPS and Care Rx often require certification or partnership agreements before connectivity is granted
- Multi-product spread: EPS, Care Rx, Absolute AR, and Turn Rx each have their own object models, IDs, and lifecycle states to reconcile
- Authentication complexity: Pharmacy environments commonly enforce per-store credentials and MFA, complicating headless automation
- Regulated data handling: PHI, controlled-substance dispensing (EPCS), and third-party claim records require strict audit trails and access control
- Chain and central-fill topology: National chains, mail-order, and central-fill sites span many stores, so integrations must handle location-scoped data consistently
How Supergood Creates PDX APIs
Supergood reverse-engineers authenticated PDX application flows across EPS, Care Rx, Absolute AR, and Turn Rx to deliver a resilient API layer for your pharmacy or chain—without waiting on a public developer program.
- Handles username/password and MFA (SMS, email, TOTP) securely with per-store credential scoping
- Maintains session continuity with automated refresh and change detection
- Normalizes responses across prescriptions, patients, prescribers, inventory, and claims so you integrate once and rely on consistent objects
- Preserves PHI handling, EPCS audit trails, and location scoping for compliant access
Use PDX with AI agents: PDX MCP Server →
Getting Started
- Schedule Integration Assessment
Book a 30-minute session to confirm your PDX products, store topology, and authentication model.
- Supergood Generates and Validates Your API
We deliver a production-ready PDX adapter tailored to your EPS configuration and entitlements.
- Deploy with Monitoring
Go live with continuous monitoring and automatic adjustments as PDX evolves.
Potential API Endpoints
Authentication
/authenticateAuthenticate to a PDX EPS environment using username/password or MFA and obtain a session token for downstream calls.
Patient Operations
/patientsRetrieve patient central records with filters for name, date of birth, store, and identifier.
Prescriptions
/prescriptionsList prescriptions, fills, and refill status across stores with date, drug, and patient filters.
Prescriptions
/create_fillSubmit a new prescription fill or refill request against an existing patient and prescriber record.
Inventory
/inventoryPull drug, NDC, on-hand quantity, and reorder data from Turn Rx inventory management.
Billing
/claimsRetrieve third-party claim, adjudication, and AR records managed through Absolute AR services.
Use Cases
Sync prescription and patient data into your warehouse
- Pull prescriptions, fills, and refill status from EPS across all stores into a single warehouse - Reconcile patient central records, allergies, and medication history for a unified patient view - Stream dispensing events to downstream analytics, adherence, and reporting tools
Automate clinical services and immunization reporting
- Pull immunization, MTM, and lab-testing records from Care Rx into clinical and reporting systems - Push new clinical service and medication-reconciliation records back into PDX - Route eligible patients into outreach and adherence campaigns without manual portal work
Reconcile third-party claims and accounts receivable
- Sync third-party claims, adjudications, and AR records from Absolute AR into finance systems - Surface rejected or chased claims to reconciliation workflows - Match remittances against expected payments across stores
Drive inventory and replenishment automation
- Pull on-hand quantities, reorder points, and NDC data from Turn Rx - Trigger replenishment and ordering workflows when predicted demand crosses thresholds - Reconcile inventory across central-fill and store locations
Technical Requirements
Authentication
Username/password and MFA (SMS, email, TOTP) handled in a managed session with per-store credential scoping
Connectivity
Authenticated PDX application flows across EPS, Care Rx, Absolute AR, and Turn Rx
Response format
Normalized JSON across prescription, patient, prescriber, inventory, and claim objects
Rate limits
Adaptive throttling tuned to your environment to avoid PDX-side limits
Session management
Automatic session refresh, MFA replay handling, and credential rotation
Data freshness
Near real-time pulls for prescriptions, patients, and claims with optional scheduled batch syncs
Security
Encrypted credential vault, scoped access tokens, PHI and EPCS-aware controls, and audit logging
Webhooks
Event-style callbacks for new fills, refills, claim status, and inventory changes
Latency
Sub-second reads on cached entities; multi-second writes when posting fills and clinical records
Throughput
Horizontally scaled workers sized to chain, mail-order, and central-fill volume
Reliability
Retry, backoff, and idempotency keys for fills, refills, and claim transactions
Adaptation
Continuous monitoring of PDX EPS releases and configuration drift across stores
Frequently asked questions
Yes. Supergood normalizes data across the Enterprise Pharmacy System, Care Rx clinical services, Absolute AR claims, and Turn Rx inventory, so you can integrate prescription, patient, claim, and inventory entities through one consistent API surface.
PDX does not publish an open self-serve developer API; integrations typically run through authenticated application surfaces and partner agreements. Supergood works against your existing authenticated PDX sessions, so you don't have to wait on a public program.
Access runs through your own authenticated sessions and entitlements. Supergood preserves PHI handling, EPCS audit trails, and store-level scoping rather than forcing a generic schema, with encrypted credential storage and audit logging.
Yes. The API is location-aware, so data from independents, regional and national chains, mail-order, central-fill, and long-term-care sites is scoped and reconciled per store while remaining queryable across the organization.
Each environment is profiled against its EPS configuration. Supergood continuously monitors PDX releases and configuration drift, adapting the adapter automatically so integrations keep working as the platform evolves.