What a DON Looks for in an AI Documentation Vendor
with Sarah K., DON · Director of Nursing, Texas home health agency
Sarah has evaluated four AI documentation vendors in the past year. She walks through her checklist — what makes a vendor pass the compliance committee, what makes them get rejected, and the one question she asks every demo that decides whether the conversation continues.
Key takeaways
- The compliance committee is the gatekeeper. Lose them and the deal is dead.
- Auto-submit to the EMR is an immediate no — every record needs human-in-the-loop.
- The question that decides every demo: 'Will you sign a BAA before pilot?'
- Accuracy claims without a HITL layer are red flags, not green flags.
Transcript (excerpt)
Sarah, you've evaluated four AI documentation vendors in the past year. What's your filter?
First filter is compliance. If they can't articulate their BAA, SOC 2, and human-in-the-loop story in the first ten minutes of the demo, the conversation is over.
What's the most common red flag?
When the vendor says 'fully autonomous documentation.' That's an immediate no. We need a human in the loop on every clinical record. The risk to the agency is too big otherwise.
And the question that decides the deal?
'Will you sign a BAA before we start the pilot?' If the answer is anything other than yes, we don't proceed.
Full transcript publishing with the audio. Subscribe for new episodes.