<html><head></head><body style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div apple-content-edited="true"><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><span class="Apple-style-span" style="border-collapse: separate; color: rgb(0, 0, 0); font-family: Helvetica; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-align: -webkit-auto; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; -webkit-border-horizontal-spacing: 0px; -webkit-border-vertical-spacing: 0px; -webkit-text-decorations-in-effect: none; -webkit-text-size-adjust: auto; -webkit-text-stroke-width: 0px; font-size: medium; "><div style="word-wrap: break-word; -webkit-nbsp-mode: space; -webkit-line-break: after-white-space; "><div>On Oct 5, 2013, at 8:37 PM, Richard Fontana wrote:</div></div></span></div></span></span></div><div><blockquote type="cite"><div><br>On Sat, 5 Oct 2013 11:58:36 -0700<br>Howard Look <<a href="mailto:howard@tidepool.org">howard@tidepool.org</a>> wrote:<br><br><blockquote type="cite">“Open” as applied to Health Data will have the meaning ascribed to<br></blockquote><blockquote type="cite">such term by the Open Definition promulgated at <a href="http://opendefinition.org">opendefinition.org</a>,<br></blockquote><blockquote type="cite">version 1.1 and any later version; <br></blockquote><br>What if a future version of the Open Definition conflicts with the<br>current version? (Should "and any" be "or any"?)<br></div></blockquote><div><br></div>Great point, thanks. I think you are right and it should be "or any."</div><div><br></div><div><blockquote type="cite"><div><blockquote type="cite">For avoidance of doubt, as applied to Health Data under this license,<br></blockquote><blockquote type="cite">“Open” means that in the event you apply any encryption or<br></blockquote><blockquote type="cite">obfuscation to the Health Data using the Software, you must provide<br></blockquote><blockquote type="cite">the Data Owner with any encryption keys or other suitable means, free<br></blockquote><blockquote type="cite">of charge, to access such Health Data, in a manner sufficient to<br></blockquote><blockquote type="cite">allow a Data Owner with ordinary skill and knowledge to extract and<br></blockquote><blockquote type="cite">store the Health Data in a non-proprietary format, in both<br></blockquote><blockquote type="cite">human-readable and machine-accessible forms.<br></blockquote><br>A comment on the end of this sentence: You say in your FAQ:<br><br> Q: Is it good enough to provide access to a downloadable CSV or excel<br> file?<br><br> No, that's not good enough. You need to provide a mechanism for<br> another application to automatically access the data, such as through<br> a published API. This is what we mean by "machine-accessible."<br><br>Perhaps you should define "machine-accessible" in the license as I am<br>not sure it would be obvious that, say, a CSV file would not satisfy<br>the requirement.<br></div></blockquote><div><br></div>Yes, we struggled with this. We were trying to avoid including specific</div><div>technology. In today's terms, we want to say something like "just giving</div><div>access to downloading a CSV or PDF of the data is not good enough;</div><div>you need to provide RESTful API access to the data."</div><div><br></div><div>I would love suggestions anyone had for license language that achieve this but</div><div>that don't refer to specific machine-accessibility techniques.</div><div><br></div><div><blockquote type="cite"><div><br><blockquote type="cite">(C) Open Health Data. You must ensure that the Health Data remains<br></blockquote><blockquote type="cite">Open to its Data Owner for a period of three years after the Health<br></blockquote><blockquote type="cite">Data is first generated. <br></blockquote><br>Am I correct that, under this license 3(C) is meant to be triggered even<br>if the user is engaged in purely internal or private use of the<br>software? (Perhaps this is not a usage you contemplate for the<br>software you intend to release, but I think it is a key issue to be<br>considered.)<br></div></blockquote><div><br></div><div>Excellent question. I think that if a clinic or hospital adapted</div><div>our code for use with their patients, then we would expect that they would</div><div>make the data collected available to patients, even if it was a completely</div><div>private institution.</div><div><br></div><div>We also discussed the case of "purely internal" for example if a research</div><div>institution was doing a study using our platform. We decided that it</div><div>was important to us that even in this case that data be made available</div><div>to the patient if they so desired.</div><div><br></div><div>Please let us know if you are envisioning something else in the way</div><div>of "private use" pr "purely internal."</div><div><br></div><div>Thank again! We really appreciate your thoughtfulness. This will definitely</div><div>help us make sure we get this right.</div><div><br></div><div>Cheers,</div><div>Howard</div><div><br></div><br><blockquote type="cite"><div><br>- RF<br><br></div></blockquote></div><br></body></html>