Interoperable Aged Care Data in Australia: Connecting Health, Home Support and Community Intelligence

Australia’s aged care system depends on information moving safely between many different people, organisations and technologies.

An older person may receive support from a home-care provider, general practitioner, pharmacist, hospital, allied health professional, housing organisation, community transport service, family carer and specialist aged care team. Each service may hold important information, yet much of that information remains divided between separate systems, paper records, emails, telephone calls and manually transferred documents.

This fragmentation creates more than administrative inconvenience. It can contribute to delayed care, repeated assessments, medication errors, unsafe hospital discharge, missed referrals, avoidable deterioration and frustration for older people who are repeatedly asked to explain the same circumstances.

Interoperability offers a different future.

It enables authorised systems and services to exchange, understand and use information consistently. Rather than expecting people and families to carry information between disconnected organisations, the care system itself becomes responsible for creating continuity.

The wider Australia Social Care and Community Services Knowledge Hub explores how digital transformation, governance and integrated support can contribute to safer and more person-centred aged care.

The objective is not to create one enormous database containing every detail about every older person. It is to ensure that the right information reaches the right authorised person, in the right format, at the right time and for a clearly defined purpose.

What Interoperability Means in Aged Care

Interoperability is often described as the ability of digital systems to communicate with one another. In aged care, this definition is too narrow.

True interoperability requires information to be:

• available when it is needed;
• understandable by the receiving service;
• accurate and current;
• connected to the correct person;
• shared through secure channels;
• used only for an authorised purpose;
• presented in a form that supports action;
• traceable to its source;
• capable of being corrected; and
• governed throughout its life cycle.

A successful exchange is not achieved merely because one system sends data to another. The receiving organisation must be able to interpret the information correctly and use it within care, clinical, operational or safeguarding decisions.

The Four Levels of Interoperability

Foundational Interoperability

Foundational interoperability allows one system to transmit information to another.

For example, a hospital may send a discharge summary electronically to a home-support provider. This is an improvement on paper or fax-based communication, but it does not guarantee that the receiving system can interpret the content automatically.

Structural Interoperability

Structural interoperability ensures information is organised consistently.

This may include agreed formats for:

• personal identifiers;
• medication information;
• allergies;
• care-plan elements;
• clinical observations;
• referral details;
• risk information;
• service actions;
• review dates; and
• responsible professionals.

Without structural consistency, information may arrive but still require extensive manual interpretation.

Semantic Interoperability

Semantic interoperability means different organisations interpret information in the same way.

Terms such as “high risk”, “requires assistance”, “medication support” or “independent mobility” may be understood differently across services. Shared terminology, definitions and coding help reduce ambiguity.

Organisational Interoperability

Organisational interoperability concerns the relationships, agreements and responsibilities that allow information sharing to work in practice.

This includes:

• who is permitted to share information;
• who receives it;
• who acts on it;
• how consent is managed;
• how urgent information is escalated;
• how errors are corrected;
• how incidents are investigated;
• how suppliers are governed; and
• how accountability is maintained across organisational boundaries.

A technically sophisticated system may still fail if these responsibilities are unclear.

Why Fragmented Information Creates Risk

Older people frequently move between services that use different record systems.

Common transition points include:

• hospital admission and discharge;
• changes in medication;
• new home-support arrangements;
• allied health referrals;
• temporary respite;
• transition into residential aged care;
• changes in family-carer availability;
• housing modification;
• emergency response;
• palliative care; and
• community-service involvement.

When information does not move with the person, each transition becomes a point of vulnerability.

A home-support worker may not know that medication has changed. A hospital may not understand the person’s usual communication needs. An allied health professional may not know that a referral has already been made. A family member may assume that one provider has informed another.

The result can be duplication, delay and avoidable harm.

The Older Person Should Not Become the Integration System

In fragmented systems, the burden of coordination often falls on the older person or family.

They may be expected to:

• repeat medical history;
• carry medication lists;
• explain support arrangements;
• identify which professionals are involved;
• remember recent changes;
• follow up referrals;
• correct inconsistencies;
• transfer documents;
• coordinate appointments; and
• alert services when information has not been shared.

This is particularly unsafe where the person is unwell, fatigued, distressed, living with dementia, experiencing sensory loss, has limited digital access or does not speak English confidently.

Interoperability should reduce this burden rather than adding another digital process that people must manage themselves.

Person-Centred Data Architecture

A person-centred data environment starts with the individual rather than the organisation.

Information should be organised around questions such as:

• What matters to this person?
• What support do they currently receive?
• Which risks require shared awareness?
• What communication adjustments are needed?
• Who is involved in decisions?
• Which information changes frequently?
• What must be available during an emergency?
• What should remain private?
• Who is responsible for acting on updates?
• How can the person correct inaccurate information?

This may involve a shared core record containing essential information, while more detailed records remain within individual organisations.

A shared core record could include:

• identity and contact details;
• preferred name and communication needs;
• important relationships;
• current support providers;
• medication and allergies;
• significant risks;
• mobility and equipment;
• current goals;
• advance-care information;
• consent preferences;
• emergency contacts;
• recent hospital activity;
• open referrals; and
• responsibility for follow-up.

The purpose should be continuity, not unrestricted access.

Operational Scenario One: A Safer Hospital-to-Home Transition

Context: An older person is discharged from hospital after a fall and medication review. They require temporary mobility assistance, increased home-support visits and follow-up from physiotherapy.

Step 1 – Creating a shared discharge record: The hospital records medication changes, mobility requirements, equipment needs, follow-up appointments and warning signs requiring escalation.

Step 2 – Secure transfer: Relevant information is made available electronically to the authorised home-support provider, general practitioner, community pharmacist and physiotherapy service.

Step 3 – Confirmation of receipt: Each receiving service confirms that the information has been received and identifies who will act on it.

Step 4 – Closed-loop coordination: The provider confirms the first home visit, the pharmacy confirms the medication update and physiotherapy confirms the assessment date. Unresolved actions remain visible.

Step 5 – Ongoing review: Home-support workers record changes in mobility, pain, confidence and medication management. Significant deterioration triggers an agreed escalation route.

The interoperable pathway turns discharge from a one-way transfer of documents into a coordinated sequence of confirmed actions.

Structured Information and Human Narrative

Structured information is essential because it allows systems to identify and compare specific data fields. However, aged care cannot be represented entirely through codes and checkboxes.

Important narrative information may include:

• how the person communicates distress;
• what helps them feel safe;
• how routines affect wellbeing;
• which relationships are important;
• why the person may decline support;
• cultural or spiritual priorities;
• recent changes in confidence;
• family circumstances;
• personal goals; and
• context surrounding risk.

A strong interoperable system combines structured fields with concise human narrative. Too much unstructured information may make important details difficult to locate. Too little narrative may remove the meaning required for person-centred care.

Common Data Standards

Shared data standards allow organisations to exchange information consistently without requiring every provider to use the same software.

Providers and system leaders need agreement on:

• field names;
• definitions;
• coding systems;
• date and time formats;
• risk categories;
• care-plan structures;
• medication terminology;
• status indicators;
• referral stages;
• priority levels;
• outcome measures;
• responsibility fields; and
• record-update rules.

Standards should reduce unnecessary variation without forcing every organisation into an identical service model.

The objective is shared understanding, not organisational uniformity.

Reliable Digital Identity

Information must be connected to the correct person.

Identity errors may occur because of:

• similar names;
• changed addresses;
• duplicate records;
• different spelling;
• missing identifiers;
• outdated contact details;
• incorrect dates of birth;
• separate records held by different services; and
• family members sharing contact information.

Reliable digital identity helps ensure that authorised information from different organisations relates to the same individual.

Identity matching should be accurate, proportionate and supported by clear correction processes.

Consent Must Be Understandable and Usable

Consent should not be reduced to a broad statement that information may be shared with anyone involved in care.

Older people should understand:

• which information may be shared;
• which organisations may receive it;
• why sharing is proposed;
• how it may improve support;
• what may happen if information is not shared;
• whether access is continuous or event-based;
• how consent can be changed;
• how representatives are involved;
• what happens during an emergency; and
• how inappropriate access can be challenged.

Consent preferences may vary according to the type of information and the receiving service.

A person may agree to medication information being shared across authorised health and care services while preferring other personal information to remain restricted.

Emergency Access

Some situations require rapid access to essential information.

Emergency access arrangements may be necessary where:

• the person cannot communicate;
• there is immediate risk to life or safety;
• usual systems are unavailable;
• urgent clinical decisions are required;
• medication information is incomplete;
• the person is displaced during a disaster; or
• the normal care team cannot be contacted.

Emergency access should remain controlled and auditable.

Systems should record:

• who accessed the information;
• when access occurred;
• which information was viewed;
• the reason for access;
• whether the person was informed afterwards; and
• whether further review is required.

Families and Informal Carers

Family members and informal carers often hold valuable knowledge about daily routines, preferences, deterioration and practical support.

However, involvement should not be assumed.

Providers need clear arrangements covering:

• the person’s wishes;
• decision-making authority;
• consent to share information;
• which family members are involved;
• what information each person may receive;
• how disagreement is managed;
• how carer stress is recorded;
• how changing family capacity is communicated; and
• how inappropriate access is prevented.

Interoperability should help families participate appropriately without weakening the older person’s privacy or control.

Closed-Loop Referrals

Many referrals fail not because they were never sent, but because no one confirms receipt, acceptance, action or completion.

A closed-loop referral process should show:

• who made the referral;
• why it was made;
• when it was sent;
• which organisation received it;
• whether it was accepted;
• who is responsible for action;
• the expected timescale;
• whether the person was contacted;
• what outcome occurred; and
• whether further action is required.

Unresolved referrals should remain visible until responsibility has been confirmed and the pathway is complete.

Operational Scenario Two: Allied Health Referral Tracking

Context: A home-support worker notices increasing difficulty with transfers and records concern about falls risk.

Step 1 – Structured concern: The worker records the observed change using an agreed mobility and risk format, alongside a short narrative describing the context.

Step 2 – Referral creation: The provider sends an electronic referral to the appropriate allied health service, with the older person’s consent and relevant care information attached.

Step 3 – Confirmation and triage: The allied health service confirms receipt, assigns a priority level and identifies the responsible clinician.

Step 4 – Shared progress: The home-support provider, older person and authorised family contact can see whether the referral is awaiting assessment, scheduled or completed.

Step 5 – Integrated follow-up: Recommendations are returned to the care team, equipment actions are assigned and the care plan is updated.

This creates a visible chain of responsibility rather than leaving the person or family to chase multiple services.

Real-Time Operational Awareness

Interoperability can also support safer operational oversight.

Relevant live or near-real-time information may include:

• missed or delayed visits;
• changes in medication support;
• new falls concerns;
• hospital admission;
• equipment failure;
• family-carer breakdown;
• worker access difficulties;
• home-environment risk;
• new safeguarding concerns;
• power outages;
• extreme weather alerts; and
• service capacity constraints.

Connected information can help providers understand whether an event is isolated or part of wider deterioration.

For example, a missed visit may be more significant when combined with recent discharge, living alone, medication changes and reduced mobility.

Preventing Alert Overload

More connected information can create more alerts, but more alerts do not automatically create safer care.

Poorly designed systems may generate:

• duplicate warnings;
• low-value notifications;
• conflicting priorities;
• alert fatigue;
• unclear ownership;
• unnecessary escalation;
• delayed response to genuinely urgent concerns; and
• overreliance on automated thresholds.

Every alert should have:

• a clear purpose;
• defined urgency;
• named responsibility;
• an expected response time;
• an escalation route;
• a closure requirement; and
• regular review of whether it improves outcomes.

Alerts should support professional judgement rather than overwhelm it.

Home Support Must Be Fully Included

Interoperability discussions can become dominated by hospitals and clinical systems, even though home-support workers often see the earliest signs of change.

Frontline home-support information may reveal:

• reduced appetite;
• increasing confusion;
• declining mobility;
• changes in continence;
• missed medication;
• social withdrawal;
• carer exhaustion;
• difficulty managing the home;
• unsafe heating or cooling;
• financial stress;
• new bruising or injury; and
• loss of confidence.

These observations should be captured proportionately and made available to authorised professionals who need them.

Home-support workers should not become informal data clerks, but their practical knowledge should not remain invisible.

Housing and Community Information

Health and care outcomes are shaped by factors beyond formal services.

Interoperable systems may need to connect relevant information about:

• housing accessibility;
• repairs and maintenance;
• heating and cooling;
• digital connectivity;
• transport access;
• food security;
• social participation;
• community programmes;
• neighbourhood safety;
• home modifications;
• power-dependent equipment; and
• local emergency support.

Not every organisation requires access to every detail. Information should be shared according to purpose and role.

However, excluding housing and community intelligence entirely can create an incomplete view of the person’s circumstances.

Rural and Remote Interoperability

Interoperability is particularly important in rural and remote areas where services may be separated by distance and limited capacity.

Challenges may include:

• limited connectivity;
• smaller provider networks;
• workforce shortages;
• long travel distances;
• fewer specialist services;
• greater reliance on informal carers;
• cross-regional referrals;
• limited emergency alternatives;
• delayed equipment delivery; and
• greater vulnerability during extreme weather.

Connected information can reduce unnecessary duplication and help scarce services coordinate more effectively.

Offline and Low-Connectivity Capability

Digital systems should not assume constant internet access.

Providers may need:

• secure offline access to essential records;
• automatic synchronisation when connection returns;
• clear version control;
• conflict-resolution rules;
• emergency contact information;
• minimal-data operating modes;
• device-security controls;
• local backup procedures; and
• contingency processes for prolonged outages.

A system that works only under ideal connectivity conditions may increase rather than reduce risk.

Cultural Safety

Information is not culturally neutral.

Data structures influence what is recorded, what is treated as important and how circumstances are interpreted.

Culturally safe interoperability should allow for:

• preferred language;
• communication support;
• family and kinship structures;
• cultural identity;
• spiritual priorities;
• community relationships;
• gender preferences;
• cultural obligations;
• different understandings of wellbeing; and
• community-controlled service involvement.

Standardisation should not erase identity or force every person into the same assumptions about family, independence or care.

Indigenous Data Sovereignty

Information involving Aboriginal and Torres Strait Islander peoples should be governed in ways that respect Indigenous data sovereignty.

This may require:

• partnership with Aboriginal community-controlled organisations;
• community authority over data use;
• co-design of information standards;
• local control over access;
• transparent secondary-use arrangements;
• culturally meaningful outcomes;
• protection against extractive data practices;
• clear benefit to communities;
• appropriate retention and deletion; and
• ongoing community oversight.

A technically interoperable system may still be culturally unsafe if communities do not have meaningful influence over how their information is defined, shared and used.

Cyber Security Is Part of Care Safety

Interoperability increases the number of connections between organisations, systems, devices and users. Each connection can improve coordination, but it can also create a potential route for unauthorised access, disruption or data loss.

Cyber security should therefore be treated as part of care quality and operational resilience rather than as a separate technical matter.

Providers should consider:

• role-based access controls;
• multi-factor authentication;
• secure device management;
• encryption during transfer and storage;
• supplier security assurance;
• staff training;
• phishing prevention;
• security monitoring;
• incident response;
• business continuity;
• data backup and restoration;
• access review; and
• timely removal of former staff accounts.

A compromised care system may affect visit schedules, medication information, emergency contacts, risk records and communication with partner organisations. Cyber resilience is therefore directly connected to continuity of support.

Privacy by Design

Privacy should be embedded within the design of interoperable systems rather than added after implementation.

Privacy-by-design principles include:

• collecting only information that is needed;
• limiting access according to role;
• separating especially sensitive information where appropriate;
• recording access and changes;
• setting clear retention periods;
• supporting correction and deletion processes;
• providing understandable privacy information;
• testing systems before launch;
• reviewing unintended information flows; and
• restricting secondary use unless properly authorised.

The existence of a technical connection should never be treated as automatic permission to share all available information.

Data Quality Determines Whether Interoperability Is Safe

Connected systems can spread accurate information quickly, but they can also spread inaccurate information quickly.

Common data-quality problems include:

• outdated medication lists;
• duplicate records;
• incorrect contact details;
• unclear authorship;
• missing review dates;
• conflicting risk ratings;
• copied-forward information;
• unclosed referrals;
• unclear responsibility;
• poorly defined fields;
• free-text entered in the wrong location; and
• information that is technically complete but clinically or operationally misleading.

Providers need clear rules for:

• who creates information;
• who verifies it;
• how frequently it is reviewed;
• how discrepancies are resolved;
• which source is authoritative;
• how corrections are communicated;
• how duplicate records are merged;
• how old information is archived; and
• how quality concerns are escalated.

Data quality should be monitored as an operational assurance issue.

The Quality Dashboard Builder can help organisations structure oversight of information quality, unresolved actions, referral completion, access exceptions, overdue reviews and other indicators that show whether interoperability is working safely in practice.

Operational Scenario Three: Coordinating Risk During Extreme Weather

Context: A regional heatwave is forecast. Several older people receive home support, use power-dependent equipment or live in properties with limited cooling.

Step 1 – Identifying vulnerability: Authorised information from home-support records, housing data and emergency-planning systems is used to identify people at increased risk.

Step 2 – Prioritising action: The system groups concerns such as living alone, recent hospital discharge, mobility limitations, medication sensitivity, unreliable cooling and limited family support.

Step 3 – Coordinating responses: Providers, housing organisations, community services and local emergency partners agree who will contact each person, assess the home environment and arrange additional support.

Step 4 – Recording completion: Welfare checks, equipment actions, transport arrangements and escalation decisions are recorded against named responsibilities.

Step 5 – Reviewing outcomes: Leaders assess whether all high-risk people were contacted, which actions were delayed and what changes are required before the next emergency.

Interoperability helps transform broad emergency alerts into targeted, accountable support.

Governance Across Organisational Boundaries

Interoperability creates shared operational processes, but accountability must remain clear.

Governance arrangements should define:

• the purpose of each data exchange;
• the legal and ethical basis for sharing;
• participating organisations;
• data ownership and stewardship;
• authorised user groups;
• consent responsibilities;
• record-correction processes;
• security requirements;
• incident-reporting arrangements;
• response times;
• supplier obligations;
• audit rights;
• business-continuity requirements;
• dispute resolution; and
• termination arrangements.

Governance should also address what happens when organisations disagree about accuracy, urgency, responsibility or access.

Without clear cross-system governance, shared information can create shared confusion rather than shared accountability.

Data Stewardship

Data stewardship concerns the active management of information quality, meaning, access and use.

A data steward may be responsible for:

• maintaining definitions;
• reviewing data-quality issues;
• coordinating corrections;
• monitoring inappropriate access;
• supporting staff interpretation;
• reviewing new data-sharing proposals;
• maintaining standards;
• resolving duplication;
• reporting assurance information; and
• ensuring that person-centred meaning is not lost through standardisation.

Stewardship should exist at both organisational and partnership level.

Supplier and Platform Governance

Many providers rely on external software suppliers, integration platforms and cloud services.

Contracts should address:

• data location;
• security certification;
• system availability;
• backup arrangements;
• incident notification;
• subcontractors;
• access to audit information;
• interoperability standards;
• data export;
• service termination;
• system upgrades;
• technical support;
• response times;
• ownership of derived data; and
• restrictions on secondary use.

Providers should avoid becoming dependent on systems that make it difficult to transfer information safely when contracts change.

Open standards, documented interfaces and practical data-portability arrangements reduce long-term dependency.

Board and Executive Assurance

Boards and executive teams do not need to manage technical detail, but they should understand whether connected information is improving care and whether significant risks are controlled.

Useful assurance questions include:

• Which critical care pathways depend on information exchange?
• Where do staff still rely on manual transfer?
• Which referrals are not closed-loop?
• How often is information delayed or incomplete?
• How are consent preferences recorded and respected?
• How are inappropriate access events identified?
• What happens during system failure?
• How are suppliers assured?
• Can the organisation export its own data?
• How are older people involved in design and review?
• What evidence shows that interoperability has reduced risk?
• Which groups remain digitally or culturally excluded?

The Governance Maturity Assessment can support structured review of accountability, oversight, risk management, information governance and cross-organisational assurance.

Measuring Whether Interoperability Is Working

Success should be measured through outcomes and operational reliability rather than the number of technical connections created.

Possible measures include:

• percentage of discharge information received before the first home visit;
• time between referral and confirmation of receipt;
• percentage of referrals with named responsibility;
• medication discrepancies identified after transition;
• duplicate assessment rates;
• unresolved data-quality issues;
• access exceptions;
• consent-related complaints;
• information-related incidents;
• system downtime;
• offline synchronisation failures;
• older-person satisfaction with information sharing;
• family confidence in coordination;
• staff time spent chasing information;
• avoidable hospital readmission following discharge;
• response times to deterioration alerts; and
• equity of access across rural, remote and culturally diverse communities.

Measures should be interpreted carefully. A reduction in recorded incidents may indicate improvement, but it may also reflect weaker reporting. Quantitative indicators should therefore be combined with audit, feedback and case review.

Co-Design With Older People and Frontline Workers

Interoperability should not be designed solely by technical teams.

Older people can help identify:

• which information they repeatedly have to provide;
• which sharing feels helpful;
• which sharing feels intrusive;
• how consent should be explained;
• what information should be visible during emergencies;
• how representatives should be involved;
• how errors should be corrected; and
• which digital channels are accessible.

Frontline workers can identify:

• where information is currently lost;
• which fields are impractical;
• which alerts create value;
• which alerts are routinely ignored;
• where duplication occurs;
• what must be available offline;
• which responsibilities are unclear; and
• how systems affect time spent with older people.

Co-design increases the likelihood that interoperability will support real work rather than create another layer of administration.

A Phased Implementation Roadmap

Providers and regional partnerships should avoid attempting to connect every system and dataset at once.

Phase One – Identify High-Risk Information Gaps

Map where information failure currently contributes to harm, delay or duplication.

Priority pathways may include:

• hospital discharge;
• medication change;
• falls escalation;
• safeguarding;
• emergency response;
• allied health referral;
• care-plan change; and
• family-carer breakdown.

Phase Two – Agree Purpose and Minimum Information

Define the smallest useful dataset required for each pathway. Avoid sharing information simply because it is available.

Phase Three – Establish Governance

Agree consent, access, responsibilities, correction, incident response, supplier assurance and audit arrangements before technical integration begins.

Phase Four – Pilot With Real Pathways

Test interoperability with a small number of services, people and use cases. Include routine work, urgent escalation, system failure and incorrect-information scenarios.

Phase Five – Measure Impact

Assess whether the pilot reduced delays, duplication, risk and administrative burden.

Phase Six – Scale Carefully

Expand only where standards, governance and operational capacity remain reliable.

Phase Seven – Review Continuously

Interoperability should evolve as services, technologies, risks and community expectations change.

Common Pitfalls

Common weaknesses include:

• treating interoperability as a software-purchasing project;
• sharing excessive information without clear purpose;
• failing to include home-support providers;
• unclear consent processes;
• poor identity matching;
• inconsistent terminology;
• unresolved duplicate records;
• no confirmation that referrals were received;
• alert overload;
• weak offline capability;
• overdependence on one supplier;
• insufficient cultural governance;
• limited involvement of older people;
• poor staff training;
• unclear responsibility across organisations;
• assuming connectivity is reliable everywhere;
• using data for secondary purposes without transparency; and
• measuring technical activity rather than care outcomes.

The Future of Connected Aged Care in Australia

Australia’s future aged care system will need to operate across homes, health services, community organisations, housing, technology platforms and informal support networks.

Fragmented records are increasingly incompatible with this complexity.

Interoperability can help create:

• safer transitions;
• faster escalation;
• fewer repeated assessments;
• better medication continuity;
• more reliable referrals;
• stronger emergency coordination;
• better use of frontline observations;
• greater visibility of unresolved actions;
• more informed planning; and
• less coordination burden for older people and families.

However, connection alone is not enough.

The strongest systems will combine technical standards with human judgement, privacy, cultural safety, Indigenous data sovereignty, accountable governance, cyber resilience and meaningful control for older people.

Interoperability should not make the aged care system more intrusive or more complicated. It should make support feel more continuous, more responsive and easier for people to navigate.