Sociotechnical ecosystem
Health software works or fails as a sociotechnical arrangement: the people, the tasks, the technology, the organisation and the environment together. The draft's text is not public.
What the public record carries
Not stated in the public record beyond the title and the introduction's framing. The introduction of the first edition says the document allows for a changing and complicated setting in healthcare, with people, technology (hardware and software), organisations, processes and the outside world all in view. The sub-clause itself is not public.
Basis. The public contents carry the sub-clause title. The first edition's introduction names the evolving context of people, technology, organisations, processes and the external environment. The draft text is not public.
Why it matters in a health estate
A sociotechnical view is the corrective to a software-only view. The same application can be safe in one ward and unsafe in another because the workaround, the staffing or the device differs. An incident that is logged as user error is often a design or procurement finding. The theme asks the organisation to treat the work as the unit of analysis, not the code.
What to do now
For each clinical workflow in scope, record the people, the task, the technology, the environment and the organisational constraints. Add the workarounds observed in use, because they are the best evidence of where the design and the work diverge.
The evidence a reviewer will ask for
| Evidence | What it is |
|---|---|
| Workflow record | People, task, technology, environment and organisational constraints for each workflow |
| Workaround log | Observed workarounds, where they occur and what they compensate for |
| Incident reading | Incidents re-read with a sociotechnical lens, not only a code lens |
| Change note | How a change to staffing or environment affects the system's safety case |
What a reviewer will ask
A reviewer will ask where the system is used, by whom, under what constraints. A safety case written from the development environment alone does not answer.
Common gaps
- Incidents are closed as user error with no review of the design or the workflow
- A workaround is known but not recorded, so the risk is carried informally
- The system is assessed in one ward and deployed in another with different staffing
- A staffing change is made with no review of the system's assumptions
Before the draft publishes
Walk one workflow and write the five elements plus the workarounds. The workarounds are the shortest route to the real gaps.
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 clinical leader, the human factors lead and the system owner, because this theme treats people, process and technology as one arrangement.