What Would a Truly Interoperable Adult Social Care System Look Like?

A person leaves hospital with a revised medicines regime, new mobility needs and an agreed package of homecare. The hospital has recorded the clinical changes, the local authority has arranged support, the care provider has opened a digital care record and the community nursing team has its own documentation. Everyone has information, but no single professional can necessarily see the complete picture.

This is one of the defining challenges of digital transformation in adult social care. The opportunity explored across the Digital Transformation in Social Care Knowledge Hub is not simply to replace paper records with electronic systems. It is to make information more reliable, accessible and useful across organisational boundaries while protecting the rights of people receiving support.

Genuine interoperability and system integration would allow authorised professionals to access relevant information without repeatedly reconstructing a person's circumstances. It would also depend on strong digital records and information governance, because greater connectivity is valuable only when information is accurate, appropriately shared and protected.

For England's adult social care system, the central question is therefore wider than whether different software products can exchange data. It is whether health, social care, housing and community partners can coordinate decisions around the person, maintain clear accountability and demonstrate that connected information leads to better care.

Interoperability Is More Than Connecting Digital Systems

Interoperability describes the ability of different systems and organisations to exchange information and use it meaningfully. Technical connectivity is one component, but a system can transfer information successfully without supporting effective practice.

Consider a local authority assessment transferred electronically to a homecare provider. If the receiving system places the assessment in a document repository but does not identify current risks, agreed outcomes or outstanding actions, the information has moved without becoming operationally useful.

Similarly, a medicines record might be accessible across organisations but remain unsafe to rely upon if it is unclear which professional authorised a change, when the change took effect or whether the information has been reconciled against the person's current prescription.

A mature interoperable system needs several connected capabilities:

• Technical interoperability: systems can exchange information securely using compatible interfaces and standards.
• Semantic interoperability: receiving organisations interpret information consistently, including its meaning, status and clinical or social care context.
• Organisational interoperability: partners have agreed responsibilities, workflows, escalation routes and information-sharing arrangements.
• Practical interoperability: frontline workers can find and use the information they need within their actual working environment.
• Person-centred interoperability: people can understand, contribute to and exercise appropriate control over information used in their care.

These dimensions are interdependent. A technically sophisticated interface cannot compensate for an outdated assessment, ambiguous responsibilities or a workforce that does not trust the information displayed.

The distinction also matters for procurement. Purchasing software described as interoperable does not automatically create an interoperable service. Providers need to establish what information can actually be exchanged, with whom, under which conditions and whether the exchange supports decisions rather than simply transferring files.

Why England's Adult Social Care Information Remains Fragmented

England's adult social care landscape includes local authority assessment and commissioning teams, independent and voluntary-sector providers, NHS organisations, housing providers, personal assistants, direct payment arrangements and unpaid carers. Each operates within different funding, governance and information systems.

A person may receive domiciliary care from one organisation, community nursing from another and occupational therapy through a local authority or NHS service. Their GP holds important medical information, while the housing provider may manage adaptations, repairs and environmental risks.

These boundaries are not necessarily evidence of poor practice. Different organisations have legitimate responsibilities and different requirements for recording information. The difficulty arises when essential information is inaccessible, duplicated, contradictory or transferred too late to support safe decisions.

Providers have also invested in digital care planning at different times and with different suppliers. Smaller organisations may have limited technical capacity, while larger groups may operate multiple inherited systems following expansion or acquisition.

Even within one provider, care planning, rota management, medicines administration, incident reporting, workforce records and quality assurance may operate on separate platforms. Staff can spend considerable time moving information between them.

Stronger digital care planning therefore requires attention to the relationships between systems, not merely the functionality of an individual care record.

National programmes supporting digital social care records and shared care information have created important foundations. However, adoption of electronic records and the existence of regional information-sharing arrangements should not be confused with universal, consistent interoperability across England.

Local infrastructure, supplier capability, information governance agreements and operational maturity continue to vary. Any credible future model needs to accommodate that variation without accepting permanent fragmentation as inevitable.

What a Connected Person-Centred Care Record Could Contain

A truly interoperable model would not necessarily place every piece of information in one enormous database. That could create unnecessary security, accuracy and governance risks.

A more credible approach would allow authorised users to access an appropriately controlled, current view of information held by different organisations, supported by common standards and clear responsibility for maintaining each record.

For a person receiving care, the relevant information might include their preferred name, communication needs, consent preferences, personal goals, current support arrangements, key risks, medicines information where appropriate, professional contacts and recent changes affecting care.

Crucially, the record should distinguish between information that is clinically verified, information reported by the person, professional assessments, historical observations and matters requiring review.

Not every professional needs access to every detail. A homecare worker may need to know that a person's transfer arrangements have changed, but not necessarily have access to an unrelated historical clinical record.

People should also have meaningful opportunities to correct inaccuracies and contribute information about what matters to them. This connects interoperability with co-production, choice and control rather than treating individuals as passive subjects of data exchange.

Accessible information is particularly important for people with learning disabilities, autism, sensory impairments, acquired brain injuries or communication differences. A connected system that remains inaccessible to the person whose information it contains would deliver only a partial form of integration.

Scenario: Hospital Discharge Into Homecare

An older woman is preparing to return home following a hospital admission. Before admission, she received two daily homecare visits. Her mobility has deteriorated, her medicines have changed and she now requires additional assistance with transfers.

The hospital discharge team, local authority, homecare provider and community nursing service each hold part of the relevant information. Under a fragmented arrangement, the provider might receive a discharge summary by email, a separate commissioned-hours notification and a telephone update about equipment. The Registered Manager must reconcile these sources before deciding whether the package can begin safely.

In a more interoperable arrangement, authorised professionals would access a shared view of the discharge plan, with clear identification of the current medicines information, mobility assessment, equipment arrangements, support requirements and outstanding actions. The provider would receive structured notification of material changes rather than relying entirely on someone remembering to send an update.

However, the system would not replace the provider's assessment of whether staff have the required competencies, whether the home environment is suitable or whether the commissioned visit pattern is sufficient. The Registered Manager would still need to resolve uncertainties and escalate concerns before accepting arrangements that cannot safely be delivered.

The woman would be involved in confirming her preferences, including when she wishes to receive support and what independence she wants to regain. Where appropriate, her family could contribute with her agreement.

After discharge, changes identified by care workers could be communicated to relevant professionals through agreed pathways. The local authority and provider could review whether the package remains appropriate, while the person describes whether she feels safe and is making progress.

The strongest evidence of interoperability would not be the successful transmission of a discharge document. It would be fewer avoidable misunderstandings, timely responses to changing needs and a discharge experience that supports recovery rather than creating further disruption.

Information Sharing, Consent and Legal Accountability

Interoperability creates significant opportunities for safer coordination, but it also expands the consequences of poor information governance. Information that was previously held within one organisation may become available to several others, increasing the importance of lawful access, accuracy, security and accountability.

In England, relevant obligations arise under the UK General Data Protection Regulation, the Data Protection Act 2018, confidentiality requirements and applicable health and social care legislation. The Health and Social Care Act 2008 (Regulated Activities) Regulations 2014 also establish requirements relevant to safe care, person-centred care, consent and good governance for CQC-regulated providers.

Organisations need to distinguish the lawful basis for processing personal information from any separate condition required for processing special category data. They must also consider duties of confidentiality and whether an appropriate basis exists for disclosure.

Consent to care or treatment is not automatically the same as data protection consent. Nor should organisations assume that every necessary care-related information exchange requires UK GDPR consent as its lawful basis. The correct approach depends on the circumstances, purpose, organisational responsibilities and applicable legal requirements.

Where a person lacks capacity to make a particular decision, the Mental Capacity Act 2005 provides the relevant decision-making framework in England and Wales. Capacity is decision-specific, and a best-interests decision about care does not automatically authorise unrestricted information sharing.

Good interoperability therefore requires clear rules about purpose, access and disclosure. Role-based permissions, access logs, identity verification, retention arrangements and processes for correcting inaccurate information are essential safeguards.

The information-sharing and confidentiality challenge is particularly important where safeguarding concerns arise. Appropriate information sharing can support protection from abuse or neglect, but safeguarding does not justify indiscriminate access to every aspect of someone's life.

Organisations should establish when urgent disclosure is necessary, how decisions are recorded and who is responsible for reviewing concerns about inappropriate access. Where complex legal questions arise, specialist information governance or legal advice may be needed.

Scenario: Supported Living, Privacy and Shared Risk Information

A man with a learning disability lives in supported accommodation and receives support from an independent provider. He also attends community activities, receives specialist input from NHS professionals and has regular contact with his family.

His support team uses a digital care record. A community health professional recommends changes to how staff recognise and respond to episodes of distress, while a family member requests wider access to the provider's records because they are concerned about his safety.

An interoperable system could make relevant professional recommendations available to authorised support workers promptly. It could also identify when the support plan requires review and provide an auditable record of who has accepted responsibility for implementing changes.

But wider connectivity must not override the man's rights. Staff should support him to understand how his information is used, using accessible communication and appropriate decision-making support. The provider should establish what he wishes to share with his family and consider his capacity in relation to relevant decisions where there is a reason to doubt it.

Family members may provide valuable information without automatically having unrestricted access to confidential records. Equally, information from relatives should not be dismissed simply because they are not formal decision-makers.

The Registered Manager and relevant professionals would agree which information needs to be shared, how discrepancies will be resolved and how staff will know which guidance is current. Where concerns involve restrictive practice or safeguarding, established escalation and review arrangements remain necessary.

The provider could test implementation through staff discussions, observation, support-plan reviews and feedback from the man himself. The outcome sought is not greater surveillance or a larger digital record. It is consistent, respectful support that reflects his communication needs, relationships, preferences and rights.

Clinical and Social Care Boundaries Need Clear Operational Rules

Interoperability becomes particularly complex where social care workers support people with significant health needs. Digital access to clinical information can improve coordination, but it does not automatically expand a worker's professional competence or authority.

For example, a community nurse may update a clinical care plan following an assessment. A provider receiving the update must still establish whether it changes the tasks its workers are expected to perform, whether additional training is required and whether an appropriate delegation arrangement exists.

Information exchange should therefore connect with professional accountability, competency assessment and escalation processes. The receiving organisation needs to understand whether information is an instruction, recommendation, observation or notification requiring further clarification.

This is especially relevant to multidisciplinary working and integrated clinical pathways, where several professionals contribute to one person's support.

In practice, shared records should identify who is responsible for each decision, who can amend the relevant information and what happens when professionals disagree. A digital record should not create the appearance of consensus where responsibilities remain unresolved.

The same principle applies to medicines. Access to an NHS medicines list can be useful, but providers still need safe medicines processes, reconciliation where appropriate, current instructions and clear routes for resolving discrepancies. Interoperability supports those controls; it does not replace them.

Commissioning a Connected Care System

Local authorities and NHS commissioners have an important influence over interoperability through service specifications, procurement, contract management and partnership arrangements.

Commissioners can encourage connected working by defining what information needs to move between organisations, the outcomes that exchange should support and the minimum security and operational requirements expected of participating providers.

However, a blanket requirement for every provider to use one proprietary platform may create disproportionate costs, reduce supplier choice or disadvantage smaller organisations. A more sustainable approach is to specify the required capabilities, interfaces, standards and assurance arrangements wherever feasible.

Commissioning requirements should distinguish between routine performance reporting and information needed for direct care. A commissioner may require aggregate evidence about outcomes, capacity or service quality without needing unrestricted access to individual care records.

Equally, a provider may need timely information about an individual person's changing support requirements without receiving broad access to local authority assessment systems.

These distinctions should influence contract schedules, data-sharing agreements, mobilisation plans and service review arrangements. Providers can use the Commissioner Evidence Builder to structure evidence about contractual responsibilities, outcomes and assurance, while separately confirming the legal and technical requirements of information exchange.

Cost is another significant consideration. Integration may involve supplier fees, configuration, testing, staff training, cybersecurity controls and ongoing maintenance. Funding models that assume interoperability is free risk creating obligations that providers cannot implement reliably.

Smaller providers and organisations supporting people through direct payments may require proportionate routes into shared information arrangements. Otherwise, better connectivity could become concentrated among larger organisations, widening existing inequalities in access to coordinated support.

Scenario: A Local Authority and Its Homecare Market

A local authority commissions domiciliary care from a mixture of large regional providers, smaller local businesses and voluntary-sector organisations. Each provider uses different digital systems, and the council receives performance information through several reporting formats.

The commissioning team wants better visibility of service capacity, delayed starts, missed visits and changes in people's support needs. It initially considers requiring all contracted providers to adopt one digital platform.

Following engagement with providers and people receiving care, the authority identifies a more proportionate approach. It defines a limited set of shared data requirements and explores secure interfaces that allow providers to retain suitable existing systems while exchanging agreed information.

The authority separates individual care information from aggregated contract monitoring data. It also establishes rules for correcting discrepancies, identifying responsibility for updates and responding when a provider's system is unavailable.

One smaller provider explains that integration costs would be difficult to absorb within existing fee rates. The council considers implementation support and realistic transition periods rather than treating technical readiness as an immediate pass-or-fail measure.

For people receiving care, the practical benefit could be faster confirmation of care arrangements and fewer repeated requests for information. For providers, it could mean less duplicate reporting and clearer communication about commissioned changes.

The commissioning team tests the arrangement against actual cases before expanding it. It checks whether information arrives accurately, whether staff can act on it and whether individuals experience improved continuity.

This illustrates why digital procurement and contract management should be concerned with operational outcomes and market sustainability, not simply the number of systems connected.

Workforce Adoption Determines Whether Information Becomes Better Care

Interoperability changes how people work. Care workers, social workers, nurses, administrators and managers may need to understand information created by other organisations, recognise its limitations and respond to digital notifications.

The workforce challenge is therefore broader than learning a new interface. Staff need confidence in the meaning, reliability and appropriate use of shared information.

A care worker should know whether a displayed instruction is current, who to contact when it conflicts with the person's expressed preferences and how to record an observation that may require professional review.

Registered Managers need sufficient capacity to oversee digital workflows, review unresolved alerts and test whether staff understand the systems used in practice. Directors should recognise that introducing integration can temporarily increase workload while processes are redesigned.

Effective digital skills and workforce adoption involves practical competency assessment, supervision and feedback rather than relying exclusively on training attendance.

Providers can assess whether staff can locate essential information, recognise when a record may be inaccurate, follow escalation procedures and explain how digital information informs their decisions.

Implementation also needs to account for mobile working, unreliable connectivity, shared devices, accessibility requirements and varying levels of digital confidence. A system designed around office-based users may be poorly suited to lone workers visiting people in their homes.

The stronger objective is to reduce unnecessary administrative work while preserving time for relationships, professional judgement and meaningful support. If connected systems generate additional alerts, duplicated tasks or repeated authentication problems, the anticipated productivity gains may not materialise.

Governance, Cybersecurity and Supplier Accountability

Interoperability changes organisational risk because a weakness in one system can affect several partners. An integration failure may delay information, introduce inaccuracies or expose confidential records beyond the organisation where the original problem occurred.

Providers therefore need a clear understanding of their digital dependencies, including which suppliers process information, which interfaces support essential workflows and what alternative arrangements exist during disruption.

Strong cybersecurity and digital resilience involves access management, secure configuration, incident response, supplier assurance, backup arrangements and tested business continuity procedures.

Cybersecurity is not solely an IT department responsibility. Registered Managers need to understand how disruption affects care delivery, while directors and boards should receive assurance about significant digital risks and unresolved dependencies.

Providers can use the Digital Transformation Readiness Assessment to examine their wider digital strategy, workforce capability, information governance and resilience before expanding integration arrangements.

Supplier contracts also matter. Organisations should understand data ownership and access arrangements, support responsibilities, security expectations, system availability, incident notification provisions and how information can be transferred if the supplier relationship ends.

Proprietary systems that make it difficult to retrieve information in usable formats can create long-term dependency. This may weaken competition and make service transitions more expensive.

Interoperability should therefore be considered alongside exit planning and continuity of care. A provider changing software should be able to preserve relevant records, maintain essential access and demonstrate that information has transferred accurately.

Scenario: A Cyber Incident Across Connected Services

A regional care provider operates supported living and homecare services. Its digital care records exchange selected information with a partner organisation through a secure interface.

One morning, the provider discovers suspicious activity affecting its main digital platform. The organisation restricts access while its supplier investigates. Because the systems are connected, the incident response team must also establish whether shared information or partner systems could be affected.

The Registered Managers activate established continuity arrangements. Staff use controlled access to essential offline information and confirm urgent care requirements through approved communication routes. The organisation prioritises medicines, high-risk support arrangements and people whose needs may change rapidly.

The provider's information governance and technical leads assess the incident, coordinate with the supplier and determine appropriate notification obligations, including whether the circumstances require reporting to the Information Commissioner's Office or other relevant bodies.

Partner organisations receive proportionate information needed to protect their own systems and maintain care. The provider avoids sharing unverified technical conclusions while ensuring that operational risks are not concealed.

Following restoration, records created during the disruption are reconciled carefully. Managers check whether changes to care arrangements, incidents or medicines information were missed or duplicated.

The board receives an account of the disruption, its impact on people, the effectiveness of contingency arrangements and outstanding corrective actions. Lessons influence supplier assurance, staff exercises and the organisation's risk register.

The scenario demonstrates an important distinction: interoperability can improve coordination during normal operations, but mature integration also requires organisations to remain safe when connected technology is unavailable.

Quality Assurance Must Test the Whole Information Pathway

A provider may be able to demonstrate that information was transmitted successfully without knowing whether it was received, understood or acted upon.

This is why digital audit and assurance should examine the complete pathway from the original information source through to the decision and its effect on the person receiving support.

Useful assurance questions include whether the information was current, whether the correct recipient had access, whether any discrepancy was resolved and whether the resulting action was appropriate.

Digital audit trails can establish when information was accessed or changed, but they cannot independently demonstrate that staff understood the implications or delivered better support.

A stronger assurance model triangulates several forms of evidence:

• System evidence: interface reliability, failed transfers, access exceptions and unresolved data discrepancies.
• Operational evidence: timeliness of decisions, escalation quality and completion of agreed actions.
• Workforce evidence: observed competence, supervision findings and staff feedback about usability.
• Person-centred evidence: people's experiences of continuity, communication, choice and involvement.
• Governance evidence: recurring risks, corrective action, independent challenge and sustained improvement.

Leadership teams can use the Quality Dashboard Builder to structure performance and outcome reporting, while ensuring that dashboards are supported by case-level review and direct feedback.

For example, a dashboard may show fewer delayed information transfers after a new interface is introduced. That is encouraging, but further examination should establish whether care starts were more reliable, staff spent less time resolving discrepancies and people experienced fewer disruptions.

Where data quality problems persist, organisations should examine their causes rather than simply asking staff to complete more fields. Poor information may reflect unclear ownership, unsuitable workflows, excessive duplication or unrealistic recording expectations.

CQC Expectations and Evidence of Integrated Practice

For CQC-regulated services in England, interoperability is relevant to several regulatory expectations, although CQC does not require every provider to use a particular integration platform.

Regulation 17, good governance, is particularly relevant to accurate records, effective systems for assessing and monitoring quality and the management of risks. Regulation 12, safe care and treatment, may also be relevant where incomplete or delayed information creates avoidable risks.

Depending on the circumstances, interoperability can support evidence relating to safe systems, pathways and transitions; care provision, integration and continuity; governance, management and sustainability; and partnerships and communities.

However, CQC assurance should not be reduced to demonstrating that electronic records exist. Assessors may explore whether people receive coordinated support, whether staff can access essential information and whether leaders understand the risks created by fragmented systems.

Strong CQC digital records and data assurance should therefore connect technical arrangements with the lived reality of care.

For example, a provider might present evidence that hospital discharge information is imported automatically. A more convincing account would also show how managers check its accuracy, resolve missing information, update care plans and confirm that workers understand revised support arrangements.

The CQC Evidence Gap Analyzer can help providers examine whether their evidence addresses relevant quality expectations, but it does not replace direct testing of practice or regulatory judgement.

Commissioners and CQC may examine overlapping concerns, but their roles differ. CQC assesses compliance with applicable regulatory requirements, while commissioners monitor contractual obligations, service performance and agreed outcomes.

Providers should maintain coherent evidence that can support both forms of scrutiny without assuming that one reporting framework automatically satisfies the other.

Building an Interoperability Strategy That Providers Can Deliver

For many adult social care organisations, full interoperability will be a gradual development rather than a single implementation project.

The most useful starting point is often to identify where fragmented information creates the greatest operational risk or unnecessary workload. Hospital discharge, medicines changes, safeguarding communication, multidisciplinary reviews and commissioned support changes may offer stronger initial priorities than connecting every available dataset.

Providers should then map the information pathway: who creates the information, who needs it, what decisions depend on it and how the organisation currently verifies its accuracy.

Only after this analysis should leaders determine whether a technical interface, redesigned workflow, revised information-sharing arrangement or combination of measures is required.

Implementation should include testing with real operational scenarios, involvement of frontline workers and people receiving support, and a clear process for managing exceptions.

Organisations also need to assess whether their existing supplier contracts and systems support the proposed exchange. Some integrations may be technically possible but financially disproportionate or unsuitable for the organisation's current digital maturity.

The Governance Maturity Assessment offers a way to examine whether leadership responsibilities, risk ownership and assurance arrangements are sufficiently developed to support wider organisational change.

Boards should expect a credible business case to explain not only implementation costs but also ongoing support, workforce time, cybersecurity, supplier dependency and how benefits will be measured.

Successful implementation may produce fewer duplicated assessments, faster resolution of discrepancies and improved continuity. It should not be judged primarily by the number of interfaces activated or records exchanged.

What Could the Next Generation of Interoperability Enable?

Over the coming years, stronger interoperability could support more timely coordination across health, social care, housing and community services. However, progress will depend on standards, funding, supplier cooperation, governance and the ability of organisations to implement change safely.

One plausible development is greater use of event-based information sharing. Rather than requiring professionals to search several systems for updates, relevant changes could generate controlled notifications to those responsible for responding.

For example, a material change in mobility needs could prompt review of the care plan, equipment arrangements and workforce competencies. Such notifications would require careful design to prevent alert fatigue and ensure that responsibility for action is explicit.

Another opportunity lies in better population-level planning. Where information is lawful, sufficiently reliable and appropriately aggregated, commissioners could identify patterns in demand, delayed care starts, workforce capacity and changing support needs.

Improved data quality and performance intelligence could help local systems distinguish genuine changes in need from artefacts caused by inconsistent recording.

Artificial intelligence may eventually assist with identifying discrepancies, summarising relevant information or highlighting potential coordination problems. These applications remain dependent on reliable data, appropriate validation and clear human accountability.

AI-generated summaries could also introduce errors or omit important context. They should not be treated as authoritative clinical or social care decisions simply because they draw information from multiple systems.

The most valuable long-term development may be a shift from organisation-centred records towards coordinated, person-centred information pathways. That would allow individuals to experience care as a connected service even where responsibility remains distributed across several organisations.

Yet this vision must preserve choice. Some people may prefer limited digital sharing, need support to understand their options or have legitimate concerns about who can access sensitive information.

A genuinely mature system will accommodate these differences rather than equating maximum information exchange with maximum quality.

Conclusion

A truly interoperable adult social care system would not be defined by a single national database, a universal software supplier or the ability to transfer every available record between organisations.

It would be defined by whether relevant information can move safely and meaningfully between the people and organisations responsible for delivering support, without losing accuracy, accountability or the person's voice.

For providers, this requires more than investment in digital infrastructure. It demands clear information ownership, reliable care processes, workforce competence, proportionate cybersecurity, effective supplier management and governance that tests whether information sharing improves decisions.

For local authorities and NHS partners, interoperability creates an opportunity to strengthen coordination and commissioning intelligence, but only where requirements are practical, financially sustainable and designed around real service pathways.

For people receiving support, the benefits should be tangible: fewer repeated explanations, better continuity, timely responses to changing needs and greater involvement in decisions about their care and information.

The strongest direction for England is therefore not simply more connected technology. It is a more coherent care system in which digital connections support professional relationships, shared responsibilities and person-centred outcomes.

Interoperability becomes meaningful when information does not merely arrive at its destination, but helps the right person make the right decision at the right time, with the individual receiving support remaining central throughout.