OHIP Billing

A practical guide to cleaner Ontario billing workflows.

Build a repeatable process for claim preparation, MCEDT submission, error follow-up and remittance reconciliation.

Last reviewed: August 21, 2026

Practical guide

An OHIP claim workflow checklist: from service to submission

Accurate billing begins before a claim file is created. A good workflow preserves the service context, validates required information and makes exceptions visible before submission.

Capture the source information

Record the actual service date, provider, patient identifiers, location and clinically supported billing details as close to the encounter as practical. Treat missing information as work to resolve—not a reason to guess. Current fee and diagnostic-code requirements should be checked against Ministry materials.

Validate before batching

Use health-card validation where appropriate, confirm required fields and separate claims needing documentation or manual review. The Ministry recommends daily or weekly submission because smaller, regular batches support timely adjudication and easier correction of rejected claims.

Create an owned follow-up queue

A submission is not finished when it is uploaded. Assign responsibility for Claims Error Reports, corrected resubmissions, supporting documents and unresolved items. Monitor service dates so claims do not quietly approach the three-month stale-date window.

Practical guide

MCEDT, error reports and Remittance Advice: a reconciliation routine

MCEDT is the secure transfer channel; billing software creates and manages the claim workflow around it. Reconciliation connects what was submitted with what was accepted, reduced, rejected or paid.

Know the file cycle

MCEDT supports claim-file uploads and report downloads. Error reports are generally produced shortly after processing, while the monthly Remittance Advice records approved claims and payment information. Downloading a file is only the first step; its items must become assigned work.

Separate rejection from adjudication

A rejected claim did not pass processing and usually needs correction before resubmission. A paid, reduced or disallowed item on an RA requires a different review using the applicable explanatory code and source documentation. Keeping these queues separate improves clarity.

Close the loop

Match each submitted item to its outcome, document corrections and retain the context needed to reproduce decisions later. Review Ministry messages included with the RA and observe current inquiry timelines. Escalate ambiguous coding or eligibility questions to an appropriate billing expert.

Official sources and further reading

These resources provide general operational information. Confirm current requirements with the responsible authority and obtain professional advice for your circumstances.

More detailed help

Looking for product instructions or additional answers?

The HYPE Systems Knowledge Base includes more product-specific guidance, workflow help and answers to common customer questions.

Explore the full Knowledge Base