DataBreaches.Net

Menu
  • About
  • Breach Notification Laws
  • Privacy Policy
  • Transparency Report
Menu

Privacy and use of newborns’ blood samples

Posted on April 15, 2011 by Dissent

Over on Privacy Lives, Melissa Ngo blogs about an issue I’ve discussed a number of times on this blog:  the collection, storage, and use/misuse of newborns’ blood samples.  Melissa points us to a discussion on Minnesota Public Radio:

… On Tuesday, parents, doctors and researchers urged state lawmakers to reject proposed restrictions on Minnesota’s Newborn Screening program — changes that could keep other parents from such lifesaving results.

Amendments in two Senate bills would require the Minnesota Department of Health to promptly destroy the blood samples that are collected from newborns to identify rare medical disorders that aren’t obvious at birth.

“Our genetic information is ours … until there is consent for the use of our genetic information, no research should happen.”

Currently, the agency stores the blood samples indefinitely so they can be used for quality control tests or disease research. The new rules would allow parents to give their written permission to store the material up to a maximum of two years.

Read more on MPR.  It’s probably one of the more balanced discussions of the issue that I’ve seen in a while.

Some of the issue comes down to transparency and consent.  Why is so that very hard for governments and researchers to embrace?   That if you explain what you want to do, explain how it will benefit the individual or others, and then ask for consent, many will consent?  It’s always seemed to me that government simply doesn’t trust its own citizenry and takes a “we know best” attitude that justifies them riding roughshod over crucial consent and ethical issues.

Related posts:

  • The Havasupai Indians, Genetic Research and the Problem of Informed Consent
  • Article: Relative Futility: Limits to Genetic Privacy Protection Because of the Inability to Prevent Disclosure of Genetic Information by Relatives
Category: Uncategorized

Post navigation

← Hundreds of College and Government websites still redirecting to fake stores
IN: Credit card scam hits local eatery →

4 thoughts on “Privacy and use of newborns’ blood samples”

  1. Anonymous says:
    April 18, 2011 at 11:15 am

    The issue is that it’s axiomatic in public health research that when consent is required, some percentage of individuals will opt out and then you no longer have a complete sample set, so there is the risk of statistical bias in the results. In other words, the results will not truly reflect the underlying pattern being studied. This is a serious problem since it affects the reliability of the research.

    1. Anonymous says:
      April 18, 2011 at 11:23 am

      As someone who taught research design and data analysis for a decade, I’m aware of the issue/concerns. The concern, however, does not justify ignoring a patient’s right to control who has access to their information – particularly when there have been outrageous failures in protecting both the privacy and security of such data.

      I think we also need to examine the subset of those who would not opt-in to see if they’re randomly distributed or if there really would be some selection bias or factor that could confound interpretation of available data. If their main reason for not opting in is data security or privacy, is it because they have some unusual or stigmatizing condition that they are worried about or is it more randomly distributed across all conditions, etc. If the latter, then the argument against respecting patient privacy rights falls by the wayside.

      1. Anonymous says:
        April 18, 2011 at 11:38 am

        then presumably you are familiar with the Common Rule.

        1. Anonymous says:
          April 18, 2011 at 9:36 pm

          Yes. And that it applies to federal agencies. This is a state-level issue, is it not?

Comments are closed.

Now more than ever

"Stand with Ukraine:" above raised hands. The illustration is in blue and yellow, the colors of Ukraine's flag.

Search

Browse by Categories

Recent Posts

  • Breaches have consequences (sometimes)
  • Kansas City Man Pleads Guilty for Hacking a Non-Profit
  • British national “IntelBroker” charged with causing $25 million in damages; U.S. seeks his extradition from France
  • France issues press statement about arrest of ShinyHunters members
  • Patients Allege Home Delivery Pharmacy Failed to Timely Notify Them of Data Breach
  • Hackers breach Norwegian dam, open valve at full capacity
  • Patient death at London hospital linked to cyber attack on NHS
  • ShinyHunters and team members arrested in France (2)
  • Texas Enacts Liability Shield From Punitive Damages for Certain Small Businesses That Adopt Cybersecurity Programs
  • Dublin ETB fined €125,000 for data protection breaches

No, You Can’t Buy a Post or an Interview

This site does not accept sponsored posts or link-back arrangements. Inquiries about either are ignored.

And despite what some trolls may try to claim: DataBreaches has never accepted even one dime to interview or report on anyone. Nor will DataBreaches ever pay anyone for data or to interview them.

Want to Get Our RSS Feed?

Grab it here:

https://databreaches.net/feed/

RSS Recent Posts on PogoWasRight.org

  • How Internet of Things devices affect your privacy – even when they’re not yours
  • Sky Views Personal Data as a Potential Weapon in IPTV Piracy War
  • Florida Used a Nationwide Surveillance Camera Network 250 Times To Aid in Immigration Arrests
  • Federal Court Strikes Down HIPAA Reproductive Health Care Privacy Rule
  • The Markup caught 4 more states sharing personal health data with Big Tech
  • Privacy in the Big Sky State: Montana’s Consumer Privacy Law Gets Amended
  • UK Passes Data Use and Access Regulation Bill

Have a News Tip?

Email: Tips[at]DataBreaches.net

Signal: +1 516-776-7756

Contact Me

Email: info[at]databreaches.net

Mastodon: Infosec.Exchange/@PogoWasRight

Signal: +1 516-776-7756

DMCA Concern: dmca[at]databreaches.net
© 2009 – 2025 DataBreaches.net and DataBreaches LLC. All rights reserved.