Capture
Record the visit on the appliance
AGIMINION captures room audio and AGIMAN transcribes it on the appliance inside your network. No internet connection is needed to transcribe or draft, and the audio stays on the practice network.
All integrationsEpic
EHR integration
Send the signed note and codes back into Epic
AGIMAN captures the visit on an appliance inside your network, drafts the chart note in the clinician's style, and suggests ICD and CPT codes. After the clinician reviews and signs, AGIMAN exports the note and codes to your Epic instance over FHIR.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- Epic
- Category
- EHR
- Used by
- Hospitals and academic health systems
- Connects over
- Epic on FHIR, Backend Services
The connection
How AGIMAN connects to Epic.
What Epic is
Epic is the electronic health record used by most large hospitals and academic health systems in the United States. A health system runs its own Epic instance, with its own clinical build, its own FHIR endpoints, and its own administrators who approve outside access. Clinicians work in Hyperdrive, and patients reach their charts through MyChart.
Who runs it
Hospitals and academic health systems
The access path
FHIR R4USCDISMART on FHIROAuth 2.0 Backend Services
AGIMAN connects to your Epic instance through Epic on FHIR using the OAuth 2.0 Backend Services flow, the same system-to-system path Epic documents for server applications. AGIMAN registers a public key, signs a JSON Web Token with the matching private key, and requests a scoped access token against your instance FHIR endpoints. Your Epic administrator maps the client to an audit user and approves the scopes before production access is granted, so every web service call is attributed and logged. The export path is scoped to the FHIR resources your team approves and tested against your own instance before go-live. This is a standards-based connection to your instance, not a certified Epic partnership or an endorsement.
AGIMAN connects over Epic on FHIR Backend Services with OAuth 2.0, and production client registration with your Epic administrator is completed and tested against your instance before go-live.
The workflow
From the exam room to Epic, with you in control.
Draft
Note plus ICD and CPT codes
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 follow-up tasks tied to the visit.
Review and sign
The clinician reviews and signs
The clinician reads the draft, edits anything that needs it, confirms the codes, and signs. Nothing reaches Epic until a person approves it.
Sync
Export to your Epic instance over FHIR
AGIMAN maps the signed note and confirmed codes to the FHIR resources your team approved and posts them to your Epic instance through Epic on FHIR Backend Services. Each call is attributed to the audit user your Epic administrator mapped.
After sign-off
What AGIMAN hands back to Epic.
The chart note
After the clinician signs, AGIMAN sends the note text to your Epic instance, mapped to the document fields your team approved. The clinician's signed version is the one that lands.
The encounter codes
AGIMAN attaches the ICD and CPT codes the clinician confirmed to the encounter over FHIR. A coder or clinician can still review them in Epic before the claim moves.
Letters and handouts
Referral letters, patient handouts, and intake or visit forms drafted from the visit can be saved to the encounter for a person to send. AGIMAN drafts them, the clinician decides what goes out.
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 Epic until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
Epic, answered.
Where does the visit audio and the draft live?
On the appliance inside your practice network. Room audio, transcripts, and drafts stay local, and no internet connection is needed to transcribe or draft. Only the signed note and confirmed codes leave, over the FHIR path your team approves.
How does AGIMAN reach our Epic instance?
Through Epic on FHIR using OAuth 2.0 Backend Services. AGIMAN registers a public key and signs a JWT to request a scoped token, and your Epic administrator maps the client to an audit user and approves the scopes before production access. The path is tested against your own instance before go-live.
Does AGIMAN write to the chart on its own?
No. The clinician reviews, edits, confirms the codes, and signs before anything is sent. AGIMAN drafts and maps, the human decides, and every call to your instance is attributed and logged.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside Epic.
Buy the appliance and room devices, then scope the Epic export path with us. We test it against your instance before it is turned on.