Capture
AGIMINION records the room
The AGIMINION device captures the visit audio and AGIMAN transcribes it on the appliance inside your practice network. No internet connection is needed to transcribe or draft.
All integrationsathenahealth
EHR / PM integration
AGIMAN drafts the note and codes for athenaOne
AGIMAN captures the visit on an appliance inside your practice network, drafts the note in the clinician's style, and suggests ICD and CPT codes for the encounter. After the clinician reviews and signs, the approved note and codes map to the matching fields in athenaOne.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- athenahealth
- Category
- EHR / PM
- Used by
- Independent and group practices on athenaOne
- Connects over
- athenahealth Marketplace and developer APIs
The connection
How AGIMAN connects to athenahealth.
What athenahealth is
athenahealth runs athenaOne, a cloud-based ambulatory system that combines the EHR, practice management, and revenue cycle billing on one national network. It is common in independent and group practices that keep scheduling, charting, and claims in the same record. athenahealth exposes its data through the athenahealth Marketplace and a developer program covering FHIR R4 and proprietary REST APIs.
Who runs it
Independent and group practices on athenaOne
The access path
FHIR R4SMART on FHIROAuth 2.0athenaOne REST APIs
AGIMAN registers as an application in the athenahealth developer program and authenticates with OAuth 2.0 over SMART on FHIR scopes. Your practice has to authorize the app before it can read or write any data, so nothing moves until you grant access. Encounter data reads through FHIR R4, and the signed note and codes map to athenaOne fields using the FHIR R4 and proprietary REST endpoints that fit each field. We scope and test that export path against your own athenaOne instance before go-live, so the mapping is verified for your templates and code sets first.
The athenahealth export path is scoped and tested against your own athenaOne instance before go-live. This is a standards-based integration, not a certified partnership or an endorsement by athenahealth.
The workflow
From the exam room to athenahealth, with you in control.
Draft
Note and codes drafted locally
AGIMAN drafts the chart note in the clinician's style and suggests ICD and CPT codes for the encounter. It also prepares referral letters, patient handouts, and intake forms tied to the visit.
Review and sign
The clinician signs off
The clinician reads the draft note and the suggested codes, edits anything, and signs. Nothing reaches athenaOne until a human approves it.
Sync
Mapped into athenaOne
The signed note and approved ICD and CPT codes map to the matching athenaOne chart and billing fields over the FHIR R4 and athenaOne REST APIs your practice authorized. A review log records what was written and when.
After sign-off
What AGIMAN hands back to athenahealth.
The encounter note
The reviewed and signed chart note maps to the encounter document fields in athenaOne, so it lands where the clinician expects to find it.
Codes for the claim
Approved ICD and CPT codes map to the diagnosis and procedure fields that feed athenaOne practice management and billing. The clinician approves every code before it syncs.
Letters and forms
Referral letters, patient handouts, and intake and visit forms save back as documents on the patient chart for a human to confirm or send.
On your network
Local first, before any export.
- Room audio and transcripts stay on the appliance on your network.
- Transcription and note drafting run on site, with no internet connection required.
- Nothing reaches athenahealth until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
athenahealth, answered.
Where do the visit audio and the draft note live?
Room audio, transcripts, and drafts stay on the AGIMAN appliance on your practice network. Only the note, codes, and documents the clinician signs off on are sent to athenaOne over the access path you authorized. A BAA is available, and AGIMAN is HIPAA compliant.
How does AGIMAN connect to our athenaOne instance?
AGIMAN registers as an application in the athenahealth developer program and connects with OAuth 2.0 and SMART on FHIR scopes after your practice authorizes it. We scope and test the export path against your own instance before go-live, so it maps to your templates and code sets, not a generic example.
Does AGIMAN write to the chart on its own?
No. A clinician reviews and signs every note and approves every code first. AGIMAN only maps the text and codes the clinician approved into the athenaOne fields, and it keeps a review log of what was written.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside athenahealth.
Buy the appliance and room devices, then scope the athenahealth export path with us. We test it against your instance before it is turned on.