At the core of Fee Revision DX sits the "common billing module." The name alone gives little away, but this is an effort to unify the fee calculation logic itself into a single nationwide implementation—a change to how rececons are built. This article organizes what the module is, why it was needed, and how it bears on clinic operations and system selection.
Disclaimer: This article is general information. The scope of provision, timing of support, and available systems may change. In practice, always confirm the latest primary sources (the Social Insurance Medical Fee Payment Fund, MHLW, and others).
For the overall map of Medical DX, see What Is Medical DX? The Government Roadmap and Its Three Pillars.
What the Common Billing Module Is
The common billing module is a nationwide common electronic program for calculating medical fees and patients' copayments. The Social Insurance Medical Fee Payment Fund provides it, and rececon and EMR vendors incorporate it into their products.
It is not something institutions install and operate directly. It is a calculation engine running inside the rececon; from the institution's viewpoint, "the internals of the rececon are being replaced."
Why It Was Needed
Fee calculation rules are extremely complex: the fee schedule, billing requirements, bundled scopes, and additions that vary by age or time of day. Conventionally, each rececon vendor implemented this logic independently.
That structure created problems:
- Every vendor repeats the same work at every revision: each reads the same notices and implements the same rules separately—duplicated investment when viewed society-wide
- Interpretations diverge by vendor: differences in implementing complex rules can surface as differences in billing results
- Modification costs are passed to institutions: vendors' revision costs ultimately land on institutions as maintenance or modification fees
The common billing module aims to eliminate this "build the same thing many times" structure. At revision time, the Payment Fund modifies the module and masters, and each vendor simply incorporates the result.
Progress So Far
| Period | Content |
|---|---|
| 2023 | Development policy set out in the Roadmap for Promoting Medical DX |
| FY2024–FY2025 | Design, development, and verification through model projects |
| June 1, 2026 | Full operation begins for medical and DPC; usable on rececons provided by ORCA |
It starts with medical and DPC, and the scope is expected to widen in stages. Dental and dispensing use different billing structures, so they are under separate consideration.
Note that the start of full operation on June 1, 2026 coincides with the effective date of the FY2026 revision's main body. Switching at the revision's timing is designed to make the migration a single event.
Impact on Medical Institutions
No Direct Work Arises
To repeat: the common billing module is not something institutions adopt. It affects them indirectly, in the form of whether the rececon they use has adopted the module. The near-term picture differs depending on whether you currently use an ORCA-based rececon.
Expected Benefits
- Lower revision-handling costs: as vendors' modification scope shrinks, upward pressure on maintenance and modification fees should ease
- Standardized billing results: variation stemming from implementation differences between vendors decreases
- Lower post-revision defect risk: because one nationwide program is verified intensively, defects arising from individual implementation mistakes should decline
That said, these will not translate into lower fees immediately. For now, it is realistic to understand this as "the cost structure is heading in a different direction over time."
What to Confirm When Selecting a System
When considering a new rececon/EMR or a switch, confirm the following:
- The policy and timing for supporting the common billing module
- Whether support, once implemented, requires work or costs on the institution's side
- Whether current revision handling is included in maintenance fees or billed each time
"Not supported yet" is not a disqualifier. What matters is how the vendor explains its direction.
Relationship to the Standard Rececon Concept
Alongside providing the common billing module, the roadmap states that provision of a standard receipt computer will also be considered, to minimize the burden on small and mid-sized hospitals and clinics. If the common billing module is the "calculation engine," the standard rececon is the "finished product carrying that engine."
However, this remains a concept under consideration; unlike the standard EMR, no concrete provision timing has been indicated. It would not be realistic to make decisions on the premise of waiting for a standard rececon at this point.
Common Misunderstandings
It does not eliminate the need for claim checking
The module performs fee calculation and copayment calculation. Claim review—consistency between diagnoses and procedures, missed billing, and detecting return/reduction risk—still requires separate mechanisms.
It does not make rececons unnecessary
The module covers only the calculation portion; it does not replace the rececon's full functionality such as patient registration, daily operations, and claim creation and submission.
With AI Karte
The AI-native EMR "AI Karte" is a cloud service with an integrated rececon, designed so that fee schedule revisions are handled entirely on the service side. We are also examining our approach to developments in Fee Revision DX, including the common billing module, in light of regulatory changes. AI claim checking additionally helps detect missed billing and reduction risk, supporting clinic clerical work from both the calculation and the review side.
Conclusion
Because institutions never touch it directly, the common billing module is hard to feel. Yet it changes how the rececon product category is built, and over the medium to long term it affects the cost structure of revision handling. What clinics can do now is confirm each vendor's approach when selecting or updating a rececon or EMR. What happens at each revision becomes a difference you cannot ignore over a product's lifetime.
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.
