Re:Open-source HIPAA compliance company policies
by brechmos on Wednesday October 15, 2014 @04:04PM
(#8461359)
I too would love to be able to use the verbiage as a base for my extremely small (me) company that does deal with some PHI. I have no desire to sell your documents but in reading through the license it does appear that I can't use it. Any chance that you could re-license it so that I/we can use it within a commercial (small!?) venture?? :-) Please? I am happy to attribute or not attribute Catalyze. Either way, thanks for releasing these.
Re:Open-source HIPAA compliance company policies
by markolschesky on Wednesday October 15, 2014 @04:09PM
(#8461391)
We're going to re-license and release these with CC BY-SA 4.0. Just updated the github repo. Let us know if you need any help!
Re:Open-source HIPAA compliance company policies
by brechmos on Wednesday October 15, 2014 @04:13PM
(#8461423)
Oh, wow, you guys are awesome. Thank you so much for doing this. About a year ago I went through websites to try and figure out what all this HIPPAA means for my website but it is very confusing. It is great to have a template to at least start with. Thank you!!!
Re:Open-source HIPAA compliance company policies
by dublinben on Wednesday October 15, 2014 @04:35PM
(#8461541)
You might want to update your language that forbids commercial use.
Re:Open-source HIPAA compliance company policies
by markolschesky on Wednesday October 15, 2014 @04:48PM
(#8461608)
Just did. Thank you!
Re:Open-source HIPAA compliance company policies
by Titanous on Wednesday October 15, 2014 @04:13PM
(#8461421)
Awesome, thanks! Don't forget the gh-pages branch.
Re:Open-source HIPAA compliance company policies
by markolschesky on Wednesday October 15, 2014 @04:29PM
(#8461508)
Just updated that too. Should be BY-SA 4.0 across the board now. Thanks!
Re:Open-source HIPAA compliance company policies
by danielsiders on Wednesday October 15, 2014 @04:15PM
(#8461436)
Awesome!
Re:Open-source HIPAA compliance company policies
by danielsiders on Wednesday October 15, 2014 @03:55PM
(#8461297)
From the CC license: "NonCommercial means not primarily intended for or directed towards commercial advantage or monetary compensation."
I'm definitely not a lawyer and would like to hear from one interpreting the license for this use case, but it sounds like that could be interpreted to mean not okay to use for a business if it generated a commercial advantage, like HIPAA compliance.
Clarification from your lawyer (published on your site) would be good if you aren't okay switching to a more permissive license.
Suggestion: name them "FREE HIPAA DOCS AVAILABLE AT [URL]" and use a license requiring attribution, should make them hard to resell?
Re:Open-source HIPAA compliance company policies
by superuser2 on Wednesday October 15, 2014 @03:56PM
(#8461302)
I think you are looking for ShareAlike - i.e., that you can modify the content but must redistribute under the same license.
Re:Open-source HIPAA compliance company policies
by laurenstill on Thursday October 16, 2014 @02:36PM
(#8466536)
Said it before, say it again, thank you Mark. I wonder what our industry would look like if we spent less time reinventing the wheel all day long and more time working on the problems we love.
EDIT: Yeah, it seems like there are some far reaching not-understood legal implications of the "NC" license. Ok, we're going to re-commit and re-issue these with the BY-SA. Should be up in a few minutes.