<?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: Monday Morning Update 11/3/08</title>
	<atom:link href="http://histalk2.com/2008/11/01/monday-morning-update-11308/feed/" rel="self" type="application/rss+xml" />
	<link>http://histalk2.com/2008/11/01/monday-morning-update-11308/</link>
	<description>Healthcare IT News and Opinion</description>
	<lastBuildDate>Tue, 22 May 2012 14:25:13 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3</generator>
	<item>
		<title>By: emrsage</title>
		<link>http://histalk2.com/2008/11/01/monday-morning-update-11308/comment-page-1/#comment-2558</link>
		<dc:creator>emrsage</dc:creator>
		<pubDate>Sun, 02 Nov 2008 13:08:19 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/11/01/monday-morning-update-11308/#comment-2558</guid>
		<description>I&#039;d love to know when the last time Sage was relative in the ambulatory space.  The fact that they are announcing an 8 doc current customer &quot;upgrades&quot; to Intergy is staggering.  This company (when it was Med Mgr) had a huge chunk of the market.  Now, it&#039;s an afterthought unless it&#039;s an existing customer.</description>
		<content:encoded><![CDATA[<p>I&#8217;d love to know when the last time Sage was relative in the ambulatory space.  The fact that they are announcing an 8 doc current customer &#8220;upgrades&#8221; to Intergy is staggering.  This company (when it was Med Mgr) had a huge chunk of the market.  Now, it&#8217;s an afterthought unless it&#8217;s an existing customer.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dr. Herzenstube</title>
		<link>http://histalk2.com/2008/11/01/monday-morning-update-11308/comment-page-1/#comment-2557</link>
		<dc:creator>Dr. Herzenstube</dc:creator>
		<pubDate>Sun, 02 Nov 2008 04:33:37 +0000</pubDate>
		<guid isPermaLink="false">http://histalk2.com/2008/11/01/monday-morning-update-11308/#comment-2557</guid>
		<description>Re: ICD-10-CM.  I think Frankie Saluto actually referring to post-coordination when he (or she?) uses the term &quot;normalization&quot;.  Post-coordination is where a user of a structured structured terminology identifies a concept by selecting one code for each of several axes (e.g. one code for the disorder, like &quot;insect bite,&quot; one for the anatomic location, and one for the ordinality of visit).  Pre-coordination, on the other hand, is where the terminology includes pre-built concepts that specify values for all the relevant axes, like the ICD-10-CM codes.  The problems with post-coordination include:
1. You end up with many more potential combinations than with pre-coordinated codes
2. Many post-coordinated codes might be meaningless (e.g. &quot;classic migraine&quot; combined with &quot;right big toe.&quot;)
3. It is easier for the user to select a pre-coordinated code (if the user can be presented with a list that is reasonable in length and includes something representing what they have in mind.

 The problem with ICD-10-CM is that it is really the worst of both worlds.  The lists of codes are in general a slavish enumeration of nearly every possible combination of pathology, anatomic location, laterality, and ordinality of visit-It is essentially a set of pseudo-post-coordinated codes. 

 But, amazingly, they have made it impossible for information systems to automate the process of code selection, because of inconsistency as to which of the 7 characters in the code represents what concept.  In some cases laterality (i.e. left vs. right) might be represented by the value of 4th character in the code, in others by the 5th.  Thus, it is impossible to design a solution for end-users that allows them to, for instance, have a handy radio button to indicate right vs. left, and have the application reliably select the right ICD-10-CM code behind the scenes.  FEH.</description>
		<content:encoded><![CDATA[<p>Re: ICD-10-CM.  I think Frankie Saluto actually referring to post-coordination when he (or she?) uses the term &#8220;normalization&#8221;.  Post-coordination is where a user of a structured structured terminology identifies a concept by selecting one code for each of several axes (e.g. one code for the disorder, like &#8220;insect bite,&#8221; one for the anatomic location, and one for the ordinality of visit).  Pre-coordination, on the other hand, is where the terminology includes pre-built concepts that specify values for all the relevant axes, like the ICD-10-CM codes.  The problems with post-coordination include:<br />
1. You end up with many more potential combinations than with pre-coordinated codes<br />
2. Many post-coordinated codes might be meaningless (e.g. &#8220;classic migraine&#8221; combined with &#8220;right big toe.&#8221;)<br />
3. It is easier for the user to select a pre-coordinated code (if the user can be presented with a list that is reasonable in length and includes something representing what they have in mind.</p>
<p> The problem with ICD-10-CM is that it is really the worst of both worlds.  The lists of codes are in general a slavish enumeration of nearly every possible combination of pathology, anatomic location, laterality, and ordinality of visit-It is essentially a set of pseudo-post-coordinated codes. </p>
<p> But, amazingly, they have made it impossible for information systems to automate the process of code selection, because of inconsistency as to which of the 7 characters in the code represents what concept.  In some cases laterality (i.e. left vs. right) might be represented by the value of 4th character in the code, in others by the 5th.  Thus, it is impossible to design a solution for end-users that allows them to, for instance, have a handy radio button to indicate right vs. left, and have the application reliably select the right ICD-10-CM code behind the scenes.  FEH.</p>
]]></content:encoded>
	</item>
</channel>
</rss>

