Question 1

Does DenialOS have a live athenahealth connection?

Accepted Answer

No. DenialOS implements the athenahealth connector foundation and the FHIR R4 retrieval mapping path, but live connectivity is unproven. Tenant provisioning, application authorization, credentials, and customer UAT require athenahealth-side evidence before any production claim is made.

Question 2

What is implemented in the athenahealth connector today?

Accepted Answer

Read-only adapter-pack validation, connector profiles, contract-scoped adapter routing, FHIR R4 SMART Backend Services signing and token-exchange primitives, public JWKS publication, document-exchange safety checks, and non-executing write-back planning.

Question 3

What has to happen before the athenahealth connection is production usable?

Accepted Answer

Three things: athenahealth-side tenant provisioning and application registration, customer-supplied credentials and scopes configured against the connector profile, and retained sandbox plus customer UAT evidence. Until those exist the connection stays unvalidated.

Question 4

Why build the connector foundation before the connection is active?

Accepted Answer

Because the control plane — canonical mapping, provenance hashing, checkpointing, reconciliation, and production gates — is the part that has to be correct before any live clinical data is read. Building it first means activation is a provisioning exercise rather than a rewrite.

athenahealth Integration