Home / Insights
Healthcare AI Subprocessors: Map Who Handles Practice Data
Map healthcare AI subprocessors by data, purpose, access location, applicable BAA chain, change notices and deletion boundaries with a practical worksheet.
Healthcare AI subprocessor reviews should map each downstream provider to the practice data it handles, the purpose, processing and access locations, applicable agreements, change notices and deletion boundaries. Ask for a product specific map, not just a company wide supplier list. A subprocessor list is not certification or proof of compliance, and a signed agreement does not demonstrate that every data flow follows its terms. For owners and operations teams, the useful procurement output is a worksheet that answers: who receives what, why, from where, under whose responsibility, and what happens when that arrangement changes or ends? This article proposes a practical worksheet for that task. It is not a replacement for broader clinical validation, security assessment or legal advice. Start with the service your practice will actually use For this worksheet, a subprocessor means a downstream provider engaged by your AI supplier to process practice data in delivering the service. Contract definitions and legal roles can differ. A supplier's published list may include companies that never receive data from your particular product, alongside providers enabled only by optional features. Identify the contracted legal entity, product, subscription configuration, deployment region and integrations. Include test environments and support pathways. Ask the supplier to mark which downstream providers apply to that configuration and which are excluded. Keep the dated response with the relevant contract version. The NIST AI RMF Playbook's GOVERN 6 guidance addresses risks from third party software, data and supply chains. It supports examining dependencies across the product lifecycle. NIST describes the Playbook as voluntary suggestions, not a checklist. The worksheet below is Eunoia's proposed operating method, not a NIST certification standard. Build one worksheet row for each material data handling role Use separate rows when one provider performs different functions with different purposes or retention rules. Cloud hosting and model inference should not share a vague entry called “infrastructure”. Inference means running the model to produce an output from an input. Give every row an evidence reference, practice owner, unanswered question and resolution date. Use “unknown” rather than a blank cell or an inferred answer. Ask the supplier to confirm the completed map in writing. Store supporting documents securely without copying patient content into procurement correspondence. 1. Provider identity and connection to your product Record the downstream legal entity and service name, the party that engages it, and the feature using it. Distinguish a model developer from the company actually operating the endpoint that receives prompts. Ask whether further providers sit beneath that endpoint. Check supporting functions too: transcription, hosting, monitoring, support ticket systems and human quality review. These are questions to investigate, not assumptions that every AI product uses all of them. Where the supplier says a listed provider does not receive your data, request a product specific explanation. 2. Data received and processing purpose Record the data classes transmitted, created or retained at that step. For documentation tools, these might include audio, transcripts, prompts and draft notes. Scheduling tools may use contact details, appointment information and message text. Diagnostic logs may contain identifiers or fragments of content. Separate delivering the contracted service from support, abuse monitoring, evaluation, analytics, model training and other improvement purposes. Ask whether feedback or support uploads create a new route outside the normal workflow. Require the supplier to explain whether each use is necessary, optional or disabled in your configuration. A “no training” statement should identify the covered inputs, outputs, feedback and downstream providers. It does not, by itself, answer whether people can inspect content or how long logs persist. For HIPAA regulated arrangements, HHS business associate guidance explains that permitted uses and disclosures depend on the agreement and applicable law. A supplier cannot justify a new purpose merely by adding another company to a list. 3. Processing, storage and human access locations Create separate entries for processing location, primary storage, backups and remote access. “US hosted” does not answer whether support staff elsewhere can view a transcript. Ask which countries and regions apply, who can authorise exceptional access, and whether customer settings constrain every downstream route. Record whether access is automated, human or both. For human access, ask about roles, approval, time limits and access evidence. Distinguish permission to access from routine use of that permission. HHS cloud computing guidance does not impose a blanket prohibition on overseas ePHI storage or processing. It says geographic risks and enforceability considerations belong in risk analysis and management. Do not translate that into automatic approval of any location. Other applicable requirements and negotiated commitments still need review. 4. Applicable agreements and the downstream BAA chain Where HIPAA applies, identify the business associate agreement, or BAA, between the practice and its direct business associate. Then identify responsibility for the agreements at subsequent subcontracting steps. Request confirmation of the legal entities, covered service, effective status and relevant restrictions. HHS explains that subcontractors creating, receiving, maintaining or transmitting protected health information on behalf of a business associate are themselves business associates. The upstream business associate must ensure applicable subcontractors accept the same restrictions, conditions and requirements. This does not mean the practice must sign a separate BAA directly with every downstream company. Do not exclude encrypted storage from the map simply because the provider cannot read it. HHS's cloud guidance says a cloud provider maintaining ePHI on behalf of a covered entity or business associate remains a business associate even without the decryption key. Veterinary teams can use the same worksheet for client details, staff information and animal records. Assess the applicable privacy, contractual and professional duties rather than assuming HIPAA governs every veterinary dataset. 5. Changes, notices and the practice's response Record the supplier's process for adding or replacing downstream providers, changing purposes, introducing human review or moving processing locations. Capture the notice channel, advance notice commitment, effective date and any contractual objection or termination route. Do not invent a universal notice period or assume the practice has approval rights. Ask whether notices identify the affected product and data classes. A webpage updated without a named recipient may not reach the person responsible for the practice's decision. Allocate a monitored inbox and a deputy reviewer. Keep planned service change notices separate from security incident and breach reporting obligations. They have different triggers. Review each applicable agreement rather than applying one deadline to everything. When a change arrives, compare it with the saved worksheet and record the decision. A different inference provider may require data handling review and targeted output testing. Use the published healthcare AI vendor update change control guide for the testing handoff, rather than expanding this worksheet into a full revalidation programme. 6. Retention, deletion and downstream evidence For each provider and purpose, record what persists, the retention trigger and duration, who requests deletion, and who confirms completion. Include support attachments, logs, temporary model inputs, outputs and derived datasets where they exist. Ask how the direct supplier passes deletion instructions downstream. Distinguish deletion from the active service, backup expiry, restricted retained copies and legal hold exceptions. Request the evidence available for each, without assuming immediate erasure from every backup or guaranteed removal of information from trained model parameters. HHS's business associate contract guidance addresses return or destruction of PHI at termination if feasible, with continuing protections and limited uses where return or destruction is infeasible. Its sample language is not a complete contract or substitute for legal advice. Use the companion healthcare AI retention guide to develop data class schedules. Here, the narrower question is whether each downstream recipient is included in the agreed lifecycle and completion evidence. Work through a hypothetical documentation supplier Suppose an outpatient practice is considering an AI documentation service. The following is illustrative, not a description of a named product or customer. Its worksheet has separate rows for hosting, transcription, note generation and support. The hosting row identifies storage and backup regions. The transcription row records who receives audio and whether humans can review it. The note generation row identifies the operated model endpoint and its input, output and logging boundaries. The support row asks whether staff can upload recordings into tickets, which provider hosts those tickets, and when attachments are deleted. A supplier's “audio removed after processing” statement would not settle the lifecycle of a recording later attached to a support case. The operations lead finds that support access locations are unspecified and that the deletion statement covers only the primary application. These gaps are not proof of non compliance, but they prevent an informed decision on those routes. The practice requests clarification and does not enable the unresolved support upload pathway. If that restriction cannot be enforced, the owner must reconsider proceeding with the service. Turn the worksheet into a procurement decision Before practice data is connected, the owner and relevant specialists should check that: The mapped entities and features match the contracted product and configuration. Each material data route has a stated purpose and accountable upstream party. Processing, storage, backups and human access have location specific answers. Applicable agreements cover the relevant relationships and permitted activities. Change notices reach a named reviewer who can act before the contractual window closes. Deletion commitments describe downstream copies, exceptions and available evidence. Treat unresolved answers according to their consequences. A feature dependent gap may be addressed by an enforceable restriction. An unknown recipient for sensitive clinical content may prevent proceeding. Name who accepts any residual uncertainty and when the restriction or decision will be reviewed. Evidence requests are procurement choices, not universal statutory audit rights. HHS's cloud guidance says HIPAA does not expressly require cloud providers to supply customers with security documentation or allow customer audits, although additional assurances can be negotiated. Agree proportionate evidence requirements instead of promising access the contract does not provide. Frequently asked questions Is a published subprocessor list proof that an AI supplier is compliant? No. It identifies disclosed providers, but does not prove which ones handle your product's data, whether the list is complete, or whether controls and agreements operate as described. Use it to start a product specific worksheet. Connect each provider to data, purpose, locations, applicable agreements, changes and deletion evidence before making the practice's decision. Must our practice sign a BAA with every downstream AI provider? Not simply because a provider appears on a list. Where HIPAA applies, the practice generally contracts with its direct business associate, which must establish the applicable downstream subcontractor agreements. Confirm the actual relationships and covered services with privacy and legal specialists. A separate direct relationship with another provider may need its own assessment and agreement. What should we do when a supplier adds a new subprocessor? Save the notice and compare it with the current worksheet. Identify affected features, data classes, purposes, access locations and lifecycle commitments. Route material changes to the relevant privacy, security and workflow owners, and check contractual response windows. Record whether to accept, restrict, seek clarification or stop the affected route, with a named decision owner. Eunoia Consulting Co.'s team helps healthcare and veterinary organisations turn fragmented data sharing information into practical ownership, lifecycle and third party review controls. Explore our data governance services to discuss a product specific subprocessor worksheet and an accountable process for maintaining it as suppliers change. References HHS: Business Associate Contracts. Supports applicable subcontractor relationships, permitted uses and termination provisions; sample clauses are not a complete legal agreement. HHS: Guidance on HIPAA and Cloud Computing. Applies to covered entities, business associates and cloud providers handling ePHI; addresses encryption, overseas risks and negotiated assurances. NIST: AI RMF Playbook, GOVERN. Provides suggested third party AI and supply chain risk actions, not vendor certification. NIST: AI RMF Playbook overview. Defines the voluntary scope and states that the Playbook is not a checklist to follow in its entirety. This article was produced by the Eunoia Consulting Co. Editorial Team. Eunoia Consulting Co. specialises in AI governance, healthcare operations, and data strategy for healthcare and veterinary organisations.