Resource Library · November 2026

Building AI Systems for HIPAA-Regulated Work

Design tests for AI that may touch protected health information — not a compliance certificate, not legal advice, and not a claim that a system “meets HIPAA.”

18 pages28 min readAdvancedCompanion workbook included

By AsymiLink Meta · Published · Updated

Request the guide and workbook

Summary

Design tests for AI that may touch protected health information — not a compliance certificate, not legal advice, and not a claim that a system “meets HIPAA.” Frameworks excerpted on this page: Fourteen design tests (excerpt); What this framework will not do. A 18 pages November 2026 document, with a companion workbook.

  • Fourteen design tests, including questions for counsel: whether this is PHI, what your role is, and whether a Business Associate Agreement is needed.
  • A Business Associate Agreement is a contract, not a badge this framework will issue.
  • Hosting is a design input, decided before a case is funded.
  • This document is not legal advice, not a compliance certificate, and not a finding that a system meets HIPAA.

A crawlable plain-text copy of this page is also at /resources/hipaa-compliant-ai.txt. The canonical URL is https://asymilinkmeta.com/resources/hipaa-compliant-ai.

Written for Privacy, compliance, clinical, technology and operations leaders whose AI work may touch protected health information, and the sponsors who have to fund it.

What's in this framework

This 18-page framework is a set of design tests for AI that may touch protected health information. It is not a compliance certificate, not legal advice, and not a claim that a system “meets HIPAA.” The library has sometimes described this document as a technical blueprint for full regulatory compliance. It is not that. We will not certify a system, and we will not close a legal question that belongs to counsel and the privacy officer.

What it is, instead, is fourteen tests to apply before a first case is funded, and to the systems that are already running. Several of those tests are questions for counsel — including whether a given record, prompt, log or corpus is protected health information, what your role is, and whether a Business Associate Agreement is the contract that has to be in place. A missing answer is a reason to pause, not permission.

It is written for privacy, compliance, clinical, technology and operations leaders, and for the sponsors who have to fund the work. A companion workbook holds the tests, a role-and-contract sheet, and a hosting sheet. A completed workbook means the tests were asked. It is not a certificate, and it is not a finding that a system is aligned with HIPAA.

How the tests are meant to be used

T1, T2, T3 and T13 are questions for counsel. This document will not close them, and it will not recite a date by which a rule applies. What applies, and when, is a question for your counsel and your privacy officer, asked in time, with a written answer. A review at the end of a build is a failed test.

Hosting is a design input, not a later preference. If data cannot leave, or should not leave, the offline deployment guide in this library is the companion, and that decision is made before the case is funded. A pilot that has already sent data to a hosted tool “to see if it works” has already taken the decision. Minimum necessary, named access, and an audit trail that can show what the system saw, what it proposed, what it did, and who approved it, are architecture.

The honest first case is bounded: a named job, a named corpus, a person on the action that matters, and a switch-off. “AI across the clinical record, unsupervised,” is not a first case this framework will recommend. The governance framework and the LLM security paper in this library are companions for the path around this work. This framework will not stand in for them, and it will not stand in for counsel.

Fourteen design tests (excerpt)

The same fourteen tests apply to a document assistant and to a system that would inform a clinical or billing decision. T1, T2, T3 and T13 are counsel questions. The full wording is in the PDF and the workbook.

  1. T1

    Is this PHI, or might it be? Counsel and the privacy officer decide whether a given record, prompt, log, recording or corpus is protected health information.

  2. T2

    What is our role? Covered entity, business associate, subcontractor, or something else. The role is a legal conclusion. This framework will not make it.

  3. T3

    If a Business Associate Agreement is needed, is it in place? A BAA is the HIPAA contract that governs how PHI is used, safeguarded and reported. It is a contract, not a badge.

  4. T4

    Minimum necessary, in the design. Is the system designed to see, retrieve and retain only what the job needs? A generous corpus or a wide log is a failed test.

  5. T5

    Access is named, and is role-based. Named users, no shared “the model” account that can see every chart.

  6. T6

    An audit trail that can show what the system saw, what it proposed, what it did, who approved it, and who the patient was, when that is the work.

  7. T7

    A person can stand behind a decision that affects a patient. The gate is architecture. This framework will not describe an unsupervised high-consequence system as a first case.

  8. T8

    Hosting is decided before the case is funded. A pilot that has already sent data “to see if it works” has already taken the decision.

The remaining tests cover training and reuse, a switch-off, what people who are affected can be told, and counsel asked in time (T13). The complete fourteen are in the guide and the workbook.

What this framework will not do

The cover and the opening are explicit about the limits. They are part of the method, not a disclaimer tacked on.

  1. Not a certificate

    A completed workbook, or a system that was designed with these tests, is not a finding that the system “meets HIPAA,” and it is not a certification we will issue.

  2. Not legal advice

    What applies, the role you have, and whether a BAA is required, are questions for counsel and the privacy officer. This document will not close them.

  3. Not a date

    This document will not recite a date by which a rule applies, and it will not be used as a calendar.

Get the guide and workbook

Enter your name, work email and company. The files appear on this page immediately. A backup download link is also emailed when email delivery is available.

By requesting this resource you agree that AsymiLink Meta may contact you about it. See our Privacy Policy and Terms of Use.

Frequently asked questions

Does this framework certify that a system meets HIPAA?

No. It is a design framework, not a compliance certificate and not a finding that a system meets HIPAA. A completed workbook means the tests were asked. It is not a certification.

Is this legal advice?

No. Several tests are questions for counsel and the privacy officer — including whether this is PHI, what your role is, and whether a Business Associate Agreement is needed. This document will not close those questions.

What is a Business Associate Agreement in this framework?

The contract that governs how PHI is used, safeguarded and reported, where that contract is required. It is a contract, not a badge this framework will issue.

What is in the companion workbook?

The fourteen tests, a role-and-contract sheet, and a hosting sheet. For each test: a sentence, a named owner and a piece of evidence. A completed workbook is not a certificate.