Skip to content
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.

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

Update releasing-files.md #433

Draft
wants to merge 6 commits into
base: main
Choose a base branch
from
Draft

Update releasing-files.md #433

wants to merge 6 commits into from

Conversation

amirmehrkar
Copy link
Contributor

Addition of information to clarify with who data released from Level 4 can be shared and to reinforce researchers must obtain publication (aka exit approval) for studies from NHS England and how to obtain this.

Addition of information to clarify with who data released from Level 4 can be shared and to reinforce researchers must obtain publication (aka exit approval) for studies from NHS England and how to obtain this.
@cloudflare-workers-and-pages
Copy link

cloudflare-workers-and-pages bot commented Sep 30, 2021

Deploying with  Cloudflare Pages  Cloudflare Pages

Latest commit: 76cc008
Status: ✅  Deploy successful!
Preview URL: https://ecf27d37.opensafely-docs.pages.dev

View logs


### Study GitHub repository

Similarly, **the study repository must be kept private until project completion and NHS England approval has been obtained**; however, the OpenSAFELY Oversight Board has recommended that all study GitHub repositories (to include the study definition code, codelists and released results) be make public 12 months after any code has been executed against the underlying patient data.
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This isn't quite right, if the repository doesn't contain any outputs - right?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

yes but for now we have this dual process where it might have outputs (as we havent fully moved to jobserver output process). Once we have we we can change this/ remove this. I thought after we discussed we were covering ourselves for this issue for now.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

needs to marry up with point 7 on latest Data Access Agreement want to send out too https://docs.google.com/document/d/1Kf8vL1Gy8t_AJgTTOcPtwl1vlBNQSCu855Bd4JUoL9I/edit so if we change this (which is fine), need to update the DAA too.

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Please HOLD OFF on this commit

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

We may have another solution that need to work up and discuss with Ben and Seb Tuesday

@StevenMaude StevenMaude marked this pull request as draft November 3, 2021 15:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants