CClaimGuard Sign in

MBS Pre-flight · Australian practices

The claims your billing desk almost lodges wrong.

ClaimGuard checks every invoice against the live MBS schedule before it hits ECLIPSE: same-day co-claiming, referral clocks, hospital flags, clinical minimums. 6,050 items, deterministic checks, same answer twice.

6,050 itemsReal MBS schedule, fees, rebates and exclusions
Clauses ECLIPSE needsHospitalInd, LSPN, telehealth setting, 100/50/25 T8
Notes never storedAPP 8 de-identification before any review happens
Rejection 179 tomorrow morning, from a 10-minute consult with an item 36 on it, is the same Tuesday that rejection 160 or 252 might have been. The bill arrives weeks later. ClaimGuard turns it into a one-click line: item 36 → item 23, delete the co-claim, re-check, lodge.
Co-claimingSame-day GP items 3, 23, 36, 44 blocked with the likely rejection code and the one-click fix.
ReferralsGP 12 months, specialist 3 months; clock starts from first specialist attendance, not the written date.
ECLIPSEHospitalInd mismatch, LSPN for group I/R items, Multiple Operations 100/50/25, override flag review.
Clinical minimumsItem 36 wants a 20-minute consult; a 10-minute note warns. Deterministic, no guesswork.
Item lookupSearch the schedule by number or plain English. Fees, 75/85/100 rebates, derived-fee flag.
End-of-day batchDrop the CSV, get the 12 claims that matter out - blocked first, dollars first.
Audit trailEvery claim keeps what was checked and what changed. Note text is never stored.
APP 8 by constructionRedaction happens before the engine sees the text, and the rules never guess.

The honest review

Deterministic rules decide. Notes stay in their box.

If the schedule can say it, that is final. If the schedule cannot say it, ClaimGuard writes what is known, shows what a note says, and refuses to guess. Medicare numbers, DOBs and phone numbers are stripped on the server before any rule reads the note, and the raw text is never stored, logged or sent to a model.

Live walk-through Sign in as a new practice, load the sample day (12 claims) and watch: 5 blocked with reasons, 6 clear, 1 flagged to check the consult length. That is the product.
Not legal, clinical or billing advice. ClaimGuard surfaces what the schedule and loaded rules imply; the practice decides what to lodge. Rejections still happen in the real world - ClaimGuard just makes them rare instead of routine.

Free pilot

ClaimGuard is free while we're in early clinics. No cards, no features held hostage behind a plan. If it starts charging, pilot practices hear first and nothing changes without notice.

Solo
Free during pilot
One practice, your desk only
  • 1 shared worklist, durable
  • All deterministic rules + items
  • New check, batch pre-flight
  • CSV export of reviewed claims
Start free

Running several sites? Each site is its own practice with its own worklist; cross-site reporting is not built yet.

Questions we hear

Do you lodge claims for us?No. ClaimGuard checks and produces an export for ECLIPSE; your software lodges. We never store a patient name, Medicare number or date of birth.
What if the schedule is wrong in a release?We update from the official MBS XML with each release; the version in the footer tells you exactly what is loaded before anything else.
Can we keep our own rules?The deterministic rule set is open to review by your practice manager or consultant. Change proposals get the same careful reading a tax rule change gets.
Can our whole front desk use one worklist?Yes. Every practice gets one shared worklist. The owner mints single-use invite codes in Settings; teammates redeem them from their own sign-in, keep their old solo queue, and act on the shared one.
Data residency?The live service and its database run in Sydney. Notes are de-identified as soon as they reach the server, before any rule reads them, and the stored claim never contains note text.