first bits of security content added #8
Conversation
|
bump @seankross 🙏🏽 |
| ### Examples | ||
|
|
||
| We strongly encourage all exported, user-facing functions, to have examples. However, when PII/PHI data is a crucial part of an example for a function/class/etc. we need to take extra precautions. |
There was a problem hiding this comment.
I don't think that anything in the WILDS would have PII/PHI data. If data is de-identified, it's not considered to be PHI.
I am not sure how I am going to do data-as-a-product on the CARDS platform and if would be possible/advisable to create R packages that someone live just on there. I think that is the only time that we would have PHI in an R package though.
There was a problem hiding this comment.
Okay, thanks very much @monicagerber ! Do you think we just remove this comment about PII/PHI data in examples?
There was a problem hiding this comment.
Definitely nothing in WILDS should contain PII/PHI in the package itself, but I imagine several WILDS packages will touch/transmit PII/PHI.
| ## Data | ||
|
|
||
| Software created in the WILDS may touch PII/PHI data. |
There was a problem hiding this comment.
I think that instead of writing sensitive data handling practices here we should link to the sciwiki or something.
There was a problem hiding this comment.
Okay. Are you thinking we just remove this chapter? Or keep the chapter but simply link out to sciwiki/other resources with very little text in the chapter itself?
There was a problem hiding this comment.
I think we should keep it and link out. The we could have sections like "how to securely integrate [a WILDS thing] with [a service discussed on sciwiki]"
|
This chapter is on hold for now ... |
Any thoughts on the first bits of content for the security chapter?
This is a bit different from the other chapters in that i imagine we want to think harder about this chapter given where we work.
There's some half finished thoughts on purpose in here for your feedback. thanks!
We're only building the book for congtent on
main, but you can pull this repo down, then runmake preview#6