Direction to the Independent Hospital Pricing Authority on the performance of its functions under section 226 of the National Health Reform Act 2011 - No. 2/2016

Sentinel event. The Direction defines a sentinel event as “one of a subset of adverse events that result in death or serious harm to a patient.” The Australian Sentinel Events List, curated by ACSQHC, specifies which events qualify. Examples include wrong site surgery, retained instruments, and medication errors leading to death. Because these are rare but devastating, the Direction imposes a strict zero funding penalty: nil funding for the entire episode. This is a blunt instrument: a hospital that performs life saving surgery but has an unrelated sentinel event (e.g., a retained swab) loses all funding for that admission, even though most of the care was necessary and appropriate. The Direction does not distinguish between preventability or culpability; any sentinel event triggers the penalty.

Hospital acquired complication (HAC). A HAC is defined by reference to the national list developed and amended from time to time by ACSQHC. The definition includes the important nuance that clinical risk mitigation strategies “may reduce (but not necessarily eliminate) the risk of that complication occurring.” This acknowledges that some complications are not fully preventable; the national list will likely include pressure injuries, falls, urinary tract infections, and venous thromboembolism. The Direction mandates a “reduced funding level” (not nil) to reflect the additional cost of the complication. Option 3 of the draft Pricing Framework 2017 18 (existing at 30 November 2016) presumably involves funding only the base admission cost and not the incremental cost attributable to the complication. This creates a financial incentive for hospitals to invest in prevention, but also risks penalising hospitals that treat complex, high risk patients who are more prone to complications.

Avoidable hospital readmission. This concept is still being defined. The Direction defines it as “readmission to hospital for a condition or conditions arising from complications of the management of the condition for which the patient was originally admitted.” Not all readmissions are avoidable; the Direction asks ACSQHC to develop a list of clinical conditions and suitable condition specific timeframes (e.g., readmission within 30 days for surgical site infection). IHPA must then consult on potential pricing adjustments. This is a longer term project; no funding changes are mandated in the Direction.

Activity based funding vs block funding. The Direction applies to “hospitals where the services are funded on an activity basis and hospitals where services are block funded.” This means the sentinel event nil funding applies universally, but the mechanics may differ. For activity based hospitals, the funding weight for the entire episode is set to zero. For block funded hospitals, a retrospective adjustment reduces the block grant by the value of the episode. The Direction references Chapter 4 of the Act, which governs these funding models.

Shadow implementation. For HACs, the Direction requires IHPA to conduct a shadow period before full implementation on 1 July 2018. During the shadow period, funding is not yet reduced, but the impact on funding, data reporting, condition onset flags, clinical information systems, and population groups is assessed. A final report must go to COAG Health Council by 30 November 2017. This phased approach aims to reduce unintended consequences, but it places a heavy burden on states to prepare their clinical coding and audit systems without knowing the exact final model.

Risk adjustment methodology. The Direction repeatedly mentions “risk adjustment” to account for different patient complexity across hospitals and jurisdictions. The COAG Health Council intended to refine this methodology before July 2017 for HACs. Without adequate risk adjustment, a hospital that treats a high proportion of elderly or comorbid patients may appear to have higher HAC rates, even if its quality of care is good. The Direction’s design principles require that adjustments be “based on evidence of a causal link” and “commensurate with the additional care required.” This raises difficult empirical questions about attribution.

The most immediate and direct impact is on the Independent Hospital Pricing Authority itself. IHPA is the sole recipient of the Direction, and it must recalibrate its Pricing Framework by March 2017 to incorporate the sentinel event nil funding and HAC reduced funding. This requires IHPA staff to develop new pricing models, conduct the shadow exercise, run public consultations, and coordinate with ACSQHC and state health departments. IHPA’s independence in setting prices is constrained; the Direction overrides its usual discretion.

Public hospitals across Australia are the primary target. Every public hospital that receives Commonwealth funding through the National Health Reform Agreement will see its revenue affected if a sentinel event or HAC occurs. For small hospitals with low volumes, a single sentinel event could wipe out a meaningful portion of their activity based revenue. For large teaching hospitals that manage complex trauma and high risk surgery, the HAC penalties could aggregate to significant sums. The financial exposure is concentrated on hospital budgets, which in turn affects the ability to invest in equipment, staffing, and prevention programs.

State and territory health departments are affected because they own and operate most public hospitals, and they will bear the financial consequences of reduced Commonwealth funding. The Direction requires states to audit medical records and coding to support improved reporting of HACs (Item 2(ii)(d)). This imposes compliance costs on state health bureaucracies, which must invest in clinical coding audits and condition onset flag systems. States that have weaker coding practices may initially under report HACs, but over time the audit expectation will force increased transparency, potentially revealing higher complication rates than previously acknowledged.

Patients are indirect but important stakeholders. The stated aim of the reforms is to improve patient health outcomes by reducing preventable harm. If the financial incentives work, patients may experience fewer complications. However, there are risks. Hospitals may become reluctant to admit patients with high risk of complications (e.g., the very elderly, those with multiple comorbidities) for fear of triggering HAC penalties. This could lead to avoidance behaviour, which the Direction’s design principles seek to prevent by mandating risk adjustment. But if risk adjustment is imperfect, the worst affected patients may find it harder to access care.

The Australian Commission on Safety and Quality in Health Care plays a critical operational role. It curates the Sentinel Events List and the HAC List, develops preventability rates, and leads definition work on avoidable readmissions. The Direction gives ACSQHC responsibility for ongoing curation, meaning that the list of HACs can expand over time without further legislation. Hospitals and clinicians must monitor these lists and adjust clinical practices accordingly.

Private hospitals are not explicitly mentioned, but if they treat public patients under activity based funding arrangements, they could be caught by the same rules. The Direction says “all public hospitals” for HACs, but the sentinel event provision applies to “hospitals where services are funded on an activity basis and hospitals where services are block funded.” That phrasing could capture private hospitals that receive public funding for certain services. The interaction is ambiguous.

Clinicians and medical coders also face increased burden. Condition onset flags must be accurately recorded to distinguish pre existing conditions from hospital acquired complications. This requires better clinical documentation at the time of admission. Coders must be trained to apply the HAC definitions consistently. If documentation is poor, hospitals may inadvertently miss condition onset flags and be incorrectly penalised for complications that were present on admission.

The Direction creates duties on IHPA, not rights for other parties. IHPA must undertake the three functions listed in Item 1 of the Schedule. These are mandatory: “is to undertake implementation of agreed recommendations” (Item 1(i)). IHPA cannot refuse or delay implementation without breaching the Direction. Item 1(i)(a) requires nil funding for sentinel events from 1 July 2017; Item 1(i)(b) requires reduced funding for HACs (initially shadow, then implement); Item 1(i)(c) requires further public consultation on avoidable readmissions.

IHPA also has a duty to have regard to the matters in Item 2. “Have regard to” is a weaker obligation than “must implement.” It means IHPA must consider these matters, but may depart from them after proper consideration. For example, Item 2(i) says IHPA must have regard to the COAG Health Council’s intention to implement an adjusted funding model for sentinel events from 1 July 2017. But the Direction already mandates nil funding; the “intention” is consistent. More significantly, Item 2(ii)(e) says reduced funding for HACs is to be implemented “subject to the results of the shadow period.” This gives IHPA some wriggle room: if the shadow period reveals major data or equity problems, IHPA could recommend delaying or modifying the model. But the Direction is itself the COAG agreement; IHPA’s ability to push back is limited.

Item 2(v) sets forth design principles that IHPA must have regard to. These include requirements that reforms be evidence based, that adjustments have a causal link, that they not compromise state system financial sustainability, and that they provide transparency. These principles are statements of intent, not enforceable rights. A hospital that suffers a funding cut cannot sue IHPA on the basis that the cut was not evidence based; the principle only guides IHPA’s discretion.

The Direction imposes a duty on IHPA to include the options in the Pricing Framework by March 2017 (Item 2(iv)). This is a strict deadline. If IHPA fails to meet it, the Minister could issue a further direction or take other steps, but there is no private right of action.

Other bodies have duties indirectly. ACSQHC must curate the lists, develop preventability rates, and lead definition work. The Commonwealth, states, and territories are expected to provide submissions, but this is not a binding duty. States must audit medical records and coding under Item 2(ii)(d), but the duty is on IHPA to “have regard to” that intention; states are not directly directed.

No rights accrue to patients or clinicians. A patient who suffers a sentinel event does not gain a right to demand that the hospital receive zero funding; the funding adjustment is between the Commonwealth and the state. A clinician cannot use the Direction to avoid a penalty; the Direction does not change clinical liability.

The Direction does not impose civil or criminal penalties. Enforcement is through the Commonwealth’s control over hospital funding under the National Health Reform Agreement. If a state does not properly report sentinel events or HACs, the Commonwealth can adjust the payments it makes to the state. The Direction gives IHPA the task of setting the pricing rules; the National Health Funding Body (NHFB) then administers the payments. The effectiveness of enforcement depends on data integrity.

States must report condition onset flags and other coded data to IHPA. The Direction expects that sentinel events will be “adequately reported for the purpose of funding adjustments” (Item 2(i)(c)). If a state under reports sentinel events, it will receive more funding than it should, but that would be a breach of the agreement. The COAG Health Council is to monitor and review reporting. However, the Direction does not specify audit powers or back dating penalties. It states that ACSQHC will curate the lists and develop preventability rates; oversight is diffuse.

For HACs, the shadow period will reveal whether states have the data systems to support the model. If data quality is poor, reduced funding may be applied inaccurately, leading to either overpayment or underpayment. The Direction requires states to audit medical records and coding; if they fail to do so, the risk adjustment may be faulty, and some hospitals may be unfairly penalised. But there is no prescribed penalty for a state that neglects auditing.

The biggest enforcement gap is that the Direction does not specify what happens if a hospital disputes a classification. A hospital might argue that a complication was present on admission and not hospital acquired, but the coding rules may not capture that accurately. The condition onset flag system is critical; without it, a hospital could be penalised for a pre existing condition. The Direction expects refinement of risk adjustment but does not provide a dispute resolution mechanism.

The sentinel event nil funding penalty is absolute. There is no appeal process within the Direction. If a hospital believes the event was not truly a sentinel event (e.g., a borderline classification), its only recourse may be to seek a correction of the coding, and then challenge the funding adjustment through the NHFB’s payment processes. This creates an incentive for hospitals to code sentinel events downwards to avoid the penalty, undermining patient safety transparency.

In practice, enforcement relies on state compliance with the National Health Reform Agreement and the financial consequences of losing funding. If a state systematically under reports, the Commonwealth could withhold funding or require a repayment, but that would be a political negotiation rather than a legal penalty. The Direction itself is not an enforcement instrument; it is a policy instruction to IHPA. The real hammer is the funding agreement, which is outside the Direction’s text.

The Direction is made under section 226 of the National Health Reform Act 2011, which allows the Minister to give directions to IHPA after consulting the Standing Council on Health. The validity of the Direction depends on proper consultation and on the Direction not exceeding the scope of s 226. The Act does not define the limits of “direction,” but a direction that is inconsistent with IHPA’s statutory functions could be ultra vires. The Direction addresses functions under s 131(1)(a) (pricing public hospital services) and (h) (anything incidental). These are broad.

The Direction intersects with the National Health Reform Agreement (NHRA), which is a multi party intergovernmental agreement. The Direction implements a COAG Health Council decision, which itself is a product of the NHRA. Commonwealth funding to states for public hospitals is determined under NHRA schedules; the Direction changes the pricing rules that feed into those schedules. Any conflict between the Direction and the NHRA would be politically resolved, but the Direction could be argued to be a variation of IHPA’s role under the agreement.

The ACSQHC’s role is governed by the National Health Reform Act (or separate establishment legislation?). The Direction relies on ACSQHC’s national lists of sentinel events and HACs. These lists are not legislative instruments; they are published by the Commission. This means the definition of a HAC can change via a Commission update, without parliamentary scrutiny. Hospitals must keep current with the list. The Direction says the list is “amended from time to time” , no notice period specified. This creates regulatory risk for hospitals, which could face new categories of HAC penalty with little warning.

The Direction does not override state clinical governance laws. Hospitals must still comply with state health regulations, accreditation standards, and clinical guidelines. The funding changes add financial pressure but do not confer or remove legal duties of care. Similarly, medical negligence claims remain unaffected; the Direction does not change tort law.

The Direction might interact with the National Health Funding Pool arrangements. The NHFB administers the flow of Commonwealth funds. If a sentinel event zero funding rule reduces a state’s entitlement, the NHFB must adjust its payments. This could create disputes about timing, estimates, and reconciliations. The Direction does not address these mechanics.

There is no mention of competition law, privacy law, or procurement law. The Direction does not affect patient consent or health records beyond the requirement for condition onset flags, which may require improved data collection.

This Direction is titled “No. 2/2016” but was dated February 2017. The discrepancy suggests it may have been drafted in 2016 but signed in 2017. The source does not provide any amendment history. As a ministerial direction, it can be amended or revoked by a later direction under s 226. It is not a legislative instrument (though it must be registered on the Federal Register of Legislation). The Direction appears to be a single, stand alone instrument that has not been amended as of the date shown. Subsequent governments may have issued superseding directions on hospital pricing and safety. The content is limited to the three functions; any revision would likely adjust the timeline or scope. The user should check the Federal Register for later directions (e.g., 2018, 2019, 2020) that may have modified or replaced this one.

The source text contains no references to litigation. The Direction is an administrative instrument, not a statute, so it is not directly challengeable in the same way as primary legislation. However, judicial review of a ministerial direction under s 226 is theoretically possible. A party (e.g., a state or a hospital) could argue that the direction is ultra vires the Act, that consultation was inadequate, or that IHPA failed to comply with the direction to the detriment of the party. No known cases are available from this source. Given the direction’s limited scope and the political nature of COAG decisions, litigation is unlikely but not impossible. The shadow period and data quality issues could give rise to administrative law challenges if a hospital believes it was incorrectly classified. The absence of a dispute resolution mechanism within the direction makes judicial review a more plausible avenue. However, no such cases are recorded in this document.

Sentinel event nil funding applies to the whole episode, not just the event cost. The Direction says “nil funding for a public hospital episode including a sentinel event.” This means that if a patient is admitted for hip replacement (which costs $20,000 under activity based funding) but suffers a retained swab (a sentinel event), the entire episode receives zero funding. The hospital loses revenue not just for the complication cost but for all the necessary care provided. This is a disproportionate penalty that could exceed the cost of the complication itself. Hospitals may react by trying to code the sentinel event as a HAC instead, which carries a less severe penalty.

HAC lists can change without notice. ACSQHC “develop[s] and amend[s] from time to time” the national list. This means IHPA’s funding model must be updated each time the list changes. Hospitals must track these updates or risk being penalised for a new HAC they did not anticipate. The Direction does not require a transition period for list amendments.

Risk adjustment may be inadequate. The design principles say changes “should not compromise state system financial sustainability.” But if risk adjustment is poor, hospitals that treat high risk populations will be penalised more, potentially leading to avoidance behaviour. The Direction acknowledges the need for refinement but does not guarantee that the final model will be risk adjusted properly. The shadow period is meant to identify problems, but the timeline (report due Nov 2017, implement July 2018) is tight.

State audit expectations are vague. The Direction requires IHPA to “have regard to” the intention that states audit medical records and coding. This does not impose a binding obligation on states to conduct audits. If states drag their feet, the data quality for HAC reporting will remain poor, and reduced funding will be based on inaccurate coding. IHPA cannot force states to audit; it can only encourage.

Definition of avoidable hospital readmission is provisional. The Direction says ACSQHC will develop a list of clinical conditions with condition specific timeframes. Until that list is published, no funding adjustments are made. But the Direction does not set a deadline for ACSQHC. This part of the direction could languish. Meanwhile, hospitals may not invest in reducing readmissions because they face no financial penalty yet.

The phrase “nil funding” may be interpreted differently for block funded hospitals. Block funded hospitals receive a lump sum for a range of services. How does IHPA apply nil funding to a single episode within a block funding arrangement? The Direction says “applying to all relevant episodes of care … in hospitals where services are funded on an activity basis and hospitals where services are block funded.” The application to block funded hospitals is ambiguous; IHPA will need to devise a method for adjusting block grants retrospectively, which adds administrative complexity.

No grandfathering for existing complications. The Direction applies to sentinel events occurring on or after 1 July 2017. For HACs, reduced funding applies from 1 July 2018 after the shadow period. There is no phase in for hospitals that already have high complication rates due to case mix. A hospital that provides risky procedures like cardiothoracic surgery will face penalties immediately, while a hospital that does only low risk procedures will not. The risk adjustment may partially address this, but it is not guaranteed.

The consultation obligation for readmissions does not require IHPA to adopt any particular model. Item 1(i)(c) says IHPA is to “undertake further public consultation to inform a future pricing and funding approach.” This is essentially a research project. No timeline is given. The COAG Health Council intentions (Item 2(iii)) say IHPA must provide additional advice on feasibility and financial implications, but again no implementation date. This part of the direction may produce little binding change.

The direction may conflict with other Commonwealth quality initiatives. The design principles say reforms should “complement existing national and state measures.” But nil funding for sentinel events could discourage truthful reporting. The hospital has a perverse incentive to code the event as something else (e.g., a HAC) to avoid zero funding. This could undermine the accuracy of national sentinel event data, which is used for benchmarking and safety monitoring.

Compliance with this Direction falls on multiple actors, but IHPA is the entity directly bound. For IHPA, the immediate step is to amend the Pricing Framework for Australian Public Hospital Services 2017 18 to include the sentinel event nil funding and the HAC reduced funding rule. IHPA must develop the specific pricing weights for zero funding and for reduced funding under Option 3. This requires data on the average cost of an admission with and without each HAC, and the cost of an entire episode for sentinel events. IHPA must also design the shadow exercise for HACs: a parallel run where funding is calculated as if the reduced rate applied, but actual payments are unchanged. IHPA needs to coordinate with the NHFB and state health authorities to obtain condition onset flag data.

IHPA must have regard to all matters in Item 2, which means documenting its consideration of the COAG Health Council intentions, design principles, and stakeholder submissions. A formal “statement of reasons” or compliance checklist would help demonstrate this. IHPA must publish the Pricing Framework by March 2017 (Item 2(iv)). This is a tight deadline given the long list of consultations required.

For state and territory health departments, compliance involves preparing their hospitals for the new funding model. They must ensure that clinical coding staff are trained to accurately record condition onset flags for each admission, so that complications present on admission are distinguished from hospital acquired ones. Without proper flags, the reduced funding model will penalise hospitals for pre existing conditions. States must also install or upgrade clinical information systems to capture sentinel events and HACs in a timely manner. The Direction expects states to audit medical records and coding; states should allocate resources for regular audits to validate the accuracy of reported HACs. A failure to audit will leave hospitals vulnerable to incorrect penalties and may lead to disputes with the Commonwealth.

Hospitals themselves, particularly those with high risk caseloads, must implement clinical risk mitigation strategies for the HACs on the national list. This includes evidence based protocols for preventing pressure injuries, falls, infections, and other common complications. Hospitals should also establish internal reporting systems for sentinel events, even if the financial penalty is severe, because not reporting could be more damaging in the long run. Clinical leaders should monitor ACSQHC’s list for changes and update prevention strategies accordingly.

For avoidable hospital readmissions, compliance is prospective. Hospitals should start tracking readmission rates and identifying gaps in discharge planning that lead to avoidable readmissions. While no funding adjustment is yet mandated, the literature and regulatory direction suggest such adjustments are coming. Early investment in transitional care and follow up may reduce future financial exposure.

The Australian Commission on Safety and Quality in Health Care must deliver the curated lists and definitions as specified. It must develop rates of preventability for each HAC to inform risk adjustment. For avoidable readmissions, it must produce a list of conditions and timeframes. These outputs are critical for IHPA’s work.

All parties should monitor the Federal Register for any subsequent directions that may amend timelines or scope. The Direction is dated 2017; it has likely been superseded or revised by now. The compliance obligations described here are based only on this single instrument.