An event-sourced platform with a public canonical model.
One endpoint takes your events. Everything above it is documented: the entities, the routes, the delivery guarantees, and exactly what you take with you if you leave. Every endpoint Attergo exposes is on these pages, implemented and reachable today.
Canonical entities
| Entity | Identified by | Emitted on |
|---|---|---|
| Fill | Tenant, location, internal reference | Data entry, status change, complete, cancel |
| Claim | Fill, payer, sequence | Submit, adjudicate, reverse, remit |
| Encounter | Tenant, patient reference, service date | Document, sign, submit, adjudicate |
| Product | NDC-11 | Inventory receipt, cost update |
| Plan | BIN, PCN, group | First adjudication against the plan |
| Prescriber | NPI | First fill, registry refresh |
| Evidence bundle | Fill | Continuously, as sources arrive |
Guarantees
At-least-once delivery
Every event carries a stable id and a monotonic sequence per entity, so a consumer that is idempotent can retry without thinking about it.
Ordering per entity
Ordering within one fill or one claim is guaranteed, which is the ordering that decides an outcome.
Replay on request
Any window can be re-emitted from the archive without contacting the source system.
Explicit staleness
Derived figures carry the timestamp of the last event they included. A lagging figure says so.
Where to go next
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.