Update documentation to make guidance around data clearer #1351
Conversation
This file contains bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
…nsitive data are.
…sensitive data are. Also add in caution about using wildcards.
…is aggregated patient data
Deploying with
|
| Latest commit: |
f14f29c
|
| Status: | ✅ Deploy successful! |
| Preview URL: | https://e90e2a7d.opensafely-docs.pages.dev |
| Branch Preview URL: | https://update-documentation-to-make.opensafely-docs.pages.dev |
bloodearnest
reviewed
Nov 1, 2023
docs/actions-scripts.md
Outdated
| * allow a thorough review of the outputs in a reasonable time | ||
|
|
||
| **Files with `patient_id` in the header** | ||
|
|
||
| Any CSV file with a `patient_id` header will not be moved to Level 4 |
There was a problem hiding this comment.
"not be made available in level 4"?
alexwalkerepi
approved these changes
Nov 1, 2023
acagreen17
deleted the
update-documentation-to-make-guidance-around-data-clearer
branch
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Updates to docs to make it clearer what data is allowed on L3/L4 and what we mean by aggregated patient data. The following files have been amended: