By Cătălin Andrei Bora · Founder, re:solved
AI Automation for Healthcare: HIPAA, GDPR, and the Self-Hosted Option
What is built at Multidiet, what remains a scenario and how to check data access and external processing. Hosting does not guarantee compliance.

Healthcare has more repetitive admin work than almost any other sector. Appointment reminders, intake forms, insurance follow-ups, prescription refills, no-show recovery. It's also the industry where handing that work to a cloud AI tool is the most dangerous. Patient data isn't just sensitive; it's regulated by name in HIPAA and GDPR.
Hosting alone does not establish who sees data. We check access, providers and contracts. Live agents use re:solved’s server in Timișoara and the OpenAI API under a data-processing agreement.
What healthcare teams actually want to automate
These are possible scenarios, not existing booking or reminder deployments. At Multidiet the built agent handles intake and triage.
- appointment scheduling, rescheduling and reminders across WhatsApp, SMS and email
- new-patient intake forms and triage questions before the first visit
- insurance eligibility checks and prior-authorisation follow-ups
- prescription refill requests routed to the right clinician
- no-show recovery and waitlist backfilling
- post-visit follow-ups, satisfaction surveys and review requests
None of that is clinical decision-making. All of it touches Protected Health Information (PHI) under HIPAA or special-category personal data under GDPR, which is exactly why the tool that does it can't be a random SaaS chatbot.
What HIPAA requires (the short version)
HIPAA doesn't ban AI. It requires that any service touching PHI is a Business Associate under a signed Business Associate Agreement (BAA), that access is auditable, and that the covered entity. The clinic. Remains accountable. In practice, three things follow:
- You need a BAA with every vendor that can see PHI, including AI providers. Consumer versions of ChatGPT, Claude, Gemini, and most Zapier/Make setups don't come with one.
- You need audit logs: who accessed what, when, and why. "The AI did it" is not an acceptable answer.
- You need a minimum-necessary discipline: the agent should see only the data it needs for the task, not the whole record.
The clinic stays liable no matter how many vendors sit between it and the patient. Signing a BAA transfers some risk, but not accountability.
What GDPR adds for European clinics
Health data is a "special category" under Article 9 of GDPR. The highest sensitivity tier. On top of the usual GDPR duties, that means an explicit legal basis (usually explicit consent or a specific healthcare provision), a Data Protection Impact Assessment (DPIA) before deploying the AI system, and much stricter rules on international transfers.
If patient data leaves the EU/UK on its way to a US cloud AI provider, you need a documented transfer mechanism and a very good reason. "The tool is convenient" is not a reason a regulator will accept. We covered the general GDPR picture in our post on giving customer data to an AI. The healthcare rules are the same principles, one notch stricter.
Why self-hosted AI is the honest answer for clinics
Live agents run in isolated instances on re:solved’s server in Timișoara. Message text is sent to the OpenAI API under a data-processing agreement. Entirely local hosting and processing are design options, not descriptions of live deployments. Local hosting alone does not guarantee compliance.
We do not promise compliance from hosting. Process, access and providers must be checked together.
What a self-hosted clinic agent looks like in practice
A hypothetical example, not an existing deployment, could include:
- reads incoming WhatsApp and email messages, classifies them (booking, refill, question, complaint)
- checks the practice-management system for open slots and books or reschedules directly
- could send reminders at times agreed in the specification, with exceptions handed to staff
- collects intake answers through a secure link and attaches them to the patient's record
- escalates anything clinical to a human. The agent never gives medical advice
Fully local processing is a design option. Live agents run in isolated instances on re:solved’s server in Timișoara, and message text is processed by an external provider under a data-processing agreement.
Cloud vs self-hosted for a clinic (side by side)
| Concern | Standard cloud AI | Self-hosted AI agent |
|---|---|---|
| Where PHI lives | Vendor servers, often outside EU/US clinic jurisdiction | Hosted on our server in Timișoara, or on your premises on request |
| BAA / DPA | Only with specific enterprise tiers | Check providers and contracts |
| Audit logs | Vendor-provided, limited scope | Full logs of what the agent sent, available to you |
| International transfers | Common, needs SCCs and DPIA | Depends on processing and providers |
| Training on your data | Depends on tier and settings | Depends on configuration and contracts |
| Fit for clinical use | Ambiguous; case-by-case legal review | Requires legal review |
Five questions to ask any AI vendor selling to a clinic
- Will you sign a HIPAA BAA (or an Article 28 GDPR data-processing agreement) for this deployment?
- Where, physically, does patient data live during processing and at rest?
- Is patient data ever used to train or improve any AI system?
- Can the solution run entirely on our own infrastructure if we need it to?
- What does the audit log look like, and how long is it retained?
A serious vendor answers all five in two sentences each. Vague answers, jargon, or "our lawyers are working on it" are the signal to walk away. Our guide on how to choose an AI automation agency has more questions worth borrowing.
What it costs. And what it saves
The 30 minute conversation is free. The specification costs 400 EUR, credited against the build if you sign within 60 days and free with an existing DIGIVEST strategy or feasibility study. A build starts at 1,500 EUR, fixed from the specification. Monthly operation for agents connected to business systems starts at 250 EUR.
We have no measured hours saved or reduction in no-shows for this scenario. At Multidiet, the built agent handles intake and triage, and reports contain counts only.
Frequently asked questions
Is AI automation HIPAA compliant?
Hosting alone does not establish who sees data. We check access, providers and contracts. Live agents use re:solved’s server in Timișoara and the OpenAI API under a data-processing agreement.
Can a clinic use ChatGPT for patient communication?
Hosting alone does not establish who sees data. We check access, providers and contracts. Live agents use re:solved’s server in Timișoara and the OpenAI API under a data-processing agreement.
What does 'self-hosted AI' mean for a clinic?
Live agents run in isolated instances on re:solved’s server in Timișoara. Message text is sent to the OpenAI API under a data-processing agreement. Entirely local hosting and processing are design options, not descriptions of live deployments. Local hosting alone does not guarantee compliance.
Do we still need a DPIA if the AI is self-hosted?
Assess the need for a DPIA based on risk. Local hosting does not automatically remove international transfers or provider access.
Will an AI agent give medical advice to my patients?
Kara at Multidiet explains the programme and checks that lab tests are present without interpreting values. Cases requiring medical decisions go to practice staff. It does not handle bookings or reminders.
Want to see what this looks like for your clinic?
Book a 30 minute conversation. In 30 minutes we look at one process that costs you time. We tell you honestly whether an agent can take it over and what it would cost. No sales presentation.
Related reading: Is it safe to give your customer data to an AI? GDPR and automation, explained · What to look for in an AI automation agency · AI automation for law firms (self-hosted legal agents) · AI automation services. Managed roles overview
Related reading
- What to Look For in an AI Automation Agency (+ Red Flags)
A practical buyer's guide for founders: what to ask, what to verify, and how to tell a partner that runs your operation from a vendor that ships a slide deck.
- Two rules, both correct: what the EU AI Act actually asks of a business using an AI assistant
European law says a conversational system must tell people it isn't human. A client's brand guidelines said never sound technical with patients. Both rules were correct. Here's how we resolved it. And what the AI Act actually asks of an ordinary business.
- AI Automation for Law Firms: Scenarios and Boundaries
Hypothetical scenarios for intake, documents and deadlines. We have no law-firm client. Check data processing before construction.
