More time for learners.
Less paperwork on your mind.
Focus on the child in front of you.
The AI Note Auditor reviews supervision and session notes and asks one question: would this documentation hold up if a payer reviewed it? It looks for missing elements, inconsistencies, and billed services that do not match the note, so your team can fix gaps before the claim goes out.
Select the full screen icon in the video player for the best viewing.
It tells you what is missing. You fix it. Off it goes.
Run the auditor before a clinician signs a note, after it is signed, or both.
The auditor reviews the note
Each note is checked against Hi Rasmus base rules and your organization’s own learnings.
Clinicians see what to fix
Findings appear in the final step before signing, so the clinician can fix issues in real time.
The note passes
Passed means the auditor found nothing that would likely lead to a denial.
Illustrations of the flow. Product screens vary.
Flagged while you write, before the claim goes out
Two ways to audit
Run it before a clinician signs, so they can fix issues in real time. Or review notes in bulk after signing, as a safety net for supervisors, QA and admin teams.
Built on payer requirements
Base rules cover medical necessity: session details, whether the billed service matches what is described, goals and progress, interventions, and how the client responded.
Learns your rules
Add learnings for your own requirements, such as a payer-specific rule. Write them yourself, or rate findings with a thumbs up or down so the rules sharpen over time.
Results and strictness you set
Each note is Passed, Flagged or Failed. Choose Lenient, Balanced or Strict to set how serious a gap has to be before a note is flagged or failed.
Want the full walkthrough?
Watch the workshop for a longer look at how the auditor fits into day-to-day documentation.
Select the full screen icon in the video player for the best viewing.
Questions we hear
What does the auditor check?
It checks notes against Hi Rasmus base rules built from common payer requirements, plus your organization’s learnings. It looks for gaps that often lead to payer questions or denials, such as missing elements, inconsistencies, or a billed service that does not match the note. It does not grade writing style or clinical quality.
Does a fail stop a clinician from signing?
No. Clinicians can still sign and save a note regardless of the result or findings.
Does a pass guarantee a payer will accept the claim?
No. The auditor is a review assistant, and your team always makes the final call.
When can I run the auditor?
Before a clinician signs a note, after it is signed, or both. Before signing, clinicians can fix issues in real time. After signing, supervisors, QA or admin teams can review notes in bulk.
Can I review results for a batch of notes?
Yes. Add auditor result columns to a table view on the Activities reporting page to filter to what failed, confirm what passed, and catch notes that were edited after their audit ran. Your role needs the View Auditor Feedback privilege.
How do I add it to my account?
The auditor is a paid add-on. A Manager level user opens the Subscription page, selects Edit Subscription, and turns on AI Note Auditor under Add-Ons, then chooses which roles can use it on the User Privileges page. Our getting started guide walks through it. If you are new to Hi Rasmus or have questions, fill out our form and it routes you to the right person on our team.
Is my data safe?
The auditor is powered by Google Gemini and is fully HIPAA compliant. Your organization’s data is not used to train AI models.
Curious to learn more?
Tell us a bit about your team and we will connect you with the right person.
Talk with our team
