MPI · Case tracking
Track Manitoba auto-insurance cases and bill them your way.
Manitoba collision patients are covered by MPI, which authorises treatment and requires documentation as care proceeds. Clinicmaster gives you the case management side of that work: the case is tagged as MPI, authorised visits and coverage are tracked, the documentation the program expects is produced from templates, and you invoice MPI from the same ledger as every other payer. What it does not do is submit to MPI electronically — no Clinicmaster integration exists for that.
MPI in Clinicmaster
Manitoba Public Insurance is the province’s public auto insurer, funding care for people injured in collisions. In Clinicmaster, MPI is a case type — not an electronic billing channel. That means you can run the clinical and administrative side of these cases properly: classify them, track authorised visits and coverage, produce the required reports from templates, invoice the payer, and report on the work. Submitting the claim to MPI remains your team's step, done the way that payer requires.
What Clinicmaster does for MPI cases.
Everything below is real. There is no electronic submission to MPI — so the value is in making the case, the paperwork and the invoice manageable.
Cases classified by payer
A case is tagged as MPI, which makes this work a distinct, filterable, reportable group rather than something mixed in with your private and public payers.
Authorised visits tracked
Approved visit counts and case dates are held on the case, so treating beyond what the payer authorised is something you can see coming rather than discover at invoicing.
Required documentation from templates
The reports and forms MPI expects are produced from configurable templates against the chart, so the paperwork is generated from the clinical record rather than retyped.
Invoice the payer from one ledger
MPI invoices are raised through the same accounting path as every other funder, so they appear in the same receivables and financial reporting.
Split billing across payers
Where a patient’s care is shared between the payer and another party, billing splits by coverage so each portion is invoiced to the right payer.
Reportable as its own payer
Because the case type is stored on the case, you can report on MPI volume, revenue and outstanding balances specifically.
From referral to invoiced MPI case.
The case is opened as MPI.
Tagging the case by payer type is what makes the work identifiable, and it drives the templates, coverage tracking and reporting that follow.
Care is delivered and recorded.
Visits are tracked against what was authorised, and the reports MPI requires are produced from templates against the chart.
You invoice, then send it your way.
The invoice is raised to MPI through the normal ledger. Getting it to the payer is your team's step — by the payer's own portal, form or process.
What this is — and is not
Stated plainly, because it matters: Clinicmaster does not submit claims to MPI electronically, and does not post MPI remittances automatically. In the product MPI is a case type, not a billing integration. You track the case, produce the documentation and raise the invoice here; sending it to MPI and recording the payment are manual steps. If you need automated electronic submission, the programs that genuinely have it are listed on regional billing.
What Clinicmaster tracks on a MPI case.
Deliberately scoped. Every item below is a real capability, and nothing here implies a submission channel that does not exist in the product.
Back to regional billing- Payer case type
- Case dates and status
- Authorised visit counts
- Coverage details
- Chart notes and reports
- Configurable form templates
- Invoices to the payer
- Split billing by coverage
- Reporting by case type
MPI questions.
Scale your Organization with Clinicmaster.
30-minute working session with a solutions engineer. Bring your current numbers — we'll show you the gap.