From f82cf27abf1a0073e1c3dc8d6877c0b6e5715905 Mon Sep 17 00:00:00 2001 From: Seb Bacon Date: Fri, 4 Sep 2026 10:30:08 +0100 Subject: [PATCH] Add developer access examples --- docs/data-access-policy.md | 7 +++++++ 1 file changed, 7 insertions(+) diff --git a/docs/data-access-policy.md b/docs/data-access-policy.md index 2ba7cb33c..7ba6a9404 100644 --- a/docs/data-access-policy.md +++ b/docs/data-access-policy.md @@ -242,6 +242,13 @@ Access to backend systems is via secure, authenticated, encrypted channels. This * intermediate outputs (study dataset) ([level 3 data](security-levels.md#level-3-nhs-england-are-data-controllers-of-the-data)) * unchecked, unreleased aggregated study outputs ([level 4 data](security-levels.md#level-4-nhs-england-are-data-controllers-of-the-data)). +Examples of development and maintenance activities include: + +* viewing and searching application, job, container and system logs +* inspecting intermediate outputs to investigate suspected software or data issues +* running application management commands for operational support +* testing performance and integrity against production-scale data within the secure environment + This policy does not allow the extraction of pseudonymised patient data or study outputs from the system via this process; the data can only be studied within the system itself. Some operational data may be released under controlled conditions, as detailed in a separate Operational Data Policy.