Most clinicians sign their first usable note in under fifteen minutes. The flow is the same on day one as it is on day three hundred. Here is what the path looks like.
Pick your template before you record
Open Templates from the sidebar (/apps/custom-prompts). Pick the format that matches the visit type you are about to
record. SOAP for a routine medication-management visit, Intake for a new patient, DAP for therapy, BIRP for supervised
practice. The selected template is what AriaMD will fill in. You can switch templates per encounter, so a daily clinic
with mixed visit types is fine.
If your practice has a custom format, paste a sample note into the template editor and AriaMD converts it into a reusable template. Most practices have one custom template running by the end of the first afternoon.
Start the recording
From the sidebar, click New Recording for a guided per-patient flow, or AriaMD for ambient capture without a patient selected upfront. New Recording is the simpler path on day one because the patient is associated before you start. You will be prompted for microphone permission. Grant it. The browser remembers the setting per device.
Record the visit the way you normally would. Talk to the patient. The system captures the audio and produces a transcript, a structured note in your selected template, an AI peer review, and a list of suggested ICD-10 codes.
Review the draft
When AriaMD finishes processing (typically under sixty seconds for a routine visit), the encounter moves from Processing
to Ready. Open the encounter (/sessions/view/<encounter-id>). The Note tab is the primary view. The Transcript, Peer
Review, and Context tabs are available for cross-reference if you need them.
Read the note. Edit anything that needs editing. The diff between the draft and your final version is what trains the personalization layer, so edit the way you would normally chart.
Accept the codes
The right sidebar shows suggested ICD-10 codes with a confidence score for each. Accept the ones that fit your assessment, reject the ones that do not, and add codes manually if something is missing. Coding suggestions read your assessment, so a clean assessment produces clean codes.
Sign
Click Sign. The encounter locks. Downstream events fire: claim creation if billing is enabled, AI Timeline update, Treatment Pulse refresh on the next load, and any automations you have wired to the Encounter Signed event.
If you need to revise after signing, use Unsign. The encounter returns to editable state. The downstream systems handle versioning per their own rules.
That is the full loop. Most providers run it three or four times on day one and then stop thinking about the steps.