Skip to content

Add examples of developer access activities #2052

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
sebbacon wants to merge 1 commit into
base: main
Choose a base branch
from
+7 −0
Open

Add examples of developer access activities #2052

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
7 changes: 7 additions & 0 deletions docs/data-access-policy.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.

Expand Down