A Medicare Benefits Schedule item claim is a clinical and administrative statement in one: it says a service of a defined kind, and often a defined duration, was actually provided. The record that supports it does not need to be long. It needs to be contemporaneous, clinically relevant, and specific enough that another clinician, or an auditor, could read it months later and see what happened and why.
What "contemporaneous" actually requires
Contemporaneous does not mean instantaneous. It means the record is made at the time of the consultation or as soon as practicable afterwards, while the clinical detail is still fresh and accurate, rather than reconstructed from memory at the end of a long day or backfilled before a compliance review. Services Australia and the Professional Services Review scheme both look at timing as a proxy for reliability: a note written the same day, referencing what was actually discussed and examined, carries more weight than a tidy paragraph written a week later that reads like a summary rather than a record.
The practical failure mode is not fraud. It is drift: a clinician intends to finish notes at day's end, the list runs long, and by the time they sit down four consults have blurred together. The note gets written, but it is thinner and less specific than what actually happened in the room, and the gap between the two widens every time it happens without being noticed.
What clinically relevant detail means
"Clinically relevant" is doing real work in that phrase. It does not mean exhaustive. A note that supports an item claim needs to show the elements that justify the level of service claimed: presenting complaint, relevant history actually taken, examination findings actually elicited, the clinical reasoning that led to a diagnosis or differential, and the management plan agreed with the patient.
Padding a note with template text that was not actually discussed does not strengthen a claim. It weakens it, because a reviewer comparing the note to the patient's own recollection, or to prescriptions and referrals actually issued, will notice text that does not match the visit. Boilerplate examination findings copied into every consult are a common version of this: a system review that reads identically across a dozen patients on a busy afternoon is more likely to draw attention than reassure a reviewer. The safer discipline is the opposite of padding: write what was actually done, in enough clinical detail that the reasoning is visible, and stop there.
Time-based items and what the record needs to show
Several MBS items are structured around time spent with the patient rather than a flat description of the service. For these, the record needs to support duration as well as content: what filled the time, not just how long it took. A note that states a duration without corresponding clinical substance, such as a lengthy consult recorded in two lines, is the pattern that draws attention in a compliance review, because the time claimed and the detail on the page do not line up.
The fix is not to inflate the note to match the time. It is to make sure the note actually reflects what the extra time was spent on: more history, a more complex differential, counselling, or coordination of care that a shorter item would not capture. A useful habit is to note, briefly, what the extra time bought clinically, such as working through a differential that a five minute consult would not have allowed, rather than simply logging a start and end time.
What a compliance review actually asks for
When Services Australia or the Professional Services Review scheme looks at a practitioner's billing, the process is not a search for perfect prose. A reviewer typically requests the clinical record for a sample of claimed items and checks whether the documented service is consistent with the item description and the time or complexity it implies. They are looking for evidence the service happened as claimed, not for a particular writing style.
That distinction matters because it means the practical defence against a review is not better phrasing, it is a record that was actually written close to the encounter and actually reflects what was done. A note that is honest and slightly plain reads better under review than one that is polished but generic, because the reviewer is comparing the note against the item, not against a style guide.
Where practices get caught out
The common documentation gaps are mundane rather than dramatic. Notes that record an outcome ("plan discussed, patient agrees") without recording the reasoning that led there. Follow-up consults that copy forward the previous note's assessment without recording what changed. Team-care and chronic-disease management items where the plan exists but the file does not clearly show the review that the item structure assumes.
None of these are deliberate; they are what happens when documentation is squeezed into the gaps between patients rather than built into the consult itself. Specialty-specific documentation patterns compound the problem: a mental health consult, a skin check, and a chronic disease review all need different things to be visible in the note, and a generic template flattens those differences until the record no longer distinguishes one item's requirements from another's.
Why documentation quality is also a clinical governance question
AHPRA's expectations of practitioners and RACGP's standards for general practices both treat the medical record as a continuity-of-care document first, not a billing artefact. That framing matters because the same note that supports an MBS claim is the note another clinician relies on at the next visit, the note that supports a My Health Record shared health summary, and the note an indemnity insurer or AHPRA notification process will read if something goes wrong.
A practice that documents well for continuity of care will, as a natural consequence, also document well enough to support its billing. Chasing the reverse, writing to satisfy an audit rather than to describe the patient, tends to produce records that are defensible in form but thin in substance, and that thinness tends to show up in exactly the encounters that later turn out to matter most.
Where a scribe fits, and where it does not
This is where a tool like Aurii is relevant, and where its limits matter as much as its benefits. Aurii listens to the consult, with the patient's consent, and drafts the note: presenting complaint, history, examination findings as described in the room, assessment and plan, in the clinician's own structure. It does not decide what the plan is, and it does not decide what item number to claim. The scribe writes; the doctor decides.
A clinician reviews the draft, corrects anything that is missing or wrong, and signs before it becomes part of the record, in the same way they would review a note typed by a registrar or a locum. What the tool changes is the odds that the note is written the same day, in detail, because it is drafted during or immediately after the consult rather than reconstructed from memory hours later. That directly supports the contemporaneous and clinically relevant standard the MBS assumes, without changing what actually gets billed.
It also does not change where the record lives: Aurii drafts feed into the practice's existing system, such as Best Practice, MedicalDirector, Genie, Cliniko, or Halaxy, rather than replacing it, and the signed note carries the same audit trail as any other entry in that system.
Common questions
Not if the review step is real. The risk in any documentation workflow, scribed or handwritten, is a note that does not match what happened. A clinician who reviews and edits the draft before signing is applying the same judgment they would to any note, and a same-day, detailed record is generally easier to defend than a delayed, thin one.
No, and it should not try to. Item selection is a clinical and billing decision that belongs to the treating clinician, based on what was actually done and how long it actually took. Aurii drafts the clinical note; it does not recommend or select MBS items.
It means the note shows the reasoning a colleague would need to pick up the case: what was raised, what was found on examination, what the differential was, and what was agreed with the patient. It does not mean recording everything that was said, and it does not mean using template language for things that were not actually discussed.
The note needs to make clear what filled the time, not just state a duration. That usually means more visible history-taking, a documented differential, or counselling and care coordination detail that a shorter consult would not need to record.
Typically the clinical record for a sample of the claimed items, checked against what the item description requires. It is a comparison between the note and the item, not a review of writing style, which is why a plain, accurate, same-day note holds up better than a polished one written well after the fact.
This article is general information only and is not clinical, legal or financial advice; practices should confirm MBS billing and documentation requirements against current Services Australia guidance and their own professional obligations. More guides sit on the resources hub. If your practice needs a question answered before it adopts AI documentation, tell us and we will write it: hello@aurii.com.au.