Know where every claim stands.
Enter a claim, send it to the Ministry, and follow it to payment without leaving one screen. If a code looks likely to be rejected, OHIPay flags it first. It never blocks a valid claim.
Your first 2 months are free.
One place to see every claim in flight
A live inbox shows every claim's status. Beside it, a per-code breakdown of what you submitted against what the Ministry actually paid.
Claims inbox
Sample data · this month
| Patient | Health card | Code | Status | Amount |
|---|---|---|---|---|
| M. Alaoui | •••• 4821 | A007A | Paid | $36.90 |
| R. Singh | •••• 1093 | K017A | Needs correction | $64.05 |
| J. Whitfield | •••• 7742 | C122A | Submitted | $84.15 |
| D. Osei | •••• 3305 | A888A | Rejected | $52.30 |
| L. Bergeron | •••• 6014 | A003A | Draft | $36.90 |
| P. Nassif | •••• 2287 | E082 | Paid | $11.07 |
Remittance summary
Sample data · current period
- A007A General assessment $36.90
- K017A Individual counselling $64.05
- C122A Inpatient subsequent visit $84.15
- E082 MRP premium $11.07
- A888A Special visit premium — rejected $52.30
The billing cycle, in one workspace
OHIPay stays with a claim from the first code you enter to the remittance that closes it. Four steps, one workspace.
Prepare
Start from a health card, add fee codes and a diagnosis, and watch premiums calculate as you type. Likely problems appear as advisories next to the field they concern. A valid claim is never blocked.
A003A + E082 · premium applied automatically
Track
One inbox holds every claim: draft, submitted, paid, rejected. You stop rebuilding a claim's status from the portal and a spreadsheet. Filter by status or physician to see what's outstanding.
14 in flight · 2 need attention
Correct
When a claim comes back rejected, the Ministry's reason sits on the claim itself. There is no separate report to cross-reference. Fix the field it points to and resubmit from the same screen.
EH2 · mismatched version code
Reconcile
Each remittance is matched line by line against what you submitted. A partial payment or a quiet rejection surfaces on its own, instead of hiding inside a batch of paid claims.
53 lines matched · 1 flagged
Built around patient data
OHIP claims carry protected health information, so the workspace treats it that way by default.
- Health-card numbers and demographics are encrypted at rest and in transit, decrypted only when a claim or lookup needs it.
- Patient identifiers are decrypted in-process on the server, never held in the browser or a client-side cache.
- Every read and edit to a patient record is written to an audit trail, so who saw what, and when, stays answerable.
These reflect current engineering practices, not a claim of certification under any specific compliance framework. Ask us for specifics on how your data would be handled before you rely on it.
Ready to see it on your own claims?
Walk through the workspace with your own fee codes and diagnoses. No commitment, just a look at how it fits your practice.
Prefer email? Write to hello@ohipay.ca