OHIP Error Code EH2: What "Mismatched Version Code" Means and What It Costs Your Practice

There is a particular kind of billing problem that does not feel urgent until you do the math. OHIP error code EH2 is one of them. Individually, each rejection looks like a minor administrative hiccup. Add them up across a busy week of patient visits, factor in the staff time to find and fix them, account for claims that quietly expired before anyone noticed, and the number gets real fast.

This post breaks down exactly what EH2 means, how it differs from the version-code codes you see on your Remittance Advice, how to estimate what it is actually costing your practice, and what a realistic prevention workflow looks like for a front desk that is already stretched.

What EH2 Actually Says About Your Claim

EH2 appears on the OHIP Error Report, not the Remittance Advice. That distinction matters more than most practices realize.

When the Ministry receives your billing file, it runs a pre-adjudication check before claims ever reach the payment calculation stage. Claims that fail these checks are returned on the Error Report with a rejection code. EH2 is the code for mismatched version code: the two-character alphanumeric suffix on the patient's health card number in your submission does not match what the Ministry's Health Card Validation system has on record for that health number.

The claim does not proceed. It is not adjudicated. It is not listed on the Remittance Advice as denied. It simply does not enter the payment queue.

This is where practices run into trouble: if your billing workflow only reviews the Remittance Advice (what got paid and what got denied), EH2 rejections can be invisible. They live on the Error Report, which is a separate document that requires a separate review step.

The version-code family across Ministry documents

The Ontario Ministry of Health's Remittance Advice Explanatory Codes document lists several related codes that appear once a claim makes it further into the system:

E2: Incorrect version code for the service date
EF: Version code missing or invalid
EV: Health number or version code does not match registration

EH2 is the Error Report analogue to this family. All of these codes point to the same root cause: the two-character version code in your system does not match the Ministry's record for that patient on that date of service. The difference is where in the billing cycle the mismatch is caught. EH2 catches it before adjudication; E2, EF, and EV catch it after.

Confusing Error Report codes with Remittance Advice codes is common and understandable. The Ministry does not make this easy. The Error Report and RA are separate outputs, use overlapping but non-identical code sets, and most EMRs surface them in different parts of the interface.

Why EH2 Is Revenue Leakage, Not Just Paperwork

A single EH2 rejection for a $35 minor assessment feels negligible. Practices see it, the biller corrects the version code, and they move on. The problem is the assumption that this is a one-off.

Version codes change. Patients receive new health cards periodically, and the version code on the new card is different from the old one. Patients who move within Ontario may be re-registered. Patients who let their coverage lapse and reinstate it get new version codes. None of that shows up automatically in your EMR. The EMR stores what was entered at the last update, and if no one captured the change at check-in, the stored version code drifts silently out of sync with Ministry records.

In a practice seeing 80 to 120 patients per week, even a 2% EH2 rate means two to three claims per week returned on the Error Report. At an average OHIP value of $50 to $150 per encounter depending on specialty, that is $100 to $450 per week in claims that did not enter the payment queue. Over a year, before accounting for any claims that expired uncorrected, that range is roughly $5,000 to $23,000 in delayed or lost revenue from one rejection code.

That math does not include the labor cost. Each EH2 rejection requires someone to identify it on the Error Report, locate the original claim, find the correct version code (which usually means contacting the patient or asking them to come in with their card), correct the record in the EMR, and resubmit. At a conservative 15 minutes per rejection, and a front-desk billing rate of $22 to $28 per hour, that is $5.50 to $7.00 of staff time per claim, before accounting for resubmission delays or the compounding effect of a correction backlog.

This is the core of what we see across practices without routine oversight: individually small errors that compound into measurable leakage. In our experience working with Ontario physician-owners, billing oversights and invisible rejections can represent 20 to 40 percent or more of recoverable revenue in practices that do not have a regular data-driven review loop. EH2 alone will not account for all of that, but it is a consistent contributor that almost never shows up in a practice owner's line of sight.

If you want a broader picture of how this kind of compounding works across multiple rejection types, our piece on what medical school did not teach you about OHIP and Medicare billing walks through how billing gaps accumulate quietly over time.

A Framework for Estimating EH2 Cost in Your Practice

You do not need precise numbers to build a useful estimate. Risk management frameworks commonly apply a probability-times-impact model to quantify recurring operational losses, and the same logic applies here.¹

Try this four-variable calculation:

Step 1: Estimate your monthly EH2 volume If you do not have an Error Report review, start by pulling the last three months of error reports and counting EH2 codes. If you do not have access to historical error reports, estimate conservatively: 1 to 3 percent of monthly claims is a reasonable starting assumption for a practice without a card-verification protocol at check-in.

Step 2: Apply average encounter value Multiply monthly EH2 volume by your average OHIP encounter value. Be honest here: use a weighted average if your billing mix includes assessments, procedures, and premiums.

Step 3: Add labor cost Multiply the same monthly EH2 count by your estimated correction time per claim (typically 10 to 20 minutes) and your biller's hourly rate. This is the operational drag that most practices never quantify.

Step 4: Apply a recovery discount Not every EH2 claim gets corrected and resubmitted within the window. Apply a 10 to 20 percent haircut to account for claims that expire or fall through the cracks during a busy month. This is the unrecoverable portion.

The resulting number is your monthly EH2 cost: delayed revenue plus staff overhead plus permanent loss. Most practices, when they run this for the first time, are surprised at how quickly it exceeds the cost of a systematic fix.

The project management literature on cost overruns is instructive here: repeated small losses that each feel manageable in isolation tend to accumulate into significant totals because they are never aggregated and reviewed.² The same dynamic applies to OHIP rejection volume.

Prevention That Survives a Busy Front Desk

The goal is not a perfect process. The goal is a process that works when the front desk is managing a full waiting room, a ringing phone, and a physician who is already behind schedule.

Card check at every visit The single highest-impact intervention is a physical health card check at every patient encounter, not just new patients. The version code on the card the patient presents today is the version code that needs to be in your EMR today. A visual check takes under 30 seconds. A swipe through a card reader connected to your Health Card Validation query takes about the same. Build it into the check-in script the same way you confirm the patient's date of birth.

EMR demographic update as a triggered action When the card check reveals a version code that differs from what is stored, the update needs to happen before the patient leaves the desk, not as a note for later. Later becomes never when the afternoon fills up.

Batch verification before submission Most EMRs allow you to run a Health Card Validation query on the patient list before you generate the billing file. Running this check as a standard pre-submission step catches version code mismatches before they become EH2 rejections. It adds roughly 10 to 15 minutes to the billing workflow and prevents claims from entering the error queue in the first place.

Monthly Error Report review Set a fixed day each month to pull the Error Report alongside the Remittance Advice. Tally EH2 codes separately. Tracking the volume month over month tells you whether your card-check protocol is working, and it surfaces any patients whose records are persistently stale.

For a broader look at how your EMR setup interacts with these workflows, the discussion in what your Ontario EMR choice says about you is worth a read, particularly on how different systems handle demographic validation.

When EH2 Patterns Signal a Deeper Oversight Problem

A single EH2 rejection is a data entry miss. A pattern of EH2 rejections is a systems problem.

If your monthly Error Report review reveals EH2 appearing consistently across multiple patients or showing up repeatedly for the same patient, the root cause is almost certainly not a front-desk error rate. It is an absent reconciliation loop. Patient demographic data drifts continuously. Cards expire and renew. Patients move. Version codes change. Without a scheduled, documented process for catching that drift, the gap between your EMR records and Ministry records widens over time, and EH2 volume grows with it.

The Ministry does not make this easy to see. Error codes are not designed to be intuitive, and there is no dashboard that summarizes your rejection rate by code, cost, or trend. That opacity is exactly why practices end up treating EH2 as an annoyance rather than a metric. When there is no visibility, there is no accountability, and when there is no accountability, nothing changes.

This is the same dynamic we discuss in the context of DIY billing broadly: the hidden cost is not usually a single catastrophic error. It is the steady, invisible accumulation of small leakages that never get aggregated, reviewed, or addressed. Our resource on the true cost of DIY OHIP billing goes into this in more detail.

If EH2 is showing up as a recurring pattern in your practice, the question worth asking is not how to fix this week's batch. It is what else is falling through the same gap.

Frequently Asked Questions

What is the difference between EH2 on the Error Report and E2 on the Remittance Advice?

EH2 appears on the OHIP Error Report and means the claim was rejected before processing because the version code in your submission does not match what the Ministry has on file. E2 and related codes EF and EV appear on the Remittance Advice and signal a version code problem identified during or after the adjudication pass. Both flag the same root cause, but at different points in the billing cycle. EH2 claims never enter adjudication; they need to be corrected and resubmitted from scratch.

How long do I have to correct an EH2 rejection before the claim is lost?

OHIP generally allows resubmission within six months of the service date, though specific timelines can vary by claim type. Because EH2 rejections can sit unnoticed in an Error Report that is not reviewed weekly, that window can close faster than practices expect. A monthly Error Report review is the practical minimum for catching rejections while they are still correctable.

Can a practice prevent EH2 errors entirely, or are they inevitable?

You cannot guarantee zero EH2 rejections permanently, because patients renew cards, move, and change coverage without always informing your front desk. You can get EH2 volume close to zero with a card check at every visit and a monthly rejection review that catches drift before it compounds. Practices that implement both steps consistently see EH2 as an occasional exception rather than a recurring pattern.

Why does my EMR produce EH2 rejections even when the card looks current?

The EMR stores whatever was entered at the last update. If a patient received a new card with a different version code and your front desk did not capture it at that visit, the stored version code is stale. The physical card the patient is carrying today may look perfectly valid, but the version code on it no longer matches what was in the system when the claim was submitted.

Does an EH2 rejection mean the patient was uninsured on that date?

No. EH2 is a data-matching failure, not a coverage failure. The patient almost certainly had valid OHIP coverage on the date of service. The Ministry's system could not match your submitted version code to its records, so the claim was returned on the Error Report. Correct the version code, confirm it against the current card, and resubmit.

If you want to know how much EH2 and other avoidable rejection codes are costing your practice each month, a billing review is the fastest way to get that number. Book your free OHIP billing review and we will look at your Error Report and Remittance Advice together, put a dollar figure on what is leaking, and outline what a realistic fix looks like for your practice.

References

MIGSO-PCUBED. "The Risk Management Process: 4 Essential Steps." October 15, 2025. https://www.migso-pcubed.com/blog/risk-management/four-step-risk-management-process/
Hubstaff. "Project Cost Overrun: Understanding, Managing, and Preventing." March 10, 2026. https://hubstaff.com/blog/project-cost-overrun/