Prepare, track, correct, and reconcile OHIP claims from one operational workspace.
A live inbox of every claim's status, plus a clear per-code breakdown of what was submitted and what was paid — instead of piecing it together across a portal, a spreadsheet, and memory.
Sample data · 6 of 14 shown
| 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 |
Sample data · current period
OHIPay follows a claim through its whole life — from the first code entered to the remittance that closes it out.
Start a claim from a health card, add fee codes and a diagnosis, and see applicable premiums calculated as you enter them. Likely issues surface as advisories next to the field they concern — nothing is blocked before it's sent.
A003A + E082 · premium applied automatically
Every claim lives in one inbox — draft, submitted, paid, or rejected — instead of split across a portal, a spreadsheet, and memory. Filter by status or physician to see exactly what's outstanding.
14 in flight · 2 need attention
When a claim comes back rejected, the reason sits next to the claim itself — no separate report to cross-reference. Fix the field it points to and resubmit from the same screen.
EH2 · mismatched version code
Incoming remittance is matched line-by-line against what was submitted, so a partial payment or a quiet rejection doesn't get lost inside a batch of otherwise- paid claims.
53 lines matched · 1 flagged
Handling OHIP claims means handling protected health information. The workspace is designed with that as the default, not an afterthought.
Health card numbers and demographic details are encrypted at rest and in transit. Decryption happens only when a claim or a lookup genuinely needs it.
Patient identifiers are decrypted in-process on the server for the moment they're needed — not held in the browser or shipped to a client-side cache.
Reads and edits to patient records are recorded in an audit trail, so who looked at what — and when — is always 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.
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