Who runs health? Shared responsibility and person-centred collaboration

The useful way to hold this is by function, not by name. Ask of any service: who funds it, who delivers it, and who regulates it? Those are frequently three different bodies.

The single most useful fact in this dot point: the level that funds a service is often not the level that delivers it. Most of the system's coordination problems trace back to that split.

Shared responsibility is not automatically a defect. It puts decisions closer to the population affected, allows states to differ where local conditions differ, and spreads risk. But it produces four predictable problems, and naming them by mechanism is what an explanation question is asking for.

• Cost-shifting. When two funders each pay for part of a person's care, each has an incentive to have the other bear it. A patient who could be managed in the community may be treated in a hospital funded by a different level of government, or the reverse.
• Gaps at the boundary. Services fall between funders. The clearest example is the boundary between hospital care and aged care, and between health and disability support, where a person can be ready to leave hospital and have nowhere funded to go.
• Duplication and inconsistency. Programs overlap; rules, eligibility and data systems differ between states and between funders, which multiplies administration and confuses the people using them.
• Accountability that is hard to locate. When an outcome is poor, responsibility is genuinely divided, so improvement is harder to demand than in a single-payer arrangement.

The seams are not evenly distributed. They fall hardest on people who need several services at once: older people, people with disability, people with several chronic conditions, and people moving between hospital and home. That is the same population that appears in every other lesson in this module, and it is not a coincidence — fragmentation compounds with disadvantage exactly like the access gates do.

Person-centred care is not politeness and it is not patient satisfaction. It is a structural claim: that care should be organised around the person's goals, values and circumstances rather than around the convenience of the organisations delivering it.

Five things it requires, each of which can be checked:

• The person's goals set the plan. Two people with the same diagnosis can want different things — one wants to keep working, another wants to avoid hospital admissions — and those goals imply different treatment.
• Shared decision-making. Options, benefits, risks and uncertainty explained so the person can choose, rather than consent being sought for a decision already made.
• One plan, visible to everyone involved. Including the person. If four providers each hold their own version, there is no plan.
• Continuity and a known point of contact. Someone who knows the history and who can be called when something changes.
• The whole person, not the presenting complaint. Housing, income, carers, culture, language and what matters to them are clinical information, not background.

The test of person-centred care is simple: does the person have to be the one who carries information between services? If they do, the system is provider-centred and is outsourcing its coordination to the patient.

And that test is why person-centred care and shared responsibility are in the same dot point pair. Fragmentation is precisely what makes person-centred care hard, so collaboration is not an add-on — it is the mechanism by which a divided system can still produce undivided care.

Collaboration happens at three levels, and a strong answer names all three because they fail differently.

• Around the person. Multidisciplinary teams; a care plan agreed between general practice, specialists, allied health and community services; discharge planning that starts on admission rather than on the day of discharge; case management or care coordination for people with complex needs; shared records so information moves without the patient carrying it; and carers and families included as part of the team.
• Between organisations. Regional health planning bodies that commission services against local need; formal referral pathways and agreements between hospitals and community providers; government contracting not-for-profit organisations to deliver aged care, disability and community services; and joint programs where a council, a health service and a community organisation each contribute what they have.
• At the system level. Intergovernmental agreements setting how hospitals are funded and what each level is accountable for; national strategies and standards that make practice consistent across states; and shared data and reporting so performance can be compared.

What makes collaboration work, and what makes it fail:

• Works when someone is clearly accountable for the whole person, information moves without the person carrying it, funding follows the person rather than the setting, and the arrangement lasts long enough for relationships to form.
• Fails when collaboration is added on top of unchanged funding incentives, when it depends on individual goodwill instead of structure, when contracts are too short for continuity, or when systems cannot exchange information.

That last point is why digital health, in Lesson 17, is treated as a system-integration question rather than as a technology question. The problem it exists to solve is the one described here.

Students routinely reduce this to “private hospitals and charities”. The sector does much more, and it does things government cannot.

• It delivers a large share of care, including most general practice, most specialist practice, and a majority of aged care and community services — much of it publicly funded. Private delivery of publicly funded care is the normal case in Australia, not the exception.
• It reaches people government reaches badly. Community-controlled and community-based organisations have trust and local knowledge that a government service often does not, which is an access advantage on the acceptability dimension from Lesson 8.
• It advocates. Health charities and peak bodies put issues on the agenda, represent people affected, and hold government to account — a role government cannot perform on itself.
• It funds and conducts research, and supports people living with a condition through information, peer support and practical help that no clinical service provides.
• It innovates at smaller scale, testing models that government can later adopt.

Its constraints are worth naming too: funding is often short-term and contract-based, which makes continuity and workforce retention hard; coverage depends on where organisations happen to exist rather than on where need is; and a for-profit provider's incentives are not automatically aligned with population health, which is why regulation is part of the picture rather than an afterthought.

For each service, name the funder, the deliverer and the regulator, and say whether the split creates a seam.

Return to the discharge in card 01. Design the collaboration that would make it work: who holds the plan, who contacts whom and when, what information has to move and how, and what the person themselves is asked to do.

Then apply the test from card 06: is the person being asked to carry information between services? If they are anywhere in your design, redesign that step.