Insurance Claim Submission and Tracking

Insurance billing in a BC clinic is not one system — it is four or five systems with different submission mechanisms, different timelines, and different consequences for missing a deadline. Jane App handles direct billing to most Canadian extended health plans cleanly. ICBC’s HCPP portal and WorkSafeBC’s Teleplan work differently, and AFU (Autism Funding Unit) adds a monthly submission cycle with a hard deadline. Without a single tracker and automated deadline reminders, claims slip through, payments get delayed, and resubmissions eat the time you saved by submitting early.

This workflow builds the infrastructure that Jane doesn’t provide: a clinic-owned tracking spreadsheet for individual claim records, an Airtable dashboard for aggregated status summaries and aging reports, n8n automation to pull session data and push aggregate metrics, deadline reminders that fire before the window closes, and a monthly reconciliation routine that catches discrepancies before they become write-offs.

The stack

Jane App ($79–$149/month) is the practice management platform this workflow is built on. Jane handles direct billing to most Canadian extended health insurers natively. The workflows described here extend Jane’s billing capability into the portals Jane cannot reach directly.

Heidi Health ($99/month) generates ICBC progress reports and WorkSafeBC functional summaries in the exact formats those portals expect. The clinical content comes from the in-session assessment; Heidi structures it into the report. Running Heidi for insurer reports costs less per month than writing one report by hand.

Airtable (free to $20/month per user) is the aggregated tracking layer. A single base tracks claim volume and status summaries across the practice: counts by insurer and funder, submission status breakdowns (pending, approved, rejected, resubmitted), aging reports by funder, and monthly reconciliation totals. No patient names, claim numbers, or file numbers go into Airtable — individual claim records stay in Jane and the clinic’s own spreadsheets. Multi-practitioner clinics get a shared view by therapist showing submission counts and outstanding amounts; solo practitioners use a filtered personal view. Airtable is preferred over a shared spreadsheet for the aggregate layer because it supports automations, structured views by status, and rollup fields that produce a monthly reconciliation summary without manual calculation.

n8n on OVH Canada VPS (~$15 CAD/month) is the automation layer. It pulls session data from Jane, formats it for submission templates, updates the clinic’s own claim tracking spreadsheet, pushes aggregated status counts to Airtable, and triggers calendar reminders. Patient names, claim numbers, session dates, and file numbers stay on Canadian infrastructure — they never leave Jane and the clinic’s own records. Don’t use Zapier or Make here — no BAA, US servers, and any PHI-adjacent flow through either is a PIPEDA problem.

Google Docs templates serve as the claim template layer for ICBC and AFU submissions. Because neither ICBC’s HCPP portal nor the AFU’s ICM Service Provider Portal has a public API, the automation covers everything upstream of the actual portal entry: pre-filling the template with session data from the clinic’s own systems, staging it for submission, and confirming after the clinician has submitted.

How it gets wired

Extended health (Jane-native): Jane handles direct billing to most Canadian extended health plans. No external workflow is needed beyond confirming the patient’s insurer at intake and keeping Jane’s billing codes current.

ICBC HCPP (manual portal, workflow-assisted): The HCPP portal has no public API. The workflow is:

1. After each ICBC session, Jane records the session with the ICBC file number tagged.
2. An n8n workflow running on the Canadian VPS pulls the session data daily and pre-fills an ICBC claim template in Google Docs with session date, treatment codes, and clinician details.
3. The clinician reviews the pre-filled template, makes any corrections, and submits through the HCPP portal.
4. After submission, the clinician logs the claim number, submission date, and expected payment date in the clinic’s own tracking spreadsheet (Google Sheets or Excel on the clinic’s Canadian infrastructure). The n8n workflow updates Airtable’s aggregate counts — one more ICBC claim submitted, status set to pending.
5. If a claim is rejected, the rejection reason and resubmission deadline are recorded in the clinic’s tracking spreadsheet. A calendar reminder fires 48 hours before resubmission is due. Airtable’s aggregate view reflects the updated status counts (one more rejection, one pending resubmission).

WorkSafeBC Teleplan (Jane-supported, fax required): Jane supports Teleplan billing. The clinical report requirement — faxed within 7 days of the initial assessment — is outside Jane’s billing flow. The workflow:

1. Jane sends the Teleplan billing claim as usual.
2. Heidi Health drafts the clinical report from the in-session assessment notes.
3. The clinician reviews and approves the Heidi draft.
4. The report is faxed within the 7-day window. A calendar reminder fires at day 5 to ensure the window doesn’t close.
5. The clinician logs the fax date and claim status in the clinic’s tracking spreadsheet. Airtable’s aggregate view updates the WorkSafeBC submission count and status summary.

AFU (monthly cycle, deadline-driven): The AFU program ends March 31, 2027. BC is replacing it with new disability benefit programs; new authorization structures and service codes are expected in Q3 2026. Any tracking system built now should be designed for a planned migration by Q3 2026.

Today’s AFU workflow:

1. Each AFU-funded session is tagged in Jane with the client’s AFU file number and session service code.
2. A monthly n8n workflow running on the Canadian VPS pulls that month’s tagged session data from Jane and formats it for the AFU submission template.
3. Each submission is logged in the clinic’s own tracking spreadsheet with client name, file number, amount claimed, submission date, and approval status — this stays on the clinic’s Canadian infrastructure and never enters Airtable. The n8n workflow pushes aggregated totals to Airtable: number of AFU claims submitted that month, total amount claimed, and status breakdown (pending, approved, rejected).
4. Calendar reminders fire 5 business days before the monthly submission deadline so nothing goes in at the last hour.
5. After approval, the clinic’s tracking spreadsheet is updated with the approved amount and payment date. Airtable’s aggregate view reflects the updated totals — approved amounts and outstanding balances by month — feeding the monthly reconciliation summary.

Monthly reconciliation: On the first business day of each month, an n8n workflow generates a reconciliation summary combining the clinic’s detailed tracking spreadsheet with Airtable’s aggregate dashboard: total claims submitted, approved, pending, and rejected by funder, and payments received against expected amounts. Any discrepancy between submitted and received triggers a follow-up task in the clinic’s own system. Airtable shows the high-level reconciliation totals — the clinic’s spreadsheet has the individual claim detail needed to resolve discrepancies. This routine turns a scattered quarterly catch-up into a 20-minute monthly review.

Compliance posture

This workflow processes patient names, claim numbers, session dates, and funder file numbers. All automation must run on Canadian infrastructure. The OVH Canada VPS (Beauharnois, Quebec) is ISO 27001 and SOC 2 Type II certified and falls outside US CLOUD Act jurisdiction. n8n is self-hosted on that VPS with no data transiting non-Canadian servers.

Airtable stores only aggregated operational metrics — claim counts by funder, submission status summaries, aging reports, and reconciliation totals. No patient names, claim numbers, file numbers, or session dates enter Airtable. Individual claim records with patient-identifiable data stay in Jane and the clinic’s own tracking spreadsheet on Canadian infrastructure. If your clinic is on Microsoft 365, Power Automate inside the Canadian M365 tenant replaces n8n and the VPS — it is included in Business Standard, handles PHI-adjacent data within the Canadian tenant, and removes the VPS administration requirement.

The ICBC HCPP portal and the AFU ICM portal are accessed by the clinician directly. Automation populates templates and manages the tracking layer; no automated system submits to government portals on your behalf. The clinician reviews every submission before it goes in.

Common pitfalls

• WorkSafeBC’s 7-day clinical report window is a hard deadline. Missing it delays payment and can result in the claim being denied. Set the calendar reminder at day 5, not day 7.
• ICBC claim rejections that don’t get resubmission dates logged in the clinic’s tracking spreadsheet get forgotten. An n8n automation should create a calendar follow-up task automatically on any rejection so that nothing relies on the clinician remembering to return to it.
• AFU submissions that go in without cross-referencing Jane’s session tags against the client’s remaining fund balance create approval problems. Track fund balances per client in the clinic’s own spreadsheet and confirm available balance before each monthly submission. Airtable’s aggregate view can show total remaining AFU funds across all clients without exposing individual balances.
• The AFU program ends March 31, 2027. Clinics that build the AFU workflow without planning for migration will need to rebuild the tracking logic under whatever authorization structures BC’s replacement programs introduce. Build the current workflow with clean separation between AFU-specific fields and the general claim tracking structure so the migration is a modification, not a rebuild.
• n8n workflows that pull Jane session data rely on Jane’s data structure remaining stable. When Jane releases an update that changes field names or export formats, the n8n workflows may break silently. Schedule a monthly check of workflow logs to catch failures before a month of session data goes untracked.

When this is worth the setup

The tracking and automation layer described here is worth building for any clinic billing to two or more of the four systems (extended health, ICBC, WorkSafeBC, AFU). The overhead of managing four different submission cycles manually, with different deadlines and different consequences for error, produces steady claim leakage — rejected claims not resubmitted, 7-day windows missed, AFU deadlines caught late. At $95–$180 per session, three to five missed or written-off claims per month justifies the setup investment inside the first quarter.

For a solo physio or OT seeing 20 patients per week with a mixed ICBC and extended health caseload, the monthly time recapture on claim prep and follow-up typically runs 3–5 hours. For a multi-practitioner clinic, the combination of a structured clinic tracking spreadsheet (individual claims) and Airtable’s aggregate dashboard (status summaries, aging reports, reconciliation totals) replaces the ad-hoc tracking spreadsheet that someone is currently updating inconsistently. The setup is most valuable at clinics where insurance admin is currently untracked, partially tracked in a spreadsheet, or delegated to a clinician who is also seeing patients.