Authentication and network¶
The service is registered with Epic as a Backend Systems app, named "Abacus One Group Integration Services". Nobody signs in to it, and it needs no password or shared secret from you.
How it authenticates¶
The service follows SMART Backend Services. It signs a short-lived JSON Web Token (JWT) with its private key, and exchanges it at your OAuth 2.0 token endpoint for an access token.
Signing keys¶
- Algorithm: ES384 (ECDSA with the P-384 curve and SHA-384).
- Private keys can't be exported. They are created and kept in a managed key service, and signing happens inside it, so a private key never appears in our code, configuration or logs.
- Signing is restricted to the service, and every use of a key is logged.
- Non-production and production have separate keys.
JWK Set URLs¶
Epic reads the service's public keys from these URLs.
| Epic environment | JWK Set URL |
|---|---|
| Non-production | https://jwks.test.io.abacusops.com/.well-known/jwks.json |
| Production | https://jwks.prod.io.abacusops.com/.well-known/jwks.json |
If your Epic version has you register the app's key in your own system (a step in the integration guide), enter the URL, not a static public key file. A file would stop working when the keys rotate.
Key rotation¶
Keys rotate every year, and sooner if a key may have been compromised. You don't need to do anything, because Epic reads the new key from the JWK Set URL.
Network¶
- The service calls your FHIR endpoint over the internet, from the United States, using TLS 1.2 or later for every call.
- IP allowlisting: if your endpoint requires it, tell us during setup. We then give you a fixed address that the service's requests come from.
Request limits¶
The service limits how many requests it sends you at once and per minute, and it slows down when
your system asks it to: it honors Retry-After, and backs off on HTTP 429 and 503 responses. When
it retrieves a range of past visits, before go-live for example, it stays under Epic's daily limit
on document queries. Tell us your limits during setup, and we set the service to stay within them.