Back to Columns
EMR11 min read

Complete Guide to the EMR Information Sharing Service: Shared Information and Addition Requirements

July 4, 2026

Complete Guide to the EMR Information Sharing Service: Shared Information and Addition Requirements
Share this article

Key Takeaways

  • The service lets medical institutions, pharmacies and patients share and view EMR information nationwide.
  • MHLW aims to make it available nationwide around winter of FY2026.
  • EMRs must support HL7 FHIR and standard coding.

The EMR information sharing service is a core piece of medical DX. Even those who know the name often haven't grasped what is shared, how it relates to fee additions, or the standards and consent involved. This article organizes the shared information, addition requirements, HL7 FHIR standardization, patient consent, and adoption prep, based on official MHLW information.

Disclaimer: This is general information. Rules, launch timing, and fees change via revisions/notices; always confirm the latest primary sources (MHLW notices and official materials).

What it is

The service lets a patient—by checking in with the Myna insurance card and consenting to information provision—make part of the EMR information recorded at one institution viewable at other institutions nationwide. Using the online eligibility-verification infrastructure, and as part of the National Medical Information Platform, it standardizes and streamlines inter-institution linkage. It is rolling out in stages after model projects (confirm the latest status officially).

Previously, learning another institution's diagnoses, allergies, or test results relied on referral letters or patient interviews. The service shares such information in a standardized format, supporting safer, more efficient care in transfer, emergency, and primary-care linkage.

The "three documents, six information categories"

Three documents: referral letter / discharge summary / health checkup result report.

Six categories: diagnoses / allergy information / contraindicated-drug information / infectious-disease information / test information (emergency and lifestyle-disease related) / prescription information.

Allergy and drug-contraindication data bear directly on patient safety. Because the exact definitions are updated in official materials, confirm the latest definitions in MHLW primary sources such as "Handling of Document Information (3 documents) and EMR Information (6 categories)" at implementation.

Standardization via HL7 FHIR

The crux is sharing information structured to a standard. The service presumes support for HL7 FHIR (an international standard for exchanging health information) and registering/exchanging the six categories via standard codes (for diagnoses, tests, etc.). Free-text alone cannot realize the value, so whether the EMR supports the standard and builds standardized entry into operations is key.

Patient consent and data protection

Sharing EMR information requires the patient's consent to information provision. Because clinical data is "special care-required personal information," set up a proper consent flow (clear explanation and recording at reception). Design the institution's safe management per the three-ministry guidelines (see Implementing the Three-Ministry Guidelines; for handling of personal data, the legal view of generative AI is also useful).

Relation to fee additions

Support relates to medical-DX fee additions. The electronic clinical information coordination fee, among others, increasingly positions support for this service—alongside online eligibility verification and electronic prescriptions—as a system requirement. Because point values, requirements, and deadlines are revised each cycle, we avoid asserting them; confirm the latest via MHLW/regional bureau notices.

Adoption prep

  1. Online eligibility verification in operation (the prerequisite)
  2. EMR standard (HL7 FHIR) support: register/exchange the six categories via standard codes
  3. Standardized entry of the six categories via standard codes
  4. Consent flow: properly obtain and record consent at reception
  5. Apply and connect on the portal

The key is whether the EMR supports the standard. Because retrofitting an existing EMR can be costly, if you are choosing one now, evaluate on standard support as a premise.

With AI Karte

Pottech's AI Karte, AI-native by design, handles data structured from the start—making it easier to manage diagnoses, allergies, and prescriptions in a standardized form and to support the standards the service requires. Voice-to-SOAP reduces documentation burden while accumulating structured data. Rececon-integrated, it connects booking, intake, records, and billing on one platform, with a three-ministry-compliant security design (see Designing Security for an AI EMR).

Conclusion

The service safely shares patient information across institutions to raise quality and safety. Considering the three documents/six categories, additions, HL7 FHIR, and consent, "can it support information sharing?" becomes a key axis in choosing an EMR. As rules update toward wider operation, always confirm the latest official content. Please feel free to contact us.

References and sources

This is general information. Rules and fees change via revisions/notices; confirm the latest primary sources in practice.

Share this article

Related Articles

EMR

How to Avoid EMR Vendor Lock-In: Contracts, Data, and Standards

Many clinics discover only when attempting to switch that data cannot be extracted, migration costs were unbudgeted, or the contract term still runs. We break lock-in into three layers—data, functionality, and contract—then organize what to verify before signing and the role standards play.

August 10, 2026
EMR

EMR Data Migration Aligned with Standard Requirements: HL7 FHIR, SS-MIX2, and Standard Codes

EMR data migration changes significantly when data conforms to standards (HL7 FHIR, SS-MIX2, standard codes). Based on EMR information standardization and the standard-type EMR, this article organizes migration methods, steps, and limitations aligned with the standard requirements, referencing official MHLW information.

August 2, 2026
AI & DX

What Is HL7 FHIR? The Healthcare Data Standard, Explained for Clinics

HL7 FHIR is a shared format for exchanging healthcare data between different systems. We explain why it is needed, the idea of resources, why its web-based design pairs well with APIs, its position in Japan, and what it means for clinics in terms of data migration, integration, and avoiding vendor lock-in.

September 7, 2026
AI & DX

MCP vs. API vs. FHIR: Sorting Out the Three Layers of Healthcare Integration

MCP, API, and FHIR all appear in integration conversations, but they are not three competing options—they sit at different layers with different jobs. We trace one request, "get the latest HbA1c," through all three, and show how this bears on EMR selection.

August 28, 2026
Billing

Medical DX-Related Fees in the 2026 Revision: Abolition and Reorganization

In the fiscal 2026 revision, the medical DX promotion system development fee and the medical information acquisition fee were abolished and consolidated into the electronic clinical information coordination fee. The old fees ended May 31, 2026, and billing under the new fee began June 1. We organize the changes and required responses, including the need to re-file even if previously filed.

August 11, 2026
AI & DX

What Is a PHR? How It Differs from an EMR and What It Means for Providers

A PHR is a mechanism through which individuals manage their own health and medical information—differing from an EMR in who holds it. We organize what is viewable via the national portal, how it relates to the EMR information sharing service, and what patients holding their own data changes for clinical practice.

August 10, 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.