Ontario OHIP validation for any system you run

Ontario OHIP validation

The OHIP Validation API connects to the Ministry of Health's Health Card Validation (HCV) system so that a health number and version code can be checked in real time — typically in under a second — before a service is rendered. It replaces a SOAP integration with client certificates, WS-Security and a mandatory conformance process with a single HTTPS request carrying an API key header.

Because it is a plain REST/JSON service, it is built to integrate with whatever a practice already runs: EMR systems, health applications, billing software, booking and scheduling tools, patient intake workflows and in-house builds. There is no SDK to adopt and no certificate store to maintain. Batch validation lets many cards be checked in one call, which is how billing agencies and multi-provider clinics use it. If you are trying to understand a specific result, the OHIP response code reference explains every code band the ministry returns.

Validation is one half of the OHIP billing cycle. The MCEDT/EDT integration handles the other half — submitting claim files to the ministry and retrieving remittance advice and error reports — and when claims do come back rejected, the MOH Rejection Correction Report decodes the ministry's error codes, groups rejections by underlying cause and identifies which claims are still recoverable. That one is free and does not require an account.

What else we build

Dr. Tools also develops electronic medical records, clinical transcription and AI-assisted form completion for Canadian healthcare professionals. The work is focused on Ontario, because the systems that matter here — HCV, OHIP claim submission, Medical Claims Electronic Data Transfer — are provincial infrastructure, and integrating with them properly is not something you do generically.

Our users are specialist physicians and the practices around them: dermatology, cardiology, internal medicine, rheumatology, gastroenterology, endocrinology, nephrology, neurology, psychiatry and surgery, along with the billing agencies and software vendors who serve them.

Clinical documentation

AI Transcriber provides GPU-accelerated medical speech recognition with speaker diarization, so the transcript distinguishes clinician from patient, and assembles a SOAP note draft with clinical entities extracted. It is designed to run on self-hosted hardware, keeping patient audio inside the practice network. FormsMD automates the completion of lab requisitions, insurance claim forms, disability applications, referral letters and government forms from chart data, with optional PHI de-identification. In both cases the output is a draft for a qualified clinician to review and sign.

The practice itself

PocketEMR is a web-based electronic medical record with patient management, e-prescribing with pharmacy fax delivery, clinical notes with AI voice transcription, a virtual fax centre, appointment scheduling and integrated OHIP billing. The other tools are built into it, so validation happens at intake and rejected claims come back decoded inside the system that produced them.

Where your data lives

All Dr. Tools infrastructure runs within Canadian data centres. Patient data is processed and stored in Canada and is not transferred outside the country in the ordinary operation of our services. Controls include encryption in transit and at rest, API keys hashed with Argon2id, health card numbers HMAC-hashed in audit logs, role-based access, two-factor authentication on administrative accounts, and separate validation, security and administrative audit logs. These are built for the obligations Ontario healthcare providers carry under the Personal Health Information Protection Act (PHIPA) and Canada's federal privacy legislation (PIPEDA). No external body has audited or certified them, and we will not imply otherwise.