# Clinical responsibilities and safe sharing **Safe digital sharing requires relevant, accurate and timely information to reach the right people, with clear responsibility for its use.** Failure to share, excessive access, a mistaken patient match or an incomplete record can each create clinical risk. The organisation and its clinicians have connected responsibilities for that outcome. [SRC-174](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-174), [SRC-171](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-171) A result delivered to the wrong patient record, or a discharge update left without a responsible receiving team, illustrates why transmission alone is insufficient. Use the [requirements table](https://uk-digital-healthcare-legal-requirements.pages.dev/digital-requirements/index.md) for the required electronic action, then assess the care pathway described in the [blood-results](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/blood-tests-results/index.md) and [discharge](https://uk-digital-healthcare-legal-requirements.pages.dev/examples/hospital-discharge/index.md) examples. A clinical need for communication and a legal requirement for a particular interface remain separate questions. ## Professionals and organisations have connected responsibilities General Medical Council (GMC) guidance addresses sharing relevant information with people providing or supporting direct care, with conditions on confidentiality and consent. Nursing and Midwifery Council (NMC) standards address privacy, informing people about information use, communication and records. Health and Care Professions Council (HCPC) standards require appropriate sharing with colleagues involved in care while respecting confidentiality. Each applies to its respective registrants; the codes are professional standards, not interchangeable statutory gateways. [SRC-174](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-174), [SRC-175](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-175), [SRC-176](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-176) The organisation provides the working environment in which these responsibilities are carried out. Records, access arrangements and communication processes must support safe practice. In England, applicable Care Quality Commission (CQC) regulation includes accurate, complete and contemporaneous records and governance duties. The other national chapters explain their care-provider regimes. [SRC-018](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-018) For a discharge, the clinical question is what the receiving team needs to continue this person's care safely. That purpose informs the relevant information and its urgency. Confidentiality, data protection and any specific sharing duty still determine the lawful arrangements. [SRC-006](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-006), [SRC-010](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-010) ## Digital exchange needs local safety assurance A shared record can display correct information in a misleading context, or fail to deliver an important update. These are practical examples of hazards to assess in the actual care pathway. Supplier assurance and local deployment assurance address different responsibilities. DCB0129 addresses clinical risk management in developing and maintaining health IT. DCB0160 addresses deployment and use by health and care organisations. Their scope and notices matter. NHS England's June 2026 review distinguishes existing standards that relevant bodies must have regard to from future use of enhanced compliance powers. The framework should not be presented as a blanket UK-wide statutory mandate. [SRC-101](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-101), [SRC-102](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-102), [SRC-103](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-103) Other nations and contracts can adopt particular assurance requirements. A provider's duties depend on that adoption and its own care responsibilities. The [national accounts](https://uk-digital-healthcare-legal-requirements.pages.dev/comparison/index.md) and [digital exchange chapter](https://uk-digital-healthcare-legal-requirements.pages.dev/topics/interoperability/index.md) explain the relevant routes. ## When product regulation also matters Some software used to share information may also perform functions that engage medical-device regulation. Its intended purpose and functionality determine that question. A digital record is not automatically a medical device. The wider GB/NI device framework is retained in [software and devices context](https://uk-digital-healthcare-legal-requirements.pages.dev/context/software-and-devices/index.md). [SRC-104](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-104), [SRC-105](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-105), [SRC-107](https://uk-digital-healthcare-legal-requirements.pages.dev/sources/index.md#src-107) For the organisation, the immediate task is to implement the particular digital exchange safely. Device classification, procurement assurance and contractual risk allocation provide further requirements where their scope is engaged. Read next: [patient rights and accountability](https://uk-digital-healthcare-legal-requirements.pages.dev/topics/accountability/index.md) or [care-sharing examples](https://uk-digital-healthcare-legal-requirements.pages.dev/decision-workflow/index.md).