Capture
Record the visit in the room
AGIMINION captures the conversation in the exam room and sends audio to the AGIMAN appliance on the practice network. Transcription and drafting run locally, with no internet connection required.
All integrationseClinicalWorks
EHR integration
Draft the eClinicalWorks note in the practice, sign it, send it back
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, the approved note and codes map to your eClinicalWorks encounter over FHIR R4.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- eClinicalWorks
- Category
- EHR
- Used by
- Independent and small to mid group ambulatory practices
- Connects over
- Standards-based FHIR developer access
The connection
How AGIMAN connects to eClinicalWorks.
What eClinicalWorks is
eClinicalWorks is one of the largest ambulatory EHR and practice management vendors in the United States, used by independent and group practices across primary care and many specialties. It pairs charting and e-prescribing with billing and scheduling, and runs the patient-facing healow portal. Practices connect to outside systems through a standards-based FHIR developer program and the Carequality and CommonWell record-sharing networks.
Who runs it
Independent and small to mid group ambulatory practices
The access path
FHIR R4US CoreSMART on FHIROAuth 2.0
AGIMAN registers as a provider-facing app through the eClinicalWorks FHIR developer program and connects with SMART on FHIR for clinician launch or Backend Services with a private-key JWT for automated server access, both over OAuth 2.0. The practice turns on FHIR access for its instance, and AGIMAN maps reviewed chart text and codes to the FHIR R4 and US Core resources that instance exposes. The first export path is scoped to the resources your practice approves and tested against your own eClinicalWorks instance before it is turned on. This is a standards-based connection, not a certified partnership or an endorsement.
The eClinicalWorks export path is scoped to the FHIR resources your practice approves and tested against your own instance before it is turned on. This is a standards-based connection, not a certified partnership.
The workflow
From the exam room to eClinicalWorks, with you in control.
Draft
Note, codes, and documents
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 or visit forms tied to the visit.
Review and sign
The clinician decides
The clinician reviews the draft, edits anything, and signs off. Nothing leaves the appliance for eClinicalWorks until a person approves it.
Sync
Map to the eClinicalWorks encounter
AGIMAN maps the signed note and approved ICD and CPT codes to the matching FHIR R4 resources on your eClinicalWorks encounter, using the scopes your practice enabled. The clinician confirms the encounter in eClinicalWorks before the claim moves.
After sign-off
What AGIMAN hands back to eClinicalWorks.
The chart note, mapped
The reviewed and signed note maps to the eClinicalWorks encounter through the FHIR R4 resources your instance exposes, in the clinician's own wording.
Codes for the encounter
AGIMAN attaches the suggested ICD and CPT codes to the encounter so coding and billing staff start from a reviewed draft, not a blank claim.
Referrals and handouts
Referral letters, patient handouts, and intake or visit forms are prepared as documents the clinician or staff confirm before sending or filing.
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 eClinicalWorks until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
eClinicalWorks, answered.
Where do the audio and drafts live?
Room audio, transcripts, and drafts stay on the AGIMAN appliance on your practice network. Transcription and note drafting need no internet connection, and only the approved note and codes are sent to eClinicalWorks over the access path you enabled. A BAA is available.
How does AGIMAN reach eClinicalWorks?
AGIMAN registers through the eClinicalWorks FHIR developer program and connects with SMART on FHIR or Backend Services over OAuth 2.0, mapping to FHIR R4 and US Core resources. Your practice turns on FHIR access for its instance, and the export path is scoped and tested against your instance before go-live.
Does AGIMAN write to the chart on its own?
No. The clinician reviews and signs every note and confirms the codes before anything maps to eClinicalWorks, then confirms the encounter in eClinicalWorks before the claim moves. AGIMAN drafts and maps. The clinician keeps clinical judgment and the final say.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside eClinicalWorks.
Buy the appliance and room devices, then scope the eClinicalWorks export path with us. We test it against your instance before it is turned on.