Back to Columns
Healthcare Security9 min read

The Three Ministries' Two Guidelines Explained Simply: Essential Checks When Adopting an EMR

July 2, 2026

The Three Ministries' Two Guidelines Explained Simply: Essential Checks When Adopting an EMR
Share this article

Key Takeaways

  • The framework consists of MHLW's guidelines for medical institutions (Edition 7.0) and METI/MIC's guidelines for service providers (Edition 2.0).
  • Electronically stored medical records must satisfy authenticity, readability and preservability.

When you consider adopting an EMR or a cloud service, you are certain to come across the term "the Three Ministries' Two Guidelines." However, many find it hard to grasp what exactly they stipulate and what a medical institution should check. This article explains what the Three Ministries' Two Guidelines are in an easy-to-understand way and organizes the points you must check when adopting an EMR.

What Are the Three Ministries' Two Guidelines?

The "Three Ministries' Two Guidelines" is a collective term for two guidelines established by three ministries to handle medical information safely. Their characteristic is that they present the roles of the medical institution side and the system provider side separately for the safe management of medical information systems.

TargetGuidelineJurisdiction
Medical institutionsGuidelines for the Safe Management of Medical Information SystemsMinistry of Health, Labour and Welfare
System/service providersSafety Management Guidelines for Providers of Information Systems and Services Handling Medical InformationMinistry of Economy, Trade and Industry; Ministry of Internal Affairs and Communications

There was a period when the Ministry of Internal Affairs and Communications and the Ministry of Economy, Trade and Industry issued separate guidelines, so it was called "the Three Ministries' Four Guidelines." The two have since been integrated, and the current framework is "the Three Ministries' Two Guidelines."

Why They Matter

An EMR gathers extremely sensitive personal information such as patients' names, diagnoses, and test results. If these are leaked, tampered with, or lost, it harms not only patients but also seriously affects the trust in the medical institution. The Three Ministries' Two Guidelines present the "standards to be observed" for protecting medical information from such risks, and they form the foundation for operating an EMR safely.

Three Basic Principles for the Medical Institution Side

The Ministry of Health, Labour and Welfare's guideline sets out, for electronically stored medical information, meeting the following "three principles of electronic storage" as fundamental:

  • Authenticity: records are created under proper authority, it is clear who created/revised them and when, and they have not been tampered with
  • Readability: content can be displayed or output in a form legible to the naked eye whenever needed
  • Preservability: records are stored in a restorable state throughout the statutory retention period

In addition, operational safety management is required, such as access-permission management, authentication via passwords, backups, and countermeasures against cyberattacks. In recent years, against the backdrop of increasing cyberattacks, the importance of these measures has risen further.

Checkpoints When Adopting an EMR

1. Whether the Product/Provider Complies with the Guidelines

First, confirm that the EMR or cloud service under consideration complies with the provider-side guideline. Ask the vendor to clearly state its "compliance status with the Three Ministries' Two Guidelines."

2. Whether the Point of Responsibility Demarcation (Role Allocation) Is Clear

In the cloud model, the "point of responsibility demarcation"—how far the provider handles security measures and where the medical institution's responsibility begins—is important. Confirm it in the contract and service specifications.

3. Whether the Medical Institution Can Establish Operational Rules

Even if you adopt a guideline-compliant product, it is meaningless without accompanying in-house operational rules such as password management, access permissions, and deleting the accounts of departing staff. Establish your operational structure together with adoption.

4. Backup and Business Continuity

Confirm that there are mechanisms for data backup and recovery to prepare for failures and cyberattacks.

Note That the Guidelines Are Updated

The Three Ministries' Two Guidelines are continuously revised in response to technological progress and new threats. For the medical-institution-facing "Guidelines for the Safe Management of Medical Information Systems," the latest version (Ver. 7.0) has been published. At adoption and during operation, it is important to always refer to the latest version and the official Q&A.

AI Karte's Compliance with the Guidelines

The AI-native EMR "AI Karte" is provided in a cloud environment compliant with the Three Ministries' Two Guidelines, equipped with the mechanisms necessary for safe management, such as access-permission management, authentication, and backups. While consolidating patient information on a single foundation with its integrated receipt computer (rececon), features such as voice input and AI claim checking can also be used safely within the same security standards. We also explain the point of responsibility demarcation and operational structure individually at adoption.

Conclusion

The Three Ministries' Two Guidelines consist of two guidelines—one for medical institutions and one for providers—and present standards for safely protecting medical information. When adopting an EMR, it is essential to check the compliance status of the product/provider, the point of responsibility demarcation, in-house operational rules, and the backup structure, and to refer to the latest version of the guidelines as well. Safe management is not something that ends at adoption; regard it as something to review continuously.

Through providing AI Karte, Pottech aims to be the ideal business partner for clinics—improving the working environment for physicians, nurses, and medical clerical staff, and supporting clinics in fully realizing what they want to achieve.

For more details, please feel free to contact us.

References

Share this article

Related Articles

Healthcare Security

Selecting a Cloud Provider: Seven Things a Hospital Must Check

How a hospital should choose the cloud provider that will hold its medical information: verifying guideline alignment, data residency across production, backups and logs, how to read ISO/IEC 27001 and 27017 certifications, data return on exit, and transparency of subcontracting — set out as tables to use before comparing quotes.

September 14, 2026
Healthcare Security

Breach Reporting Duties: Preliminary and Final Reports, and Notifying Individuals

What healthcare providers in Japan must report when personal data is leaked: when reporting to the Personal Information Protection Commission is required, the two-stage preliminary/final report structure, notifying affected individuals, and why clinical records being special-care-required data changes the threshold.

September 14, 2026
Healthcare Security

Reviewing EMR Access Logs: Detecting and Deterring Improper Viewing

EMR access logs are usually collected and rarely read. Viewing the record of an acquaintance or a well-known patient outside any clinical need is an internal event, not an external attack. This article covers what signals to look for, how to set the cadence and ownership of reviews, and why telling staff that reviews happen is itself a control.

September 14, 2026
Healthcare Security

Endpoint Management: Securing Laptops and Tablets Taken Off Site

Tablets taken on home visits, laptops used from home, staff reading work email on personal phones. How to manage devices once they leave the building, what must be possible when one is lost, and how endpoint management connects to the asset register.

September 14, 2026
Healthcare Security

The Governance Part of the Guidelines: What Executives Are Accountable For

The governance part of Edition 7.0 is written for directors, board members, and administrators. What must executives decide, and what do they answer for? This article covers why outsourcing does not transfer responsibility, and what it means that FY2026 made a dedicated medical information system security manager a condition of the new add-on.

September 14, 2026
Healthcare Security

The System Operations Part of the Guidelines

The system operations part of Edition 7.0 is written for the people who actually run the systems: access control, logging, backups, equipment management, and what to do when an incident occurs — including the FY2026 add-on's backup requirements for multiple methods, offline copies, and generation retention.

September 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

ISMS Certification Support as an Option

From scope design and documentation to training, internal audit, and dealing with the certification body. Pottech supports healthcare companies through ISO/IEC 27001 certification end to end.