Core themes
Clause 4 carries the themes of the document: the sociotechnical ecosystem, the system of systems, the life cycle, roles and responsibilities, communication, and the interdependence of the three properties.
What the public record carries
Not stated in the public record beyond the structure. The first edition's contents place seven sub-clauses under the core themes heading: a general opening, the sociotechnical ecosystem, the system of systems, the life cycle, roles and responsibilities, communication, and the way the three properties depend on each other. The titles are in the public contents; this page does not reproduce the text under them. The introduction of the first edition says the eight foundational elements in Clause 5 underpin the themes set out in Clause 4. The draft's own text and any change to the structure are not public.
Basis. The public preview's contents and introduction name Clause 4 and its seven sub-clauses. The clause text is not public.
Why it matters in a health estate
Clause 4 is the argument the rest of the document rests on. It says that health software is not a product in isolation but a sociotechnical arrangement, that it sits inside a system of systems, that it has a life cycle with handovers, that responsibilities move across that life cycle, that communication at the handovers is the control, and that the three properties move together. A reader who skips to Clause 5 will collect elements without the reason they are grouped.
What to do now
Use the seven themes as the headings of the transition plan. Under each, write the evidence the organisation already holds and the evidence it does not. The plan then reads as an argument rather than a checklist, and the gaps are visible in the order the document itself uses.
The evidence a reviewer will ask for
| Evidence | What it is |
|---|---|
| Theme note | One page per theme, with the organisation's position and the evidence held |
| Handover map | The life cycle stages and the handovers between parties |
| Communication record | What is exchanged at each handover, in what form and by whom |
| Interdependence note | Where a change to one property carries a change to the other two |
What a reviewer will ask
A reviewer will ask how the register's rows connect to the document's own themes. A flat checklist with no theme headings is harder to defend and easier to leave incomplete.
Common gaps
- The register lists controls with no link to the theme each one serves
- The life cycle is drawn as a supplier's process rather than the system's whole life
- Communication is treated as meetings rather than as records exchanged at handovers
- The three properties are managed by three teams with no shared change record
Before the draft publishes
Write the seven headings and place every existing register row under one. Rows that fit nowhere are either out of scope or the gap.
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 system owner, because Clause 4 sets the themes the eight foundational elements in Clause 5 are meant to support.