Connect in an afternoon. Nothing changes at the counter.
One credential per location, entered once, and your events flow. We ask for no database credentials, install nothing that touches dispensing, and cannot write a prescription back into your system. Events arrive over HTTPS with TLS 1.2 or better, authenticated per location.
What a connection brings you
| What connects | How | What you get |
|---|---|---|
| Your dispensing system | PioneerRx, over its event API | Every fill, claim and adjudication, seconds after it happens |
| Claims and remittances | Claim.MD clearinghouse | Medical claims out, remittances back, each one followed to payment |
| Your wholesaler | Invoice and catalogue files | Real acquisition cost behind every margin figure on every screen |
| Prescribers, drugs and payers | National public directories | Reference data loaded before your first day, not typed in during it |
Everything vendor specific lives in one adapter. The margin arithmetic, the claim logic and the evidence trail never learn which system produced an event, so what you see on screen is the same whichever system you run.
What you are agreeing to
Read only, always
We receive events. We cannot create, edit or cancel anything in your dispensing system, and no credential we hold would let us.
Yours to revoke
Credentials are issued per location and revoked in a click. Turning us off is a setting on your side, not a support ticket on ours.
Nothing on your workstations
No agent, no screen scraper, no nightly export somebody has to remember to run. Nobody's daily workflow changes.
Your data leaves with you
Complete export in open formats at any time, including the archive of raw events exactly as they arrived.
What onboarding a location looks like
Day zero, morning
Business associate agreement signed. Per location credentials issued.
Day zero, afternoon
Credential entered in your dispensing system. We confirm the first events landing, live, on a call.
Day one
Wholesaler invoices imported. Margin switches from benchmark cost to your real cost.
Day two onward
Roles assigned, digest recipients set, alert thresholds tuned to your tolerance.
The technical reader has the whole contract: the event catalog, the ingestion endpoint and the API reference live in the developer documentation.
Connect one store. We will tell you what the month cost you.
Read-only credentials you can revoke. We come back with the fills that went out under cost, the services you could have billed, and the fills an auditor would ask about.