<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
	xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>Gavin Baker &#187; Privacy</title>
	<atom:link href="http://www.gavinbaker.com/category/privacy/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.gavinbaker.com</link>
	<description>A Journal of Insignificant Inquiry</description>
	<lastBuildDate>Fri, 28 Oct 2011 14:56:26 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Openness to protect human subjects in research</title>
		<link>http://www.gavinbaker.com/2011/10/27/openness-to-protect-human-subjects-in-research/</link>
		<comments>http://www.gavinbaker.com/2011/10/27/openness-to-protect-human-subjects-in-research/#comments</comments>
		<pubDate>Thu, 27 Oct 2011 19:33:39 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Open access]]></category>
		<category><![CDATA[Open government]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Science]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/?p=395</guid>
		<description><![CDATA[The Department of Health and Human Services recently published a proposal to update the federal regulations that govern research on human subjects. It&#8217;s a very interesting proposal with a lot of potential changes on the table, and has received more &#8230; <a href="http://www.gavinbaker.com/2011/10/27/openness-to-protect-human-subjects-in-research/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p>The Department of Health and Human Services recently published a <a href="http://federalregister.gov/a/2011-18792">proposal to update the federal regulations that govern research on human subjects</a>. It&#8217;s a very interesting proposal with a lot of potential changes on the table, and has received more than 1,000 comments (rare for this sort of thing). Yesterday, I submitted comments on the proposal. Unfortunately, I had to deal with a personal matter just as the comments were due, so they&#8217;re less detailed and less polished than I would have liked. The comments are below: <ins datetime="2011-10-28T14:55:16+00:00">(Update: my comments are <a href="http://www.regulations.gov/#!documentDetail;D=HHS-OPHS-2011-0005-1089">now available on Regulations.gov</a> as well.)</ins></p>
<blockquote><p>I welcome the opportunity to comment on the Department of Health and Human Services&#8217; (HHS) advance notice of proposed rulemaking (ANPRM) on human subjects research protections. Modernizing federal regulations to better protect human subjects could advance science and bolster public trust in the research system, strengthening the economy and improving health while upholding human rights.</p>
<p>I submit these comments in my personal capacity, representing solely my own opinion. However, my background may inform the reading of these comments. I have participated in research as a human subject, including survey research as well as greater-than-minimal risk research. Professionally, I research government transparency, including topics such as scientific integrity, focusing on the role of information in improving lives and increasing democratic accountability. Previously, my work focused on public access to scientific information. In addition, I am a graduate student in the School of Library and Information Studies at Florida State University, studying information seeking and use. </p>
<p>In my opinion, several of the information management reforms proposed in the ANPRM could enhance the protection of human subjects and increase public trust in the research system. These changes could benefit the research system by aiding in the recruitment of human subjects. In addition, HHS should consider other reforms not specifically proposed in the ANPRM.</p>
<p>I recommend that HHS consider amending the federal rules on human subjects protection to:</p>
<ol>
<li>Respect and enhance scientific openness;</li>
<li>Empower research participants and their communities;</li>
<li>Minimize and mitigate information risks; and</li>
<li>Collect the data necessary for system oversight.</li>
</ol>
<p><strong><em>1. Human subjects research protections should respect and enhance scientific openness</em></strong></p>
<p>Openness is a fundamental characteristic of science, and human subjects research protections should respect and enhance scientific openness. I applaud HHS&#8217; consideration of increasing the reuse of existing data and biospecimens (see Question 23). HHS should seek ways to expand appropriate sharing of data and biospecimens, while mitigating information risks to such sharing (see #3).</p>
<p>Openness can strengthen human subjects protections in other ways as well. Articles 20 and 21 of the <a href="http://www.wma.net/en/30publications/10policies/b3/index.html">Helsinki Declaration</a> prohibits the repetition of a study where the outcome is already known, to avoid exposing human subjects to unnecessary risk. As a result, prompt and widespread communication of results is necessary to ensure human subjects are protected, along with sharing and reuse of data and biospecimens. To avoid unnecessarily exposing human subjects to the risks of research, HHS should ensure that the results of human subjects research are rapidly and effectively disseminated to the research community, such as under the <a href="http://publicaccess.nih.gov/policy.htm">National Institutes of Health (NIH) Public Access Policy</a>.</p>
<p><em><strong>2. Human subjects research protections should empower research participants and their communities</strong></em></p>
<p>Although human subjects protection is the responsibility of the research and oversight community rather than of the subject, federal regulations should empower subjects to protect themselves to the greatest extent possible. HHS&#8217; consideration of mechanisms to improve informed consent is particularly important in this regard (see Questions 35-53). HHS may also wish to consider readability and comprehension testing to improve consent forms. HHS should also ensure that subjects and potential subjects are informed of potential risks through public access to the proposed database of adverse events reporting (see Question 69).</p>
<p>With regard to the extension of federal regulations to some non-Federally funded research (Question 71), without prejudice to the resolution of the overall question, it is important that subjects and potential subjects be informed of the protections applicable to the context. HHS should require studies to inform subjects whether or not the federal human subjects research protections apply to the study, with a brief description of said protections and a reference to an easy-to-understand website with additional information.</p>
<p>Because the goal of human subjects research is ultimately to improve health, it is important that human subjects research protections leverage opportunities to do so, both for the subjects specifically and for their communities. Access to information is a key method for doing so. For instance, results should be returned to research participants whenever possible, including publications describing overall results of the study (see Question 18). Public access to research results (see #1) and to trial information (see #4) also would advance this aim.</p>
<p><em><strong>3. Human subjects research protections should minimize and mitigate information risks</strong></em></p>
<p>The adequate protection of research participants&#8217; privacy is critical to the functioning of the research system and an important factor in the successful recruitment of human subjects. To prevent the damage that data breaches could wreak on the research system, human subjects research protections should ensure proper data security, such as by establishing mandatory standards for data security as proposed in the ANPRM. In addition, promptly notifying individuals of data breaches, as proposed in the ANPRM, is important to mitigate the impact of any security failures.</p>
<p>However, while it may be necessary to reexamine the role of institutional review boards (IRBs) in ensuring data security, HHS should be hesitant to eliminate such a role altogether. Through their approval and oversight, IRBs are the institutional guarantors of human subjects protection, and HHS should be cautious to remove vital aspects of that protection from the boards&#8217; purview. HHS should carefully consider the most effective role of IRBs in ensuring data security: for instance, whether inspector certification of compliance and retrospective IRB audits would ensure protection.</p>
<p><em><strong>4. Human subjects research protections should collect the data necessary for system oversight</strong></em></p>
<p>The ANPRM correctly identifies the need for effective data collection and information management in conducting oversight of human subjects research protections. However, HHS should consider expanding required reporting where necessary, in addition to streamlining existing reporting requirements. </p>
<p>For instance, with regard to Question 70 re: ClinicalTrials.gov, the <a href="http://bioethics.gov/cms/sites/default/files/ResearchAcrossBorders.pdf">recent report</a> of International Research Panel of the Presidential Commission for the Study of Bioethical Issues identifies needed improvements to trial registration and reporting, including increased reporting and public access to information. </p>
<p>In another example where increased reporting and transparency could strengthen oversight, <a href="http://dx.doi.org/10.1001/jama.2010.1492">Menikoff in 2010</a> proposed that investigators should disclose their consent forms. Such disclosure, the author argued, would ultimately improve the quality of consent forms, in addition to allowing potential subjects to more easily locate appropriate trials.</p>
<p>Sincerely,</p>
<p>Gavin Baker</p></blockquote>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2011/10/27/openness-to-protect-human-subjects-in-research/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Nitpicking the Google Books Settlement 2.0</title>
		<link>http://www.gavinbaker.com/2009/11/18/nitpicking-the-google-books-settlement-20/</link>
		<comments>http://www.gavinbaker.com/2009/11/18/nitpicking-the-google-books-settlement-20/#comments</comments>
		<pubDate>Wed, 18 Nov 2009 18:38:27 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Copyright]]></category>
		<category><![CDATA[Creative Commons]]></category>
		<category><![CDATA[DRM]]></category>
		<category><![CDATA[Privacy]]></category>
		<category><![CDATA[Publishing]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/?p=342</guid>
		<description><![CDATA[I previously posted on the Google Books Settlement, avoiding the well-trod ground and focusing on points that were salient but hadn&#8217;t received much discussion. Now that there&#8217;s a new draft of the proposed settlement, I&#8217;ll do the same: The revised &#8230; <a href="http://www.gavinbaker.com/2009/11/18/nitpicking-the-google-books-settlement-20/">Continue reading <span class="meta-nav">&#8594;</span></a>]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.gavinbaker.com/2009/09/a-few-thoughts-on-the-google-books-settlement/" title="A few thoughts on the Google Books Settlement">I previously posted</a> on the <a href="http://www.googlebooksettlement.com/">Google Books Settlement</a>, avoiding the well-trod ground and focusing on points that were salient but hadn&#8217;t received much discussion. Now that there&#8217;s a new draft of the proposed settlement, I&#8217;ll do the same:</p>
<ul>
<li>The revised settlement cuts out a huge swath of international works. There&#8217;s no legal reason for this, since the settlement is based in U.S. law, which treats works equally regardless of where they were published. (Moreover, the settlement only provides access to users in the U.S.) Yet I haven&#8217;t seen one public interest advocate criticize the loss to access that will be the result of this change.</li>
<li>The discussion of this change has mostly been summarized as &#8220;foreign language works are now excluded&#8221;. But that&#8217;s a misleading oversimplification. The new settlement includes works published in the U.S., UK, Canada, or Australia, or registered with the U.S. Copyright Office. That will certainly include many non-English works (remember Canada is bilingual?). It will also <em>exclude</em> many English works: consider New Zealand, Jamaica, India, or many other English-speaking countries.</li>
<li>
<p>Much criticism has focused on the question of orphan works. This is a bit baffling to me. The settlement would provide an unprecedented access to orphan works. Indeed, to me this is the biggest <em>benefit</em> of the settlement.</p>
<p>The main criticism of this is that Google would be the <em>only</em> provider of access to these orphan works. Monopoly access is certainly undesirable (particularly given the other flaws of the settlement: the privacy weaknesses, the DRM, the single interface, the overall market position of Google, etc.). But isn&#8217;t monopoly access (with antitrust scrutiny) better than no access?</p>
<p>The only way the answer is &#8220;no&#8221; is if the settlement holds back progress toward non-monopoly access. For instance, a settlement clause that guaranteed Google competitors the same terms (even if they had to do the scanning themselves) would open competition. Obviously, Google is not interested in such an approach, and since the settlement is a negotiation between Google and the plaintiffs (who I would guess to be agnostic on that question), we shouldn&#8217;t expect to see those terms unless the judge or the Department of Justice forces them.</p>
<p>A legislative solution, such as proposed by the Copyright Office, would be an improvement as well. But orphan works reform has so far stalled in Congress, and I haven&#8217;t seen any indication it will be a priority for the current Judiciary Committee. For its part, Google says it will still support orphan works reform if the settlement is approved.</p>
<p>I&#8217;m not sure how to predict what the effect of the settlement would be on the prospects for legislative action. One the one hand, Congress might say, &#8220;It looks like Google has solved that problem, so we don&#8217;t have to do anything.&#8221; Alternatively, Congress might say, &#8220;That Google settlement seems to have riled a lot of people up; I&#8217;d rather not put my stick in that antpile.&#8221; On the other hand, the settlement might give greater impetus to Google&#8217;s competitors to tell Congress, &#8220;We&#8217;re on unequal terms now; we need you to pass orphan works reform to level the playing field.&#8221; No matter what happens, I don&#8217;t expect this Congress to pass orphan works reform. How long are we willing to wait?</p>
</li>
<li>Speaking of orphan works, the Unclaimed Works Fiduciary is a trustee with one hand tied. <a href="http://www.earlham.edu/~peters/fos/2009/11/revised-google-book-settlement-what-it.html">As I reported for <cite>OAN</cite></a>, the UWF &#8212; an independent agent entrusted to manage the works of rightsholders who haven&#8217;t claimed their works under the settlement &#8212; doesn&#8217;t have all the powers of an actual rightsholder. Whereas a rightsholder is guaranteed under the settlement the options to, e.g., set a zero price for her work, to apply a <a href="http://creativecommons.org/">Creative Commons</a> license, or to remove DRM, the UWF isn&#8217;t guaranteed those same options. In fact, the UWF can only exercise those options with the approval of the Book Rights Registry, which is run by publisher and author representatives. So if the UWF came to the conclusion that the best fiduciary interest of its absentee rightsholders was represented by making their works freely available, it would not necessarily be able to do so. Given the growing suggestions that making a book freely available often has no discernible negative consequence on sales revenues for that book, and in some cases may even increase sales, the settlement should not exclude that option.</li>
</ul>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2009/11/18/nitpicking-the-google-books-settlement-20/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Great campaign on privacy and surveillance</title>
		<link>http://www.gavinbaker.com/2008/03/20/great-campaign-on-privacy-and-surveillance/</link>
		<comments>http://www.gavinbaker.com/2008/03/20/great-campaign-on-privacy-and-surveillance/#comments</comments>
		<pubDate>Thu, 20 Mar 2008 21:35:23 +0000</pubDate>
		<dc:creator>Gavin Baker</dc:creator>
				<category><![CDATA[Privacy]]></category>

		<guid isPermaLink="false">http://www.gavinbaker.com/2008/03/20/great-campaign-on-privacy-and-surveillance/</guid>
		<description><![CDATA[The ACLU has a great message for its campaign on privacy and surveillance. I think it captures the way a lot of us feel about recent trends, and expresses the big-picture consequences.]]></description>
			<content:encoded><![CDATA[<p>The ACLU has a great message for its <a href="http://www.aclu.org/clock">campaign on privacy and surveillance</a>. I think it captures the way a lot of us feel about recent trends, and expresses the big-picture consequences.</p>
<div style="text-align: center"><a href="http://www.aclu.org/clock"><br />
<img src="http://www.aclu.org/images/buttons/surv_clock_content.gif" alt="Surveillance society: 23:55" style="border: none"><br />
</a></div>
]]></content:encoded>
			<wfw:commentRss>http://www.gavinbaker.com/2008/03/20/great-campaign-on-privacy-and-surveillance/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

