How is V64 different from V62?

V64 is a missing indicator. V62 is an indicator that was present but outside the accepted set of HDS, HED, HIP, HOP and HRP. A single claim cannot produce both.

I supplied the indicator and the claim rejected again. Why?

Because the ministry tests three fields in sequence. All five indicators require a master number, which produces V65 if it is missing, and HIP also requires an admission date, which produces V66. Supply the companion fields in the same correction.

The indicator is visible in our EMR. Why does V64 keep firing?

Some systems keep a separate submission record from the screen record, so a field can be populated in the interface and absent from the file that reaches the ministry. If the value is demonstrably on screen, check the outbound claim file rather than the data entry.

OHIP error report

V64

Hospital and emergency equivalent

OHIP error code V64: missing service location indicator on a hospital diagnostic claim

V64 means a hospital diagnostic claim that requires a service location indicator was submitted without one. The field is absent rather than wrong, which is what separates it from V62.

Ministry wording: Missing service location indicator. Most often affects Internal medicine, Neurology, Hospitalists, Orthopaedic surgery.

You already know V64. A single rejection is rarely the whole pile. Specialists we work with recover $10,000 to $100,000+ from rejected and unpaid claims, then average a 20–40% revenue increase within 90 days.

Each minute looking this up is about $5 of clinic time.

1Why it fires
2What it costs
3What you can recover

See what you can recover

V64 at a glance

V64 is a V-series validation edit. The claim is rejected on the Claims Error Report and is not adjudicated, so it never appears on the Remittance Advice as paid or reduced.

The ministry lists V64 immediately alongside V62, V65, V66 and V67, and the set reads as one decision tree over three fields: the service location indicator, the master number and the admission date. V64 is the first branch. There is no indicator at all, so the ministry cannot establish where the service was rendered and stops before testing anything else.

That ordering is useful when a report carries several of these codes at once. A claim cannot produce V64 and V62 together, because one means the field is empty and the other means it holds a value outside HDS, HED, HIP, HOP and HRP. A report showing both is describing two different populations of claims, usually two sites or two templates.

Why it fires

The claim is a hospital diagnostic service billing and the service location indicator field was left empty.
The indicator is stored against some sites or listings and not others, so part of the diagnostic volume submits without it.
A manually entered or imported claim bypassed the template that normally supplies the indicator.
A software change, upgrade or new interface dropped the field from the outbound claim file while leaving it visible on screen.

The most common pattern is partial configuration. A group sets the indicator up for the site it bills most, and claims from a second site, a locum arrangement or a covering rotation submit with the field blank. Nothing looks wrong at entry because the field is optional in most other circumstances.

Manual entry is the second pattern. Where the indicator arrives from a template, anything entered outside that template arrives without it. That includes claims typed to catch up after an absence, claims rekeyed after a failed import, and claims entered by someone covering for the usual biller.

The third pattern is worth checking specifically because it is invisible from the user interface. Some systems keep a separate submission record from the screen record, so a field can be populated in the EMR and absent from the file that actually reaches the ministry. If the indicator is demonstrably present on screen and V64 keeps firing, the outbound file is the place to look rather than the data entry.

A blank field and a wrong field are different failures with different causes, which is why they carry different codes. Treating V64 as a variant of V62 leads a practice to check the value it chose instead of checking why no value was sent.

What it costs

The claim is rejected in full and nothing is paid until a corrected claim is accepted. The amount at risk is the entire diagnostic fee.

There is no partial payment on a V64. The claim did not reach adjudication, so the full professional or technical fee for the service stays unpaid until the practice resubmits.

Like the rest of this cluster, the loss is driven by repetition. A blank indicator is almost never a one-off, because the reason the field was empty applies to every claim that took the same route. The report will usually show the same code against a block of claims sharing a site, a date range or an entry method.

The three-month submission window for services on or after 1 April 2023 applies, per ministry INFOBulletin 230402. A blank field is one of the cheapest errors to correct and one of the most expensive to ignore, because nothing about the clinical record needs to change and the only thing standing between the practice and payment is someone reading the report.

Step-by-step: how to clear this rejection

Confirm the report line is V64 and not V62, because an absent indicator and an invalid one have different causes.
Establish where the diagnostic service was performed before choosing which of HDS, HED, HIP, HOP or HRP applies.
Supply the indicator, and supply the master number as well, since the ministry requires one with all five indicators.
If the indicator is HIP, include the admission date, otherwise the corrected claim will reject with V66.
Resubmit inside the three-month window and check whether the field is populated on the outbound file rather than only on screen.

Correcting V64 usually means supplying two or three fields rather than one. The indicator alone will clear V64 and produce V65 if the master number is still missing, or V66 if the indicator is HIP and the admission date is absent. Working the whole set at once avoids three cycles on one claim.

That cascade is the single most useful thing to know about this cluster. The codes are sequential tests, so clearing the first one exposes the next. A practice that resubmits field by field will see the same claim three times and conclude the ministry is being obstructive, when the requirements were all stated at the outset.

Verify the fix at the file level once. If the indicator shows in the EMR and the claim still rejects, the data entry was never the problem and no amount of re-entering will fix it.

Money you already earned, still unpaid

Recovery is separate work from ongoing billing. Charging only a percentage of what we recover, we review the backlog, correct what your documentation supports, and resubmit. Recent engagements have recovered five- and six-figure amounts, including rejected claims well past the 3-month stale dated deadline going back into 2023.

The alternative is usually your evenings or admin blocks, not billable clinic time. No setup or service fees. Every dollar recovered is money already written off, you keep most of it, and you pay nothing if nothing comes back.

“These claims weren’t chased up on. These claims have been stale dated. You add up the volume of money in there and it’s a consequential sum.”

Dr Sanjay Acharya, on what the recovery review found

Show me what is still recoverable

How to fix it going forward

Make the service location indicator mandatory for hospital diagnostic listings at the point of entry, so a claim cannot be built without it.
Configure the indicator for every site the group bills from, not only the primary one.
Check the outbound claim file after any billing software change, upgrade or new interface.
Give anyone who enters claims outside the usual template a written rule for which indicator applies where.

A mandatory field is the whole prevention story here. V64 exists because the indicator was optional at the moment of entry, and every other control is a way of compensating for that.

Site coverage is the second control. Audit the list of locations the group actually bills from against the list of locations with a stored indicator. Those two lists drift apart whenever a new privilege, a covering arrangement or a satellite site appears, and the gap is where V64 lives.

Treat software changes as a billing risk. The field surviving an upgrade is worth five minutes of checking, because the alternative is discovering it at the end of a submission cycle with a quarter of diagnostic claims rejected identically.

Is it recoverable?

Recoverable by resubmission inside the window

Supply the indicator together with the master number, add the admission date if the indicator is HIP, and resubmit inside the three-month window from the date of service.

V64 is among the most recoverable codes in this cluster, because nothing clinical is in dispute. The service happened, the record supports it, and a required administrative field was empty.

Supply the companion fields in the same correction. The ministry tests the indicator, the master number and the admission date in sequence, so a correction that addresses only the indicator will come back as V65 or V66.

Where the three-month window has closed, INFOBulletin 230402 allows claims that reached the Claims Error Report inside three months to be corrected and resubmitted through the ministry stale-date process. The report line proves the claim was submitted on time. Where a claim was never submitted inside the window, recovery runs through a written application instead, which is a separate process from a corrected resubmission.

For in-province services on or after 1 April 2023, claims must be submitted within three months of the date of service, not six. Ontario INFOBulletin 230402 is the Ministry notice. Many third-party pages still quote six months. That window is closed for current work. If the original claim reached the Claims Error Report inside three months, a corrected resubmission can still be filed after the window in the Ministry's stale-date process. If the claim was never submitted in time, payment may be recoverable by written application. That is not a routine resubmit.

Related codes

Frequently asked questions

What does OHIP error code V64 mean?: V64 means a hospital diagnostic claim that requires a service location indicator was submitted without one. The field was empty rather than incorrect.
How is V64 different from V62?: V64 is a missing indicator. V62 is an indicator that was present but outside the accepted set of HDS, HED, HIP, HOP and HRP. A single claim cannot produce both.
I supplied the indicator and the claim rejected again. Why?: Because the ministry tests three fields in sequence. All five indicators require a master number, which produces V65 if it is missing, and HIP also requires an admission date, which produces V66. Supply the companion fields in the same correction.
The indicator is visible in our EMR. Why does V64 keep firing?: Some systems keep a separate submission record from the screen record, so a field can be populated in the interface and absent from the file that reaches the ministry. If the value is demonstrably on screen, check the outbound claim file rather than the data entry.

References

For how error reports relate to the remittance advice, see how to read your OHIP remittance advice and what rejection codes actually mean. Official wording for this code: Ministry of Health, Error Report Rejection Conditions (December 2022).