Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Patrick Houston

Patrick Houston



When Data Is A Matter Of Life Or Death

Healthcare analytics startup offers insights into how to develop the numbers when it counts for everything.

8 Health Information Exchanges Lead The Way
8 Health Information Exchanges Lead The Way
(click image for larger for slideshow)
Not long ago, a colleague clapped me on the back as we were leaving the office. "It's been a good day," he crowed. "No one died." He was kidding and to make a point: Don't take work too seriously when the stakes aren't mortal.

But what if they are? As they are for Ash Damle, the 35-year-old founder of an about-to-be launched, cloud-based, big data healthcare analytics company called MEDgle.

More Insights

Webcasts

More >>

White Papers

More >>

Reports

More >>

Because MEDgle could make the difference between life and death, I found myself pestering Damle for details. I discovered what it takes to collect copious amounts of raw data from obscure journals and exotic databases and create sophisticated probability algorithms, while making it useful to help nurses, doctors and others diagnose, triage, and treat flesh-and-blood people.

Maybe seeing how MEDgle met the standards required by such high stakes will offer you some insights for developing, crunching, or using your own data more effectively, too.

[ Tech is having a major impact on healthcare. Read When Smart Mobile Technology Meets Good Science. ]

Damle was among about 200 entrepreneurs in San Francisco last week for a two-day Life Sciences Venture Summit. While the burgeoning opportunities in medtech lured most of those attending, Damle arrived no doubt at the behest of nature and nurture: His father is a pulmonary physician, his mother a pediatrician.

An only child, he grew up to the heartbeat of conversations about the common concerns shared by docs. He went off to MIT, earned degrees in computer science and mathematics, and started a search consultancy. Then began connecting dots to what he learned from the time he occupied a high chair.

Dot 1: The emergence of diagnostic tools--like WebMD's symptom checker.

Dot 2: The coming explosion of data spawned a growing number of medical devices and sensors hitting the market.

Dot 2 seemed particularly important because of a law of nature Damle identified. "If you have data," he said, "there's an inherent demand to do something with it."

As personality types go, Damle describes himself a clinician--curious about conditions, diseases, and their causes. As he began to survey the market, he knew, by temperament and training, there had to be better system to help healthcare pros determine what's ailing a patient.

So began what has since become a laborious five-year effort to build--and bulletproof--MEDgle, a name, by the way, created to suggest MEDicine's GooGLE. (Get it?)

It took so long for a good reason: MEDgle relies on an intricately branched decision-making tree, comprised of symptoms and the probabilities among their multitudinous relationships to each other. Damle has been trying, in effect, to replicate with software the same diagnostic intelligence, intuition and judgment exercised by TV's "House."

"Little did we know how much data is needed to mimic the human mind," Damle said.

Thus began the search for data. But, as in any data-based endeavor, quality isn't to be confused with quantity. To build MEDgle, Damle says he's relied on that programmer's adage--you know, GIGO, for garbage-in-garbage-out. (It is comforting that some things don't change.)

For input, he had to tap into a broad array of sources--medical journals, government statistics, and obscure rare-disease databases. Over time, he says, the company collected medical data from hundreds of sources. "We had no idea how much data it would take," he told me.

Of course, Damle and his engineers applied their own algorithms to the data, including a semantic search technology for which Damle says he'll soon receive a patent.

But patent or not, software programming smarts alone weren't up to this task. As Damle says, you can't finesse the outcomes to a system like MEDgle's by creating machine instructions. No matter how brilliantly conceived, the rules invariably result in unforeseen consequences--unacceptable in healthcare.

That led to a second laborious facet of developing MEDgle's big data analytics: Peer review. Over time, he had physicians--one of them his father--reviewing every output, to the tune of 20,000 hours. He didn't consider his results acceptable until the doctors said they were. Good enough wasn't good enough.

Damle says MEDgle is being used now by five beta customers. He offered me a glimpse at several demonstration applications for the platform. One could be used by a patient, another by a nurse at the end of phone line.

eNurse Kim
(click image for larger view)
MEDgle's eNurse Kim

But the most intriguing of these was a mobile SMS service that resembles the back and forth between a physician and a patient. Though the exchange appears to be conversational, it's not. Using MEDgle's platform, the responses are prompted by answers, which prompt more questions prompted by the analytics-based probabilities, leading to more questions, and so on. (Click on the image to the right for an example.)

Damle says, in one deployment, the MEDgle platform slashed the time for an acute conditions diagnosis from 15 to eight minutes.

In the end, Damle believes he's working on a way to scale "hyper-personalized" healthcare--by enabling providers to make better decisions faster from anywhere, based on a data-driven model of an individual, who lives and could very well die.

Patrick Houston is the co-founder of MediaArchitechs. He's a former SVP for a new media startup, a GM at Yahoo, and editor-in-chief at CNET.com. He can be reached at patrick.houston@mediaarchitechs.com.

Get the new, all-digital Healthcare CIO 25 issue of InformationWeek Healthcare. It's our second annual honor roll of the health IT leaders driving healthcare's transformation. (Free registration required.)



Related Reading




Currently we allow the following HTML tags in comments:

Single tags

These tags can be used alone and don't need an ending tag.

<br> Defines a single line break

<hr> Defines a horizontal line

Matching tags

These require an ending tag - e.g. <i>italic text</i>

<a> Defines an anchor

<b> Defines bold text

<big> Defines big text

<blockquote> Defines a long quotation

<caption> Defines a table caption

<cite> Defines a citation

<code> Defines computer code text

<em> Defines emphasized text

<fieldset> Defines a border around elements in a form

<h1> This is heading 1

<h2> This is heading 2

<h3> This is heading 3

<h4> This is heading 4

<h5> This is heading 5

<h6> This is heading 6

<i> Defines italic text

<p> Defines a paragraph

<pre> Defines preformatted text

<q> Defines a short quotation

<samp> Defines sample computer code text

<small> Defines small text

<span> Defines a section in a document

<s> Defines strikethrough text

<strike> Defines strikethrough text

<strong> Defines strong text

<sub> Defines subscripted text

<sup> Defines superscripted text

<u> Defines underlined text

BYTE encourages readers to engage in spirited, healthy debate, including taking us to task. However, BYTE moderates all comments posted to our site, and reserves the right to modify or remove any content that it determines to be derogatory, offensive, inflammatory, vulgar, irrelevant/off-topic, racist or obvious marketing/SPAM. BYTE further reserves the right to disable the profile of any commenter participating in said activities.

Disqus Tips To upload an avatar photo, first complete your Disqus profile. | View the list of supported HTML tags you can use to style comments. | Please read our commenting policy.

Follow InformationWeek

By The Numbers

What Are Your Primary Concerns About Using Big Data Software?

Base: 417 respondents at organizations using or planning to deploy data analytics, BI or statistical analysis software
Data: InformationWeek 2013 Analytics, Business Intelligence and Information Management Survey of 541 business technology professionals, October 2012

What Do You Think?

What's your attitude about SQL analysis on top of Hadoop?
We want fast, standard SQL analysis capabilities on Hadoop ASAP
Hadoop is for unstructured data; SQL is for relational databases
We'll give SQL on Hadoop a try, but relational DBs will remain the mainstay
Given strong SQL support on Hadoop, we'd nix the data warehouse
We're not interested in Hadoop
No opinion



Related Content

From Our Sponsor

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Five Big Data Challenges and How to Overcome Them with Visual Analytics

Business leaders often need a visual snapshot of data to quickly grasp and use it. This paper identifies five challenges in presenting data and how visual analytics can resolve them. Solutions are suggested to overcome the challenges of: speed, data clarity, data quality, displaying meaningful results, and dealing with outliers.

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Game-Changing Analytics: How IT Executives Can Use Analytics to Create Innovation and Business Success

Today's competitive advantage requires a deeper understanding of your business, your market and your customers. As an IT executive, you can drive that knowledge transformation. In this white paper, learn how to make decisions as a strategic business leader and three steps to begin an analytics initiative within your enterprise.

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

Data Visualization Techniques: From Basics to Big Data with SAS Visual Analytics

High-performance data visualization turns sophisticated analyses into meaningful graphics, leading to faster and smarter decision making. In this white paper, learn how visual analytics can transform big data, with additional features such as real-time functionality, mobile compatibility, robust applications for technical groups and accessibility for nontechnical users.

Big Data: Lessons from the Leaders

Big Data: Lessons from the Leaders

Financial performance, competitive advantage, operational efficiency, strategic decision making - every business goal can extract value from big data, and the time for doubt or inaction has long passed. In this Economist Intelligence Unit report, in-depth interviews with data pioneers reveal the link between the effective use of big data and the bottom line among other results.

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Decision-Driven Data Management: A Strategy for Better Decisions with Better Data

Which came first, the data or the decision? This white paper makes the case for having a decision in mind, then tailoring big data's volume, variety and velocity to achieve business results such as overcoming customer dissatisfaction or creating well-informed strategies in real time.

Informationweek Reports

Research: The Big Data Management Challenge

Research: The Big Data Management Challenge

The challenge of big data is real, but most organizations don't differentiate 'big data' from traditional data, and nearly 90% of respondents to our survey use conventional databases as the primary means of handling data. We'll help you understand what constitutes big data (it's not just size) and the numerous management challenges it poses.