Capture
AGIMINION records the room
The AGIMINION device captures the visit audio in the room and sends it to the AGIMAN appliance on the practice network. Audio and transcript stay local, with no internet connection needed to transcribe.
All integrationsCanvas Medical
EHR integration
AGIMAN drafts the visit, your team signs it into Canvas Medical
On a Canvas Medical practice, AGIMAN captures the visit on a local appliance, drafts the note in the clinician's style, and suggests ICD and CPT codes. The clinician reviews and signs, then the approved note and codes map to your Canvas instance over the Canvas FHIR API.
- HIPAA compliant
- Runs on your network
- Clinician signs every note
- System
- Canvas Medical
- Category
- EHR
- Used by
- Tech-enabled care delivery, value-based, and virtual care groups
- Connects over
- Canvas FHIR API and SDK
The connection
How AGIMAN connects to Canvas Medical.
What Canvas Medical is
Canvas Medical is an API-native ambulatory EHR built for care delivery organizations that want to shape their own clinical workflows. It exposes a FHIR R4 API and the Canvas SDK, a Python plugin runtime that runs inside the Canvas server and reacts to events on the instance. It is run by tech-enabled groups such as virtual care companies, value-based and at-risk care organizations, specialty telehealth groups, and independent primary care practices.
Who runs it
Tech-enabled care delivery, value-based, and virtual care groups
The access path
FHIR R4OAuth 2.0Canvas SDK plugins
AGIMAN writes the approved note and codes to your Canvas instance through the Canvas FHIR API, using OAuth 2.0 credentials registered the same way your team registers any Canvas API client. Documents, referral letters, and intake forms map to the matching Canvas FHIR resources, and a Canvas SDK plugin can place each exported item where it belongs in the chart. The first export path is scoped to your fields and tested against your own Canvas instance before it is turned on. Nothing reaches the chart until a clinician signs.
The Canvas Medical export path is tested against the Canvas FHIR sandbox, and the first production path is scoped and tested against your own Canvas instance before go-live.
The workflow
From the exam room to Canvas Medical, 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 any referral letters, patient handouts, and intake or visit forms the visit calls for.
Review and sign
The clinician owns the chart
The clinician reviews the draft note and the suggested codes, edits anything, and signs. AGIMAN does not write to the chart and does not replace clinical judgment.
Sync
Map to your Canvas instance
After sign-off, the note, codes, and documents map to the matching Canvas FHIR R4 resources on your Canvas instance over the Canvas FHIR API. A Canvas SDK plugin can route each item to the place your team expects in the chart.
After sign-off
What AGIMAN hands back to Canvas Medical.
The chart note
The reviewed, signed note maps to the encounter on your Canvas instance through the Canvas FHIR API, written in the clinician's style.
Encounter codes
Suggested ICD and CPT codes the clinician approved attach to the encounter, so coding and the claim start from the documented visit.
Letters and forms
Referral letters, patient handouts, and intake or visit forms map to the matching Canvas FHIR document and form resources 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 Canvas Medical until the clinician reviews and signs.
- Exports use the access path your practice approves, with a BAA available.
Questions
Canvas Medical, answered.
Where does the visit data live on a Canvas practice?
Room audio, transcripts, and drafts stay on the AGIMAN appliance on your practice network. Only the note, codes, and documents a clinician has approved leave the appliance, and they travel to your Canvas instance over the Canvas FHIR API. A BAA is available, and AGIMAN is HIPAA compliant.
How does AGIMAN connect to Canvas Medical?
AGIMAN uses the Canvas FHIR R4 API with OAuth 2.0 credentials registered on your Canvas instance, and a Canvas SDK plugin can route each exported item into the chart. The export path is scoped to your fields and tested 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 every code first. AGIMAN maps only the approved text and codes to Canvas, and the documents it prepares are left for a human to confirm or send.
Other EHR integrations
See all integrations
Get started
Run AGIMAN alongside Canvas Medical.
Buy the appliance and room devices, then scope the Canvas Medical export path with us. We test it against your instance before it is turned on.