Knowledge transfer
Knowledge transfer is the second family: risk, safety, security and privacy management, each with communication at the transition points.
What the public record carries
Not stated in the public record beyond the structure. The public contents place a second family at 5.3, covering collaboration within and between organisations, with a general opening and four elements at 5.3.2 to 5.3.5. The first edition's introduction adds that those four, the ones that reach across organisations, carry extra text on how the parties communicate and share information when a major handover happens. The text is not public.
Basis. The public contents list 5.3 Knowledge transfer with a general part and four sub-elements. The first edition's introduction says the four cross-organisational elements carry extra sub-clauses on communication. The text is not public.
Why it matters in a health estate
Knowledge transfer is the element family that makes the life cycle work. A supplier can hold excellent risk, safety, security and privacy processes and still leave the buyer unable to operate the system safely, because what was known in development did not cross the boundary. The four elements are grouped under transfer rather than under management for that reason.
What to do now
For each of the four elements record what must cross each boundary, in what form, at which transition and to whom. Test one transfer end to end and record what arrived and what did not.
The evidence a reviewer will ask for
| Evidence | What it is |
|---|---|
| Transfer list | What must cross each boundary for each of the four elements |
| Format note | The form each transfer takes and the level of detail the receiver needs |
| End-to-end test | One transfer followed from sender to receiver, with what arrived |
| Receiver confirmation | The receiver's written confirmation that the transfer was usable |
What a reviewer will ask
A reviewer will ask what the receiving organisation actually got. A transfer that was sent is not a transfer that was usable.
Common gaps
- The supplier sends a large document set and the receiver cannot find the operating limits
- Each element transfers at a different time with no shared schedule
- The receiver has no way to ask a question after the handover
- A transfer is recorded as complete when it was sent, not when it was understood
Before the draft publishes
Follow one transfer end to end and write what the receiver could and could not use. Fix the first unusable item.
If the draft changes this row
The draft is edition 2 and 62 pages, one page more than the first edition. Its text and any change summary are not public as at 21 October 2026. This row follows the published first edition's structure, which is what your procedure should name today. The change watch emails you when the record changes or the draft text lands, and the row is re-read then. No one can tell you what moved before that, and this page does not guess.
Related rows
Who this binds. The CISO and the clinical safety officer, because knowledge transfer is the second family of elements and the one that crosses organisations.