Breach Risk Assessment When an n8n Workflow Sent PHI to a Non-BAA Model
Under the HIPAA Breach Notification Rule, a disclosure of PHI not permitted by the Privacy Rule is presumed to be a breach unless your risk assessment demonstrates a low probability of compromise. For a workflow that sent PHI to a model provider without a BAA, that means documenting four factors in writing: the PHI involved, the recipient, whether the data was acquired or viewed, and mitigation. Runtime policy enforcement reduces recurrence by acting on model calls before they leave your environment. The notification decision itself is a legal judgment for counsel.
Runtime controls that stop the same path from recurring
- 1
Allow
The call goes to an approved, BAA-covered endpoint and the payload fits policy. The decision is recorded.
- 2
Redact
PHI is detected and removed or masked in the payload before the model call, when the use case does not need it.
- 3
Block
The destination is not an approved endpoint, or the payload contains PHI that policy does not permit for that destination.
- 4
Escalate for human approval
The call is ambiguous or high-impact and is held until an authorized person decides.
Evaluation questions for any runtime control
- Does it act on each model call and tool call from a workflow node, before the request leaves the environment?
- Can it detect PHI in the payload and redact, block or escalate by policy, and what are its detection accuracy limits?
- How does it decide that a destination endpoint is approved, and who maintains the BAA-status inventory?
- What does each decision record (identifiers, timestamp, policy, data classes), how long is it retained, and can it be exported for an assessment or audit?
- When policy evaluation fails or an approver does not respond, does it fail closed or fail open?
What the rule requires, and where the burden sits
As of November 2026, 45 CFR 164.402 defines a breach as the acquisition, access, use or disclosure of PHI in a manner not permitted under subpart E that compromises the security or privacy of the PHI. Such an event is presumed to be a breach unless the covered entity or business associate demonstrates a low probability that the PHI has been compromised. The burden of that demonstration is on the entity. If it is not made, the presumption stands.
The BAA requirement is what makes the n8n scenario a question at all. HHS guidance states that a covered entity may disclose PHI to a business associate only with satisfactory assurances in the form of a written BAA. For cloud service providers that create, receive, maintain or transmit ePHI, HHS states that a BAA is required. Applying that reasoning to an AI model API is an inference from the cloud guidance, and counsel should confirm how it applies to your provider.
If notification is required, a covered entity must notify each affected individual without unreasonable delay and no later than 60 calendar days after discovery, except as provided in 45 CFR 164.412. HHS guidance adds that breaches affecting 500 or more individuals require prompt notice to the Secretary, and media notice applies when more than 500 residents of a state or jurisdiction are affected. If the assessment demonstrates a low probability of compromise, notification is not necessary.
Applying the four factors to a workflow-to-model transmission
HHS states that the assessment must be thorough, completed in good faith, and reach conclusions that are reasonable given the circumstances. It also encourages entities to consider additional factors where the facts warrant. For a workflow disclosure, the four factors map to concrete questions.
Nature and extent of the PHI: which data elements were in the payload sent to the model, such as identifiers, clinical content or free-text notes, and how many individuals were affected. Workflow nodes often pass whole records or concatenated text, so the payload as transmitted matters more than the intended design.
The recipient: who received the data and what obligations bind them. Without a BAA, the provider's contractual terms on retention, abuse monitoring, training use and deletion carry most of the weight, and they should be obtained from the provider in writing.
Acquired or viewed: whether the PHI was actually acquired or viewed, or only transmitted and not retained. This is the hardest factor to answer from your own systems, because it depends on what the provider did after receipt.
Mitigation: the extent to which the risk has been reduced. Written deletion confirmation from the provider, revoked credentials, and a disabled workflow path are mitigation evidence. The fix to the workflow is relevant here, but it does not by itself show that the data already sent was not compromised.
Where the evidence is usually incomplete
Assessment gaps tend to cluster in four places. First, the payload record. Whether workflow execution history retains the full request body, only metadata, or nothing depends on how the instance was configured, so confirm what your own history actually holds before relying on it. If payloads were not retained, reconstructing the data elements means working from the workflow definition, the source systems and sampled executions, and the assessment should say so plainly.
Second, the execution scope. Notification duties attach to each individual whose PHI was, or is reasonably believed to have been, accessed, acquired, used or disclosed. Enumerating the affected executions and mapping them to individuals is therefore a required step, not a refinement.
Third, the provider's side. Retention, abuse-monitoring and training-use terms, and any deletion confirmation, exist in the provider's contract and documentation rather than in your logs. Fourth, the discovery date. Record who discovered what and when, because the 60-day period runs from discovery.
HHS ransomware guidance illustrates the same principle for incident evidence: what communications occurred, which systems were affected and whether activity propagated all feed the four-factor assessment. For a model-call event, workflow execution logs, node configurations and provider records play that role. State each gap in the written assessment, along with the conservative assumption you applied, so that counsel can review the reasoning rather than only the conclusion.
Enforcement evidence and 164.312(b) audit controls
A risk assessment is only as strong as the record behind it. Evidence generated at the point of enforcement can include the decision taken, the policy applied, the data classes affected, a timestamp, and the workflow and execution identifiers. That is the material an assessor needs to answer the data-element and scope questions, and the material an auditor needs when reviewing audit controls under 45 CFR 164.312(b). It also shows that a prior gap was closed and that the control continues to operate.
Trussed enforces policy in the execution path across models, agents, tools and MCP servers, at the level of individual interactions and tool calls, with allow, redact and block outcomes and escalation for human approval. Enforcement produces continuous audit-ready evidence mapped to HIPAA, and deployment is self-managed in the customer cloud with configurable retention and data residency. Trussed runs in production with healthcare and pharma organizations.
The limits are worth stating. Enforcement reduces the chance of a repeat disclosure and improves the evidence record. It does not decide whether a past event is a reportable breach, and it does not replace the written assessment, the provider's confirmations or counsel's review.
From discovery to defensible record
Establish discovery
Record who found the disclosure and when, since the 60-day outer limit runs from discovery.
Scope executions
Identify affected workflow runs and the individuals whose PHI was sent.
Assess four factors
Write each factor up with the evidence relied on and any gaps.
Prevent recurrence
Enforce policy on model calls in the execution path.
Close the path, and keep the record
Talk to an expert about enforcing policy on model and tool calls in the execution path, and about the audit-ready evidence that supports your assessment record.
Request a Demo