Practice Operations
Security Documents to Request Before You Sign a Vendor
The documents to request in one email before an AI vendor connects to athenaOne, what each artifact proves, and the replies that should stop a signature.
Most vendor security reviews fail in a specific and avoidable way. The practice asks good questions, gets reasonable answers, and never sees a document. Six weeks later the vendor is connected to athenaOne and the entire review exists as a memory of a video call.
Questions are the right instrument for a conversation. Artifacts are the right instrument for a file. A question can be answered by whoever is on the call, in the register they choose, and nothing about the answer persists. A document has a scope section, a report date, an auditor and a list of systems, and it either covers the thing you are buying or it does not.
So the ask is not a longer questionnaire. It is a short list of documents, sent in one email, early enough that the answers can still change the decision. What follows is that list, what each item actually proves, and the specific responses that should slow a signature down.
Send the request as one email, before the demo sequence ends
The timing matters more than the wording. A document request sent after the practice has decided, during contracting, becomes a formality that nobody has time to read against a go-live date. Sent while two vendors are still in play, the same request carries weight, and the speed and completeness of the reply is itself a data point.
One email, one list, and a stated deadline that is generous but real. A serious vendor has these on a shelf and returns most of them in days. A vendor that treats the request as unusual is telling you something before you have read a single page.
The document set
1. The business associate agreement, unexecuted, for review
Request the actual BAA you would sign, not a summary and not a statement that one exists. The useful reading is in the clauses most summaries skip: breach notification timing, subcontractor flow-down, what happens to your data at termination and how long return or destruction takes, and whether the vendor reserves any right to use your data outside operating your own workflows.
That last clause is where the real variance is. Two BAAs can both be HIPAA-compliant while one quietly permits de-identified use for product development and the other does not.
2. The SOC 2 Type II report, and specifically its scope section
Ask for the report under NDA, then read the scope before the opinion. A Type II report covers a defined period and a defined set of systems. A vendor whose report scope excludes the platform you are buying has answered a different question than the one you asked, and the cover page will not tell you that.
Read three things: the report period and how recently it ended, the systems named in scope, and the exceptions. Exceptions are normal. A report with none at all, or one whose period ended eighteen months ago, deserves a follow-up rather than a filing.
3. Current certification artifacts, with scope attached
Whatever frameworks the vendor claims, ask for the certificate or letter with the scope statement. The Pretty Good AI platform has attained HITRUST i1 certification. ISO 27001 certification carries a scope statement naming what is covered. Both are specific documents and neither is a logo.
Two cautions here, because this is the single easiest place to be misled. First, a certification in progress is not a certification held, and a vendor describing an in-flight audit in the present tense is a serious signal about everything else it has told you. Second, do not accept a marketplace listing or a directory flag as evidence of any vendor’s certification status. Those fields are frequently self-reported and they are wrong in both directions. Ask for the artifact.
4. The subprocessor list, and the agreement covering each one
Every vendor uses other vendors. The question is which ones touch protected health information and whether each of those is covered by a signed business associate agreement. Request the list naming each subprocessor that processes PHI, what it does, and written confirmation that each one has signed.
For an AI vendor, ask one additional thing explicitly: whether the model providers that process patient data in production operate under zero-data-retention terms. A vendor that has not negotiated that, or cannot describe its terms, has a gap in the part of the stack that is newest and least examined.
5. A written statement on training data
Ask in writing whether your patient data is used to train AI models, the vendor’s own or anyone else’s. Get the answer as a document rather than as reassurance on a call, because this is the clause most likely to be read differently later by two people who both remember the conversation well.
6. The penetration test summary and the security contact
A recent third-party penetration test summary, with its date, and the name and address of whoever at the vendor receives a security report. The second item sounds trivial and is not. A practice that discovers something odd on a Friday should not be finding out then that there is no route to anyone.
7. What the integration can actually reach inside athenaOne
This is the item generic security questionnaires miss entirely, and for an athenaOne practice it is the one that most changes the risk. Ask what the integration reads, what it writes, and which parts of the record are in scope at all. A vendor should be able to tell you, in plain terms, the surfaces it touches and the ones it does not.
Depth of integration is not a risk in itself. An integration nobody can describe is.
Read the replies for shape, not just content
A practice administrator with an afternoon cannot audit a SOC 2 report, and does not need to. Three patterns tell you most of what the file will tell you later.
What arrives, and how fast. A vendor returning six of seven items in four days with one explained gap is operating a real security program. A vendor returning a slide deck is not.
Whether the scope sections match the thing you are buying. This is the single highest-value five minutes in the entire review. Scope mismatch is common, rarely volunteered, and visible to anyone who reads the paragraph.
Whether any claim softens when written down. A certification that was held on the call and is in final review in the email is the answer, and the call was the error.
A multi-site group, the request that changed the shortlist
A multi-specialty group running several locations on athenaOne sent this list to two finalists in the same week, with a ten-day deadline. The first returned everything but the penetration test summary inside a week, flagged that its SOC 2 period had closed four months earlier with the next report in progress, and named its subprocessors with BAA confirmation for each.
The second answered warmly, offered another call, and sent a one-page security overview. Asked again for the SOC 2 scope section, it turned out the report covered a predecessor platform, and the product being sold had been rebuilt since.
Nothing in that outcome required security expertise. It required asking for documents early enough that the answers could still matter, and reading two scope paragraphs.
Where this lands in practice: the document request belongs in the same window as the athenahealth Authorization and Consent form work, because both are gating paperwork that a practice usually discovers late. The conversational version of this review, with the questions to ask out loud, is in the vendor security questions set. Use the questions on the call and this list in the email. They are not the same instrument and they do not substitute for each other.
A review that produces a file beats a review that produces a feeling. The file is what the practice still has in a year, when the person who took the call has moved on and the integration is still connected.
Ready to See It in Action?
See what Pretty Good AI puts in front of a reviewer before anything connects to athenaOne
Schedule a Demo →Written by Kevin Henrikson