NoteShield: AI Quality Checks

NoteShield runs a series of automated checks on session notes before they are signed. These checks fall into three categories: compliance, clinical accuracy, and completeness. Compliance checks verify that the note includes all fields required by common ABA payer guidelines, such as start and end times that match the billed units, a description of the setting, and identification of the supervising BCBA when applicable.

Clinical accuracy checks look for internal consistency within the note. For example, if the note references a target that is not on the client's current treatment plan, NoteShield will flag this discrepancy. It also checks whether the described session duration is plausible given the number of targets addressed and whether the language used is clinically appropriate rather than overly vague or generic.

Completeness checks ensure that no required sections are left blank or contain only minimal content. A note that lists targets but provides no description of the client's response will be flagged as incomplete. NoteShield also checks for common omissions like missing behavior data when the note mentions challenging behavior, or missing parent communication when the session type typically includes a caregiver component.

When NoteShield completes its review, it displays feedback directly in the note editor using a color-coded system. Green indicators mean the note passed all checks in that category. Yellow indicators represent warnings, which are suggestions for improvement that do not block signing. Red indicators are errors that must be resolved before the note can be signed.

Each flag includes a brief explanation and, where applicable, a suggested fix. For example, a yellow warning might read: "Session duration is 3 hours but only 2 targets are documented. Consider adding detail about how session time was allocated." A red error might read: "Start time is after end time. Please correct the session times." Clicking on any flag scrolls the editor to the relevant section of the note so you can make corrections in context.

You can dismiss yellow warnings if you determine they are not applicable to a specific situation. Dismissed warnings are logged for audit purposes but do not prevent signing. Red errors cannot be dismissed and must be addressed. This tiered approach ensures that critical compliance issues are always resolved while giving clinicians flexibility on stylistic or situational recommendations.

Organization administrators can adjust NoteShield's behavior through the Settings menu under Quality Assurance. The configuration panel lets you control which checks are active, which severity level each check carries, and whether certain checks apply only to specific note types or provider roles.

For example, you might configure NoteShield to require a parent communication summary on all parent training notes but make it optional on direct-service notes. You can also set minimum word counts for narrative sections, require specific phrases or disclaimers that your payers mandate, and define custom checks based on your organization's internal documentation standards.

The sensitivity slider controls how aggressively NoteShield flags potential issues. At the lowest setting, only clear errors are flagged. At the highest setting, NoteShield provides detailed feedback on writing quality, clinical specificity, and documentation best practices. Most organizations find that a moderate setting works well for day-to-day use, with the highest setting reserved for training new staff or preparing for audits.

Beyond individual note checks, NoteShield provides aggregate reporting that helps clinical directors identify documentation trends across their organization. The NoteShield Dashboard, accessible from the Reports menu, shows the most commonly triggered flags, the percentage of notes that pass all checks on the first attempt, and trend lines over time.

These reports can be filtered by provider, note type, date range, and flag category. If you notice that a particular clinician consistently triggers the same warning, that is an opportunity for targeted training. If a specific check is being dismissed frequently across the entire organization, it may indicate that the check needs to be recalibrated or that team-wide training is needed.

The dashboard also includes a "Documentation Health Score" for each provider, calculated from their NoteShield pass rates, average time to resolve flags, and the frequency of dismissed warnings. This score is intended as a coaching tool, not a punitive measure. Supervisors can use it during performance reviews to have data-driven conversations about documentation quality and to track improvement over time.