Second, after seeing the type of queries, I do not think that this is all that helpful. If a person has unexplained weight loss or yellow skin or eyes, they should always go see their doctor right away. My guess is that most of the specificity of this study comes from those two terms (weight loss combined with yellow skin). Just getting out that message will do a lot more to save people's lives than violating their privacy in this manner.
It would sure be spiffy if mining queries could identify early symptoms, working backwards if you will, rather than be used to find cancer patients by working forward from symptoms already identified by the medical establishment.
My GP had x-rayed me, looking for a cardiac anomaly - he suspected an aortic aneurism. What he should've done is order some soft tissue radiology instead. Having your GP consider a CT or MRI is my advice.
Hope in your case it's all for naught. Best to check though.
I really hope you are better.
GPs often do not catch rare conditions or determine the underlying cause of milder symptoms.
How do you suggest getting out the message? Blanket public health advertising would be very expensive and would be ignored by most people.
I think search histories are potentially very useful but privacy is important too. It would be interesting to see if there's a way of using search history information in a way that preserves privacy.
But it's funny, I was thinking the same thing the whole time I was reading the article... what are the search queries?!?
But these symptoms map closely to other serious diseases as well, notably liver disease or liver failure. (I've had them; I know.)
While it might make sense to flag such symptoms as serious and requiring professional advice, in this case I don't see how you could possibly distinguish between the two given the vagueness of the input data.
That raises a real question about how you inform the user/potential patient without freaking the person out, or driving him or her down the wrong path.
Some other commenters have mentioned that they have been mis-diagnosed by a GP, and that perhaps this system would help. I think mis-diagnosis is a different problem. This system's real potential value is in driving more people to get professional help, who likely is a GP.
Tragic exceptions aside, most GP's are very good at what they do, which most days involves keeping "regular" people healthy. Perhaps the biggest problem in health care (at least in the US) is the lack of enough GPs in many communities and the inability of people to get access to them conveniently and affordably.
How is this project anything more than "other people snooping around in my search queries," or any better than simply tuning the search engine to highlight those results more if they are believed under-represented?
As it is, nearly any symptom you put in will bring up the possibility of cancer, so it’s all just noise.
Being able to connect disparate symptoms that the patients don’t connect themselves is a good thing.
Snooping on searches isn’t necessarily the greatest way of achieving that given all the privacy implications, but it may be reasonably effective.
I think it's interesting that this research can happen.
That seems rather different than "Hey, 10 years ago you searched on some stuff that indicated you might have had pancreatic cancer. Sorry we didn't catch it sooner, since the 10 year survival rate is below 5%..."
To be clear, either one seems potentially quite cool and interesting. But if someone else besides me and Clippy are privy to these results - unless I explicitly shared them - then it seems a little creepy.
In retrospect, I suppose I wouldn't be too terribly offended if I died already, but my results were later able to help prevent someone else's untimely demise...
The article name is: J. Paparrizos, R.W. White, E. Horvitz. Screening for Pancreatic Adenocarcinoma using Signals from Web Search Logs: Feasibility Study and Results, Journal of Oncology Practice, June 2016.[2]
[1]https://blogs.microsoft.com/next/2016/06/07/how-web-search-d...
[2] http://jop.ascopubs.org/content/early/2016/06/02/JOP.2015.01...