Industries · Healthcare
PHI in a test fixture is still PHI. A pattern of it ends the BAA.
Agents read fixtures, logs, and exports. PHI reaching an uncovered model provider is the pattern a covered entity must cure or terminate over. Every session is checked against your BAA list and activity-review duties before the code ships.
Pre-production only: how agents change your systems, not how those systems run.
- Privacy Officer
- Security Officer
- Quality and Validation
- VP of Engineering
Session replay
Illustrative · demo data

Agent activity on ePHI systems is recorded for review. Evidence exports exclude raw prompts and source.
Industry trend
83%
of developers use AI tools or agents at work
Stack Overflow 2026 (opens in a new tab)Oct 2026 · n = 17,464
24%
say their organization provides approved AI tools and guidance for using them
Stack Overflow 2026 (opens in a new tab)Oct 2026 · n = 13,167
6.6%
trust AI output for important work decisions
Stack Overflow 2026 (opens in a new tab)Oct 2026 · n = 14,304
Source: Stack Overflow Developer Survey 2026, self-reported; data under ODbL 1.0. AutoDevOps is not affiliated with Stack Overflow.
01Where agents meet your obligations
Three sessions your examiner will ask about.
01
An agent opens a patient export to reproduce a bug.
In review mode, the read is blocked. If it ran anyway, a critical finding opens.
HC.NO-RAW-PHI-EXPORTS02
PHI-tagged context reaches a model provider without a BAA.
The finding names the provider and the session and cites 45 CFR 164.502(e).
HC.BAA-PROVIDERS03
An agent changes the FHIR integration that writes to the EHR.
The edit waits for an independent approver. The decision feeds activity review.
HC.EPHI-CHANGE-REVIEW
02The authorization at stake
Your customer’s compliance depends on terminating you.
HIPAA makes your customer cure a business associate’s pattern of violation or terminate the BAA.
At stake
For a business associate, the BAA itself. For a covered entity, its standing with OCR.
01
Complaint or breach report
OCR asks for the activity-review record. Unreviewed agent sessions are what it shows.
02
Resolution agreement and corrective action plan
Most OCR enforcement ends here: a payment, a published agreement, and years of reporting to HHS.
03
Civil money penalties and state attorneys general
Tiers turn on what you knew. State attorneys general enforce too.
04
BAA termination
Your customer must cure your pattern of violation or terminate the contract.
Sources: 45 CFR 164.308(a)(1)(ii)(D); 164.312(b) · HHS OCR resolution agreements · 45 CFR 160.404(b)(2); 42 U.S.C. §1320d-5(d) · 45 CFR 164.504(e)(1)(ii)
A penalty with no settlement is rare. Corrective action plans are routine, and a terminated BAA is the one a vendor does not recover from. The record is evidence for your privacy officer and OCR, not a finding of compliance.
03Obligations checked
Every clause, checked on every session.
Review and forbidden-action rules hold the agent before it acts. Provider, data, and intent rules record after.
HC.BAA-PROVIDERS
PHI reaches BAA-covered providers only
Regulation · HIPAA Privacy and Security Rules · 45 CFR 164.502(e), 164.308(b)(1), 164.314(a) (business associate assurances and contracts)
HC.EPHI-CHANGE-REVIEW
Changes to ePHI systems get an independent reviewer
Regulation · HIPAA Security Rule · 45 CFR 164.308(a)(1)(ii)(D), 164.312(b)
HC.NO-RAW-PHI-EXPORTS
Agents never open raw PHI exports
Regulation · HIPAA Privacy Rule · 45 CFR 164.502(b) (minimum necessary)
HC.PART11-CHANGE-CONTROL
Validated GxP systems keep change control
Regulation · 21 CFR Part 11 · 21 CFR 11.10(e), 11.10(k)(2) (audit trails, revision and change control)
Plus 5 baseline obligations every pack checks
BASE.SECRET-CONTEXT
Credentials stay out of agent context
Framework · ISO/IEC 27001:2022 · Annex A 5.17 (authentication information)
BASE.DPA-PROVIDERS
Model calls stay on the DPA subprocessor list
Contract · Customer data processing agreement · DPA subprocessor schedule
BASE.PROD-CHANGE-REVIEW
Infrastructure changes get an independent approver
Framework · SOC 2 Trust Services Criteria · CC8.1 (change management)
BASE.AGENT-SYSTEM-REVIEW
Agent prompts, tools, and guardrails get an independent reviewer
Internal policy · AI system change policy · Customer AI system change policy; EU AI Act Art. 14 (human oversight)
BASE.NO-FORCE-PUSH
Agents never rewrite shared history
Internal policy · Secure development standard · Protected branch policy
Templates ship without dollar figures; the register shows a labeled illustrative band until you add yours. Pre-run checks use review mode, a customer-cloud CLI capability.
04Controls evidenced
Controls this evidence supports.
From the public control catalog. Evidence mappings do not establish compliance.
- HIPAA.AUD-01Activity records45 CFR 164.312(b): audit controlsEvidence mapping
- HIPAA.REV-02Activity review45 CFR 164.308(a)(1)(ii)(D): information system activity reviewReview signal
- HIPAA.BA-03Covered model providers45 CFR 164.308(b)(1): business associate contracts and other arrangementsReview signal
- EUAI.ART12-02Agent event recordsArticle 12: record-keepingEvidence mapping
05For your risk and insurance reviewers
Evidence an AI liability underwriter can rate.
- Verified controls
- Gate coverage, independent review rate, and self-approvals.
- Change velocity
- Weekly changes to prompts, tools, or guardrails, and the share with a stated reason or approval.
- Autonomy
- Unattended sessions and the allow, hold, and block mix.
- Obligation posture
- Findings by status, priced per obligation.
Production behavior is out of scope and marked that way. The packet is evidence for a reviewer. It is not insurance, a certificate of coverage, or a premium quote.
Sources and citations · 5 rules referenced
- HIPAA Privacy Rule
45 CFR 164.502(b) minimum necessary; 164.502(e) business associates
- HIPAA business associate contracts
45 CFR 164.504(e)(1)(ii): cure the breach or terminate the contract
- HIPAA Security Rule
45 CFR 164.308(a)(1)(ii)(D) activity review; 164.312(b) audit controls
- 21 CFR Part 11
§11.10(e) audit trails; §11.10(k)(2) revision and change control
- FDA software change guidance
Deciding When to Submit a 510(k) for a Software Change to an Existing Device (October 2017)
Your privacy and security officers confirm which repositories touch ePHI and which providers your BAAs cover. Clinical pilots use metadata-only capture, and its database migration and live validation remain release gates. For your counsel and compliance team, not legal advice.
Bring one healthcare obligation
We run it against your agents’ recorded sessions and hand you the findings, priced exposure, and evidence packet.
