PDX Pharmacy API
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. This page is an independent design exercise that asks what a well-designed PDX Pharmacy API could look like: the resources it would expose, the authentication it would need, and the workflows it could unlock. Below: a hypothetical endpoint design, the technical requirements a production implementation would face, the use cases programmatic access could serve, and where to start if your team needs this kind of access today.
This page is an independent analysis by Supergood of what a well-designed PDX Pharmacy API could look like. It draws on publicly available information, vendor materials, and general integration experience in this category. Nothing on this page describes an existing PDX Pharmacy product, and Supergood is not affiliated with or endorsed by the vendor. If the vendor offers an official API, we highly recommend it.
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
An API for a platform like this would naturally organize around its core 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
What a PDX Pharmacy API Could Look Like
If PDX Pharmacy exposed a modern, general-purpose API, the integration challenges above suggest what it would need to get right. This is a design sketch, not documentation of anything that exists today:
- First-class authentication: session handling with support for MFA and enterprise sign-on where the platform uses them
- Consistent resources: normalized JSON schemas and pagination across the platform's core objects
- Reliable writes: idempotency keys and validation that mirrors the platform's own workflow rules
- Entitlement awareness: endpoints scoped to what each customer's licensing actually permits
The endpoint sketches, technical requirements, and use cases below flesh out this hypothetical design.
How AI agents could connect to software like PDX Pharmacy: MCP servers for software without a public API →
Need This Kind of Access Today?
If your team needs this kind of access today, Supergood builds integrations on request, one customer at a time. We act at the direction of our customers, within the access they already hold. Customers bring their own accounts, licenses, and entitlements. If the vendor offers an official API, we highly recommend it.
- Schedule an Integration Assessment
A 30-minute session to review your product mix, licensing, and authentication model. - Scope the Integration
We design the access pattern around your workflows and entitlements. - Deploy with Monitoring
Go live with continuous monitoring as your platforms evolve.
Potential API Endpoints
Authentication
/authenticateWould authenticate to a PDX EPS environment using username/password or MFA and obtain a session token for downstream calls.
Patient Operations
/patientsWould retrieve patient central records with filters for name, date of birth, store, and identifier.
Prescriptions
/prescriptionsWould list prescriptions, fills, and refill status across stores with date, drug, and patient filters.
Prescriptions
/create_fillWould submit a new prescription fill or refill request against an existing patient and prescriber record.
Inventory
/inventoryWould pull drug, NDC, on-hand quantity, and reorder data from Turn Rx inventory management.
Billing
/claimsWould retrieve 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
Connect via No-Code Tools
Automate this platform from the no-code stack you already use.
Technical Requirements
Authentication
Would require username/password and MFA (SMS, email, TOTP) with managed session handling with per-store credential scoping
Connectivity
Would build on 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
Would need 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
Design target: sub-second reads on cached entities; multi-second writes when posting fills and clinical records
Throughput
Design target: horizontally scaled workers sized to chain, mail-order, and central-fill volume
Reliability
Retry, backoff, and idempotency keys for fills, refills, and claim transactions
Versioning
Clear versioning and change management would matter as PDX Pharmacy evolves
Frequently asked questions
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.
Availability of official interfaces varies by product, plan, and licensing. Many platforms in this category gate access behind partner programs or paid modules, and there is often no broadly available, self-serve public API. Check the vendor's developer resources for current offerings.
The hard parts would be authentication (MFA, session management, enterprise controls), consistent schemas across the platform's products, and write semantics that reconcile the way the platform's own workflows do.
No. This page is an independent analysis by Supergood and is not affiliated with, sponsored by, or endorsed by the vendor. All product names and trademarks belong to their respective owners and are used for identification only. Nothing here documents an actual PDX Pharmacy product or service.
Supergood acts at the direction of its customers, within the access those customers already have. We respect each customer's agreements with their software vendors, and how those agreements apply to a customer's use is a determination the customer makes. If the vendor offers an official API, we highly recommend it.
Supergood builds managed API access to enterprise software for customers on request, scoped to each customer's own licensing and entitlements. If your team needs programmatic access to a platform like this, schedule an integration assessment to discuss options.