Compliance Guide | Healthcare

    n8n HIPAA BAA: What Health Systems Need Before PHI Enters a Workflow

    Treat n8n Cloud as unavailable for PHI unless a HIPAA business associate agreement covering your plan and deployment model is executed in writing before any PHI enters the platform. HHS states that using a cloud service provider to maintain ePHI without a BAA is a violation. If no BAA exists, a health system can keep PHI out of the workflows, self-host within its own environment under its own safeguards, or select a BAA-eligible alternative. A BAA is one dependency among several, alongside connected AI services, third-party nodes and audit evidence.

    Before PHI enters any workflow

    1. Confirm a written BAA exists for the exact platform, plan and deployment model, or confirm none is needed and document why.
    2. Inventory every model provider, third-party node and tool the workflow can call, with BAA status for each.
    3. Name an owner for technical safeguards and audit evidence.
    4. Define and test the control that detects, redacts or blocks PHI at each boundary where a BAA is missing.
    5. Confirm that audit records show what each workflow was permitted to do and what it did with PHI.
    6. Record the decision path, rationale and evidence retention period.

    What a BAA settles, and what it does not

    HHS guidance says a covered entity or business associate may use a cloud service to store or process ePHI, provided it enters into a HIPAA-compliant BAA with the provider that will create, receive, maintain or transmit ePHI on its behalf, and otherwise complies with the HIPAA Rules. In that guidance, maintaining ePHI includes processing it as well as storing it. A hosted automation platform that handles PHI during workflow executions therefore falls inside the BAA analysis.

    The agreement has to exist before PHI does. HHS treats use of a cloud provider to maintain ePHI without a BAA as a violation of the HIPAA Rules. It also states that a provider meeting the definition of a business associate must comply with the applicable HIPAA provisions whether or not a BAA has been signed. The customer's exposure is not removed by the provider's own obligations.

    A signed BAA is also not a complete compliance answer. HHS expects compliance with the rest of the HIPAA Rules, and any service level agreement should be consistent with the BAA. The practical test for n8n Cloud is therefore a contractual one: is there an executed agreement that names the plan and deployment model your teams will use? Until there is, assume the answer is no and design accordingly.

    The three decision paths compared

    Each path moves responsibility to a different place. The table summarizes where it lands and what remains as residual risk.

    • Keep PHI out of the workflow: Responsibility: you must prevent ePHI from ever reaching the hosted platform, including in payloads, prompts, error messages and stored execution data. Residual risk: a single misrouted record is a use without a BAA, so the control must be enforced rather than assumed.
    • Self-host inside your environment: Responsibility: the Security Rule safeguards remain with the covered entity, including access control, credential handling, transmission protection and audit controls. Residual risk: you own the operational burden, and connected services still need their own analysis.
    • Choose a BAA-eligible alternative: Responsibility: obtain a written HIPAA-compliant BAA, confirm it covers the plan and features you will use, and align the SLA with it. Residual risk: the platform's downstream services and subcontractors still need coverage.

    Self-hosting: control moves to you, obligations do not disappear

    The Security Rule applies to ePHI whoever hosts it, and the 164.312 technical safeguards apply to covered entities and business associates alike. Self-hosting changes who operates the infrastructure. It does not change who is accountable. Assign a named owner for technical safeguards and audit evidence before the first PHI workflow goes live.

    Whether the software vendor needs a BAA in a self-hosted model depends on the same test HHS applies elsewhere: does the vendor create, receive, maintain or transmit PHI on your behalf? Counsel should answer that question for the specific deployment and any support or telemetry arrangements, and record the reasoning.

    In practice, a self-hosted deployment needs credentials for connected systems held in a managed secret store, access limited to named roles, encrypted transmission, and records of who changed which workflow and when. Treat community and third-party nodes as software that will touch PHI, and review them accordingly.

    Connected AI services and third-party nodes

    The BAA obligation attaches to any provider that creates, receives, maintains or transmits ePHI on the customer's behalf. That reasoning does not stop at the automation platform. A workflow that sends a clinical note to a model provider, or passes a patient identifier to an external tool, creates a separate disclosure that needs its own assessment. HHS also notes that BAA requirements run from business associates to their subcontractors.

    Build an inventory of every service a workflow can call: model providers, third-party nodes, webhooks and downstream tools. For each, record whether it can receive PHI, whether a BAA or subcontractor arrangement covers that use, and which workflows depend on it. A platform-level BAA does not cover a model endpoint you configure yourself, and self-hosting the orchestrator does not make an external model call internal.

    This inventory is also the basis of the keep-PHI-out path. If a service has no BAA, the workflows that reach it must be unable to send it PHI.

    Audit controls and the evidence you will need

    Audit controls are one of the technical safeguards under 164.312(b). For workflow automation, the question an auditor is likely to ask is two-sided: what was the workflow permitted to do with PHI, and what did it actually do? A workflow definition answers the first only if it is versioned and its approvals are recorded. The second requires records of each model interaction and tool call, including what was sent, what was withheld or altered, and what was blocked.

    Plan evidence around the decision path you chose. For keep-PHI-out, retain proof that blocking worked, such as records of attempted PHI transfers and their outcomes. For self-hosting, retain access records, change history and the review of each connected service. For a BAA-eligible alternative, retain the executed agreement, the subcontractor chain and the SLA review.

    Whichever path applies, keep a decision record stating the path selected, the rationale, the BAA or subcontractor chain, and the retention period for evidence. A 2025 proposed update to the Security Rule would add documentation requirements, but it is a proposal as of November 2026. The current text of 164.312 remains the operative standard.

    Enforcing PHI policy in the execution path

    Procedural rules alone are weak for the keep-PHI-out path, because workflows change and free text is unpredictable. Detecting PHI in free text is imperfect, so enforcement works best at the point where data leaves your boundary: at the model call or tool call, with an explicit outcome of allow, redact or block.

    Trussed enforces policy in the execution path for models, agents, tools and MCP servers, at the level of individual interactions and tool calls. Policy is enforced at runtime, not reviewed after the fact, with the outcomes allow, redact and block. Each enforcement decision generates audit-ready evidence mapped to HIPAA, including 164.312(b) audit controls. Trussed supports self-managed deployment in the customer cloud, with configurable retention and data residency, and runs in production with healthcare and pharma organizations.

    Trussed does not substitute for a BAA. It addresses a different question: whether PHI was allowed to reach a given model or tool, and whether you can show it.

    Decision paths when no BAA is available

    Keep PHI out

    Prevent ePHI from reaching the hosted platform and be able to prove it.

    Self-host

    Run the software in your own environment and own the Security Rule safeguards.

    Choose an alternative

    Select a platform that will sign a BAA and keep the SLA consistent with it.

    Map your PHI workflows to a decision path

    Talk through your workflow inventory, connected AI services and audit evidence requirements with a Trussed expert.

    Talk to an Expert