Axiom Connect | Compounded peptide fulfillment, wired together

What it does

Three jobs. Done together. With nothing in between.

Most platforms do one of these and bolt the rest on. Axiom is built so routing, audit, and settlement are the same transaction.

01 / Routing

Universal API. Per-pharmacy adapters.

One inbound contract. Adapters translate to each pharmacy's native API. Adding a pharmacy is a new adapter file, not a schema change.

35% volume floor enforcement, configurable per state
Round-robin tiebreaker, hard-rule overrides per corp
Multi-item order splitting across pharmacies
Production schedule editor read by the routing engine in real time

02 / Audit

Append-only ledger. Immutable trail.

Every state change is a row. Every dollar is a row. Once written, never modified. 21 CFR Part 11 and HIPAA audit controls met by design.

Append-only at the database role level, not just convention
S3 Object Lock sidecar with 7-year compliance-mode retention
Hash chain verification, end to end
Scoped audit reads per tenant — no cross-tenant leakage

03 / Settlement

Net-7 ACH. No card-on-file. No surprises.

Plaid-verified bank balances before every order. Chase-backed NACHA payouts to pharmacies. Every entry posts to the ledger in the same transaction as the order.

ACH via Plaid, balance verified pre-order
Net-7 invoicing only — terms enforced at the database level
NACHA file batch payouts to pharmacies via Chase
Affiliate accruals + payouts run on the same ledger

Who it's for

Three sides of the same flow.

Clinics submit. Corporations oversee. Pharmacies fulfill. Each side gets its own portal with the data scope its role actually needs.

For Clinics

Place orders. Track every patient.

Clinic admins, physicians, and front-desk staff each see the data scope their role allows. Initials-only for front desk. Assigned patients only for prescribers. Full roster for admins.

TOS + privacy + BAA gate before first order
Role + data-scope per user (admin / physician / front desk)
Bulk patient upload with license-state validation
Plaid balance check before every order submit
Net-7 invoicing, ACH-only settlement

For Corporations

Operations summary across the tree.

Multi-location buyers (corp → franchisee → clinic) get a single pane of glass. Self-serve API keys. Integration health. Billing scoped to whichever tier you settle on.

Stackable integration channels: portal, iframe-EMR, EMR push, direct REST
White-label subdomain per corp (yourcorp.axiomscript.com)
Custom domain support — bring your own DNS
Hierarchy configurable: corp → franchisee → location, or flat
Affiliate attribution with lifetime, capped, or fixed compensation

For Pharmacies

Production view that doesn't fight you.

Daily queue grouped by API. Production schedule editor that the routing engine actually reads. Lot logging tied to fulfillment. Ticketing replaces email.

Daily queue with grouping by API and SKU
Production schedule editor consumed by routing in real time
Lot logging per batch, attached to every fulfilled order
Consumables inventory with reorder thresholds
Ticketing system replaces email for production / equipment / consumable issues

How it works

A clean line from inbound to fulfilled.

One inbound API. Routing decides where it goes. Worker fires it. Pharmacy fulfills. Status streams back. Ledger and audit log every step.

01 / Inbound

Order arrives

HMAC-signed POST from a clinic portal, marketplace, or partner EMR. Idempotency keys handle replays.

02 / Routing

Pharmacy picked

State eligibility, volume floor, hard rules, schedule capacity. Reasoning trace stored on the order.

03 / Worker

Adapter fires

Pharmacy-specific adapter translates and calls. Retries with exponential backoff. Failures land in dead-letter for inspection.

04 / Settlement

Ledger + audit

Every transition writes a ledger entry and an audit row in the same transaction. S3 Object Lock sidecar ships immutable copies.

Compliance

Designed for regulated pharma. Not retrofitted.

Compounded medication routing means FDA scrutiny, state board scrutiny, and HIPAA scrutiny. Axiom is built so the audit story is short, clear, and pre-answered.

21 CFR Part 11

Immutable audit trail

Append-only at the database role level. S3 Object Lock with 7-year compliance-mode retention. Hash chain verifiable end to end.

HIPAA 164.312(b)

Scoped audit reads

Every PHI access logged. Tenant scoping in the read query, not the application layer. Initials-only data scope for users who don't need full identifiers.

SOC 2 CC7.2

Detection of changes

Every state change wraps in a transaction with an audit row. Every config change, login, role change, and dollar event captured.

BAA & data flow

Subprocessor governance

BAAs filed with every PHI processor. Patient identifiers referenced by ID, never inlined into audit entries. Right-to-deletion compatible.

The stack

No black boxes.

Every dependency is documented, every integration is testable, and every number you see is recoverable from the ledger.

RoutingUniversal inbound API + per-pharmacy adapter layer
Pharmacies liveHillstone (SI Compounding), Mills (Pharmetika), Belcher 503B coming
CatalogNAD+ 100 / 250 / 500 mg, BPC-157 5 / 10 mg, Sermorelin 3 / 9 / 15 mg
BankingChase. NACHA file payouts. No merchant of record.
Bank verificationPlaid. Balance verified before every submit.

Audit storagePostgres live + S3 Object Lock sidecar (compliance mode)
QueuesBullMQ on Redis. Retries, backoff, dead-letter inspection.
Outbound webhooksHMAC-signed status events to corps with channels enabled
AuthSession + role + data-scope. 2FA enforcement per tenant.
Integration channelsPortal, iframe-in-EMR, EMR push API, direct REST

Compounded peptide fulfillment, wired together.