Big Data. Big Decisions
InformationWeek
Special Coverage Series

Commentary

Paul Cerrato

Paul Cerrato

Editor, InformationWeek Healthcare

Can IT Really Nail A Complex Medical Diagnosis?

State-of-the-art clinical decision-support systems can sharpen a veteran physician’s reasoning skills, but they're far from perfect.

Among the countless medical conferences I've attended over the years, one presentation stands out. Called "Stump the Professors," it featured a panel of top medical school professors who were challenged to figure out the diagnosis in several tough clinical cases.

One by one, residents would file up to the podium and describe their case, outlining signs and symptoms, lab results, and pathology findings. One thing that stands out in my mind is the lighthearted banter and laughter among the participants as professors struggled to figure out some of these esoteric disorders. The residents relished the fact that they really were stumping the professors.

Among the expert panelists was one professor who remained relatively quiet until the end of each case, only occasionally asking questions about some lab report or symptom. But when all the facts were in, he would nail virtually every diagnosis. What an amazing gift.

Fast forwarding to today and the age of clinical decision support software (CDSS) and IBM's Watson computer, the question that comes to mind is: Can health IT duplicate this kind of diagnostic reasoning, or at least facilitate the process?

What's Available?

Computer-generated diagnostic tools, which are usually part of a larger CDSS, come in a few basic flavors. Many consist of three main components: a knowledge base, an inference engine, and a communication mechanism.

The knowledge base contains reasoning guidelines, including "if/then" rules. For instance, one rule may state: If drug X is taken with drug Y, alert the physician for a possible harmful interaction. The inference engine then combines the rules with each patient's data--in this example, it would be the list of medications he's taking. The communication mechanism provides a way to give the results of the data analysis to the clinician, who then decides what action to take.

Other diagnostic programs rely not on a knowledge base, but on some form of artificial intelligence--neural networks, for instance--to find patterns in the patient's data and associate them with a list of diagnoses.

Among the players in the field of diagnostic software are Simulconsult and Dxplain. Typically, these programs use probabilistic algorithms and pattern-matching to create a list of diagnoses ranked from most likely to least likely disorders. The software generates the list of diseases by looking at each sign, symptom, and lab finding to determine how strongly each of the physical findings is associated with the disease under consideration. For example, how probable is it that a patient with carrot-orange skin is suffering from carotene toxicity.

Many of these programs also incorporate a huge database that condenses clinical research from major clinical journals and clinical practice guidelines to ensure that the final results are best practice.

Taking A Closer Look

The software developed by Simulconsult, which incorporates statistics-enhanced pattern matching, offers a good example of the impressive reasoning skills of these diagnostic tools.

The example provided by Simulconsult starts with a patient presenting with kyphosis, an abnormal curvature of the spine. The initial information screen asks for the patient's age (8 months), gender, and family history. Then it asks the physician to input the most unusual or prominent physical finding.

Once kyphosis is entered in the search engine, the system wants more details: Is the kyphosis accompanied by scoliosis? The clinician observes that there is no scoliosis, enters that fact, and the program then asks: When did the kyphosis begin? A drop-down menu lets him choose its onset.

 1 | 2  | Next Page »


Related Reading


More Insights




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.