TL;DR — MBS Item 91891 Telehealth Compliance in Australia (2026)

• Under 2026 AHPRA guidelines, telehealth AI must capture a Jurisdictional Attestation—verifiable proof the patient was physically in Australia at the time of the session—for MBS 91891/91890 claims to be legally valid.

• Generic telehealth billing guides list the codes but miss the legal trigger: without a location attestation, a compliant-looking claim can still be clawed back on audit.

• Clinical-Grade Scribing at Scribing.io converts a patient's verbally stated location into a PSMA G-NAF–normalized address, dual-checks GPS/IP, time-stamps it, and seals it as a W3C Verifiable Credential on the FHIR Encounter—hard-stopping 91891/91890 billing if the patient is offshore.

• Real audit exposure remains severe: a single unattested offshore claim can cascade into an $18,600 clawback across similar claims plus a compliance notice.

• MBS 91891 & 91890 Compliance Overview

• Jurisdictional Attestation as a Verifiable Credential

• Clinical Logic: Preventing an $18,600 Clawback

• ICD-10 Documentation Standards

• Operations Director Rollout Checklist

• Pricing & Next Steps

MBS Item 91891: Telehealth Compliance in Australia — The 2026 Operations Playbook

Most billing guides treat MBS Item 91891 as a code-selection problem: pick the item, log the time, submit the claim. That framing is now dangerously incomplete under 2026 rules. The Medical AI Scribing layer at Scribing.io exists precisely to close the gap between a clean note and a legally defensible claim.

This playbook is written for Clinical Operations Directors who carry retrospective audit liability across a full claim book. Ambient Clinical Intelligence from Scribing.io reframes telehealth compliance from a documentation-quality task into a legal-evidence discipline. The distinction is the entire subject of this document.

MBS 91891 & 91890: What Compliance Actually Requires

CLINICAL UPDATE 2026: Revised for new CMS CPT G2211 standards, SB 1120 compliance, and FHIR interoperability.

MBS Item 91891 is a Level C telephone attendance by a GP lasting 20 minutes or more; 91890 is its shorter Level B counterpart. Historically, eligibility ended at time threshold and clinician–patient relationship. That surface rule no longer determines whether the rebate holds.

The Anchor Truth for 2026: AHPRA guidelines require that telehealth AI capture a Jurisdictional Attestation—confirming the patient's physical location at the time of the session—to make the MBS 91891/91890 rebate legally valid. Eligibility no longer ends at "was this a 20-minute call?" It ends at "can you prove the patient was physically in Australia?"

This shifts telehealth compliance decisively from a documentation issue to a legal-evidence issue. A perfectly worded note attached to a claim for a patient who was in Bali is not a good note—it is an admissible record of a non-compliant claim.

Operations Directors evaluating vendors should treat jurisdictional attestation as a hard gate, not a nice-to-have. For specialty-specific workflow context, see our Clinical Specialties Directory.

The Missing Layer: Attestation as a Verifiable Credential

Competitor guides catalogue telehealth codes across the US, UK, and Australia with reasonable accuracy. What they do not address is the 2026 legal mechanism that decides whether an Australian claim survives an audit. Listing "91890–91891 with strict time thresholds" describes the surface rule while omitting the requirement that now makes or breaks the rebate: proof of physical location.

Here is the original insight that closes that gap:

Medical AI Scribing at Scribing.io converts the patient's verbally stated location into a PSMA G-NAF–normalized address and seals it as a W3C Verifiable Credential on the FHIR Encounter—creating a tamper-evident Jurisdictional Attestation that auto-binds to MBS 91891/91890 claims per the 2026 AHPRA requirement.

Why each layer carries weight:

• Verbal capture becomes structured intent. The clinician asks; the patient answers. The system transcribes and interprets the spoken location rather than trusting a checkbox anyone can tick.

• PSMA G-NAF normalization removes ambiguity. "I'm at home in Parramatta" becomes a canonical G-NAF Persistent Identifier—Australia's authoritative geocoded address register—producing a machine-verifiable jurisdiction.

• W3C Verifiable Credential seals the record. The attestation is cryptographically bound to the encounter resource. Any post-hoc alteration breaks the credential, which is exactly what an auditor wants to see.

• Auto-binding keeps proof attached. The attestation travels as claim metadata, so evidence and rebate are never separated.

Standardized documentation and clean audio are necessary but not sufficient. They improve note quality; they do nothing to establish jurisdictional legality. The Verifiable Credential layer is the information the market is missing.

For downstream data flow details, see the EHR Integration Library and the applicable AI scribe compliance laws.

Clinical Logic: Preventing an $18,600 Bali Clawback

The scenario in full. A GP conducts a 25-minute telephone review and bulk-bills MBS 91891. The patient was actually in Bali; no location attestation was captured. Six months later, a Medicare audit claws back $18,600 across similar claims and issues a compliance notice.

Under generic telehealth documentation, nothing in the workflow would have stopped this. The time was met, the note was clean, the code was correct. The claim was still invalid—and the practice carried unquantified liability across every similar claim.

Here is how Scribing.io intervenes in real time:

Result in the Bali scenario: the dual-check flags a location outside Australia, the G-NAF normalization returns no valid Australian identifier, and the system hard-stops the 91891 claim before submission. The $18,600 clawback event never originates, and the compliance notice is never triggered.

To model the financial impact of preventing clawbacks and rework at scale, use the AI Medical Scribe ROI Calculator.

Technical Reference: ICD-10 Documentation Standards

Jurisdictional attestation validates eligibility; correct diagnostic coding validates clinical necessity. Both must hold for a telehealth claim to be defensible on audit.

Two presentations dominate bulk-billed telephone reviews. Both are frequently under-documented in the audio record.

Clinical-Grade Scribing structures both the diagnostic narrative and the jurisdictional credential into a single FHIR Encounter. Eligibility and necessity are then defensible from one auditable record.

Operations Director Rollout Checklist

A staged rollout protects the claim book while clinicians adapt. The sequence below reflects deployments across multi-site GP networks.

1. Enable the attestation prompt as a mandatory pre-billing gate for all 91891/91890 sessions.

2. Configure the hard-stop threshold so offshore GPS/IP signals block claim generation, not merely warn.

3. Bind the Verifiable Credential to your FHIR Encounter resource within the EHR Integration Library.

4. Audit a retrospective sample of prior telephone claims to quantify existing offshore exposure.

5. Train clinicians on the phrasing so the location question sounds natural inside the consult.

Each step converts a soft assumption into a sealed, time-stamped fact. That conversion is what withstands a Medicare audit six months later.

Pricing & Next Steps

Jurisdictional attestation is included across relevant Australian telehealth plans. Review the tiers and per-clinician terms on Scribing.io Pricing & Plans.

Clinical Operations Directors should benchmark the cost of the attestation layer against a single $18,600 clawback event. The arithmetic is rarely close.

Start with the specialty mapping in the Clinical Specialties Directory, then quantify recovered exposure with the AI Medical Scribe ROI Calculator.