The IT side of OHIP billing.
The billing team owns the codes. We own everything that has to work in order for the claim to get out the door and the remittance to come back.
What we see most often.
Claim upload to EDT fails out of nowhere
Usually GO Secure: the credential rotated, the account locked, or a new staff member is using a shared identity that just expired. We restore access and recommend an identity setup that does not break the next time staff turns over.
MOH error reports stop arriving
The EDT download job stopped, the destination folder filled up, or a network path changed. We fix the immediate break and put monitoring in place so silence on the download side raises an alert before the billing team notices.
The EMR cannot generate a clean claim file
An EMR upgrade, a Windows update, or a path change broke the file write step. We rebuild the export configuration and test against a known-good file before live submission.
New billing submitter added and nothing works
A new physician or a new locum added to billing means new GO Secure setup, new EMR mapping, and possibly new MOH paperwork. We handle the technical setup and make sure the first real submission goes through cleanly.
Where we fit alongside the billing team.
The billing team owns claim content: fee codes, service dates, diagnostic codes, corrections, and the relationship with the Ministry of Health on rejected claims. They know the rules and the workflow.
Medibyte owns the infrastructure: the EMR's ability to write the file, the connection out to EDT, the credentials, the scheduled retrieval of reports back from the ministry, and the storage of those files in a way that survives a server failure. When the two intersect, we work together with the billing team so a problem gets owned end to end.
More clinic IT help.
OHIP billing IT questions.
EDT is the Electronic Data Transfer service the Ministry of Health uses for OHIP claims, remittance, and error reports. Clinics upload claim files to EDT and download reports back. The EMR usually packages the file and either submits directly or hands it to a billing module. When EDT submissions fail, the cause is often outside the EMR: GO Secure access, the upload path, or a credential that lapsed.
Rejected at upload usually means a credential or path issue: GO Secure has rotated, the user account is locked, or a file naming convention changed. Rejected by the ministry after upload usually means data inside the file: a missing or mistyped HCN, an invalid fee code, or service date logic. We help with the first set. The billing team owns the second set.
Yes, and that is usually what tips clinics off that something broke. If MOH error reports and remittance files stop landing, the EDT connection has dropped, the scheduled job that pulls them stopped, or the local file path filled up. We restore the link, retrieve the queued reports, and put monitoring on the path so the next break is caught the same day.
No. The clinic's billing person owns the codes, the corrections, and the relationship with the MOH on claim content. We own the infrastructure: the connection, the credentials, the file handling, and the integration between the EMR and the billing module. The two roles work together.
OHIP claims stuck? EDT downloads silent?
Same-day remote response for managed clients. We restore the connection, retrieve queued reports, and put monitoring in place so the next failure is caught early.
or send a message