Back to Columns
EMR8 min read

Integrated vs. Separate Receipt Computers: Differences, Pros and Cons, and How to Choose

June 29, 2026

Integrated vs. Separate Receipt Computers: Differences, Pros and Cons, and How to Choose
Share this article

When adopting an EMR and a receipt computer (rececon), one of the first things many clinics consider is the difference between an "integrated rececon" and a "separate" configuration. Even within the same "EMR + rececon" environment, this choice significantly affects daily data entry effort, the efficiency of claims (rezept) work, cost, and even how easy it will be to switch systems in the future. This article organizes the differences between integrated and separate receipt computers, and explains the pros and cons of each, along with how to choose based on your clinic's size and specialty, from a neutral standpoint.

What Is a Rececon? How Its Role Differs from an EMR

First, let's clarify the premise. A rececon (receipt computer) is a system that calculates medical fee points based on clinical content and creates and submits rezepts (medical fee claim statements). An EMR, on the other hand, is a system that manages clinical records (SOAP, prescriptions, test results, etc.).

  • EMR: Recording, referencing, and managing clinical records
  • Rececon: Point calculation, accounting, rezept creation, and claim submission

These two have different roles, but in actual practice, "what is written in the chart" leads directly to "billing and claims," so the quality of the link between the two determines operational efficiency.

The Difference Between Integrated and Separate

AspectIntegrated RececonSeparate
System configurationEMR and rececon are oneEMR and rececon are separate
Data linkageAutomatic internal linkageVia linking software
VendorSameOften different
Operation screenUnifiedTends to be two systems
Support contactSingle pointSplit across multiple

What Is an Integrated Rececon?

A configuration in which the EMR and rececon are designed as a single system, so that the content entered in the chart is automatically reflected in billing and rezepts. Many cloud-based EMRs adopt this integrated approach.

What Is a Separate Configuration?

A configuration in which the EMR and an independent rececon—such as ORCA (the medical clerical computer provided by the Japan Medical Association)—are each adopted as separate systems and connected via linking software. This is often seen with traditional on-premise EMRs.

Pros and Cons of an Integrated Rececon

Pros

  • No double entry: The clinical content written in the chart is reflected directly in billing, so no transcription or re-entry is needed
  • Fewer billing omissions and consistency errors: Because the chart and rezept reference the same data, discrepancies between records and claims are less likely
  • Unified operation screen: Only one screen to learn, lowering the training cost for medical clerical staff
  • Single support contact: Inquiries for adoption, maintenance, and troubleshooting are consolidated with one company

Cons

  • You cannot switch the rececon alone: You basically cannot replace only the rececon portion with another company's product
  • Dependence on the vendor's features: The scope for customizing billing logic may be constrained by the vendor's specifications

Pros and Cons of a Separate Configuration

Pros

  • You can choose the rececon independently: You can change only the EMR while continuing to use a familiar rececon (such as ORCA)
  • You can leverage existing assets: If you already have a rececon, you can add only the EMR

Cons

  • The linkage can become a source of trouble: Version mismatches in the linking software or configuration errors can cause data inconsistencies
  • Split support contacts: When a problem occurs, you need to determine "is it the chart side or the rececon side?", which tends to prolong resolution
  • Double maintenance: You need to manage revision responses and updates across two systems

How to Choose by Clinic Size and Specialty

  • Newly opening clinics: If you want to keep operations simple, an integrated type is a strong option. A single support contact and low training cost are effective during the startup phase
  • Practices already skilled with ORCA, etc.: If you want to leverage rececon assets, a separate configuration is also an option
  • Specialties with complex billing (orthopedics, home care, etc.): Compare based on the richness of billing logic and the accuracy of chart–rezept linkage
  • Clinics with few or very busy medical clerical staff: An integrated type, which reduces double entry and training cost, tends to ease the burden

In every case, the core of the decision is "how smoothly does chart documentation lead to correct billing?" We recommend using a demo or free trial to test the full flow from entry to accounting and rezept creation along your actual clinical workflow.

Boosting the Advantages of Integration with AI

The greatest value of an integrated rececon is that "the chart and claims are seamlessly connected." Pottech's "AI Karte" is not only designed as an integrated rececon, but—thanks to its AI-native design—supports everything from automatic SOAP generation of clinical content via voice input, to AI-based rezept checking of billing omissions and consistency, as a single flow. Because the AI helps ensure that what is written in the chart leads to correct billing, it further amplifies the "no double entry" advantage of the integrated type. With multi-device support, you can access the same data in the exam room and at the reception desk.

Conclusion

Neither the integrated rececon nor the separate configuration is absolutely superior; the optimal answer changes depending on your clinic's situation. If you prioritize operational simplicity, training cost, and a single support contact, the integrated type suits you; if you prioritize leveraging existing rececon assets, the separate type is a better fit. What matters is verifying, along your actual clinical workflow, whether everything from chart documentation to billing and claims connects without friction.

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.

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

What a Hospital-Grade AI-Native EMR Must Deliver

The role an AI-native EMR plays in a hospital differs from a clinic. The goal is not unstaffed operation but trimming peripheral work by profession to create time with patients and room to think. We organize the functions each profession needs, the cross-cutting requirements of permissions, departmental integration, and availability, and how to approach deployment.

August 10, 2026
EMR

Why Hospital and Clinic EMRs Differ So Much: A Comparison of Design Philosophies

Hospital and clinic electronic medical records share a name but are different products. Where does the divergence come from? We trace it to four sources—the correlation with organizational structure described by Conway's law, the differing time axes of outpatient and ward care, the separation of decision-maker from user, and revenue structure.

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 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.