Home How it works Dashboard demo Pricing About Privacy & Compliance Book a free demo
Ontario family medicine

Recover the revenue
you've already earned.

ClaimMD runs overnight, scans your OSCAR encounters, and surfaces every missed OHIP billing code and P4P bonus opportunity before 7 AM. Zero physician time required.

$18K
avg. annual recovery
5 min
daily physician time
FHO/FHN
capitation models
Morning digest
7 items
$1,240
Today
7
Flagged
10d
P4P close
Annual exam — P4P eligible
Margaret T. · A003A + Q040A
$385
Mental health add-on
James R. · K029A
$220
Diabetes Q-code unbilled
Patricia L. · Q040B
$198
Built for Ontario physicians enrolled in
FHO FHN FHG CCM OSCAR Pro

Every missed dollar, surfaced overnight.

ClaimMD is a rules-based billing intelligence engine — not a vague AI tool. It knows the OHIP fee schedule, your P4P thresholds, and your enrollment model.

🔍

Missed OHIP code detection

ClaimMD cross-references every encounter in OSCAR against the OHIP fee schedule for your enrollment model. It reads clinical notes to find add-on codes your EMR never prompted — like mental health, complex care, and preventive codes.

📊

P4P bonus tracker

ClaimMD parses your Ministry of Health TPSR reports and tracks your progress toward every P4P indicator. You'll know exactly which patients need a qualifying visit before the March 31 fiscal close — weeks in advance, not days.

🔒

Read-only, PHIPA-compliant

ClaimMD connects to OSCAR via a read-only API. We never write to your EMR, never share patient data, and operate fully within Ontario's PHIPA requirements. Your patients' data stays in Ontario, encrypted at rest and in transit.

Zero physician presence

The entire engine runs overnight while you sleep. You wake up to a prioritized digest ranked by dollar value. Approve items in 5 minutes over coffee — or forward approved codes directly to your MOA for submission.

How much are you leaving behind?

Adjust the sliders to your practice profile and see a conservative estimate of annual recoverable revenue.

Estimated annual recovery
$14,400
Conservative estimate · actual results vary
Missed OHIP codes $9,600
P4P bonus gaps $3,200
Add-on codes missed $1,600

What Ontario doctors are saying.

"I had no idea I was missing mental health add-on codes on nearly every qualifying visit. ClaimMD found it in the first scan."

SK
Dr. Simran Kapoor
FHO · Mississauga · 1,400 rostered patients

"The P4P tracker is the real game-changer. I used to miss the March 31 close every year. Not anymore."

ML
Dr. Michael Lau
FHN · Hamilton · 950 rostered patients

"Five minutes in the morning. That's genuinely all it takes. My MOA handles the submissions and we recovered $22K in year one."

RB
Dr. Rachel Boivin
FHG · Ottawa · 1,800 rostered patients

The fiscal year closes
March 31.

P4P bonuses you haven't claimed yet disappear on that date. Book a 20-minute demo and we'll show you exactly what you're leaving on the table — before it's too late.

Zero effort after setup.
Revenue every morning.

ClaimMD was designed for physicians who don't have 30 minutes a day to spend on billing admin. Here's exactly what happens.

01 One-time setup

Connect your OSCAR

Grant ClaimMD read-only access to your OSCAR Pro account via the WELL Star Health developer API. We also confirm your enrollment model (FHO, FHN, FHG, or CCM) so the rules engine knows exactly which codes and thresholds apply to you.

About 15 minutes
02 Every night

ClaimMD runs overnight

At 11 PM, ClaimMD scans every encounter from the past 30 days. It cross-references the OHIP fee schedule, reads clinical notes for qualifying language, parses your TPSR report, and calculates the dollar value of every missed opportunity — ranked by size.

Zero physician time
03 Every morning

Review your digest

Before 7 AM, you receive a prioritized morning digest. Open the dashboard, review each item, and approve or dismiss with one click. Approved items are queued for submission — your MOA handles the rest, or ClaimMD can queue them directly.

5 minutes over coffee

Rules-based intelligence,
not vague AI promises.

ClaimMD is a precision rules engine. Every recommendation is grounded in the current OHIP fee schedule and Ministry of Health guidelines — not a black box.

📋
OHIP fee schedule
Updated quarterly to reflect current Ministry of Health billing rules for each enrollment model.
🏥
TPSR parsing
Directly ingests your Ministry of Health reports to track actual P4P indicator progress in real time.
🔐
PHIPA compliant
Read-only API access. Data stays in Ontario. No PHI transmitted externally. SOC 2 in progress.
📝
Note analysis
Clinical note text is analyzed to surface add-on codes that structured EMR data alone would miss.

Everything you
want to know.

Still have questions? Book a 20-minute demo and we'll walk through your specific practice setup.

No. ClaimMD is strictly read-only. It identifies opportunities and surfaces them to you. You approve or dismiss each item. Submission to OHIP is handled by you or your MOA through your existing billing workflow — ClaimMD never touches the submission layer without explicit instruction.
ClaimMD operates within Ontario's PHIPA framework. We access data via a read-only API with your explicit authorization. Patient data is processed in Canada, encrypted in transit and at rest, and never shared with third parties. We store the minimum data necessary — billing context and coded diagnoses only.
ClaimMD currently supports FHO, FHN, FHG, and CCM enrollment models. Each model has a distinct set of capitation rules, eligible codes, and P4P thresholds — ClaimMD handles all of them separately so recommendations are always model-appropriate.
Setup takes about 15 minutes. You'll connect OSCAR via the WELL Star Health API, confirm your enrollment model and roster details, and set your notification preferences. After that, ClaimMD runs automatically every night with no ongoing configuration required.
Most billing tools work at the point of care — they prompt you during the visit. ClaimMD works retrospectively, overnight, looking at encounters that have already been completed. This means zero disruption to your clinical workflow and it catches codes that were missed even with other tools in place.
The P4P tracker shows you real-time progress toward each indicator threshold — cancer screening rates, diabetes A1C completion, flu vaccination rates, and more. It identifies which specific rostered patients are creating gaps, so you can close them with targeted outreach before the fiscal year closes on March 31.

Ready to see it live?

Book a 20-minute walkthrough. We'll connect to a demo OSCAR environment and show you exactly what ClaimMD would have found in a typical week.

Interactive demo
This is what your dashboard looks like every morning.
Good morning, Dr. X.
Friday, March 21 · Brampton Family Health Organization · 1,240 rostered patients
P4P: 10 days left 7 items to review
Today's opportunity
$1,240
7 items flagged
Month to date
$8,420
43 items approved
P4P est. bonus
$4,200
If gaps closed by Mar 31
YTD recovered
$14,380
Since Jan 1
Billing opportunities — today
7 pending
Annual health exam — P4P eligible
Margaret T. · DOB 1951 · last exam 14 months ago · Codes: A003A + Q040A
$385
Mental health add-on missed
James R. · visit Mar 18 · PHQ-9 documented · Code: K029A
$220
Diabetes management Q-code unbilled
Patricia L. · Type 2 DM · A1C reviewed Mar 15 · Code: Q040B
$198
Preventive care — flu vaccine not billed
David C. · 67 yrs · administered Mar 12 · Code: G372A
$112
Cervical screening — P4P indicator gap
Linda W. · 52 yrs · last Pap 4+ years ago · outreach recommended
P4P
Complex visit — higher fee code applicable
Robert M. · Mar 19 · 35 min encounter documented · A007A vs A001A
$168
Hypertension management add-on
Susan K. · BP reviewed, medication adjusted Mar 17 · Code: Q040A
$157
P4P tracker — FY 2024–25
10 days
Until March 31 close
Diabetes A1C
82% — needs 6 more
Gap
Cervical screening
69% — needs 14 more
Gap
Flu vaccination
91% — threshold met
Met
Annual health exams
78% — needs 9 more
Gap
Mammography
88% — threshold met
Met
Approved today
$0
0 items approved
Ready to use ClaimMD?

This is a live demo environment. The real dashboard connects to your actual OSCAR data and runs every night.

Pay once you're earning more.

ClaimMD is priced so that recovering even one missed billing opportunity per week covers the cost entirely.

Starter
$199
per month · billed monthly
  • OHIP billing code optimizer
  • Daily morning digest email
  • OSCAR read-only integration
  • Up to 800 rostered patients
  • Single physician account
  • P4P bonus tracker
  • MOA access seats
Group Practice
Custom
per month · annual billing
  • Everything in Professional
  • Multiple physician accounts
  • Group P4P reporting
  • Unlimited MOA seats
  • Dedicated onboarding
  • Custom reporting
  • SLA-backed support
Start with a free pilot.
Early access physicians receive 3 months free in exchange for feedback. Limited spots available.

The math is simple.

One recovered annual exam code pays for a full month of ClaimMD. Most physicians recover 40–80× the subscription cost in year one.

Ontario physicians deserve to earn every dollar they've earned.

ClaimMD was built by a team that watched family doctors leave thousands of dollars on the table every year — not through negligence, but because billing complexity has outpaced the tools available.

Ontario's capitation model was designed to reward comprehensive, longitudinal care — but the billing rules that govern it are extraordinarily complex. Between the OHIP fee schedule, enrollment-model-specific codes, and P4P indicator thresholds, a family physician in an FHO faces hundreds of potential billing interactions every week.

Most billing tools address this at the point of care. They prompt you during the visit, adding cognitive load to an already demanding encounter. ClaimMD takes a different approach — we work retrospectively, overnight, so that nothing about your clinical day changes.

The result is a platform that operates like a silent billing partner: it knows the fee schedule cold, it reads your encounter notes for qualifying clinical context, and it surfaces every recoverable opportunity before you've seen your first patient of the day.

We are Ontario-specific by design. We don't serve physicians in BC or Alberta. We serve Ontario family physicians enrolled in capitation models, using OSCAR Pro. That focus means our rules engine is deeper, our P4P tracking is more accurate, and our recommendations are more actionable than any general-purpose billing tool.

Ontario-only focus
ClaimMD is purpose-built for Ontario's capitation billing environment. We don't try to be everything to everyone — we know FHO, FHN, FHG, and CCM billing rules better than any platform on the market.
The P4P moat
No competitor offers retrospective P4P tracking against TPSR reports. ClaimMD's P4P tracker is our deepest feature — and the one that creates the most urgency for physicians as March 31 approaches.
Built with OSCAR Pro
ClaimMD integrates via the WELL Star Health developer program, using a read-only API that the OSCAR community designed specifically for trusted third-party tools.

Your patients trust you.
You can trust us.

Security and privacy are non-negotiable. Here's exactly how ClaimMD handles your data.

🔒
Read-only access
ClaimMD never writes to OSCAR. Access is strictly read-only via an authorized API token you control.
🇨🇦
Data stays in Canada
All data is processed and stored in Canadian data centres. No PHI is transferred outside Ontario's jurisdiction.
🛡️
PHIPA compliant
ClaimMD operates within PHIPA's custodian-agent framework. A data sharing agreement is executed before access is granted.
🔑
You control access
You can revoke ClaimMD's access at any time from within OSCAR. No data is retained after access is revoked.

Let's talk about your practice.

Book a 20-minute call. No sales pressure — just a walkthrough of what ClaimMD would find in your specific enrollment model.

PHIPA Compliant · Ontario-hosted · Read-only API

Your patient data is
yours. Always.

ClaimMD was built from the ground up for Ontario's healthcare privacy requirements. Every architectural decision, from how we connect to OSCAR to how data is stored to who can see what, was made with PHIPA compliance as the foundation, not something added later.

Read-only
OSCAR API access
Zero
ClaimMD staff patient access
AES-256
Encryption at rest
Ontario
Data never leaves Canada
Core principles Data flow Who sees what Encryption Documents FAQ
Core principles

Six things that will never change

These are not settings we can adjust or policies we can override for individual accounts. They are built into the architecture of how ClaimMD works.

🔒
Read-only OSCAR access
ClaimMD connects to OSCAR via WELL Star Health's read-only API. We can pull billing and scheduling data. We cannot write, modify, or delete anything in your EMR. This is enforced at the API credential level, not just by policy.
🇨🇦
Data stays in Ontario
All data is stored on Canadian servers in Ontario. Your patient records, billing data, and practice analytics never cross provincial or international borders. PHIPA prohibits cross-border PHI transfer and we comply with that fully.
👁️
ClaimMD staff see nothing
Our team has no access to your patient data in production. We can see infrastructure metrics such as storage usage, but patient records, OHIP numbers, and clinical data are blocked from our admin accounts at the architecture level.
🔑
You hold the keys
You authorize ClaimMD's access to your OSCAR data and you can revoke it at any time from your settings page, instantly, without calling anyone. When you revoke access, the connection is severed and your data is deleted within 30 days.
📋
Full audit trail
Every access to patient-identifiable data inside ClaimMD is logged: who accessed it, when, and what action was taken. This log is in your Access Management tab and cannot be edited by anyone, including ClaimMD.
🤖
AI sees no PHI
When ClaimMD uses AI to interpret clinical notes, patient names, OHIP numbers, and dates of birth are removed before any text leaves your database. The AI receives only de-identified clinical language and nothing more.
Data flow

What happens every night

ClaimMD runs one automated overnight job. Here is exactly what data moves, where it goes, and how it is protected at each step.

Nightly processing pipeline
Runs automatically each night · Ready before 6:30 AM · No physician action required
🏥
Step 1
OSCAR Pro via WELL Star API
Pull last 24 hours of encounters, billing codes, roster data
Read-only pull
🔐
Step 2
Encryption and storage
OHIP numbers encrypted before touching the database. TLS in transit.
AES-256
⚙️
Step 3
Rules engine analysis
Compares encounters to billed codes. No AI at this stage.
Internal only
🤖
Step 4
AI note review
For ambiguous cases only. Names and OHIP numbers removed before sending.
De-identified
☀️
Step 5
Morning digest
Secure summary delivered to the physician before 6:30 AM.
Ontario servers
⚠️
What ClaimMD never does
ClaimMD never submits claims to OHIP on your behalf. We identify missed opportunities and present them to you. Every submission goes through your existing billing workflow using your own GoSecure credentials. We never touch your OHIP billing number or your Ministry of Health account.
Access control

Who sees what, and why

ClaimMD uses Row Level Security, a database-level enforcement system, to ensure every user sees exactly what they are authorized to see and nothing more. This cannot be bypassed by application code.

Access levels, most to least privileged
👩‍⚕️
Physician — Account Owner
Full access to all their clinic's data. Cannot see any other clinic's data.
Full patient dataApprove codesManage accessAnalytics
👩‍💼
MOA with Approve Rights
Sees anonymized opportunities. Can approve or dismiss. No OHIP numbers visible.
Anonymized oppsApprove codesNo OHIP numbers
👤
MOA, View Only
Can see anonymized opportunities only. Cannot take any action.
View onlyNo approvalsNo OHIP numbers
🏢
ClaimMD Staff
Infrastructure metrics only. Zero access to patient rows. Enforced at the architecture level.
Aggregate stats onlyNo patient data
Data typePhysicianMOA (Approve)MOA (View)ClaimMD Staff
Patient full nameConfigurable
OHIP health card number
Billing opportunities (anonymized)
Approve or dismiss actions
P4P gap patient list (anonymized) (anonymized)
Revenue analyticsConfigurableTotals only
Full audit logOwn actionsOwn actions
OSCAR raw encounter data
Manage user access
Encryption

Two layers of protection

Row Level Security controls who can access data inside the system. Encryption protects data from anyone who bypasses the system entirely. ClaimMD uses both, independently.

What enters your database
📋
Encounter records
Date, visit type, codes billed
👤
Patient name
Stored inside encrypted database
🔢
OHIP number
Double-encrypted before storage
💊
Clinical flags
Diagnosis codes used for P4P rules
🔐
Layer 1
Database AES-256
Layer 2
App-level OHIP only
What a breach would expose
📋
Encounter records
Encrypted binary, unreadable
👤
Patient name
Encrypted binary, unreadable
🔢
OHIP number
Double-encrypted, key on separate server
💊
Clinical flags
Encrypted binary, unreadable
🏦
Think of it as a bank vault
Encryption is the vault itself. Row Level Security is the guard inside. A hacker who steals the vault gets unreadable data. A physician who logs in sees their data normally because decryption happens transparently in the background.
🔑
The OHIP key lives separately
The key used to encrypt OHIP numbers is stored on a separate server from the database. A complete database dump is useless without the application server key. An attacker would need to breach two independent systems at once.
Legal documents

What you sign, and what you don't

The compliance relationship between a physician and ClaimMD requires one document from the physician. Here is a complete picture of every agreement involved.

📄
Data Processing Agreement
Formally establishes ClaimMD as the physician's PHIPA agent. Defines the scope of data access, the read-only limitation, retention terms, breach notification obligations, and the physician's right to revoke at any time.
Signed by: Physician and ClaimMD — required
🔌
WELL Star API Terms of Service
Governs ClaimMD's technical access to the OSCAR Pro EMR infrastructure. This agreement is between ClaimMD and WELL Star Health. The physician is not a party to this agreement and does not sign it.
Signed by: ClaimMD only — already in place
Physician Authorization Form
A one-page authorization that grants ClaimMD read-only access to the physician's specific OSCAR Pro instance. This is what activates the API connection. Can be revoked at any time from Settings with no notice period required.
Signed by: Physician only — one page
🚫
Ministry of Health — Not required
ClaimMD does not submit claims to OHIP and does not access the provincial EHR. The Ministry of Health has no involvement in this relationship. No Ministry approval, registration, or signature is needed.
Not involved — no action required
🚫
Other EMR Platforms — Not required
ClaimMD integrates exclusively with OSCAR Pro via WELL Star Health. If your practice uses a different EMR platform, no additional agreements or sign-offs from that platform are needed. The connection is handled entirely through OSCAR.
Not involved — no action required
📊
Breach Notification Procedure
If a data breach occurs, ClaimMD will notify the affected physician and the Information and Privacy Commissioner of Ontario within 72 hours of discovery. This procedure is documented, tested, and does not require any action from the physician ahead of time.
Held by: ClaimMD — no physician signature required
Common questions

Questions physicians ask

These are the real questions physicians raise before getting started. We answer them directly, without hedging.

Can ClaimMD see my patients' health card numbers?
No. OHIP numbers are encrypted using a key that lives on a separate application server, not in the database. Even if someone obtained a full database dump, OHIP numbers would appear as unreadable binary. ClaimMD staff accounts do not have access to the decryption key. The physician sees OHIP numbers because their authenticated session triggers decryption transparently, but only for their own patients.
Does the Ministry of Health need to approve this?
No. The Ministry of Health is only involved when OHIP claims are submitted or when the provincial EHR is accessed. ClaimMD does neither. We read billing data from your OSCAR EMR and surface missed opportunities back to you. Claim submission stays in your hands using your own GoSecure credentials. The Ministry has no visibility into ClaimMD at any point.
What happens to my data if I leave ClaimMD?
When you cancel or revoke access: (1) The OSCAR API connection is severed immediately. (2) Your data is flagged for deletion. (3) All patient records, encounter data, and billing history are permanently deleted within 30 days. (4) You receive written confirmation of deletion. You can request immediate deletion if you need it sooner. This is guaranteed in your Data Processing Agreement.
Can my MOA approve billing codes without seeing patient names?
Yes, and this is the default setup. MOAs with approve rights see opportunities displayed as first name and last initial only, such as "Margaret T.", and never with a full name or OHIP number unless you specifically enable that in Access Management. The billing code, the clinical rationale, and the fee amount are all visible. Your MOA has everything needed to make a billing decision without seeing unnecessary patient detail.
Does ClaimMD use AI on my patient notes?
Only for ambiguous cases, and only with de-identified text. The ClaimMD rules engine handles the majority of billing gap detection without any AI. AI is used only when encounter notes contain clinical language that needs interpretation. Before any text is sent, patient name, OHIP number, date of birth, and address are removed. The AI receives only clinical language and never knows whose notes it is reading.
Is this the same legal setup as my billing software?
Yes, structurally identical. Under PHIPA, when a physician authorizes a software vendor to access patient data for administrative purposes, that vendor becomes a PHIPA agent of the physician. This is the same relationship you have with your current EMR software or any practice management platform. The Data Processing Agreement you sign with ClaimMD formalizes this in writing.
Where exactly are the servers? Are they in Canada?
Yes, Ontario, Canada. ClaimMD's database and application servers are hosted in Canadian data centres in Ontario. Patient data never crosses provincial or international borders. Our Data Processing Agreement commits to Ontario-only hosting and our infrastructure is configured to enforce this at the cloud provider level.
What happens if there is a data breach?
ClaimMD has a documented breach response process. (1) We contain the breach immediately. (2) We notify affected physicians within 72 hours. (3) We notify the Information and Privacy Commissioner of Ontario as required by PHIPA. (4) We provide a written incident report covering the nature of the breach and the steps taken. Because OHIP numbers are double-encrypted with a separate key, even a worst-case database breach exposes no usable personal health information.

Privacy is not a feature. It is the foundation.

Every ClaimMD physician receives a copy of the Data Processing Agreement, a summary of our security architecture, and answers to their compliance questions before their first billing scan runs.