Billing and claims

Photograph a patient sticker with your phone and the record is created from it. Email the theatre list to your own list address, or upload it in the dashboard, and the whole session is created at once. Anaemate's agentic OCR reads the page the way a person would — handling scans, photographs and awkward print — then checks what it has read against Medicare, the health funds and its reference lists. Where details differ from the patient's existing record, the case is flagged so you can choose which to keep, and anything can be corrected from the app or the dashboard before it is lodged.

• Sticker recognition from your phone camera
• Theatre lists read from a PDF, a scan or a photo of a printed page
• Returning patients matched to their existing record, not duplicated
• Details that differ from the patient’s record flagged for you to choose
• Removes the logbook and the email to a billing agent

Eligibility is confirmed as part of capture, so cover and payer are established before an estimate is issued rather than discovered after the account is raised.

• Patient eligibility confirmed at capture
• Payer identified — fund, Medicare, DVA, workers’ compensation or defence
• Missing details surfaced before lodgement, not after rejection

Rules define how a case is priced before it reaches the billing step. Set a unit value, a gap fee or a total fee, and apply it to a whole list or to an individual case. The same rule produces the same price every time, which is what makes pricing predictable across a practice.

• Unit value, gap fee or total fee
• Applied to a list or to a single case
• Consistent pricing across providers in a group

Claims are lodged to Medicare and private health funds through ECLIPSE. Workers’ compensation, DVA and defence claims are supported, as is public-in-private claiming.

• Medicare and private health funds via ECLIPSE
• Workers’ compensation, DVA and defence
• Public-in-private claiming (1% fee plus GST)
• Same-day submission

What was billed, under which rule, by whom and when is retained against the record — which is what makes a query answerable months later without reconstructing it from memory.