Built around patient data.

Handling OHIP claims means handling protected health information. We built OHIPay around that from the start. Here is how patient data is stored, moved, and shown, in plain terms and without overstating what the product does.

The practices

What we do to protect it

These are current engineering practices in the product, not certifications. They describe how the system is actually built. Nothing here claims compliance under a specific framework.

Encrypted at rest and in transit

Health card numbers and demographic details are encrypted at rest and in transit. They're decrypted only when a claim or a lookup actually needs them.

Decrypted only when a task needs it

Patient identifiers are decrypted in-process on the server, for the moment a task needs them. Your browser and the OHIPay app show them while you work and keep no copy: the app holds patient details in memory only and clears them when you sign out. You see full details for your own patients; OHIPay's administrators see them only through views that record each access.

Card images aren't kept

Scan a health card and our server reads the image in memory, then drops it; it is never written to the server's disk. The OHIPay app usually reads the card number on the phone and sends no picture at all. When it does take a photo, the photo sits in the app's private temporary storage only until it has been read, then it is deleted.

The OHIPay app on your phone

The app keeps your sign-in in the phone's secure storage, plus a few settings. It never sends claims to the Ministry itself, and no patient information stays on the phone. Signing out removes the sign-in from that phone; to end every session, change your password. The details are in our privacy policy.

What's scoped to you, and what's shared

Claims, rosters, submission batches, and reports are scoped to you, enforced on the server rather than hidden in the interface. Patient records are the one exception: a patient record is shared by the physicians who have that patient's health card in hand, so a patient two doctors both see is one record, not two. That's a deliberate design choice, and we'd rather state it here than have you discover it later.

Sensitive access is logged

Reads and edits to patient records land in an audit trail. Who opened what, and when, stays answerable after the fact. Downloading a Québec out-of-province claim form is logged too, against the patient it names — it's the most detailed document the software hands you, so it leaves a record. So is downloading a remittance advice, as the Ministry sent it or as its summary PDF: it lists every patient on that remittance, so each download is recorded. Opening or downloading a document OHIPay keeps from your MOH mailbox is recorded the same way.

Canadian data residency

The service and its data are hosted in Canada. If you need specifics on where your data lives and how it's stored, we'll walk through them before you commit.

Want the detail behind any of these? Ask how your data would be handled before you commit. We'd rather answer a specific question than point at a logo.

The specifics

Where your data lives, and who else touches it

Here are the details we'd otherwise walk you through in a call. Everything below is how the system runs today, not a roadmap.

The live system: Montréal

The application and its database run on Amazon Web Services servers in the Canada (Montréal) region, ca-central-1. Patient identifiers and demographic fields are encrypted at rest, and everything in transit runs over TLS.

The backups we make: a separate account, and we hold the only key

A full database dump runs every hour. It's encrypted on our own server before it goes anywhere, then stored in Amazon S3 in the same region, in a separate Amazon account of ours used for backups. The key that decrypts these backups is kept off our servers, so Amazon holds them as ciphertext it cannot read. Amazon also keeps its own short-lived copies of the database and the server's disk for us, for up to 14 days, encrypted with a key held in our Amazon account and operated by Amazon. Live data and backups both stay in Canada.

A Québec claim leaves on paper, by your hand

Québec isn't part of the electronic agreement other provinces use, so a claim for a Québec-insured patient is never transmitted anywhere. OHIPay fills RAMQ's official paper form and hands you the PDF; you print it, sign it, and mail it. The file is built in memory when you ask for it and streamed to your browser — no copy is kept on our servers or in our backups. The Ontario dollar figure on that form is what you're claiming, not what RAMQ will pay, which is set at Québec's own rates.

Bills to anyone other than OHIP stay with you

Private invoices and receipts, UHIP claims and Medavie Blue Cross worksheets (IFHP and the Canadian Armed Forces) are made for you to download and send or submit yourself. OHIPay never transmits them to the Ministry or to any insurer. Each PDF is built in memory when you ask for it and streamed to your browser, with no copy kept. The patient's details on a bill (name, address, insurer numbers and notes) are stored encrypted, and every view, change and download of a bill is recorded, against the patient it names or, for someone not on file, the bill itself.

Your MOH mailbox documents, kept 24 months

The Ministry sends more to your MC EDT mailbox than claim answers, and deletes each file after a year. OHIPay keeps its messages, your payment summaries and similar documents for 24 months from when they arrive, encrypted, then deletes them. The Ministry's patient lists, such as a roster report, are kept only if you turn them on, and turning one on needs two-factor sign-in. Our administrators see counts and dates; no screen or route lets them open a document. The only way we reach one is an audited export, used when you ask us for your records.

Notice before any of this changes

We tell physicians in writing before we add a company to the list below or change where data is stored. If you object and we can't work it out, you can leave at any time.

Company What they do for us Patient data? Where
Amazon Web Services Runs the servers the application and database live on, and stores the encrypted database backups in a separate account. Yes — all of it. The hourly backups we make are encrypted with a key Amazon doesn't hold. Canada (Montréal), ca-central-1
OVH Our former host. The application there is stopped. Its database files stay on that server until our first Ministry payment report has been reconciled on the new system; then the server is wiped and destroyed. Yes — a stopped copy, until then Beauharnois, Québec
Resend Sends account email — invitations, password resets — and our own operational alerts. Alerts can name a physician and practice-level dollar totals. Never patient data. No patient data United States
Google (Fonts) The health-card lookup pages load one web font from Google. The request carries page metadata — IP address, browser, page URL — and no patient content. No — page metadata only United States
Google (ML Kit) Reads the health-card number on the phone, inside the OHIPay app. It may send Google diagnostic information about the app and the device — never the card image or the text it reads. No — app and device diagnostics only On the phone; diagnostics go to Google
Medinote A separate telehealth platform. If you turn on the Medinote connection, patient data flows from Medinote into OHIPay. Yes — flows in from Medinote Per Medinote's own terms
Amazon Bedrock AI suggestions. Built but switched off — no AI provider receives any data today. We would tell you in writing before turning it on. None today Canada, ca-central-1

The Ministry of Health isn't on this list. MC EDT and health-card validation are how your claims reach the payer — the Ministry is who you're billing, not a company we hand your data to. Québec's RAMQ isn't on it either, and for a stronger reason: we send RAMQ nothing. We print the form; you mail it. The same goes for Cowan (UHIP) and Medavie Blue Cross: we send them nothing; you submit the claim yourself.

Being straight with you

What we don't claim

Saying what OHIPay is not matters just as much. So here it is, without spin.

  • We don't claim SOC 2, HIPAA, ISO, or any other compliance certification.
  • We don't claim endorsement or certification by the Ministry of Health or OHIP.
  • The billing engine is advisory: it flags likely issues, and never guarantees a claim will be accepted or paid.

Independent software

OHIPay is independent billing software. It has completed Ontario Ministry of Health conformance testing for MC EDT and Health Card Validation and is listed on ontario.ca. It is not affiliated with or endorsed by the Ministry or OHIP.

It helps you prepare and submit claims, and warns about likely rejections. The decision to accept, adjust, or reject a claim rests entirely with the Ministry.

Questions about your data

Ask us anything before you rely on it

If your practice has specific requirements about how patient data is stored and handled, bring them to a walkthrough and we'll go through the details.

Prefer email? Write to hello@ohipay.ca