remy.CareNotes

Documentation check

Find the bad note before the auditor does

It reads every case note against your state's own documentation rules and hands your QA lead a fix-it list.

Case-note export

8 notes · 4 writers

scheduled CSV over SFTP

remy.

reading against the state manual

'refused' flagged

State says write 'chose not to.' Cites the rule.

Filler flagged

'No problems, good day' says nothing about the person.

3 notes pass clean

Well-written notes come back untouched.

Works with Therap's External Data Feed, or any notes CSV

How documentation check works

01

Point it at the export

Therap's External Data Feed drops case notes as CSV on a schedule. remy reads that file - or any notes CSV you upload.

02

It checks every rule

Prohibited language, staff-judgment phrasing, boilerplate filler, missing person-centered substance - the same published rules a state reviewer uses.

03

Writers get specifics

Each finding cites the rule and shows the fix. 'Use chose not to' teaches more than 'non-compliant note' ever did.

Documentation check features

Found in last night's notes

“He refusedhis shower…”

state rule: write “chose not to”

5 of 8 notes need a fix

Rule citations

No mystery findings - every flag names the state rule it comes from.

Filler detection

Catches the copy-pasted 'AM hygiene completed' that shows up in forty notes a month.

Clean notes pass

It's calibrated against the state's own compliant sample notes - good writing isn't nitpicked.

Per-writer patterns

See which habits repeat across a writer's notes, so coaching is specific instead of general.

24

findings in an eight-note sample export, each citing its rule.

0

flags on notes written in the state's own compliant voice.

100%

of notes read - an auditor samples, this doesn't.

What changes for the agency

01

Audit-ready files

Problems surface months before a reviewer would find them.

02

Better writers

Specific, cited feedback changes habits faster than trainings.

03

Less QA drudgery

Your lead reviews findings instead of reading everything.

04

Fewer paybacks

Documentation problems are the leading driver of clawbacks.

The visible difference

By handGeneric AIremy.
CoverageSpot checksWhatever you pasteEvery note in the export
FindingsReviewer's judgmentVague suggestionsCites the state rule
Good notesAlso re-readRewritten anywayPass untouched
Time per batchHoursOne note at a timeSeconds

Questions?

Which states' rules does it use?+

The scan ships with published state documentation standards (Virginia's HCBS rules are the reference set) and the rule lists are configurable per state and per program.

Does it rewrite the notes?+

It can propose a compliant rewrite, but the writer approves it - and the original is always preserved. Nothing is silently edited.

We're not on Therap - can we use it?+

Yes. Any CSV of notes works, and CareNotes' own visit notes are checked as they're written.

Will it flag everything and exhaust my staff?+

It's tuned against the state's own compliant samples, so well-written notes come back clean. In our test sets, compliant notes produced zero findings.

Ready to try documentation check?

The trial workspace opens with demo data already in it. 14 days free, no card.