Building an AI scribe under a client's HIPAA program
Back to Blog
Healthcare

Building an AI scribe under a client's HIPAA program

UT
Unicodez Team
Product Team
November 4, 2026
8 min read

An ambient scribe listens to a visit and drafts a note. The privacy and security rules for that work sit in the clinic's program. When Unicodez builds this kind of product, we work under our healthcare clients' BAAs and HIPAA requirements. This article is the practical version of that sentence.

The US Department of Health and Human Services describes a business associate as a person or company that creates, receives, maintains or transmits protected health information for a covered entity, and it requires a contract, the BAA, that sets out what that company may do with the information. The overview is here: HHS guidance on business associates. If your company will store audio, transcripts or draft notes for a clinic, you should expect to be inside that contract. Do not start the build on a handshake and 'we'll paper it later'.

The Privacy Rule governs when protected health information may be used and disclosed. The Security Rule requires covered entities and their business associates to protect electronic protected health information with administrative, physical and technical safeguards. HHS publishes both: the Privacy Rule and the Security Rule. A product team implements the controls the client's program and the BAA require, and it can show its work.

For a scribe, the minimum necessary principle should shape the recording itself. Capture the encounter you were asked to document. Do not keep an always-on microphone in the clinic. Make the start and stop of a recording obvious to the clinician. If the visit includes a stretch that should not be in the note, the product needs a pause, not a promise that the model will 'know' to ignore it. Spell out, in the scope, whether audio is kept after the transcript exists, for how long, and who can play it back.

The draft is not the chart. Nothing should be filed until a clinician has accepted it. That is a product decision and a privacy decision at the same time. A note that lands in the EHR without review can mix a model's guess with the legal record. Build the review into the screen the clinician already expects to sign, show what was inferred, and store the fact of acceptance: who, when, and which version. If they discard the draft, the discard should be as durable as the save.

Access control is ordinary and non-negotiable. Each user is a named person. Roles decide who can start a visit, who can read a draft, and who can push it to eClinicalWorks or whichever system the client uses. Staff do not share logins. Your own engineers do not get production charts as a debugging convenience. If someone on your team needs a production record to fix a defect, that access goes through the client's process, is time-limited, and is logged. The Security Rule's technical safeguards, described by HHS, are the reason this is not optional polish.

Encryption covers the obvious paths: TLS in transit, encryption at rest for audio, transcripts and notes, and separate environments so a demo database is never the clinic's database. Audit logs should answer a clinic manager's question six months later: who opened this encounter, who changed the draft, who sent it to the EHR, and whether that send succeeded. Logs are not a marketing feature. They are how you respond when the client's privacy officer asks.

Subprocessors belong in the BAA conversation before they belong in the architecture diagram. A speech vendor, a model host and a cloud region are all places protected health information may go. Name them to the client. Confirm the region. Confirm that each of those companies is covered by the client's paperwork, not by an assumption that 'the cloud is compliant'. If a vendor will not sign what the client requires, pick a different vendor or do not send them the audio.

Retention and deletion should be a setting, not a surprise. Agree how long audio and drafts live, what happens when the engagement ends, and how a clinic can ask for deletion. HHS also explains individual rights of access in the Privacy Rule. Your product will not usually be the system of record. The EHR is. Say that clearly so nobody tells a patient to come to you for their chart.

Write the security story in the same language as the product story. A one-page description is enough at the start of a build: what you collect, where it goes, who can see it, how long you keep it, and how a clinician stops a bad note. Attach it to the BAA. When the scope changes, a new specialty, a new write into the EHR, a new vendor, update that page. The failure mode we see is a control that was true for version one and no longer true for version two.

If you are hiring an implementation partner, ask three questions. Will you work under our BAA and HIPAA requirements? Where, exactly, will audio and notes sit? Who approves a note before it reaches the chart? A useful partner can answer all three from the work itself.

UT
Unicodez Team
Product Team