System of systems
A health IT system is one system among many, and the behaviour that matters emerges from the connections. The draft's text is not public.
What the public record carries
Not stated in the public record beyond the title and the abstract's list of parties. The public abstract names integrators, administrators and cloud providers among the parties the document applies to. That is consistent with a system-of-systems theme but does not state its content. The sub-clause itself is not public.
Basis. The public contents carry the sub-clause title. The public abstract names system integrators, system administrators and cloud providers as parties. The draft text is not public.
Why it matters in a health estate
The system-of-systems theme is where most assurance claims break. An interface that was tested in isolation can fail in combination. An upgrade to an identity provider can change the behaviour of a clinical application without any change to the application. A register that treats each system as a separate row will miss the emergent behaviour that patients actually experience.
What to do now
Maintain a dependency map with an owner for every connection. Record the version of each dependency at the time of the last assurance activity. When a dependency changes, re-read the affected rows rather than waiting for the annual review.
The evidence a reviewer will ask for
| Evidence | What it is |
|---|---|
| Dependency map | Every system, interface and service the workflow depends on, with an owner |
| Version record | The version of each dependency at the last assurance activity |
| Interface evidence | Test results for each interface in the combined environment |
| Change trigger | The list of dependency changes that force a re-read of the register |
What a reviewer will ask
An auditor will ask what else the system depends on and what happens when one of those changes. A single-system answer is incomplete.
Common gaps
- Each system is assured separately and the combined workflow is never tested
- An identity or network upgrade changes clinical behaviour and no one links the two
- The dependency map omits the services the supplier operates
- Interface tests are run once at go-live and never after a version change
Before the draft publishes
Add the combined-environment test to the plan for the highest-risk workflow. Name its owner and its date.
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 integration lead and the enterprise architect, because no health IT system stands alone and the dependencies carry risk.