Innovation stop: “All they’ve done is created an extra billing event for the doctor”

It’s my first real encounter with a situation in which the officials of the state of California are clearly against innovation for financial reasons obvious enough (is enough):

Wired Science, Alexis Madrigal, upcoming BioBarCamper:

Exclusive: DNA Tester Reveals Cease-and-Desist Letter

Wired.com has obtained a copy of the cease-and-desist letter sent to Navigenics by the state of California’s Public Health Department from a company spokesperson.

The letter’s strongest wording is reserved for another section of the law, Business and Professions Code Section 1288, which requires a doctor’s note for all laboratory tests, unless, like pregnancy tests, they are exempt from that law.

“Genetic tests are NOT exempt,” the letter reads. “As such, the test must be ordered by a physician or surgeon.”

Kristine Ashcraft, director of operations for another genetic testing company, Genelex, which was not sent a cease-and-desist letter, criticized New York’s policy and the application of that framework to genetic testing in California.

“All they’ve done is created an extra billing event for the doctor,” Ashcraft said.

3 thoughts on “Innovation stop: “All they’ve done is created an extra billing event for the doctor”

  1. 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.

Comments are closed.