<?xml version="1.0" encoding="UTF-8"?><rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:dc="http://purl.org/dc/elements/1.1/"
	xmlns:atom="http://www.w3.org/2005/Atom"
	xmlns:sy="http://purl.org/rss/1.0/modules/syndication/"
		>
<channel>
	<title>Comments on: HIStalk Practice Interviews William Zurhellen</title>
	<atom:link href="http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/</link>
	<description>Physician practice and systems news and opinion</description>
	<lastBuildDate>Sat, 04 Feb 2012 20:34:20 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.2.1</generator>
	<item>
		<title>By: Jesran</title>
		<link>http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/comment-page-1/#comment-956</link>
		<dc:creator>Jesran</dc:creator>
		<pubDate>Wed, 30 Dec 2009 16:49:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/#comment-956</guid>
		<description>&quot;My own feeling is that if we could get a single data structure and let vendors compete on the user interface, then all records would be compatible with all others.&quot;

Such a data structure exists:
SNOMED CT (Systematized Nomenclature of Medicine--Clinical Terms) is a comprehensive clinical terminology
http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html

It&#039;s actually not that bad to work with. It&#039;s open standard, maintained by the right people and comprehensive... even if very redundant. 

Anyway, you are right that the problem is that it costs money to port something like this to existing EMRs that are not so much patient care tools as they are revenue capture devices. SNOMEDCT has little or nothing to do with the latter, and in the end the former is why we have health care institutions in the first place. It is such a slow process to get past the money thing though.</description>
		<content:encoded><![CDATA[<p>&#8220;My own feeling is that if we could get a single data structure and let vendors compete on the user interface, then all records would be compatible with all others.&#8221;</p>
<p>Such a data structure exists:<br />
SNOMED CT (Systematized Nomenclature of Medicine&#8211;Clinical Terms) is a comprehensive clinical terminology<br />
<a href="http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html" rel="nofollow">http://www.nlm.nih.gov/research/umls/Snomed/snomed_main.html</a></p>
<p>It&#8217;s actually not that bad to work with. It&#8217;s open standard, maintained by the right people and comprehensive&#8230; even if very redundant. </p>
<p>Anyway, you are right that the problem is that it costs money to port something like this to existing EMRs that are not so much patient care tools as they are revenue capture devices. SNOMEDCT has little or nothing to do with the latter, and in the end the former is why we have health care institutions in the first place. It is such a slow process to get past the money thing though.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bignurse</title>
		<link>http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/comment-page-1/#comment-951</link>
		<dc:creator>Bignurse</dc:creator>
		<pubDate>Mon, 28 Dec 2009 01:06:04 +0000</pubDate>
		<guid isPermaLink="false">http://www.histalkpractice.com/2009/12/27/histalk-practice-interviews-william-zurhellen/#comment-951</guid>
		<description>Great interview from the trenches.  What we need is a virtual care plan, that tracks the patient&#039;s care, and follows the patient wherever they go.  The data would exist because it would  explain the care that was given to the child for their asthma (or whatever the diagnosis is).  Outcomes would be obtained based on that data over time.  Every EHR system would &quot;talk to&quot; the virtual care plan.  Anything less than this model is fragmented and silo&#039;ed.</description>
		<content:encoded><![CDATA[<p>Great interview from the trenches.  What we need is a virtual care plan, that tracks the patient&#8217;s care, and follows the patient wherever they go.  The data would exist because it would  explain the care that was given to the child for their asthma (or whatever the diagnosis is).  Outcomes would be obtained based on that data over time.  Every EHR system would &#8220;talk to&#8221; the virtual care plan.  Anything less than this model is fragmented and silo&#8217;ed.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

