Every software evaluation in an independent pharmacy gets stuck on the same unspoken question. How much of my staff’s day does this cost me? Not the licence fee. The interruptions, the retraining, the third system somebody has to remember to update, the new reason a fill takes ninety seconds longer on a Monday afternoon.
The short version
On day one your technicians see nothing. Your pharmacist in charge sees nothing. No new screen appears inside the fill workflow, no field becomes required, no popup interrupts a verification.
The person whose day changes is whoever owns the numbers, usually the owner or a manager. They get a login, a two factor enrollment, and a per fill margin view.
Why nothing changes at the counter
Attergo reads. It does not write.
The integration consumes prescription events from your pharmacy management system through the PioneerRx Rx Event API. Events flow one direction, out of the pharmacy system and into Attergo. There is no return path. Attergo cannot change a price in your system, hold a fill, annotate a patient record or queue a task for a technician.
That boundary lives in the architecture, and three things follow from it:
- Nothing Attergo does can slow a fill, because Attergo is not in the fill path.
- An Attergo outage is invisible at the counter. Events queue and arrive later.
- A bug in our margin logic cannot corrupt your dispensing record. The worst case is a wrong number on a dashboard.
Repricing a claim, holding a fill and queueing work for a technician belong to your dispensing system. They stay there. Attergo tells you a fill lost money, close enough to the fill that you can still do something about it.
One connection, eight products
A single per store connection feeds every product, so activating one later does not mean another integration project, another credential, or another vendor in your store.
| Product | What it does on that connection |
|---|---|
| Attergo Margin | Per fill margin against acquisition cost, in real time |
| Attergo Billing | Clinical encounters to medical claims to remittance |
| Attergo Audit | Evidence assembly and PBM audit response |
| Attergo Authorizations | Prior authorization detection, submission and renewal |
| Attergo Inventory | Purchasing and stock against real demand |
| Attergo Compliance | Licences, credentials, attestations and controls |
| Attergo Intelligence | Cross store dashboards and trend analysis |
| Attergo Integrations | The event spine every other product runs on |
For staff, every product arrives on the connection you already made. No second onboarding, no second credential, no new step at the counter.
What onboarding actually asks of you
Short, and almost none of it lands on counter staff.
| Step | Who does it | What it involves |
|---|---|---|
| Approve the feed | Owner, with PioneerRx | Enabling a third party feed runs through PioneerRx’s data programs process |
| Configure delivery | Owner or IT contact | Point the store’s Rx Event API at Attergo, using the per store credential we issue |
| Enroll two factor | Every Attergo user | TOTP app enrollment, mandatory, no opt out |
| Provide acquisition cost | Owner or buyer | A cost file, or accept NADAC as the starting basis |
Credentials are issued per store, not per chain and not per user. The pharmacy system posts events outbound, and each delivery authenticates with that credential, so every arriving event is attributable to one location. Turning off one store leaves the others running.
The approval step runs on PioneerRx’s data programs timeline.
The first thing that surprises people
Event feeds are forward looking. Connect a store and Attergo starts receiving events from that moment. Connecting on a Tuesday does not retroactively deliver last quarter’s fills.
So the first week is quiet by design. You see the fills that happened since you connected, and the picture sharpens as history accumulates. Anyone describing a real time event integration that produces a full year of trend analysis on the first afternoon is describing a database extract, which carries different privacy and access implications. If you need historical analysis on day one, raise it separately.
What the owner sees
Per fill margin, calculated against acquisition cost, with the cost basis shown next to every number.
That last clause carries the weight. Every margin figure is labelled with where its cost came from: your invoice, NADAC, or a manual override. A margin computed from a real wholesaler invoice and one computed from a national average are not the same quality of number, and a dashboard presenting them identically is quietly misleading you.
You are about to take these numbers into a conversation with a wholesaler or a PBM. A number you can audit is the only kind worth having there.
What we do not do
We do not write back to your pharmacy system. Architectural.
We do not touch patients or clinical decisions. No portal, no messaging, no patient facing surface, no clinical advice. Attergo has opinions about money, not therapy.
We do not send protected health information outside the application. None appears in application logs or in any email we send. An alert saying margin fell on a drug class says that and nothing more.
We do not page your staff. Exceptions land in a work queue with an owner, and digests arrive on your cadence. A system that interrupts the counter every time a claim adjudicates badly trains everyone to ignore it, which is worse than no alerting at all.
The security posture
Three controls sit underneath day one whether or not anyone notices.
- Tenant isolation enforced in the data layer, not in application code. A query that forgets a filter returns nothing rather than another pharmacy’s rows.
- Time based two factor required on every account, including ours.
- An append only log of every read of protected health information, which the pharmacy can inspect and export. Support staff need a named, time boxed grant to view your data, and the grant appears in your log.
Full detail on security.
What to ask any vendor in this category
Two questions separate integrations that are safe to run in a live pharmacy from ones that are not. Does your integration write back into my pharmacy system, and under what conditions? If your service fails at 2pm on a Friday, what happens at my counter? The longer list is in what to ask a pharmacy revenue analytics vendor before you sign.
Day one is uneventful. The connection is read only, per store, forward looking, and invisible to counter staff. The value shows up for whoever is responsible for margin, and it compounds as history accumulates.
See Attergo Margin, or book a demo and we will walk your team through the first week.