<?xml version="1.0" encoding="utf-8"?>
<rss version="2.0"
xmlns:dc="http://purl.org/dc/elements/1.1/"
xmlns:slash="http://purl.org/rss/1.0/modules/slash/"
xmlns:wfw="http://wellformedweb.org/CommentAPI/">
<channel>
<title>Techdirt. Stories filed under &quot;hipaa&quot;</title>
<description>Easily digestible tech news...</description>
<link>http://www.techdirt.com/</link>
<language>en-us</language>
<image><title>Techdirt. Stories filed under &quot;hipaa&quot;</title><url>http://www.techdirt.com/images/td-88x31.gif</url><link>http://www.techdirt.com/</link></image>
<item>
<pubDate>Thu, 10 Jan 2013 09:17:55 PST</pubDate>
<title>Police Use HIPAA To Justify Charging Citizen For Recording Them</title>
<dc:creator>Timothy Geigner</dc:creator>
<link>http://www.techdirt.com/articles/20130109/10540821619/ramsey-county-police-use-hipaa-to-justify-charging-citizen-recording-them.shtml</link>
<guid>http://www.techdirt.com/articles/20130109/10540821619/ramsey-county-police-use-hipaa-to-justify-charging-citizen-recording-them.shtml</guid>
<description><![CDATA[ At some point, some national group is going to have to get the memo out to local law enforcement agencies within the United States that it is perfectly legal to record them while they operate in public. We&#39;ve seen <a href="http://www.techdirt.com/articles/20120726/12443919846/one-day-after-dc-police-told-not-to-interfere-with-citizens-recording-them-police-seize-mans-phone.shtml">case</a> after <a href="http://www.techdirt.com/articles/20110929/10325216136/guy-arrested-threatened-with-15-years-recording-traffic-stop-illinois.shtml">case</a> after <a href="http://www.techdirt.com/articles/20110920/07470216024/citizen-recording-police-proves-officer-lied-about-arrest.shtml">case</a> of citizens having their property taken away or being charged with trumped up crimes all because they pointed a recording device at the police. Hell, some states have tried to enact <a href="http://www.techdirt.com/articles/20120302/12363517959/yet-another-court-says-illinois-eavesdropping-law-that-criminalizes-recording-police-is-unconstitutional.shtml">unconstitutional laws</a> to back up their ill-conceived and unwarranted positions.<br />
<br />
All that being said, you just have to hand it to a police force up in Minnesota for the sheer cajones it took to do what they did. It started as other stories have, with a citizen, Andrew Henderson, recording police as they frisked a bloodied man before he was loaded into an ambulance and then having an <a href="http://www.twincities.com/localnews/ci_22333563/little-canada-man-videotaped-sheriffs-deputies-and-got">officer take his recording device away</a>.
<blockquote>
The deputy, Jacqueline Muellner, approached him and snatched the camera from his hand, Henderson said.</blockquote>
<blockquote><i>
"We'll just take this for evidence," Muellner said. Their voices were recorded on Henderson's cellphone as they spoke, and Henderson provided a copy of the audio file to the Pioneer Press. "If I end up on YouTube, I'm gonna be upset."</i></blockquote>
We've seen this kind of thing before, of course. Police use the excuse of evidence collecting to take away recording devices, which is really the only thing they're interested in. It's wrong. We get that. Usually some kind of internal review of the incident is triggered, asses are officially covered, and then the recording device is returned, sometimes after having been wiped. It's a bad enough story as it stands.<br />
<br />
And that scenario is almost exactly what happened here, as the spokesman for Ramsey County acknowledged in a quote that citizens have the right to record police. But everyday abusive practices aren't enough for Ramsey County officers, apparently. The only thing that will satisfy them appears to be a new level of bullshit hitherto unseen, because a week later, when Henderson went to retrieve the camera, the police charged him with disorderly conduct and obstruction, with the citation noting that this was due to a "Data privacy HIPAA violation." In case you aren't clear on this, in the blogging industry, we refer to this as a massive amount of bullshit (piles and piles of it).
<blockquote>
<i>The allegation that his recording of the incident violated HIPAA, or the federal Health Insurance Portability and Accountability Act, is nonsense, said Jennifer Granick, a specialist on privacy issues at Stanford University Law School. The rule deals with how health care providers handle consumers' health information.</i></blockquote>
<blockquote>
<i>"There's nothing in HIPAA that prevents someone who's not subject to HIPAA from taking photographs on the public streets," Granick said. "HIPAA has absolutely nothing to say about that."</i></blockquote>
The kicker? The deputy who had taken the camera for "evidence" purposes erased all the footage. The exchange in which she took that camera was audio recorded by Henderson separately on his cell phone, a recording which he still has. I would suggest that if the police do not immediately rescind their trumped up charges against him, Henderson should insist that we take the deputy at her word, assume she collected the camera and its footage as evidence, and then we can all begin discussing how much prison time the deputy should be doing for destruction of evidence and obstruction of justice.<br />
<br />
That's no more crazy than anything the police have done in this story.<br /><br /><a href="http://www.techdirt.com/articles/20130109/10540821619/ramsey-county-police-use-hipaa-to-justify-charging-citizen-recording-them.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20130109/10540821619/ramsey-county-police-use-hipaa-to-justify-charging-citizen-recording-them.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20130109/10540821619/ramsey-county-police-use-hipaa-to-justify-charging-citizen-recording-them.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>well-that's-just-bullshit</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20130109/10540821619</wfw:commentRss>
</item>
<item>
<pubDate>Thu, 28 Jun 2012 12:37:00 PDT</pubDate>
<title>Protected To Death: How Medical Privacy Laws Helped Kill 25,000 People</title>
<dc:creator>Tim Cushing</dc:creator>
<link>http://www.techdirt.com/articles/20120625/19574119473/protected-to-death-how-medical-privacy-laws-helped-kill-25000-people.shtml</link>
<guid>http://www.techdirt.com/articles/20120625/19574119473/protected-to-death-how-medical-privacy-laws-helped-kill-25000-people.shtml</guid>
<description><![CDATA[ <p>Privacy. Everybody talks about it. Grandstanding politicians make <a href="http://www.techdirt.com/articles/20120606/17382119230/linkedin-passwords-leaked-congress-immediately-wants-to-do-something.shtml" target="_blank">plenty of loud noises</a> in the general direction of the internet, disparaging it for turning your perusal of Kim Kardashian-related articles into <a href="http://www.techdirt.com/articles/20111219/15243117134/court-indicates-facebook-may-be-violating-your-publicity-rights-with-sponsored-stories.shtml" target="_blank">targeted ads</a> for breast enhancement surgery and Kanye West tickets. Of course, while these politicians are making all this noise about your privacy, they're quietly signing off on efforts allowing them to <a href="http://www.techdirt.com/articles/20120619/04401919384/nsa-figuring-out-how-many-us-citizens-we-illegally-spied-would-violate-their-privacy.shtml" target="_blank">sneak in the backdoor</a> and <a href="http://www.techdirt.com/articles/20120206/13143517673/lamar-smith-enemy-internet-defends-internet-snooping-bill.shtml" target="_blank">raid your browser history</a>.
<br /><br />
Putting the government in charge of your privacy has never been a great idea. When HIPAA was enacted, its privacy requirements greatly affected the medical community. Like many regulatory acts, HIPAA both raised costs (additional paperwork and other compliance factors) and lowered quality (negatively affecting retrospective research and curtailing proactive follow up care).
<br /><br />
The true cost of all this additional paperwork, regulation and privacy is now coming to light. Via <a href="http://www.volokh.com/2012/06/23/privacys-death-toll/" target="_blank">The Volokh Conspiracy</a> comes the news that HIPAA's privacy requirements may have hampered research efforts that <a href="http://blogs.law.harvard.edu/infolaw/2012/06/22/death-by-hipaa/" target="_blank">could have prevented an estimated 90,000 unnecessary heart attacks and 25,000 deaths</a>.
<blockquote>
<i>Vioxx, the non-steroidal anti-inflammatory drug once prescribed for arthritis, was on the market for over five years before it was <a href="http://www.nytimes.com/2005/02/15/business/15merck.html">withdrawn</a> from the market in 2004. Though a group of small-scale studies had found a correlation between Vioxx and increased risk of heart attack, the FDA did not have convincing evidence until it completed its own <a href="http://academic.udayton.edu/lawrenceulrich/Vioxx%20Timeline%20WSJ%20082205.htm">analysis</a> of 1.4 million Kaiser Permanente HMO members. By the time Vioxx was pulled, it had caused between <a href="http://www.consumersunion.org/pub/core_health_care/001651.html">88,000 and 139,000</a> unnecessary heart attacks, and <a href="http://www.lewrockwell.com/sardi/sardi53.html">27,000-55,000</a> avoidable deaths.</i>
</blockquote>
Even the government's own regulators were stymied by HIPAA's privacy requirements, as was pointed out by Dr. Richard Platt, a drug risk researcher for the FDA:
<blockquote>
<i>The Vioxx debacle is a haunting illustration of the importance of large-scale data research. If researchers had had access to 7 million longitudinal patient record, a statistically significant relationship between Vioxx and heart attack would have been revealed in under three years. If researchers had had access to <a href="http://www.aei.org/article/social-and-culture/drug-safety-reform-at-the-fda/">100 million</a> longitudinal patient records, the relationship would have been discovered in just three months. Of course, if public health researchers did post-market studies that looked for everything all the time, many of the results that look significant would be the product of random noise. But even if it took six months or one year to become confident in the results from a nation-wide health research database, tens of thousands of deaths may have been averted.</i>
</blockquote>
At least as troubling as the fact that several thousand deaths could have been prevented if HIPAA's restrictions and terms had not been so limiting is the fact that the privacy stipulations were put into place based on a faulty premise and the Dept. of Health and Human Services' misplaced confidence in the erroneous results.
<br /><br />
The premise, as demonstrated by Massachusetts graduate student Latayna Sweeney, was that patient reidentification was possible using only voter registration records and Massachusetts Group Insurance Commission's (GIC) anonymized records. Sweeney was able to reidentify Governor Weld using voter record information, including birth date, name, address, zip code and sex and cross-referencing it with GIC's data. But, as Info/Law points out, Sweeney made a couple of errors, not the least of which was conflating two different terms:
<blockquote>
<i>Latanya Sweeney used census data to estimate that <a href="https://www.insightcommunity.com/wr/about:blank">87%</a> of the population has a unique combination of 5-digit zip code, birthdate, and gender, and implied that the same sort of attack, using voter registration records or other public files. Phillip Golle's replication corrected the figure to <a href="http://www.truststc.org/wise/articles2009/articleM3.pdf">63%</a>, though that's hardly comforting. But these uniqueness statistics are rather misleading. There is an important difference between<b> distinguishability</b> and <b>identifiability</b>. Distinguishability is a necessary condition to conduct the sort of matching attack that Ohm describes, but it is not sufficient. Latanya Sweeney conflated the two when she suggested that a unique individual can be identified by linking the unique combination of attributes to public records-voter registration records, e.g.. But public records are never complete. We know, for example, that a significant portion of the population is not registered to vote. How was Sweeney so sure that there was not another man who shared Gov. Weld's birth date and zip code who was not registered to vote?</i>
</blockquote>
Not only was the data set incomplete, but it was overly simplistic and off by a large margin:
<blockquote>
<i>Daniel Barth-Jones has recently uploaded a <a href="http://papers.ssrn.com/sol3/papers.cfm?abstract_id=2076397">fascinating new article</a> that revisits the famous Gov. Weld reidentification. To start with, Sweeney's estimate of the Cambridge population is way off. There were nearly 100,000 people living in Cambridge at the time of the William Weld attack. This should have been the first hint that Sweeney's methodology was overly simple. She reported a population of 54,000 because that is the number of Cambridge residents who were registered to vote. Sweeney used these records as if they described the entire population.</i>
</blockquote><blockquote>
<i>By comparing Sweeney's count of Cambridge voter registrants with U.S. Census records, Barth-Jones confirmed that many voting-age adults in Cambridge (about 35%) were not registered to vote. In William Weld's case, the census data show that approximately 174 men living in Weld's zip code were Weld's age. We don't know their precise birth dates, but we can calculate that the chance another man living in Weld's zip code shared his birthdate was about 35%. This is quite important all on its own to illustrate the difference between identifiability and distinguishability. Most of those 174 men had a unique combination of birth date, gender, and zip code, but each one of them was quite likely-35% likely-to be non-unique.</i>
<br /><br />
<i>Sweeney presumably used the voter registration records to rule out the possibility that some of these 174 Cambridge men shared Gov. Weld's birth date. But even if Sweeney did indeed confirm that no other registered voter shared Weld's gender, zip, and birth date, she could not have been sure about the 50 or so Cambridge residents who were Weld's age and were not registered to vote. Thus, at best, Weld's chance of having a unique birth date, zip code, and gender combination is 87%. Put differently, the chance that Latanya Sweeney's matching attack would have been wrong using these three variables alone was 13%- much worse than traditional 5% statistical confidence.</i>
</blockquote>
Despite these erroneous assumptions based on incomplete data, the Dept. of Health and Human Services stated the study had shown that "97 percent of the individuals in Cambridge whose data appeared in a database which contained only their nine digit ZIP code and birth date could be identified with certainty." This completely ignores the fact that over a third of the population wouldn't even show up on the list.
<br /><br />
But bad data and faulty research have never stopped governmental "progress." The threat of reidentification is low and any attacks remain purely speculative. But while bad regulations have a tendency to be able to weather even the toughest criticism without making the slightest concessions, HIPAA has one thing most bad regulations don't, as Info/Law points out: "a body count."</p><br /><br /><a href="http://www.techdirt.com/articles/20120625/19574119473/protected-to-death-how-medical-privacy-laws-helped-kill-25000-people.shtml">Permalink</a> | <a href="http://www.techdirt.com/articles/20120625/19574119473/protected-to-death-how-medical-privacy-laws-helped-kill-25000-people.shtml#comments">Comments</a> | <a href="http://www.techdirt.com/articles/20120625/19574119473/protected-to-death-how-medical-privacy-laws-helped-kill-25000-people.shtml?op=sharethis">Email This Story</a><br />
 ]]></description>
<slash:department>still-feeling-safe?</slash:department>
<wfw:commentRss>http://www.techdirt.com/comment_rss.php?sid=20120625/19574119473</wfw:commentRss>
</item>
</channel>
</rss>