WSIB · Billing integration
Know exactly which WSIB lines have been sent, and how.
WSIB billing goes out through the TELUS Health network as a batch, and in practice some lines get sent electronically while others go manually. Clinicmaster runs the queue and tracks both — so the question "has this been billed?" has an answer per invoice line, per case.
The WSIB integration
WSIB is Ontario’s Workplace Safety and Insurance Board. Clinicmaster’s integration reaches it through the TELUS Health network and is built around a batch claim queue: WSIB invoice lines collect into a queue, and the system records which were transmitted electronically and which were sent manually. Case dashboards show visit counts and send status for both block-billing and fee-for-service cases, and the reports WSIB expects are tracked by case phase.
What the WSIB integration does.
WSIB billing rarely goes out in one clean channel. The useful thing is not pretending otherwise — it is tracking reality per line.
A batch queue over your invoice lines
WSIB invoice lines collect into a per-clinic claim queue built on the billing you have already recorded, rather than a parallel set of claim forms.
Electronic sends tracked
Lines transmitted through the TELUS Health network are grouped into claim requests, so each electronically-sent line is traceable to the request that carried it.
Manual sends tracked too
Lines your team sent outside the electronic channel are recorded as manually sent. That is the difference between a billing system you can trust and one that shows gaps.
Case dashboards with visit counts
Block-billing and fee-for-service WSIB cases each get a dashboard view showing visit counts and send status, so a case that has stalled is visible.
Both WSIB billing models
Block billing and fee-for-service cases are handled distinctly, matching how WSIB work is actually structured rather than forcing one model.
Reports tracked per case phase
The WSIB reports expected at each phase of a case are tracked as chart-note forms, so documentation obligations stay attached to the case.
From billable visit to accounted-for line.
WSIB lines collect into the queue.
Invoice lines on WSIB cases feed a per-clinic claim queue automatically, so nothing has to be gathered up manually before billing.
Lines go out and are marked.
Lines transmitted through the TELUS Health network are grouped into a claim request; lines sent another way are recorded as manually sent.
Dashboards show what is outstanding.
Case dashboards show visit counts and send status per line, and WSIB reports are tracked per case phase, so gaps surface rather than accumulate.
What this integration does not do
Be clear on the nature of this one: WSIB billing here is a batch queue with assisted and manual sending, reached through the TELUS Health network — it is not real-time adjudication with automatic payment posting like the private-insurer integrations. Its strength is that it tracks the state of every line honestly, including the ones sent manually. Adjudication, fee schedules and reporting requirements are WSIB’s. Enrolment is arranged separately.
What Clinicmaster records for WSIB billing.
The recurring WSIB problem is not submission, it is knowing what has and has not gone. Everything below exists to answer that.
Back to regional billing- Per-clinic claim queue
- Invoice lines on WSIB cases
- Electronic claim request groups
- Lines sent electronically
- Lines sent manually
- Block-billing case dashboard
- Fee-for-service case dashboard
- Visit counts per case
- WSIB reports per case phase
WSIB billing questions.
Scale your Organization with Clinicmaster.
30-minute working session with a solutions engineer. Bring your current numbers — we'll show you the gap.