Consent, Privacy and Everyday Information Sharing in LD Services
Information sharing often feels routine until a person’s privacy is at stake. Staff may be asked to update family, speak to a landlord, contact a GP, brief a day service, respond to a social worker or share details after an incident. Strong providers connect these decisions to the wider Learning Disability Services Knowledge Hub, because privacy, consent and safety sit at the centre of lawful support.
This is closely linked to learning disability legal frameworks and rights, especially where capacity, consent, confidentiality, safeguarding and best interests are involved. It also affects learning disability service models and pathways, because information often moves between supported living, outreach, residential care, health services, day provision, commissioners and families.
The practical standard is that providers should be able to evidence what information was shared, why it was shared, whether the person consented, how they were supported to understand the decision and what safeguards protected privacy.
Concept Explained Clearly
Everyday information sharing means deciding when personal information about a person’s health, support, risks, preferences, relationships, finances or routines can be shared with others. It may be planned, such as a GP appointment update, or urgent, such as a safeguarding concern.
Consent should be specific wherever possible. A person may agree for staff to tell their sister about hospital appointments but not about relationships. They may agree to share medication information with a day service but not with a neighbour or landlord. Strong services avoid broad assumptions.
Why It Matters in Real Services
Poor information sharing can harm trust. People may stop telling staff things if they believe private information will be passed on automatically. This can increase safeguarding risk, reduce openness and damage relationships.
Under-sharing can also create harm. If essential information is not shared with health services, safeguarding teams or other support providers, risks may be missed. Providers should be able to evidence a balanced approach that protects privacy while enabling safe support.
What Good Looks Like
Good practice starts with the person. Staff explain who is asking for information, what information is involved, why it may be shared and what could happen if it is not shared. Communication should match the person’s needs.
Strong services demonstrate that staff know the difference between helpful updates, necessary professional sharing and inappropriate disclosure. This creates a clear line of sight from consent to information sharing to outcome.
Operational Example 1: Family Request for Health Information
Context
A man attended a GP appointment about stomach pain. His mother rang the service afterwards asking what the GP said. The man had not clearly agreed that details could be shared.
Five Practical Steps
- Staff clarified the decision as whether to share GP appointment information with his mother.
- The person was supported with simple choices about what could be shared: everything, some information or nothing.
- Staff explained that he could change his mind and choose different sharing rules for future appointments.
- His consent was recorded, including the exact information he agreed could be passed on.
- Review checked whether the sharing arrangement still felt right after follow-up health discussions.
Support Approach and Delivery Detail
The provider did not treat the mother’s long-standing involvement as automatic permission. Staff supported the person to choose what he wanted shared. He agreed that staff could say the GP had prescribed medication but did not want details about symptoms discussed.
How Effectiveness Was Evidenced
Evidence included consent notes, appointment records, staff communication with family and review discussion. The provider evidenced privacy, consent and continued family involvement without over-sharing.
Deepening the Approach: Consent Is Not One Blanket Permission
Consent to information sharing should be decision-specific and context-specific. The article on mental capacity, consent and best interests in learning disability services explains why providers must avoid treating consent as a broad label across unrelated decisions.
Where the person lacks capacity to decide about sharing specific information, staff should consider best interests, necessity, least intrusive sharing and the person’s known wishes. Where safeguarding risk is present, information may need to be shared without consent, but records should explain why.
Operational Example 2: Sharing Risk Information With a Day Service
Context
A woman attending a day service had recently become distressed when unfamiliar men stood close to her. Supported living staff knew this was linked to a previous safeguarding concern, but the person did not want private history shared widely.
Five Practical Steps
- Staff identified what the day service needed to know to support her safely.
- The person was supported to agree a limited sharing statement focused on practical support, not private history.
- The day service received guidance on space, staff approach, signs of distress and escalation.
- Records showed why detailed safeguarding history was not shared because it was not necessary for daily support.
- Review monitored distress incidents, staff consistency, attendance and whether information sharing remained sufficient.
Support Approach and Delivery Detail
The provider avoided both extremes: withholding all information or sharing unnecessary personal detail. Staff focused on practical support needs. The person agreed that the day service could know she needed space and a named worker if distressed.
How Effectiveness Was Evidenced
Evidence included consent records, inter-service communication, day service feedback, incident monitoring and review minutes. Distress reduced because staff had enough information without breaching privacy.
Systems, Workforce and Consistency
Teams manage information sharing well when staff understand consent boundaries. Support plans should record who the person wants involved, what information can be shared, what should remain private, and when safeguarding or legal duties may override ordinary consent.
Handovers should include necessary information only. Supervision should test whether staff are sharing details because they are needed for support, or because informal practice has become too loose. Managers should challenge both gossip and unsafe withholding.
The principles in day-to-day MCA practice in learning disability support reinforce that consent must be supported, recorded and revisited as circumstances change.
Operational Example 3: Landlord Asking About Behaviour Concerns
Context
A landlord contacted a supported living provider after neighbours complained about late-night noise. The landlord asked whether the person had a diagnosis and whether staff were “managing behaviour”.
Five Practical Steps
- Staff separated tenancy information from private health or diagnostic information.
- The person was supported to understand what the landlord needed to know about noise concerns.
- With consent, staff shared a practical plan about reducing noise, not diagnostic details.
- The person helped choose actions, including headphones, quieter gaming times and neighbour communication support.
- Review monitored complaints, tenancy stability, privacy, consent and whether further sharing was needed.
Support Approach and Delivery Detail
The provider protected privacy while responding responsibly to tenancy risk. Staff did not disclose diagnosis because it was not necessary. They shared the agreed action plan and supported the person to understand the tenancy consequences.
How Effectiveness Was Evidenced
Evidence included consent notes, landlord communication, accessible tenancy explanation, support records and complaint monitoring. The provider evidenced lawful information sharing linked to tenancy stability.
Governance and Evidence
Governance should show how information sharing is consent-led, proportionate and safe. Useful evidence includes consent records, information-sharing logs, safeguarding records, capacity notes, best interests decisions, audits, staff training, supervision and complaints review.
Data can show privacy concerns, family disputes, safeguarding referrals, missed communication, complaints, incidents or inconsistent practice. Qualitative evidence shows whether the person feels respected, informed and in control of who knows what.
Providers should be able to evidence a clear line of sight from support model to action to outcome. If information sharing improves health access, day service safety, tenancy stability or safeguarding response, governance should show how privacy was protected at the same time.
Commissioner and CQC Expectations
Commissioners expect learning disability providers to share information safely across pathways while protecting people’s rights. They look for evidence that information supports outcomes and is not shared unnecessarily.
CQC expectations include consent, dignity, safeguarding, person-centred care and good governance. Inspectors may review whether confidential information is protected, whether people control involvement where possible and whether safeguarding information is shared appropriately. Strong services demonstrate that privacy and safety are managed together.
Common Pitfalls
- Assuming family members can receive all updates because they have always been involved.
- Sharing diagnostic or personal history when practical support information would be enough.
- Failing to explain information-sharing choices accessibly.
- Using broad consent forms without checking specific decisions.
- Withholding safeguarding information because staff are unsure about confidentiality.
- Recording that consent was given without saying what was shared and with whom.
- Letting informal staff conversations disclose more than necessary.
Conclusion
Information sharing in learning disability services must be purposeful, proportionate and respectful. Providers should be able to evidence how consent was supported, what information was shared, why it was necessary and how privacy was protected. Strong services do not treat information as belonging to the organisation; they recognise that it belongs first to the person.