Claim files up.
Remittance and errors down.
A programmatic integration with Ontario's Medical Claims Electronic Data Transfer service — submit claim batches and retrieve what the ministry sends back, without anyone logging in to fetch a file.
Claims produced by your EMR or billing software
MCEDT / EDT service
Dr. Tools sits in the middle and handles the transfer. Your ministry account, your claims.
The other half of the billing cycle
Health card validation asks a question before the visit: is this card valid, is this patient eligible today. MCEDT handles what happens afterwards — the claim file goes to the ministry, and the ministry sends back remittance advice and error reports saying what it paid and what it did not.
In most practices that second half runs on a person remembering. Someone logs in, downloads a file, and either reads it or files it somewhere nobody looks. When that step is missed for a few cycles, the first anyone hears about a systematic billing problem is a shortfall in the deposit.
Moving the transfer into software does not make claims get paid. It makes the reports arrive reliably, which is the precondition for noticing anything — and those same error reports are what the free rejection correction report reads.
Where it fits
The billing cycle, end to end
Three Dr. Tools products cover three different moments. You can use any one of them alone.
OHIP Validation API
Confirm the card is valid and the patient eligible, while they are still standing in front of you.
$49/month →MCEDT / EDT
Submit the claim file and retrieve remittance advice and error reports automatically.
You are hereRejection Correction Report
Decode the error report, group the causes and find out which claims are still recoverable.
Free →What you'll need
Your own Ministry of Health credentials, as with validation — obtaining them is a ministry process on your side. Beyond that, tell us what produces your claim files today and we'll work out the shape of the integration with you. Email support@drtools.ca or use the demo form.
Features
What it handles
Claim file submission
Send OHIP claim files to the ministry programmatically, on your schedule, from the system that already produced them.
Remittance retrieval
Pull remittance advice back down automatically instead of someone remembering to log in and check for it.
Error report download
Ministry error reports come back through the same channel — which is exactly the file the free rejection correction report reads.
One account, one integration
MCEDT shares your Dr. Tools account with the OHIP Validation API — one set of credentials, one place to look.
Audit logging
Every upload and download is logged, so what was sent, when, and what came back is answerable months later.
Your ministry account
Transfers run against your own ministry credentials. Dr. Tools moves the files; the account and the claims remain yours.
Technology
FAQ
MCEDT / EDT Integration questions
What is MCEDT?
Medical Claims Electronic Data Transfer — the Ontario ministry service used to upload claim files and download the reports that come back, including remittance advice and error reports. It is the channel through which batch OHIP billing actually moves.
How does this differ from the OHIP Validation API?
Validation asks a question before the visit: is this card valid and is this patient eligible today. MCEDT moves the claim afterwards: submitting the claim file and retrieving what the ministry sends back. Together they cover both ends of the billing cycle, and they share one Dr. Tools account.
Do I need my own ministry credentials?
Yes — MCEDT runs against your own ministry account, same as validation.
How do I get access?
Contact us with what your claim submission process looks like today and which system needs to talk to MCEDT. This one is set up in conversation rather than self-serve.
Tell us how claims move today
MCEDT access is set up in conversation rather than self-serve, because how it fits depends on what produces your claim files. Tell us that and we'll tell you what's involved.