Slashdot Mirror
Apple Has a Secret Team Working On Non-Invasive Diabetes Sensors (cnbc.com)
schwit1 quotes a report from CNBC: Apple has hired a small team of biomedical engineers to work at a nondescript office in Palo Alto, miles from corporate headquarters. They are part of a super secret initiative, initially envisioned by the late Apple co-founder Steve Jobs, to develop sensors that can non-invasively and continuously monitor blood sugar levels to better treat diabetes, according to three people familiar with the matter. Such a breakthrough would be a "holy grail" for life sciences. Many life sciences companies have tried and failed, as it's highly challenging to track glucose levels accurately without piercing the skin. The initiative is far enough along that Apple has been conducting feasibility trials at clinical sites across the Bay Area and has hired consultants to help it figure out the regulatory pathways, the people said.
schwit1 adds: "From a business aspect, the most interesting part of this venture might be how Apple combines its penchant for secrecy with maneuvering through those regulatory pathways. It's one thing to introduce another new bit of consumer electronics kit. It's an entirely other thing to get a medical device past the FDA."
schwit1 adds: "From a business aspect, the most interesting part of this venture might be how Apple combines its penchant for secrecy with maneuvering through those regulatory pathways. It's one thing to introduce another new bit of consumer electronics kit. It's an entirely other thing to get a medical device past the FDA."
Already debunked
Only a moron who doesn't understand how floating point numbers work would think anything was odd about that example. What are you even doing on Slashdot if you cannot work with simple floating point?
I mean, an AC can understand what is going on with that code and you can't?
SHAME SHAME SHAME
You're a PHP programmer, aren't you - admit it. Go back to "hacker" news.
"There is more worth loving than we have strength to love." - Brian Jay Stanley
Well at least it would mean not having to burn through lancets and strips. If a monitor that did not consume test scripts cost 300 dollars and lasted at least six months, it would have paid for itself in test strips alone.
For at least some type IIs controlling with medication, having continuous monitoring may help them when they over medicate and give them some heads up when their sugar is crashing.
Of course, healthy skepticism about Apple actually pulling it off, but it's far from the worst thing Apple could do.
XML is like violence. If it doesn't solve the problem, use more.
If this is real, Apple is very much behind the times when it comes to both sensor technology and understanding of the medical device market. Trying a spectroscopic approach (which appears to be the case) is way out of date, that's a generation behind even the FDA cleared tests, and isn't going to compete with the new generation of sensors being developed now.
There are several approaches to continuous monitoring of glucose, going back more than 10 years.
Many of these technologies, particularly the non-invasive ones, are more available outside the US than inside. This has more to do with the way medical device manufacturers are paid than any technical limitation. Bluntly, being in the glucose monitoring business is a great way to lose a lot of money quickly. Yes, the market is big, but it's brutal. Apple's strength is not dominating low margin, highly regulated markets.
I'm tired of poking a needle in my finger twice a day to make me bleed so I can check my blood sugar. Then there's the cost/bother of the strips and machine (strips have a short shelf life, machines eat batteries).
Chaos maximizes locally around me.
The problem line is [oneish integerValue], which returns zero, and the rest of your code is just trying to obfuscate this. This is because NSDecimalNumber doesn't overrider integerValue, so it returns the inherited implementation, which returns zero. This is unexpected, but not undocumented. See the Subclassing Notes at:
https://developer.apple.com/re...
I'll note that in Swift, integerValue no longer exists, having been folded into intValue, which gives the expected result of one (just like intValue in Objective-C).