Most complex care in Australia is delivered by a team. A patient managing diabetes might see a general practitioner, a podiatrist, a dietitian and an endocrinologist in the same year, and every one of those clinicians keeps a record of their part. This article covers where documentation sits in team-based care: what a case conference note needs, who owns and signs each entry, how care plans travel between disciplines, and how to share information with allied health without growing duplicate records.
Why team care multiplies documentation
Chronic and complex conditions in Australia are managed across disciplines. A general practitioner coordinates, allied health professionals deliver treatment, specialists advise, and practice or community nurses follow through between visits. Each of those clinicians carries a record-keeping obligation of their own, so a single patient generates entries in several unconnected systems at once: the practice management system, the physiotherapist's clinical software, the psychologist's file and the specialist's letters.
The documentation load grows faster than the clinical load. Every handover adds a referral out and a report back, every plan review adds an update to write and distribute, and every case conference adds a summary that several people rely on. Practices feel this as letters that lag days behind the appointment they describe, and as notes finished after hours.
A useful principle keeps the rest of this article organised. Each clinician keeps one accurate primary record of their own involvement, and everything that travels between team members is a derived document produced from that record: a referral, a report, a letter or a plan. When that principle holds, the team stays informed and the records stay trustworthy. Most duplication problems come from breaking it.
What a case conference note needs
Case conferences range from formal, scheduled discussions between a coordinating clinician and providers from at least two other disciplines through to a quick phone call between a GP and a treating physiotherapist. The formal version can attract MBS case conference items when the requirements are met. Both versions change the patient's care, so both belong in the record.
A conference summary earns its place when a colleague who was absent can act on it. In practice that means recording:
- the date and who took part, with each participant's name, discipline and organisation
- the patient, and the conditions or problems discussed
- the decisions made and the goals agreed, in terms specific enough to check later
- each action, with a named owner and a timeframe
- what the patient or carer was told, and how their views were taken into account
Who owns the note
Ownership has two layers, and confusing them causes most of the arguments. The organisation, whether a practice, a hospital or a health service, holds and controls the record itself. The individual clinician is professionally responsible for the entries they make in it. AHPRA registration attaches record-keeping obligations to each registrant personally, and membership of a team does not transfer those obligations to anyone else.
In a case conference, the convenor, usually the GP or whoever coordinates the patient's care, reviews and signs the conference summary into their own record. The other participants each document their own involvement in their own systems. That entry can be brief, noting attendance, the decisions relevant to their care and a reference to the full summary. A single shared summary is efficient, and it still leaves each clinician with a duty to record their own part.
For billed conferences, read the current item descriptor on MBS Online before claiming, because the items set out what the record must show and the claim rests on the note. For unbilled discussions the same discipline is still worth keeping, since a conference only improves care when its decisions reach a record that somebody later reads.
For an AI-drafted note the ownership rule is simple. A draft has no professional author until a named clinician reviews it, corrects it and signs it, and only at that point does it become that clinician's entry with everything that follows for accountability. In a team setting, the draft of the conference summary goes to the convenor, and any draft describing a specific discipline's assessment goes to the clinician of that discipline.
Care plans that cross disciplines
Chronic condition management plans exist to make team care deliberate. The GP documents the patient's goals, the disciplines involved and what each contributor will do, and allied health providers treating under the plan report back to the referring GP. As a document, the plan only works if every contributor can read it and if those reports actually return to the record it lives in.
The common failure modes are familiar to any practice manager. Plans get written once and never reviewed. Allied health reports arrive as PDF attachments and sit in a scanning queue for a week. Goals are phrased so generally that nobody can say whether they were met. Each of these is fixable with clear responsibility for who updates the plan, when reviews are due and how incoming reports are filed against the patient.
Drafting effort is a real reason plans go stale. Writing a thorough plan review takes time that a booked-out day rarely offers, so reviews shrink to a date change. A tool that drafts the review or the report from the conversation lowers that effort considerably, and the same rule applies here as everywhere else: the responsible clinician reviews and signs the document before it goes anywhere.
Sharing with allied health without duplicating records
The principle from the first section does the work here. Each provider keeps their own primary record, and only derived documents produced from that record move between providers. Secure messaging carries those documents between clinical systems, and services such as Medical Objects, or the messaging built into practice software like Best Practice and Medical Director, deliver them straight into the receiving system against the right patient.
Duplication starts when the same clinical content is maintained in more than one place by hand. The consult is written up in the clinical system, summarised again in a shared spreadsheet and emailed as a PDF to a case manager, and within a month the three versions disagree. When something goes wrong, nobody can say which version was authoritative. The fix is procedural. Corrections are made in the primary record and corrected documents are re-issued from it, the record notes what was sent, to whom and when, and shared drives hold copies of sent documents rather than parallel versions that anyone can edit.
Deciding what to share is a clinical judgement about sufficiency. The receiving clinician needs enough to act safely: the question being asked, the relevant history, current medicines and any risks. Pasting the full record into every letter creates privacy exposure and makes the relevant information harder to find. A short, specific letter serves the podiatrist far better than fifteen pages of history.
How aurii handles team documentation
This section is about our product. Everything above is not.
With consent, aurii captures the consult or the case conference and drafts every document the encounter calls for: the clinical note, the letter to the referring GP or the allied health provider, and the discharge summary. Each derived document comes from the same captured conversation, so the letter to the physiotherapist does not have to be retyped from the note, and the conference summary does not have to be reconstructed from memory that evening. Nothing becomes part of the record, and nothing is sent, until a clinician has reviewed and signed it.
That review step is per clinician, which matches how team documentation actually works. The convenor signs the conference summary, each discipline signs its own note, and letters go out under the name of the clinician who approved them. All capture, transcription and storage happens in Australia, and each record is encrypted individually. This matters in team care because documents move between organisations more often than they do in solo practice, and residency and review need to stay constant while they do.
Common questions
The clinician who convened or coordinates the conference reviews and signs the summary into their record, and that is usually the GP or the lead treating clinician. Every other participant still records their own involvement in their own system, which can be a brief entry that references the summary.
Yes, provided everyone being recorded has agreed, and that includes colleagues as well as any patient or carer present. The scribe drafts the summary, and the responsible clinician reviews, corrects and signs it before it enters the record.
Yes. The item descriptors set out what the record must show, including who took part and the outcomes of the conference, and the claim depends on the note supporting it. Check the current descriptors on MBS Online before billing.
This is general information about documentation in team-based care. It does not constitute clinical or legal advice. 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.