Principal Diagnosis: The Rule That Defines Every Admission

Post Author:

TalentMed

Share This:
Clinical coder applying the Australian Coding Standards ACS 0001 to select principal diagnosis from a discharge summary

Classifications Explained

Principal Diagnosis: The Rule That Defines Every Admission

The principal diagnosis is the single most important decision a clinical coder makes on an episode. Defined by ACS 0001 as the diagnosis established after study to be chiefly responsible for occasioning an episode of admitted patient care, it sits at the top of every Australian coded record and drives the AR-DRG assignment that decides how much funding a hospital receives. Selecting it correctly is the difference between a clean, defensible episode and an audit finding.

This guide explains what the principal diagnosis is, what ACS 0001 actually says, the two-step test coders apply, worked examples for common admission patterns, the mistakes that cost coders marks in assessments and money in hospitals, and the FAQs students ask most. It’s written for HLT50321 students and career changers who want a grounded introduction to the rule that defines every Australian hospital admission.

What is the principal diagnosis?

The principal diagnosis is the one condition, selected from everything documented in the record, that Australian coding standards say best explains why this admission happened. It sits in the first diagnosis position on the coded record and is the primary driver of the AR-DRG the episode groups to. Every other diagnosis on the episode is an additional diagnosis, tested separately against ACS 0002.

The rule comes from ACS 0001 Principal diagnosis, the first and most-applied standard in the Australian Coding Standards. The ACS defines the principal diagnosis as the diagnosis established after study to be chiefly responsible for occasioning an episode of admitted patient care. Every word in that sentence matters, and ACS 0001 includes clarifying directives for scenarios where the documentation does not make the answer obvious.

Understanding principal diagnosis starts with what it is not. It is not the presenting symptom, unless the underlying cause was never established. It is not the most resource-intensive condition, unless that condition also occasioned the admission. It is not the reason given on the emergency triage note, because that reason is a working impression, not a diagnosis established after study. And it is not whichever condition looks most serious on paper. The principal diagnosis is the condition that, in the clinician’s judgement after investigation, actually caused this admission.

Why principal diagnosis matters

The principal diagnosis is the single biggest input into AR-DRG assignment, which is the single biggest driver of activity-based funding for Australian public hospitals. Get the principal diagnosis wrong and you can land in a different AR-DRG, a different funding band, and a different complexity split. The ripple effect reaches the hospital’s revenue, the state health department’s benchmarking, and the national dataset used for research and policy.

Within a hospital, the consequences of a misassigned principal diagnosis are concrete. AR-DRG (Australian Refined Diagnosis Related Groups) groups episodes into clinically and resource-homogeneous categories. Each AR-DRG has a price weight expressed as a National Weighted Activity Unit (NWAU). A small shift in the principal diagnosis code can move an episode from one AR-DRG to another, which changes the NWAU, which changes the funding the hospital receives. Multiplied across thousands of episodes a year, principal diagnosis accuracy materially affects hospital viability.

Beyond funding, the principal diagnosis anchors the national dataset. Researchers looking at the epidemiology of a condition rely on principal diagnosis counts to track admission trends. Quality-and-safety teams use it to identify case-mix for clinical review. State health departments use it to plan services. An episode coded with the wrong principal diagnosis corrupts every downstream use of the data.

That is why senior coders, clinical coding auditors, and case-mix specialists spend so much time on ACS 0001. It is the rule that turns clinical judgement into a reproducible, auditable record.

The two-step test ACS 0001 actually requires

ACS 0001 defines the principal diagnosis as the diagnosis established after study to be chiefly responsible for occasioning an episode of admitted patient care. That sentence is actually two tests the coder must apply in order.

The two-step test:

  • Step 1: Established after study. A diagnosis only qualifies as the principal diagnosis if it was investigated and confirmed during the episode. This excludes presenting symptoms where the underlying cause was later identified, working impressions that were later revised, and admission diagnoses that later turned out to be something else. The coder reads the whole record, not just the admission note, before selecting.
  • Step 2: Chiefly responsible for occasioning the episode. Of the conditions that were established after study, the principal diagnosis is the one that, more than any other, caused the patient to be admitted. It is a causal test anchored to the admission decision, not a severity test or a resource-use test.

Applying both tests in order is what separates accurate coders from fast ones. An experienced coder reading an unusual episode will often verbalise the test out loud: “What was established after study? What of those conditions occasioned the admission? That is my principal diagnosis.”

ACS 0001 also contains directives for the edge cases where step 2 is not straightforward. Those directives cover admissions where two or more conditions are equally responsible, admissions for planned treatment of a known condition, admissions for complications of previous treatment, admissions where the final diagnosis remains uncertain at discharge, and admissions that end with a diagnosis documented only as provisional, probable, suspected, or similar qualifiers. Student coders learn each directive in turn through the HLT50321 assessments. In day-to-day practice, coders look up the relevant directive in ACS 0001 rather than relying on memory.

Worked example 1: diabetic patient admitted with cellulitis

Documentation reads: “Patient with a known history of type 2 diabetes mellitus presents with a red, hot, swollen lower leg and fever. Diagnosed with cellulitis of the left lower limb. Admitted for intravenous antibiotics. Blood sugars monitored but home oral hypoglycaemics continued unchanged. Discharged day 4 on oral antibiotics.”

Here is how a coder applies ACS 0001:

  1. 1Identify every documented condition. Cellulitis of the left lower limb, type 2 diabetes mellitus.
  2. 2Apply step 1 (established after study). Cellulitis was the working and final diagnosis, confirmed clinically, and was the reason for IV antibiotic therapy. The diabetes was a known, pre-existing condition, not an admission issue in itself.
  3. 3Apply step 2 (chiefly responsible for occasioning the episode). The admission was for IV treatment of the cellulitis. The diabetes did not occasion this admission.
  4. 4Select the principal diagnosis. Cellulitis of the left lower limb is the principal diagnosis.
  5. 5Test the diabetes against ACS 0002. Monitoring alone with no change in therapy does not meet ACS 0002 in this episode. The diabetes would not be coded as an additional diagnosis here. If, however, there were diabetic foot involvement, documented diabetic skin complication, or diabetes management had required new insulin or adjustment, the answer changes and the relationship between the diabetes and the cellulitis would also need to be considered.

This pattern is one of the most common ACS 0001 questions in HLT50321 assessments, and one of the most common real-world audit findings. The habit of reading a chronic condition as principal diagnosis just because it is in the problem list is a classic trainee error.

Worked example 2: heart failure with pneumonia

Documentation reads: “Elderly patient with chronic heart failure presents with a three-day history of productive cough, fevers and increasing shortness of breath. Chest imaging confirms right lower lobe pneumonia. Admitted for IV antibiotics and diuretic adjustment. Background heart failure decompensated during the admission and required intravenous frusemide and medication titration. Discharged day 6.”

This is the classic two-conditions case. Both the pneumonia and the decompensated heart failure were present, both were investigated, and both received active treatment during the admission. Which is the principal diagnosis?

Applying ACS 0001:

  • Step 1 (established after study): both the pneumonia and the decompensated heart failure are established. Both pass step 1.
  • Step 2 (chiefly responsible for occasioning the episode): the documentation frames the admission around the acute respiratory illness. The pneumonia was the precipitant that drove the attendance, the initial treatment (IV antibiotics) and the decompensation of the heart failure. In this framing, the pneumonia is chiefly responsible for occasioning the admission and is the principal diagnosis. The decompensated heart failure is an additional diagnosis, coded because it required alteration of therapeutic treatment during the admission (IV frusemide, titration).
  • If the documentation read differently, for example if the clinician had documented the admission as being primarily for decompensated heart failure with a secondary chest infection, the answer could flip. ACS 0001 follows the clinician’s documented account of what occasioned the admission. When that account is ambiguous, ACS 0001 provides a directive for two or more conditions equally responsible, and a clarifying query to the clinician is the correct step before finalising.

This is why clinical coders so often query clinicians. A three-word change in the discharge summary can move the episode between AR-DRGs. ACS 0010 Clinical documentation and general abstraction guidelines, which sits alongside ACS 0001 in the general standards, sets the expectation that the coder will query rather than guess when the record is ambiguous.

Worked example 3: symptom or underlying cause?

Documentation reads: “Patient presents with three days of severe epigastric pain and vomiting. Investigations identify acute pancreatitis secondary to gallstones. Managed conservatively with IV fluids and analgesia. Discharged day 3 with outpatient cholecystectomy planned.”

Should the principal diagnosis be the epigastric pain (the presenting symptom), the acute pancreatitis (the established diagnosis), or the gallstones (the underlying cause)?

Applying ACS 0001:

  • Step 1 (established after study): acute pancreatitis was confirmed. Epigastric pain is a symptom of the pancreatitis, not a separate established diagnosis.
  • Step 2 (chiefly responsible for occasioning the episode): the acute pancreatitis is the condition that drove the admission, investigations, and treatment.
  • Principal diagnosis: acute pancreatitis. Where a definitive diagnosis has been established for a presenting symptom, the diagnosis is coded as principal, not the symptom. ACS 0050 lists symptom codes that are unacceptable as principal diagnosis when a definitive diagnosis has been made. The underlying gallstones would be considered as a relevant additional diagnosis per ACS 0002.

When no underlying cause has been established after study, the symptom can be the principal diagnosis. ACS 0001 accommodates both situations, but the coder must read the record to know which applies.

Common mistakes and how to avoid them

Most principal diagnosis errors fall into a small number of patterns. Recognising them is half the battle.

  • Coding the presenting symptom when a diagnosis has been established. If the record shows abdominal pain on presentation and acute appendicitis confirmed on investigation, the principal diagnosis is the appendicitis. ACS 0050 backs this up by listing many symptom codes as unacceptable as principal when a definitive diagnosis is available.
  • Choosing the most resource-intensive condition. ACS 0001 is a causal test, not a resource test. A patient admitted with cellulitis who happens to have an expensive background condition is still principally coded for cellulitis. Resource use flows into additional diagnoses and procedures, not into the principal diagnosis.
  • Defaulting to the chronic condition in the problem list. Type 2 diabetes is not the principal diagnosis of every diabetic patient’s admission. It is only the principal diagnosis when it is chiefly responsible for occasioning this particular admission, for example a DKA or hypoglycaemic event. Read the admission note, not the problem list.
  • Guessing when the documentation is ambiguous. When two conditions appear equally responsible, or the discharge summary does not clearly identify the primary driver of the admission, the correct action is to query the treating clinician. ACS 0010 expects it, and the query trail is part of the auditable coded record.
  • Treating the emergency triage note as the diagnosis. The triage note is a working impression from the first few minutes. It is not a diagnosis established after study. Read the admission note, the progress notes, investigation results, and the discharge summary before selecting.
  • Forgetting to check ACS 0050. A candidate code that is valid in the tabular list may still be unacceptable as a principal diagnosis. Running the final principal diagnosis code through ACS 0050 is the last sanity check before signing the episode off.

These patterns are the recurring themes of clinical coding audits and the practice-exam weaknesses HLT50321 trainers flag most often. Every one of them is fixed by reading the record in full and applying ACS 0001 deliberately rather than defaulting to a pattern-match.

Principal diagnosis and hospital funding

The principal diagnosis is the single biggest driver of AR-DRG assignment, and AR-DRG drives activity-based funding. That mechanical link is what gives ACS 0001 its weight in the Australian coding system.

AR-DRG groups episodes with clinically and resource-homogeneous characteristics. The AR-DRG assigned to an episode is determined primarily by the principal diagnosis and the procedures performed, with additional diagnoses moving the episode up or down through the complexity and comorbidity splits. Each AR-DRG carries a National Weighted Activity Unit (NWAU) price weight. State and Commonwealth activity-based funding applies that NWAU to fund the episode.

Because the principal diagnosis sets the AR-DRG’s major category, getting it wrong can shift the episode into a completely different grouping. An inaccurate principal diagnosis also compromises comorbidity coding, because additional diagnoses are tested against an episode defined by its principal diagnosis. ACS 0001 is therefore not only the first standard in the book, it is also the first link in the chain from clinical documentation to hospital revenue.

For a deeper walk-through of how the coded record maps to AR-DRG and funding, read our spoke on AR-DRG and hospital funding.

Learning principal diagnosis through HLT50321

Australian coders learn ACS 0001 through our HLT50321 Diploma of Clinical Coding, a 12-month, 100% online qualification built around real Australian coding scenarios.

The Diploma introduces ACS 0001 alongside ICD-10-AM, ACHI and the rest of the ACS, because the rule only makes sense against the full coding workflow. Students work through graded exercises that start with clear principal diagnosis selection and progress to ambiguous two-condition and complication admissions where ACS 0001’s directives must be applied. Integrated digital coding software replicates the real hospital workflow, so students practise looking up codes and checking ACS 0050 exactly as working coders do.

Australia’s best-value Diploma of Clinical Coding includes daily intakes 365 days a year, flexible payment plans, and graded assessments that build ACS 0001 judgement the same way a hospital coder develops it: by working through episodes, one at a time, with the standards open.

Related reading

Start here

Frequently asked questions

The principal diagnosis is the diagnosis established after study to be chiefly responsible for occasioning an episode of admitted patient care. It is defined by ACS 0001 in the Australian Coding Standards and sits in the first diagnosis position on the coded record. The principal diagnosis is the single biggest driver of AR-DRG assignment and therefore activity-based funding.
ACS 0001 Principal diagnosis defines the principal diagnosis as the diagnosis established after study to be chiefly responsible for occasioning an episode of admitted patient care. It then contains directives for the edge cases where that definition is not straightforward, including admissions where two or more conditions are equally responsible, admissions for planned treatment, admissions for complications of previous treatment, and admissions where the diagnosis is documented as provisional, probable or suspected at discharge.
The reason for admission and the presenting symptom are what the patient came in with. The principal diagnosis is what investigation showed was chiefly responsible for occasioning the admission. When a definitive diagnosis has been established for a presenting symptom, the diagnosis is coded as principal, not the symptom. ACS 0050 reinforces this by listing many symptom codes as unacceptable as principal diagnosis when a definitive diagnosis is available.
ACS 0001 provides a directive for when two or more conditions equally meet the definition of principal diagnosis. In practice, the coder reads the documentation for any sequencing the clinician has given (for example which condition the admission decision was made on, or which was treated first). When the record remains ambiguous, the correct action is to query the treating clinician rather than guess.
Yes, when the chronic condition is chiefly responsible for occasioning this particular admission. Type 2 diabetes is the principal diagnosis of an admission for diabetic ketoacidosis or a hypoglycaemic event. It is not the principal diagnosis of an admission for cellulitis in a patient who happens to have diabetes, unless the diabetes is directly tied to the cellulitis and the documentation supports that framing.
The two-step test comes directly from the ACS 0001 definition. Step 1 is established after study: the candidate condition must have been investigated and confirmed during the episode, not just documented on admission. Step 2 is chiefly responsible for occasioning the episode: of the conditions that pass step 1, the principal diagnosis is the one that, more than any other, caused the admission.
The principal diagnosis is the primary input into AR-DRG assignment. AR-DRG groups episodes into clinically and resource-homogeneous categories, and each AR-DRG has a National Weighted Activity Unit (NWAU) price weight that drives activity-based funding for Australian public hospitals. A shift in the principal diagnosis can move the episode into a different AR-DRG, a different complexity split and a different funding band.
The most common mistakes are coding the presenting symptom when a definitive diagnosis has been established, choosing the most resource-intensive condition instead of the condition that occasioned the admission, defaulting to a chronic condition from the problem list, treating the emergency triage note as the final diagnosis, and failing to query the clinician when the documentation is ambiguous. Running the selected code through ACS 0050 is a useful final check.
Yes. ACS 0001 is the national standard for Australian clinical coding and applies to every admitted patient episode in both public and private hospitals. Consistent principal diagnosis selection across both sectors is what makes the national dataset comparable and supports fair activity-based funding and benchmarking.
Australian coders learn principal diagnosis selection through the HLT50321 Diploma of Clinical Coding, which teaches ACS 0001 alongside ICD-10-AM, ACHI and the rest of the Australian Coding Standards. The Diploma uses graded worked examples and integrated digital coding software so students practise applying ACS 0001 the same way working coders do.

Want to find out more?

Speak to a TalentMed course adviser about HLT50321.
12 months, 100% online, flexible payment plans, daily intakes year-round.

Preferred method of contact *
HLT50321 Clinical Coding course information pack

Share this Article