Back to Columns
AI & DX13 min read

Designing Security for an AI EMR: A Shared-Responsibility and Zero-Trust Approach

July 28, 2026

Designing Security for an AI EMR: A Shared-Responsibility and Zero-Trust Approach
Share this article

A cloud AI EMR layers cloud infrastructure, AI processing, voice input, and multi-tenancy on top of EMR functionality. So "the vendor takes care of security" is a misconception; the starting point is the shared-responsibility model—separating where the vendor's duty ends and your institution's responsibility begins.

This article organizes AI-EMR security design across five lenses: (1) shared responsibility, (2) zero trust, (3) data protection, (4) AI-specific risks, and (5) availability/BCP. See also the companion pieces on implementing the three-ministry guidelines and the legal view of generative AI.

Disclaimer: This article is general information, not professional advice. Confirm the latest primary sources and consult experts.

1. Shared responsibility: where does the vendor's duty end?

Cloud responsibility is split between vendor and customer (institution) by delivery model (IaaS/PaaS/SaaS). Even with a SaaS AI EMR, responsibilities always remain with the institution.

AreaWhere responsibility sits (SaaS example)
Data center, physical, infrastructureVendor
Platform/app vulnerability managementVendor
User accounts and privilege designInstitution
Device and network managementInstitution
Proper handling of input dataInstitution
Operational rules, training, auditInstitution

No matter how robust the product, operational gaps—shared accounts, excessive privileges, use on personal devices, dormant ex-employee accounts—break safety. Clarify the accountability boundary in contract and spec, and design your side of it. This mirrors the accountability-boundary thinking the three-ministry guidelines require.

2. Zero trust: don't rely on the perimeter alone

When an AI EMR is used from the cloud and many devices, "safe because it's inside the LAN" collapses. Design to verify at each access under zero trust (trust nothing unconditionally).

  • Multi-factor authentication (MFA)
  • Least privilege (role-based access control): grant only the minimum needed per role/task
  • Device trust evaluation (managed device, OS/security state)
  • Micro-segmentation to limit lateral movement after a breach

3. Data protection: encryption, key management, tenant isolation

  • Encryption at rest and in transit.
  • Separated key management: keep key management apart from the data and control key access with least privilege.
  • Tenant isolation: on multi-tenant platforms, isolate data logically (physically where needed) per institution and per user, blocking cross-tenant access.
  • Backup: keep recoverable (ideally immutable) backups against tampering and ransomware.

4. AI-specific risks

  • Blocking training use (ZDR/opt-out): contractually (DPA) guarantee that input patient data is not used for model training/improvement—especially when passing patient data to generative AI (see the legal view).
  • AI access boundary: if the AI EMR references/acts on external data or tools via RAG/agents, explicitly limit what the AI can touch. Design boundaries so indirect prompt injection via external documents cannot trigger unintended access or actions.
  • Voice data handling: for voice-to-chart, clarify whether recordings are stored, retention, deletion, and access control.
  • Audit-log integrity: record AI input/output and finalization in a tamper-evident form to preserve authenticity (who finalized).

5. Availability/BCP: don't stop care

Security includes availability, not just confidentiality. Because an AI EMR outage can halt care, design:

  • Redundancy and procedures for degraded/offline operation
  • Backup and restore verification (set RTO/RPO)
  • Incident response and communication for outages/attacks

Conclusion: design, contract, and operation as one

AI-EMR security is complete neither by product selection nor operation alone. The key is a unified design: set the boundary via shared responsibility (design), guarantee it via DPA/SLA (contract), and run it via zero trust, least privilege, and audit (operation).

  1. Clarify the accountability boundary (design your residual responsibility)
  2. Zero trust (MFA, least privilege, device evaluation)
  3. Encryption, key management, tenant isolation
  4. AI-specific risks (no training use, access boundary, voice, audit logs)
  5. Availability/BCP

Pottech develops AI-native healthcare information systems and supports ISMS certification and three-ministry compliance. If you want to discuss AI-EMR security design including regulatory compliance, please get in touch.

References

This article is general information, not professional advice. Confirm the latest primary sources and consult experts.

Share this article

Related Articles

Healthcare Security

Implementing the Three-Ministry Guidelines: Practical Steps, Accountability, and Risk Assessment

Beyond 'what are the guidelines': a practitioner's walkthrough of implementation—asset inventory, risk assessment, the three storage principles, accountability boundaries with cloud vendors, auditing, and BCP.

July 28, 2026
AI & DX

Using MCP with an EMR: How AI Reads and Writes the Chart, and What It Requires

Using MCP with an EMR means building a path through which AI can reference chart data and, where appropriate, act on it. There are three architectural patterns, each with different capabilities and prerequisites. We cover how it works, how to phase it in, and what to ask vendors.

August 28, 2026
AI & DX

Permission Design and Security Checks for MCP in Healthcare

MCP is a mechanism for connecting—and connecting means more paths along which information moves. For medical data, how should permissions be designed, what belongs in audit logs, and which failure patterns must be avoided? We map this against Japan's Three-Ministry Guidelines.

August 28, 2026
AI & DX

Using Generative AI in Medical Institutions: A Practitioner's Guide to Law, Vendor Selection, and Security

An in-depth guide to generative AI in medical institutions—covering Japan's APPI with article references, the three-ministry guidelines, and medical-device (SaMD) classification, plus the entrustment/third-party distinction, cross-border transfer, the shared-responsibility model, and prompt-injection defense.

July 28, 2026
AI & DX

Is AI Voice Charting Secure? Checking Personal Data Protection and Guideline Compliance

Is it safe to entrust patient conversations to AI voice input? A practitioner's take on AI voice-chart security—the entrustment/third-party distinction, three-ministry compliance, encryption/key management/audit logs, and the AI's access boundary—with article references and official sources.

July 16, 2026
AI & DX

What Is AI in Electronic Medical Records? What It Can Do, Three Types and How to Choose

What AI in an EMR can do, the different ways AI is built in, and what to check before adopting it, organized for clinic directors and office managers.

July 14, 2026
AI Karte

Explore AI Karte

An AI-native EHR connecting reception, documentation, accounting, claims, and analytics into one cycle.

View the product page

AI Karte as an Option

Most of the problems covered in this article are what AI Karte, our AI-native EHR for clinics, is built to handle. Start by seeing what it is.