Compounders
One working dossier for the pharmacies and routing partners Affinity is evaluating: current catalog coverage, public integration posture, regulatory constraints, and follow-up work before production routing.
Catalog rows
823
Priced rows
309
Medication families
333
Public targets
10
LifeFile-style activation, base URL, and credentials still need confirmation.
Useful catalog or clinic workflow, but production routing depends on onboarding.
Important for 503A/503B modeling, but not a current direct API path.
Public vendor claims still need current license checks, account-specific terms, and patient-specific order validation before live routing.
Each partner has its own page with public facts, routing rules, sources, and local catalog coverage.
PerfectRx is the strongest public API/fulfillment candidate in the current network. Its public positioning is enterprise pharmacy fulfillment, with API, portal, retail, and mail-order infrastructure.
OptioRx is a broad-footprint compounder with public locations and direct API documentation in the local dossier. It is promising for coverage, but still needs credentials and pricing for production use.
Striker Rx is one of the clearest LifeFile-style partners: a Texas sterile 503A compounder with concrete catalog, pricing, intake, and data-push materials in the local dossier.
MediVera is a strong LifeFile-style technical candidate with public compliance messaging and a large Michigan compounding facility. It fits the network as a high-compliance 503A option.
Promise is commercially active for clinics and telehealth providers, with a public 503A posture and clinic-facing portal story. It is useful for catalog coverage, but production API posture is still paperwork-gated.
Southend is an operationally promising Texas 503A partner with public telehealth-support positioning and cold-chain fulfillment language. It is best treated as onboarding-first until API access is unlocked.
ReviveRx is a Houston-based 503A/mail-order partner with useful catalog and onboarding materials. It is credible for coverage but lower priority technically until API, portal, or LifeFile support is confirmed.
Belmar is important public-regulatory context because it spans both 503A and 503B models. It is not a current direct API integration, but it is a relevant workflow/reference partner for pharmacy routing and compliance modeling.
Public API documentation is available and describes a RESTful JSON API for clinics to send prescriptions from EHR systems.
Public provider pages advertise REST JSON, OAuth 2.0, sandbox support, and API documentation during onboarding.
Full Integration is Surescripts and EPCS certified and advertises custom ePrescribing UI support with more than 250 APIs.
Public API pages focus on supplement/lab catalog and treatment plan workflows, not pharmacy prescription fulfillment.
Public API learn-more page and PDF documentation exist for EHR/pharmacy technology vendors.
Integration program is public, but the site positions this as supported onboarding rather than self-serve docs.
Public product pages describe the e-prescribing network and EHR vendor integration path.
Public telehealth partner page mentions API-based prescription intake, eRx connectivity, and portal workflows.
Public telehealth page states they have a real-time API for telehealth systems and mail-order fulfillment.
Public page describes full API integration and telehealth fulfillment, but no self-serve reference was found.
Evaluate public API reference and create an adapter spike.
Confirm sandbox scope before any real prescription transmit path is enabled.
Provide LifeFile activation, base URLs, credentials, and catalog/pricing export format.
Provide API key, group ID, and canonical pricing export.
Continue MNDA/business workflow and request API docs/sandbox credentials.
Send spreadsheet or API-readable catalog/pricing export instead of PDF-only data.
| Partner | Status | Rows | Capabilities | Notes |
|---|---|---|---|---|
| MediVera Compounding Pharmacy | docs only | 105 | catalog from pdf, local demo orders, pricing | LifeFile API docs say API base URL is provided at activation. |
| Striker Rx | docs only | 104 | catalog from pdf, local demo orders, pricing | LifeFile Data Push Service and OpenAPI PDFs are present, but credentials/base URL are not active locally. |
| OptioRx | needs account | 266 | catalog from pdf, local demo orders | API Gateway documentation is present, but API key and group ID are still required. |
| ReviveRx | local demo | 247 | catalog from pdf, local demo orders | Full catalog and peptide formulation PDFs are present, but no API docs were found in the intake. |
| Promise Pharmacy | blocked by partner | 90 | catalog from pdf, local demo orders, pricing | Master catalog has tiered pricing. Demo priceCents uses the 1-999 scripts price and preserves higher tiers in tags. |
| Southend Pharmacy | local demo | 10 | catalog from pdf, local demo orders, pricing | Pricing guide rows are parsed from block tables. First orphan row in each block may be skipped unless product context is present. |
| PerfectRx | sandbox ready | 1 | catalog from pdf, live api read, local demo orders, webhooks | Repo has PerfectRx sandbox env vars for read/list operations. |
