It’s official: The California Department of Public Health wants practicing physicians (many of them prehistorically, sorry, traditionally trained) to be the patres familias in issues between personal genetic test takers and direct-to-consumer personal genetic testing start-ups while declining the test takers’ right to get familiar with their own genetic makeup and risks by their own.
Calif. cracks down on 13 genetic testing startups
California health regulators have demanded that 13 direct-to-consumer genetic testing startups halt sales in the state until they prove they meet state standards. All the companies have two weeks to demonstrate to regulators that their laboratories are certified by the state and federal governments, said department spokeswoman Lea Brooks. The startups also must show the tests they are selling California residents have been ordered by a doctor as required by state law.
I give you trusted links instead of complicating your day with my own opinion:
California challenges genetic testing firms’ claims
Attention, California Health Dept.: My DNA Is My Data
Regulators, Genetic Testing Companies Begin Face Off
Deep, healthy lifespan extension 
Here’s an interesting post from someone who seems to be behind this legislative push. Kudos to Steve for his openness, because he gets his ass handed to him by the commenters.
Thx, very interesting thread.
Stephe Murphy says:
“As I sit in the Union League, preparing for the ICOB meeting at the Coriell Personalized Medicine Collaborative……I have now seen the arrogance with which these companies were launched. Your arrogance and sneering down the nose at physicians is precisely why you WILL be regulated.
I am deeply saddened that you think so little of people who have a doctorate degree in something that you do not have.
“23andME and these other *dedicated* services do a much better job of explaining genetics – especially on a genomic scale – to people than doctors, who are only really comfortable prescribing antibiotics.”
Ouch….this is obviously why you feel the way you do. You would have no idea what a physician is comfortable doing. I am not saying they are perfect, but they are easier to educate than the public. That being said, we need to educate both. I think you have given me great fodder to post on tomorrow. Thank you
and another comment by Sherpa…..
“I don’t mean to be arrogant. I just get frustrated with the whole DIY gang!. I went to medical school for an extra 4 years and then on to residency for 5.”
Hi,
I greatly enjoyed looking through your blog and found an informative one for health related topics.I have also some health related web sites having good PR.So,I think it would be beneficial for both of us if we will join in a community and become link partners to each other which will help your blog/site in getting more Google values.If you are interested then please contact me at-
saffron.nine(at)gmail.com
Thanks
Saffron
fotoselli musluk üretimi
This was a long time ago, they still have not implemented it well
Wow the best I Spider beautiful rare photo was actually pretty toxic strains have silk. Thank you very much to bring an efficient data sharing policy Ct to thank.
Soft-updates guarantees that the only filesystem inconsistencies on unclean shutdown are leaked blocks and inodes. To resolve this you can run a background fsck or you can ignore it until you start to run out of space. We also could’ve written a mark and sweep garbage collector but never did. Ultimately, the bgfsck is too expensive and people did not like the uncertainty of not having run fsck. To resolve these issues, I have added a small journal to softupdates. However, I only have to journal block allocation and free, and inode link count changes since softdep guarantees the rest. My journal records are each only 32bytes which is incredibly compact compared to any other journaling solution. We still get the great concurrency and ability to ignore writes which have been canceled by new operations. But now we have recovery time that is around 2 seconds per megabyte of journal in-use. That’s 32,768 blocks allocated, files created, links added, etc. per megabyte of journal.