Capture
Record the visit in the room
AGIMINION captures the encounter audio in the exam room. The audio and transcript stay on the appliance in your practice network, with no internet connection needed to transcribe.
All integrationsNextGen
EHR integration
AGIMAN drafts the note and codes, then syncs to NextGen
On NextGen Enterprise or NextGen Office, AGIMAN captures the encounter on an appliance in your practice network and drafts the chart note, the ICD and CPT codes, and the visit documents. The clinician reviews and signs, then the approved note and codes post back to the patient chart.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- NextGen
- Category
- EHR
- Used by
- Specialty and primary care ambulatory practices, from small groups to large multi-provider organizations
- Connects over
- NextGen API Developer Program
The connection
How AGIMAN connects to NextGen.
What NextGen is
NextGen Healthcare makes ambulatory EHR and practice management software for specialty and primary care groups. NextGen Enterprise serves larger multi-provider organizations, and NextGen Office is the cloud EHR for smaller practices. Both are run by the practice and its own clinical and front-office staff, not by a hospital IT department.
Who runs it
Specialty and primary care ambulatory practices, from small groups to large multi-provider organizations
The access path
FHIR R4SMART App LaunchOAuth 2.0NextGen Enterprise REST APIs
AGIMAN connects through the NextGen API Developer Program. On NextGen Enterprise the practice authorizes access through the Enterprise REST APIs, and on NextGen Office through the FHIR R4 and SMART App Launch APIs, in both cases over OAuth 2.0. We map each reviewed note, ICD code, and CPT code to the fields your NextGen instance accepts. The first export path is scoped to your encounter and document types and tested against your own instance before go-live, so nothing posts to a real chart until you have seen it land correctly.
The NextGen export path is scoped to your encounter and document types and tested against your own instance before go-live.
The workflow
From the exam room to NextGen, 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 the follow-up task and schedule note.
Review and sign
The clinician approves
The clinician reviews the draft note and the suggested codes, edits anything that needs changing, and signs. Nothing moves to NextGen until the clinician has signed off.
Sync
Post back to NextGen
The signed note and approved ICD and CPT codes post to the patient chart through the NextGen Enterprise REST APIs or the NextGen Office FHIR R4 API, mapped to the encounter and document fields your instance accepts.
After sign-off
What AGIMAN hands back to NextGen.
Chart note to the encounter
The reviewed and signed note maps to the encounter document fields in NextGen, so the clinician's final text lands in the right place on the chart.
Codes for the claim
The ICD and CPT codes the clinician approved attach to the encounter, ready for the practice to carry into the billing workflow in NextGen Enterprise or NextGen Office.
Letters and orders mapped
Referral letters, patient handouts, and intake and visit forms are prepared as documents the clinician can confirm and file to the chart through the approved access path.
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 NextGen until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
NextGen, answered.
Where does the visit audio and transcript live?
On the AGIMAN appliance inside your practice network. Room audio, transcripts, and drafts stay local, and no internet connection is needed to transcribe or draft. Exports to NextGen use only the access path your practice approves, and a BAA is available.
How does AGIMAN reach our NextGen instance?
Through the NextGen API Developer Program over OAuth 2.0. NextGen Enterprise uses the Enterprise REST APIs, and NextGen Office uses the FHIR R4 and SMART App Launch APIs. We scope and test the export path against your own instance before go-live.
Does AGIMAN write to the chart on its own?
No. A clinician reviews and signs every note and approves the ICD and CPT codes before anything posts to NextGen. AGIMAN drafts and maps the work, the clinician keeps the judgment, and the practice keeps the final say on what reaches the chart.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside NextGen.
Buy the appliance and room devices, then scope the NextGen export path with us. We test it against your instance before it is turned on.