Skip to content

EHR integration

Draft the visit locally, write the signed note back to Veradigm

AGIMAN captures the encounter on an appliance inside your practice 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 back to Veradigm EHR.

  • HIPAA compliant
  • Runs on your network
  • Clinician signs every note
Veradigm logo
System
Veradigm
Category
EHR / data
Used by
Independent and multi-specialty ambulatory practices
Connects over
Veradigm Developer Program (Veradigm Connect)

The connection

How AGIMAN connects to Veradigm.

What Veradigm is

Veradigm, formerly Allscripts, builds ambulatory EHR and practice management software, including Veradigm EHR, Practice Fusion, and Veradigm Practice Management. It also runs a separate health data and research business. The clinical products serve outpatient physician practices, from independent offices to mid and large multi-specialty groups.

Who runs it

Independent and multi-specialty ambulatory practices

The access path

FHIR R4SMART App LaunchOAuth 2.0OpenID Connect

AGIMAN reads encounter and patient context through Veradigm's FHIR R4 endpoints, authorized with SMART App Launch over OAuth 2.0 and OpenID Connect. To write the signed note and codes back, AGIMAN uses Veradigm's Unity API, the bidirectional path Veradigm Connect documents for posting clinical and demographic data to Veradigm EHR and Practice Management. We register in the Veradigm Developer Program, scope the export to the fields your instance accepts, and test it against your own sandbox and instance before go-live. This is a standards-based connection we build and support, not a certified Veradigm partnership or an endorsement.

The Veradigm export path is scoped to your instance and tested in the Veradigm Connect sandbox and your own system before go-live. It is a standards-based connection truesilver builds and supports, not a certified Veradigm partnership.

The workflow

From the exam room to Veradigm, with you in control.

1

Capture

Record the visit in the room

AGIMINION captures the encounter audio in the exam room. The audio, transcript, and drafts stay on the appliance on your practice network, with no internet connection needed to transcribe or draft.

2

Draft

Note and codes ready for the chart

AGIMAN drafts the chart note in the clinician's style and suggests ICD and CPT codes for the encounter. It can also prepare referral letters, patient handouts, and intake forms tied to the visit.

3

Review and sign

The clinician reviews every line

The clinician opens the draft, edits anything, confirms the codes, and signs. Nothing leaves the appliance until a person approves it.

4

Sync

Write back through Unity to Veradigm EHR

The signed note, the confirmed ICD and CPT codes, and the supporting documents map to the matching fields in Veradigm EHR through the Unity API. AGIMAN writes a review log that records what was sent.

After sign-off

What AGIMAN hands back to Veradigm.

Signed note

Chart note to Veradigm EHR

The clinician-signed note maps to the encounter in Veradigm EHR through the Unity API, in the structure your instance accepts.

ICD / CPT

Confirmed codes for the claim

The ICD and CPT codes the clinician confirmed travel with the note, so your billing team starts the claim from reviewed coding instead of rekeying it.

Documents

Letters and forms attached

Referral letters, patient handouts, and intake forms drafted for the visit are saved to the patient record for a person to send or finalize.

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 Veradigm until the clinician reviews and signs.
  • Exports use the access path your practice approves, with a BAA available.

Questions

Veradigm, answered.

Where does the visit audio and the draft note live?

On the AGIMAN appliance inside your practice network. Room audio, transcripts, and drafts stay local, and the appliance does not need an internet connection to transcribe or draft. The note and codes leave only through the Veradigm export path you approve, and a BAA is available.

How does AGIMAN connect to Veradigm EHR?

AGIMAN reads encounter context through Veradigm's FHIR R4 API using SMART App Launch over OAuth 2.0, and writes the signed note and codes back through Veradigm's Unity API, the bidirectional path in Veradigm Connect. We scope and test that path against your own sandbox and instance before go-live. It is a standards-based connection we build and support, not a certified Veradigm partnership.

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 Veradigm. AGIMAN handles the administrative drafting and the field mapping, and the clinical judgment and the signature stay with the provider.

Get started

Run AGIMAN alongside Veradigm.

Buy the appliance and room devices, then scope the Veradigm export path with us. We test it against your instance before it is turned on.