Athenahealth

CLINICAL SYSTEM SAFETY

An MCP designed around what must never leak.

Nine tools over athenaOne and FHIR with capability packs, confirmation, idempotency, and PHI-safe operations.

Provider-native

Build directly on Athena APIs

Use athenaOne and FHIR APIs directly when your integration team wants full control of the application, workflow, and clinical safeguards.

• Maximum implementation flexibility
• Your team owns every safety control

Quilr-managed

Add a clinical safety boundary

Use Quilr when an agent needs a deliberately constrained surface with PHI-safe telemetry, gated writes, and idempotent operations.

• Capability packs disabled by default
• Confirmed writes with no automatic retry

Decision signalFor agent access, the safety model is the product: start with the narrowest capability pack and enable writes only for a validated workflow.

Safety control	Quilr Athenahealth
Customer-owned Athena system application	✅
Operator allowlists and capability packs	✅ Disabled by default
Separate athenaOne and FHIR batch reads	✅
Confirmed writes with unique idempotency keys	✅
Automatic write retry	- Never
Separately enabled and strongly confirmed deletes	✅
FHIR bulk-export job start/status without PHI download	✅
PHI in app state, logs, traces, or persistent audit	- Prohibited

Athenahealth publishes athenaOne and FHIR APIs but no official MCP was identified. Quilr supplies the MCP boundary and its clinical safety model.