New Coding Rules from 1 July 2026: What Clinical Coders Need to Know

On 15 June 2026, the rules Australian clinical coders work to changed again. The Independent Health and Aged Care Pricing Authority (IHACPA) published a new batch of coding rules as part of its National Coding Advice, and they are current from 1 July 2026.

If you are new to the field, quarterly rule changes might sound like a lot to keep up with. They are not a warning sign. They are how the system is designed to work. Australian clinical coding runs on a living classification, not a fixed rulebook that sits still for years. Knowing how to find the latest advice, read it, and apply it is a core part of the job. Here is what the newest advice contains, what a coding rule actually looks like in practice, and what all of it means if you are training as a coder right now.

IHACPA maintains the classification system used to code every admitted patient episode in Australian hospitals. That system has three parts: ICD-10-AM for diagnoses, ACHI for procedures, and the Australian Coding Standards (ACS) that govern how the first two are applied.

The current version is the Thirteenth Edition, used for separations from 1 July 2025. A new edition arrives roughly every three years, released alongside an update to the AR-DRG classification that hospitals are funded through. On that cycle, the Fourteenth Edition is due in 2028.

Three years is a long time in medicine. New drugs reach the ward, new procedures become routine, and new conditions get named. If coders had to wait for the next edition every time something novel turned up, the data would drift out of step with what hospitals were actually doing.

That gap is filled by National Coding Advice, which IHACPA publishes quarterly, in March, June, September and December. The June 2026 batch landed on 15 June and is current at 1 July 2026. It has three parts:

• Coding Rules: national answers to specific coding questions.
• Coding Rules for provisional assignment: guidance on the placeholder codes used for brand new diseases and technologies.
• Frequently Asked Questions: responses to questions about Thirteenth Edition changes and the education program that supports them.

One point matters more than any other here, and it is the one people new to coding most often get wrong. National Coding Advice works alongside the Australian Coding Standards rather than replacing them, and it is not something you can quietly skip. Where a coding rule covers the situation in front of you, that is the advice you follow. The standards remain the governing rules, and the advice tells you how to apply them to a case the books do not settle on their own.

Abstract explanations only get you so far, so here is a real rule from the 15 June 2026 batch. It is about e-bikes.

E-bikes are everywhere now, and Australian emergency departments are seeing the injuries that come with them. So a reasonable question for a health department to ask is: how many people are being admitted to hospital after an e-bike crash, and is that number going up?

Until last month, nobody could answer it. Not because the data was missing, but because of how the classification works. An e-bicycle is a bicycle with foot pedals and an electric motor that helps you pedal. ICD-10-AM defines it as a motorcycle, in the Chapter 20 definitions for transport accidents. So a rider who came off an e-bike on a bike path and a rider who came off a motorbike on a highway were coded into the same bucket. Once the record was coded, the two were indistinguishable.

The rule fixes that. After consulting its Classifications Clinical Advisory Group, IHACPA switched on a placeholder code, U77.0 National use of U77.0 [Injury involving e-bicycle]. The coder still assigns the usual motorcycle external cause code, then adds U77.0 alongside it, and the episode becomes countable.

The rule then works a scenario through in full. A patient is admitted with a fractured elbow after colliding with a car in traffic while riding an e-bicycle. The injury itself gets coded, as you would expect. Then, to record how it happened, the coder assigns:

• V23.40, the code for a rider of a motorised bicycle hit by a car in traffic. This is the external cause, and it comes from the motorcycle block, because that is where the classification puts e-bikes.
• U77.0 National use of U77.0 [Injury involving e-bicycle]. This is the new placeholder, and it is what makes the e-bike visible in the data.
• A place of occurrence code and an activity code, recording where it happened and what the person was doing.

Notice what the rule does. It does not just hand over one code. It walks through the complete set the episode needs and says where each one comes from. A coder who assigned the external cause code and stopped there would leave the record incomplete, and it would not survive an audit.

Now the part that shows why this is a reasoning job rather than a lookup job. An e-scooter is not an e-bike, as far as the classification is concerned. ICD-10-AM treats an e-scooter as a pedestrian conveyance, which puts it under ACS 2009 Pedestrian accidents, a completely different path through the books. Two devices that look similar parked on the same footpath, two different routes through the classification. The same June batch gave e-scooters their own placeholder, U77.1, and other powered pedestrian conveyances a third, U77.2. The advice is pointed about the boundaries, too: U77.1 is for e-scooters only, and is not to be used for mobility scooters.

Knowing that distinction is the job. No amount of searching the index for “e-bike” gets you there on its own.

The result is national consistency. The same case gets coded the same way in Perth and in Hobart. That is what makes national hospital data, and the activity based funding that runs on it, trustworthy. It is also what lets a road-safety team eventually ask the e-bike question and get a real answer.

U77.0 is worth pausing on, because it is an example of a wider mechanism.

Some things cannot wait three years for a new edition. A previously unknown disease, a technology that arrives in theatre for the first time, or a vehicle that appears on every street corner in the space of a few years, needs to be captured in the data straight away.

The classification handles this with provisional, or placeholder, codes. They sit in reserved blocks and get switched on when they are needed:

• ICD-10-AM U00 to U49, for new diseases of uncertain cause or emergency use. These are activated on advice from the World Health Organization.
• ICD-10-AM U75 to U77, for diseases of national significance. These are activated in consultation with the Classifications Clinical Advisory Group.
• ACHI [8888], for new or emerging health technologies, also activated in consultation with that group.
• ACHI [8889], for emergency use interventions where data needs collecting immediately. IHACPA activates these itself.

Placeholder codes never stand alone. They are assigned in addition to the relevant ICD-10-AM or ACHI code, and sequenced after it.

It is a quietly clever piece of design. It lets a national dataset react to something brand new within weeks, without anyone rewriting the classification.

The practical lesson in all of this is simple. Staying current is not an optional extra bolted onto the job. It is the job.

IHACPA is direct about how to do that. Its own instruction is to work from the latest online version of National Coding Advice, or from the Australian Classification Exchange (ACE), rather than relying on a copy you downloaded at some point. IHACPA corrects errors in published rules without notifying anyone when the change does not alter the intent, so a PDF sitting in your downloads folder can quietly fall out of date. The rules and FAQs for the Thirteenth Edition will eventually be retired altogether when the Fourteenth Edition arrives and the content is absorbed into it.

For a working coder, this habit is what keeps audit findings away. State health departments run coding audits, and an unusual case coded without checking whether a national rule already covers it is a predictable place for a discrepancy to show up. The coder who thinks to check is the coder whose work stands up.

Becoming a clinical coder means learning that whole workflow, not just the codes. You work from the alphabetic index to the tabular list, apply the Australian Coding Standards, then check National Coding Advice for anything the standards leave open. Coders who keep up with the quarterly cycle are also the ones who stay connected to the wider field. Clinical coders in Australia are represented by the Clinical Coders’ Society of Australia (CCSA).

Worth being clear on one thing: clinical coding is not a licensed or registered profession in Australia. There is no board to register with and no licence to hold. What employers hire on is demonstrated skill with the classification, which is what a qualification is for.

None of this requires a clinical background. It requires attention to detail, comfort with structured reference material, and the discipline to check rather than assume.

Sources: Independent Health and Aged Care Pricing Authority (IHACPA), National Coding Advice: Coding Rules and FAQs for ICD-10-AM/ACHI/ACS Thirteenth Edition (current at 1 July 2026), and the IHACPA ICD-10-AM/ACHI/ACS classification pages.

TalentMed Pty Ltd, RTO 22151. Course information is current at the time of writing. For current fees, intakes and entry requirements, see the course page.