<?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/"
	xmlns:itunes="http://www.itunes.com/dtds/podcast-1.0.dtd"
xmlns:rawvoice="http://www.rawvoice.com/rawvoiceRssModule/"
	>
<channel>
	<title>Encoding information is a key part of I.T.Comments on: --</title>
	<atom:link href="http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/feed" rel="self" type="application/rss+xml" />
	<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html</link>
	<description>because health professionals can&#039;t do it alone</description>
	<lastBuildDate>Tue, 22 May 2012 03:29:30 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	
	<item>
		<title>By: Coleman Walth</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-78774</link>
		<dc:creator>Coleman Walth</dc:creator>
		<pubDate>Thu, 28 Apr 2011 05:28:55 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-78774</guid>
		<description>hello,this article is great,I found it on google and I appreciate it very much,I agree with what you have said, it help me a lot in decision,but I still have some questions with the last part,can you explain it for me ?I need your answer,and I will keep on watching your blog</description>
		<content:encoded><![CDATA[<p>hello,this article is great,I found it on google and I appreciate it very much,I agree with what you have said, it help me a lot in decision,but I still have some questions with the last part,can you explain it for me ?I need your answer,and I will keep on watching your blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Vivienne Frappier</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-78591</link>
		<dc:creator>Vivienne Frappier</dc:creator>
		<pubDate>Tue, 26 Apr 2011 11:44:51 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-78591</guid>
		<description>Hi,this is an excellent article,I found it on bing and I love it very much,I agree with what you have said, lots of things will be learned form your site,but I still have some questions with the last part,can you explain it for me ?I need your answer,and I will keep on watching your blog</description>
		<content:encoded><![CDATA[<p>Hi,this is an excellent article,I found it on bing and I love it very much,I agree with what you have said, lots of things will be learned form your site,but I still have some questions with the last part,can you explain it for me ?I need your answer,and I will keep on watching your blog</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: e-Patient Dave</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-24920</link>
		<dc:creator>e-Patient Dave</dc:creator>
		<pubDate>Fri, 15 May 2009 12:32:59 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-24920</guid>
		<description>Fascinating comment, Don. I love that the vocabulary was developed by capturing what people actually say!

Interesting that you code using ICD-9. What do you do when you&#039;re testing *for* something, and the diagnosis isn&#039;t present?</description>
		<content:encoded><![CDATA[<p>Fascinating comment, Don. I love that the vocabulary was developed by capturing what people actually say!</p>
<p>Interesting that you code using ICD-9. What do you do when you&#8217;re testing *for* something, and the diagnosis isn&#8217;t present?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Donald Green</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-24899</link>
		<dc:creator>Donald Green</dc:creator>
		<pubDate>Fri, 15 May 2009 11:36:06 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-24899</guid>
		<description>An EMR was developed for my office and the vocabulary was developed by allowing free text for 6 to 10 months and then converting it into a usable table from there.  By using past ICD codes for these assessments, friendly descriptions were matched with the ICD codes.  

Now 4 fields emerge, a friendly description(the clinician&#039;s preferred language), the ICD 9 code, and an additional field comment that is free text with a brief descriptor, and finally room for a longer comment in free text.  It is the clinician&#039;s choice which to leave in the record.  However if the ICD9 is used it will always appear with a friendly description.  

Program Maintainance allows new additions, or editing.  Nothing can be removed however since no longer used or inaccurate vocabulary may still be tied to a record and must stand.  The onus is put on the clinician to keep documentation accurate, not on the EMR itself.  

The system was created to be &quot;held open&quot; until it is complete but once closed(electronically signed) the user has only the same calendar day to change it.  After that it can not be changed.  Of course there is always the option of inserting a new &quot;Encounter&quot; that corrects any past Encounters.  This is the equivalent of putting that neat straight line through the record, dating it, and initializing it as in other legal documents.  

Yes there may be some initial extra effort to to customize language to standard vocabularies but the result, once established, is a more accurate documentation process that can be used by its creator and anyone who is a legitimate entitled caregiver to the patient or the patient themselves.  

I am, however, a strong believe that any data used outside of the relationship that created it must be corroborated by a new circumstance of a different user and the patient involved.  No data not produced by a current user should not be taken for granted.  e-patient Dave has already told his story about that one.</description>
		<content:encoded><![CDATA[<p>An EMR was developed for my office and the vocabulary was developed by allowing free text for 6 to 10 months and then converting it into a usable table from there.  By using past ICD codes for these assessments, friendly descriptions were matched with the ICD codes.  </p>
<p>Now 4 fields emerge, a friendly description(the clinician&#8217;s preferred language), the ICD 9 code, and an additional field comment that is free text with a brief descriptor, and finally room for a longer comment in free text.  It is the clinician&#8217;s choice which to leave in the record.  However if the ICD9 is used it will always appear with a friendly description.  </p>
<p>Program Maintainance allows new additions, or editing.  Nothing can be removed however since no longer used or inaccurate vocabulary may still be tied to a record and must stand.  The onus is put on the clinician to keep documentation accurate, not on the EMR itself.  </p>
<p>The system was created to be &#8220;held open&#8221; until it is complete but once closed(electronically signed) the user has only the same calendar day to change it.  After that it can not be changed.  Of course there is always the option of inserting a new &#8220;Encounter&#8221; that corrects any past Encounters.  This is the equivalent of putting that neat straight line through the record, dating it, and initializing it as in other legal documents.  </p>
<p>Yes there may be some initial extra effort to to customize language to standard vocabularies but the result, once established, is a more accurate documentation process that can be used by its creator and anyone who is a legitimate entitled caregiver to the patient or the patient themselves.  </p>
<p>I am, however, a strong believe that any data used outside of the relationship that created it must be corroborated by a new circumstance of a different user and the patient involved.  No data not produced by a current user should not be taken for granted.  e-patient Dave has already told his story about that one.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Next stage in mapping my hospital&#8217;s clinical data to PHRs &#124; e-Patients.net</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-24348</link>
		<dc:creator>Next stage in mapping my hospital&#8217;s clinical data to PHRs &#124; e-Patients.net</dc:creator>
		<pubDate>Wed, 13 May 2009 19:19:34 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-24348</guid>
		<description>[...] more info on data formats see our post on data vocabularies.    Share and [...]</description>
		<content:encoded><![CDATA[<p>[...] more info on data formats see our post on data vocabularies.    Share and [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nursing Agency Software</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-20465</link>
		<dc:creator>Nursing Agency Software</dc:creator>
		<pubDate>Wed, 29 Apr 2009 14:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-20465</guid>
		<description>Hi Dave,

You have a great blog. I found your post very interesting to read. We work with the NHS in the UK and have just launched an additional module to interface with the NHS ESR (Electronic Staff Record) system, I think this a step in the right direction that the NHS has the facility to allow third party systems like ours to syncronize with their central database.

We do not deal with Patient records, but my point is the accessability of the data is important. I wonder how long it will take Google to launch Google Health in the UK, as far as I know all my personally health records are still kept on paper.</description>
		<content:encoded><![CDATA[<p>Hi Dave,</p>
<p>You have a great blog. I found your post very interesting to read. We work with the NHS in the UK and have just launched an additional module to interface with the NHS ESR (Electronic Staff Record) system, I think this a step in the right direction that the NHS has the facility to allow third party systems like ours to syncronize with their central database.</p>
<p>We do not deal with Patient records, but my point is the accessability of the data is important. I wonder how long it will take Google to launch Google Health in the UK, as far as I know all my personally health records are still kept on paper.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ZDNet Healthcare mobile edition</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-19966</link>
		<dc:creator>ZDNet Healthcare mobile edition</dc:creator>
		<pubDate>Mon, 27 Apr 2009 19:00:55 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-19966</guid>
		<description>[...] the hospital is moving to support the SNOMED-CT codes instead.  The patient and his doctor have blogged about their lessons. All well and good. But the larger, business question should be asked at this point. [...]</description>
		<content:encoded><![CDATA[<p>[...] the hospital is moving to support the SNOMED-CT codes instead.  The patient and his doctor have blogged about their lessons. All well and good. But the larger, business question should be asked at this point. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Aaron</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-19960</link>
		<dc:creator>Aaron</dc:creator>
		<pubDate>Mon, 27 Apr 2009 17:39:25 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-19960</guid>
		<description>So how do we get the health information providers to shape up and get them to transmit the information correctly to google?  I have also tried this with Quest Diagnostics + Walgreens and I also see some detail errors in the conduits that nobody is interested in taking responsibility for.  Even the google health google group seems to be completely unmonitored.  Granted, I&#039;m not in the medical IT field (nor do I want to be, knowing this) but I certainly want to able to assist in any way possible.</description>
		<content:encoded><![CDATA[<p>So how do we get the health information providers to shape up and get them to transmit the information correctly to google?  I have also tried this with Quest Diagnostics + Walgreens and I also see some detail errors in the conduits that nobody is interested in taking responsibility for.  Even the google health google group seems to be completely unmonitored.  Granted, I&#8217;m not in the medical IT field (nor do I want to be, knowing this) but I certainly want to able to assist in any way possible.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Headlines for April 7-18 &#124; Health Content Advisors</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-18561</link>
		<dc:creator>Headlines for April 7-18 &#124; Health Content Advisors</dc:creator>
		<pubDate>Wed, 22 Apr 2009 14:14:02 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-18561</guid>
		<description>[...] » Encoding information is a key part of I.T. &#124; e-Patients.net [...]</description>
		<content:encoded><![CDATA[<p>[...] » Encoding information is a key part of I.T. | e-Patients.net [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Google Health: PHRs Still Need Human Touch &#124; Health Content Advisors</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-18558</link>
		<dc:creator>Google Health: PHRs Still Need Human Touch &#124; Health Content Advisors</dc:creator>
		<pubDate>Wed, 22 Apr 2009 14:02:09 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-18558</guid>
		<description>[...] in using medical billing codes to infer information about medical conditions.  E-Patient Dave delves more deeply into the medical coding issue on his blog and offers a good round-up of the various codes used by medical providers.  These [...]</description>
		<content:encoded><![CDATA[<p>[...] in using medical billing codes to infer information about medical conditions.  E-Patient Dave delves more deeply into the medical coding issue on his blog and offers a good round-up of the various codes used by medical providers.  These [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Completing my list of billing code errors &#124; e-Patients.net</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-18229</link>
		<dc:creator>Completing my list of billing code errors &#124; e-Patients.net</dc:creator>
		<pubDate>Mon, 20 Apr 2009 19:21:24 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-18229</guid>
		<description>[...] (For those who want more details, the ICD-9 billing codes are listed here and the Wikipedia page about ICD codes is here. Our post on other medical data formats is here.) [...]</description>
		<content:encoded><![CDATA[<p>[...] (For those who want more details, the ICD-9 billing codes are listed here and the Wikipedia page about ICD codes is here. Our post on other medical data formats is here.) [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Lodewijk Bos</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-18169</link>
		<dc:creator>Lodewijk Bos</dc:creator>
		<pubDate>Mon, 20 Apr 2009 06:09:34 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-18169</guid>
		<description>FYI http://blog.icmcc.org/2009/04/14/observations-standards-world-is-moving/
Lodewijk</description>
		<content:encoded><![CDATA[<p>FYI <a href="http://blog.icmcc.org/2009/04/14/observations-standards-world-is-moving/" rel="nofollow">http://blog.icmcc.org/2009/04/14/observations-standards-world-is-moving/</a><br />
Lodewijk</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: ICMCC Website - Articles &#187; Blog Archive &#187; Encoding information is a key part of I.T.</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-18168</link>
		<dc:creator>ICMCC Website - Articles &#187; Blog Archive &#187; Encoding information is a key part of I.T.</dc:creator>
		<pubDate>Mon, 20 Apr 2009 06:04:23 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-18168</guid>
		<description>[...] data. And that starts with understanding a few basics about I.T. … information technology.&#8221; Article e-Patient Dave, e-Patients.net, 12 April [...]</description>
		<content:encoded><![CDATA[<p>[...] data. And that starts with understanding a few basics about I.T. … information technology.&#8221; Article e-Patient Dave, e-Patients.net, 12 April [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Procter</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16773</link>
		<dc:creator>Dean Procter</dc:creator>
		<pubDate>Tue, 14 Apr 2009 01:15:03 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16773</guid>
		<description>I can see the surface level attraction in having someone take care of your records for you, but as with your choice of doctor, perhaps a choice is in order.
When I put my well worn security hat on I note that it is much more easy to compromise or break into one place to steal/alter/hijack your medical records than perhaps if there are many such repositories of information. ie if &#039;super-google&#039; health went down, no-one would get treatment, and if I wanted to access your records I know where to hack/look. Rather the other scenario where I may not even know where to find them, without your co-operation and I may have to crack several systems in order to get to them without your permission. 
Why I might choose google escapes me, considering there are other well established and proven companies such as IBM and EMC who are better experienced, qualified and equipped to do so. However they obviously haven&#039;t put the PR machine to work in the same way.
It won&#039;t be the PR machine looking after your records so best look behind and see what is really happening. You don&#039;t want them to dissappear into a cloud.

One of my first medical records projects was in the 90&#039;s and the goal was to communicate the statistics of procedures performed by doctors particularly in the area of the &#039;plumbing&#039;. The overwhelming and alarming conclusion of the data was that there were a lot of doctors performing procedures which they were unqualified to perform, based on the results of tests interpreted by personnel unqualified to interpret them after being administered by others untrained and unqualified to carry out such tests.

The experience, which was for a world leader in the field to present at a global conference, left me with a strong and lingering fear of medical treatment. Things haven&#039;t changed. I certainly would like to see improvements in medical services. 

Perhaps one good thing about a potential central record data store is that potential patient/victims may at least check whether their doctor is so qualified, and their level of experience in the particular procedure, and whoever trained them, along with the experiences of the patients, even those who perhaps fail to survive the patient experience.

Of course this will open up a big can of worms for lawyers, liability, marketing tactics etc.
Far be it from me to suggest that perhaps that would be as good a place to start as any, if you want to start storing medical records and making them publicly available.

The data on procedures is readily and generally electronically available, is easily sanitised for patient privacy, and would ensure that patients can encourage doctors to be better qualified and educated.

Perhaps this might be a nice project for google to cut it&#039;s teeth on. If google can perform that, with no doubt, much litigation from doctors, then perhaps afterwards they my be given the chance to handle actual patient records.

Our objective is better patient outcomes for fewer dollars isn&#039;t it?</description>
		<content:encoded><![CDATA[<p>I can see the surface level attraction in having someone take care of your records for you, but as with your choice of doctor, perhaps a choice is in order.<br />
When I put my well worn security hat on I note that it is much more easy to compromise or break into one place to steal/alter/hijack your medical records than perhaps if there are many such repositories of information. ie if &#8216;super-google&#8217; health went down, no-one would get treatment, and if I wanted to access your records I know where to hack/look. Rather the other scenario where I may not even know where to find them, without your co-operation and I may have to crack several systems in order to get to them without your permission.<br />
Why I might choose google escapes me, considering there are other well established and proven companies such as IBM and EMC who are better experienced, qualified and equipped to do so. However they obviously haven&#8217;t put the PR machine to work in the same way.<br />
It won&#8217;t be the PR machine looking after your records so best look behind and see what is really happening. You don&#8217;t want them to dissappear into a cloud.</p>
<p>One of my first medical records projects was in the 90&#8242;s and the goal was to communicate the statistics of procedures performed by doctors particularly in the area of the &#8216;plumbing&#8217;. The overwhelming and alarming conclusion of the data was that there were a lot of doctors performing procedures which they were unqualified to perform, based on the results of tests interpreted by personnel unqualified to interpret them after being administered by others untrained and unqualified to carry out such tests.</p>
<p>The experience, which was for a world leader in the field to present at a global conference, left me with a strong and lingering fear of medical treatment. Things haven&#8217;t changed. I certainly would like to see improvements in medical services. </p>
<p>Perhaps one good thing about a potential central record data store is that potential patient/victims may at least check whether their doctor is so qualified, and their level of experience in the particular procedure, and whoever trained them, along with the experiences of the patients, even those who perhaps fail to survive the patient experience.</p>
<p>Of course this will open up a big can of worms for lawyers, liability, marketing tactics etc.<br />
Far be it from me to suggest that perhaps that would be as good a place to start as any, if you want to start storing medical records and making them publicly available.</p>
<p>The data on procedures is readily and generally electronically available, is easily sanitised for patient privacy, and would ensure that patients can encourage doctors to be better qualified and educated.</p>
<p>Perhaps this might be a nice project for google to cut it&#8217;s teeth on. If google can perform that, with no doubt, much litigation from doctors, then perhaps afterwards they my be given the chance to handle actual patient records.</p>
<p>Our objective is better patient outcomes for fewer dollars isn&#8217;t it?</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: e-Patient Dave</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16767</link>
		<dc:creator>e-Patient Dave</dc:creator>
		<pubDate>Tue, 14 Apr 2009 00:50:58 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16767</guid>
		<description>Someone who signs herself SusanF has commented on the blog of John Halamka, my hospital&#039;s CIO. Susan, I can&#039;t reach you (no contact info on the comment), but I hope it&#039;s okay that I further broadcast what you said there. John&#039;s post was titled &lt;a href=&quot;http://geekdoctor.blogspot.com/2009/04/limitations-of-administrative-data.html&quot; rel=&quot;nofollow&quot;&gt;The Limitations of Administrative Data&lt;/a&gt;. Susan&#039;s comment:

=====

No kidding - the limits. Six degrees of separation is more like it. 

1. The US took a system which was largely created for mortality reporting and made a clinical modification so it would be useful for morbidity too. 

2. It is required to be reported for billing. 

3. Payment policy is designed around the codes. 

4. True use of the codes changes dependent upon the payment policies of the insurance company (not supposed to happen under HIPAA, but check with your billing office). 

5. ICD-9 is now over 30 years old because ICD-10 implementation, which would help, was delayed for a decade because the transition would be too hard. 

6. Now its supposed to somehow be used for true clinical condition feedback to the patients. 

It&#039;s like we are trying to use a PC with 64MB of memory to support the EHR. It just won&#039;t work very well.</description>
		<content:encoded><![CDATA[<p>Someone who signs herself SusanF has commented on the blog of John Halamka, my hospital&#8217;s CIO. Susan, I can&#8217;t reach you (no contact info on the comment), but I hope it&#8217;s okay that I further broadcast what you said there. John&#8217;s post was titled <a href="http://geekdoctor.blogspot.com/2009/04/limitations-of-administrative-data.html" rel="nofollow">The Limitations of Administrative Data</a>. Susan&#8217;s comment:</p>
<p>=====</p>
<p>No kidding &#8211; the limits. Six degrees of separation is more like it. </p>
<p>1. The US took a system which was largely created for mortality reporting and made a clinical modification so it would be useful for morbidity too. </p>
<p>2. It is required to be reported for billing. </p>
<p>3. Payment policy is designed around the codes. </p>
<p>4. True use of the codes changes dependent upon the payment policies of the insurance company (not supposed to happen under HIPAA, but check with your billing office). </p>
<p>5. ICD-9 is now over 30 years old because ICD-10 implementation, which would help, was delayed for a decade because the transition would be too hard. </p>
<p>6. Now its supposed to somehow be used for true clinical condition feedback to the patients. </p>
<p>It&#8217;s like we are trying to use a PC with 64MB of memory to support the EHR. It just won&#8217;t work very well.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: SusannahFox</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-50137</link>
		<dc:creator>SusannahFox</dc:creator>
		<pubDate>Mon, 13 Apr 2009 18:06:43 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-50137</guid>
		<description>&lt;span class=&quot;topsy_trackback_comment&quot;&gt;&lt;span class=&quot;topsy_twitter_username&quot;&gt;&lt;span class=&quot;topsy_trackback_content&quot;&gt;Catch up #3: @ePatientDave unpacks the role of encoded information in health I.T. http://is.gd/s65x&lt;/span&gt;&lt;/span&gt;</description>
		<content:encoded><![CDATA[<p><span class="topsy_trackback_comment"><span class="topsy_twitter_username"><span class="topsy_trackback_content">Catch up #3: @ePatientDave unpacks the role of encoded information in health I.T. <a href="http://is.gd/s65x" rel="nofollow">http://is.gd/s65x</a></span></span></span></p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Gilles Frydman</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16677</link>
		<dc:creator>Gilles Frydman</dc:creator>
		<pubDate>Mon, 13 Apr 2009 16:00:25 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16677</guid>
		<description>Dave&#039;s story has succeeded in having me do a 180 degree turn. 

I think we&#039;ll be much safer having our health &amp; medical data hosted by Google/Microsoft or whoever ends up being the main provider of cloud-based PHRs than what currently exists.

At least with Google we&#039;ll end up having some way to control the information, unlike today where we are completely at the mercy of a few people who tell great stories at conferences and would make you believe that current EHR can have great positive impact on the quality of care. As with everything else in Medicine we should adopt a strict &quot;Verify and then Trust&quot; policy regarding all statements made about the capabilities of the existing EHRs. It would be nice to get some idea if they are almost pure EBR (I like Dave Electronic Billing Record. Sounds better than Electronic Reimbursement Record) or if they can also be used for more useful purposes.

It is possible that some of the people involved in the design and implementation of EHRs are following our conversations. It would be nice to see them provide some answers. 

Like everything else in today&#039;s world, in our post G. Bush time, transparency about hospital EHR should be an absolute requirement. Anything else will just provide great opportunities for investigative journalism.  There is just too much that rest on having effective EHRs to keep relying on &lt;a href=&quot;http://e-patients.net/archives/2008/06/participatory-medicine-an-end-to-rational-ignorance-in-medicine.html&quot; rel=&quot;nofollow&quot;&gt;rational ignorance&lt;/a&gt;.</description>
		<content:encoded><![CDATA[<p>Dave&#8217;s story has succeeded in having me do a 180 degree turn. </p>
<p>I think we&#8217;ll be much safer having our health &amp; medical data hosted by Google/Microsoft or whoever ends up being the main provider of cloud-based PHRs than what currently exists.</p>
<p>At least with Google we&#8217;ll end up having some way to control the information, unlike today where we are completely at the mercy of a few people who tell great stories at conferences and would make you believe that current EHR can have great positive impact on the quality of care. As with everything else in Medicine we should adopt a strict &#8220;Verify and then Trust&#8221; policy regarding all statements made about the capabilities of the existing EHRs. It would be nice to get some idea if they are almost pure EBR (I like Dave Electronic Billing Record. Sounds better than Electronic Reimbursement Record) or if they can also be used for more useful purposes.</p>
<p>It is possible that some of the people involved in the design and implementation of EHRs are following our conversations. It would be nice to see them provide some answers. </p>
<p>Like everything else in today&#8217;s world, in our post G. Bush time, transparency about hospital EHR should be an absolute requirement. Anything else will just provide great opportunities for investigative journalism.  There is just too much that rest on having effective EHRs to keep relying on <a href="http://e-patients.net/archives/2008/06/participatory-medicine-an-end-to-rational-ignorance-in-medicine.html" rel="nofollow">rational ignorance</a>.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Procter</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16668</link>
		<dc:creator>Dean Procter</dc:creator>
		<pubDate>Mon, 13 Apr 2009 14:32:56 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16668</guid>
		<description>Dave, I was under the impression that advertising is how google is going to be able to generously provide the service, assuming their shareholders eventually want dividends they need to charge some way. As for ignoring ads, sure Dave, you&#039;ve just been diagnosed with disease Z and google knows, so next minute you&#039;ll have the screen telling you &quot;Dave 87% of patients who take DrugA report improvement in symptoms&quot;, Click to buy. I&#039;m sure they&#039;ll link you to a doctor somewhere willing to prescribe it to you if you can&#039;t convince your own. 
Suffering patients are particularly susceptible to such advertising.

I don&#039;t propose starting with the hardest task first, merely improving the processes where we can without forcing people to learn new things or do more than they do now. Perhaps relieve them of some of the load and they can put some time into arriving at a common language for both treatment and billing. I am not sure that coding is going to be the easiest place to gain efficiencies or improved outcomes in treatment.

I do agree that there has to be some form of common language for billing, but a common language is not the easiest way to make improvements in health care, and I would seek to pursue the easiest gains first.

Perhaps I see the priority as who, what, when, why, who paid. The billers obviously see it from another angle. Google Health sees it from the view of how do they get their hands on all that valuable data, and get it into their system so you have to visit them to see it, and see the advertisers ads. 
That&#039;s the real world of health records, but not a doctor or patient priority.
The doctors and patients want their accurate records available for treatment, not marketing or research primarily.
Who is the patient? the doctor? google health has neither the correct diagnosis nor the prescription to satisfy the primary concerns of either.

I put it to you, just because we have a super modern warehouse with all the data in it doesn&#039;t mean that patient outcomes will be better. It has little effect on the personnel and patients in the real world. To improve patient care we must seek to improve the processes that those personnel participate in, and where the information is stored is of little relevance when you are staring at a screen, what is relevant is whether they are the right records for the right person and that you have the right to access them. If that can be properly established, all else follows. Providers will be able to compete to provide records storage services and if it is easier and more efficient then customers will use their services, but it makes little difference where the records are if the mechanism to share them is in place.
Everyone is in danger of being distracted. Electronic records make sense, provided they are safely stored and adequately backed up and google may one day provide a better service than their competitors, but until all the newly created records and the old ones are digitised (impossible) there will be gaps, errors and ommissions. Simply tipping all the records into a barrel, albeit a sophisticated search enabled one, will not suffice.
While no-one can argue that e-records can improve efficiencies, they can also degrade services in the short term unless properly conceived and executed.
That means we need to improve our current processes so that whatever we build upon is a solid foundation for achieving our real goals, better outcomes and lower costs.
While others herd the cats, I&#039;ll streamline their processes so they have a little time to listen to your message and learn new things.</description>
		<content:encoded><![CDATA[<p>Dave, I was under the impression that advertising is how google is going to be able to generously provide the service, assuming their shareholders eventually want dividends they need to charge some way. As for ignoring ads, sure Dave, you&#8217;ve just been diagnosed with disease Z and google knows, so next minute you&#8217;ll have the screen telling you &#8220;Dave 87% of patients who take DrugA report improvement in symptoms&#8221;, Click to buy. I&#8217;m sure they&#8217;ll link you to a doctor somewhere willing to prescribe it to you if you can&#8217;t convince your own.<br />
Suffering patients are particularly susceptible to such advertising.</p>
<p>I don&#8217;t propose starting with the hardest task first, merely improving the processes where we can without forcing people to learn new things or do more than they do now. Perhaps relieve them of some of the load and they can put some time into arriving at a common language for both treatment and billing. I am not sure that coding is going to be the easiest place to gain efficiencies or improved outcomes in treatment.</p>
<p>I do agree that there has to be some form of common language for billing, but a common language is not the easiest way to make improvements in health care, and I would seek to pursue the easiest gains first.</p>
<p>Perhaps I see the priority as who, what, when, why, who paid. The billers obviously see it from another angle. Google Health sees it from the view of how do they get their hands on all that valuable data, and get it into their system so you have to visit them to see it, and see the advertisers ads.<br />
That&#8217;s the real world of health records, but not a doctor or patient priority.<br />
The doctors and patients want their accurate records available for treatment, not marketing or research primarily.<br />
Who is the patient? the doctor? google health has neither the correct diagnosis nor the prescription to satisfy the primary concerns of either.</p>
<p>I put it to you, just because we have a super modern warehouse with all the data in it doesn&#8217;t mean that patient outcomes will be better. It has little effect on the personnel and patients in the real world. To improve patient care we must seek to improve the processes that those personnel participate in, and where the information is stored is of little relevance when you are staring at a screen, what is relevant is whether they are the right records for the right person and that you have the right to access them. If that can be properly established, all else follows. Providers will be able to compete to provide records storage services and if it is easier and more efficient then customers will use their services, but it makes little difference where the records are if the mechanism to share them is in place.<br />
Everyone is in danger of being distracted. Electronic records make sense, provided they are safely stored and adequately backed up and google may one day provide a better service than their competitors, but until all the newly created records and the old ones are digitised (impossible) there will be gaps, errors and ommissions. Simply tipping all the records into a barrel, albeit a sophisticated search enabled one, will not suffice.<br />
While no-one can argue that e-records can improve efficiencies, they can also degrade services in the short term unless properly conceived and executed.<br />
That means we need to improve our current processes so that whatever we build upon is a solid foundation for achieving our real goals, better outcomes and lower costs.<br />
While others herd the cats, I&#8217;ll streamline their processes so they have a little time to listen to your message and learn new things.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: e-Patient Dave</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16656</link>
		<dc:creator>e-Patient Dave</dc:creator>
		<pubDate>Mon, 13 Apr 2009 13:05:00 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16656</guid>
		<description>Dean,

Yeah, I first heard GIGO several (ahem) decades ago. :&#8211;) You should go back and read my previous post, where I twisted GIGO to &quot;Garbage &lt;i&gt;out&lt;/i&gt; [of the old system], garbage &lt;i&gt;in&lt;/i&gt;&quot; [to the new one].

Gilles, you are one step ahead of me.  Just this weekend as I thought about this post I was reflecting on &quot;Wait a minute, if this vocabulary was developed for disease statistics, why on earth is it being used for billing??&quot;  And indeed, one major missing factor is that the vocabulary has no way to encode &quot;testing for this condition&quot; vs &quot;has this condition&quot; or &quot;suspect he might have this condition.&quot;  That would be a pretty fundamental thing to build into something that was &lt;i&gt;designed&lt;/i&gt; for accurate billing.

Dean, what are you talking about with &quot;ad-supported&quot;?  I don&#039;t recall seeing ads in Google Health, but besides, I have no difficulty ignoring ads that I don&#039;t care about.  Besides, Google&#039;s not the point here. The point is the accuracy of my medical records. (And yours of course.)</description>
		<content:encoded><![CDATA[<p>Dean,</p>
<p>Yeah, I first heard GIGO several (ahem) decades ago. :&ndash;) You should go back and read my previous post, where I twisted GIGO to &#8220;Garbage <i>out</i> [of the old system], garbage <i>in</i>&#8221; [to the new one].</p>
<p>Gilles, you are one step ahead of me.  Just this weekend as I thought about this post I was reflecting on &#8220;Wait a minute, if this vocabulary was developed for disease statistics, why on earth is it being used for billing??&#8221;  And indeed, one major missing factor is that the vocabulary has no way to encode &#8220;testing for this condition&#8221; vs &#8220;has this condition&#8221; or &#8220;suspect he might have this condition.&#8221;  That would be a pretty fundamental thing to build into something that was <i>designed</i> for accurate billing.</p>
<p>Dean, what are you talking about with &#8220;ad-supported&#8221;?  I don&#8217;t recall seeing ads in Google Health, but besides, I have no difficulty ignoring ads that I don&#8217;t care about.  Besides, Google&#8217;s not the point here. The point is the accuracy of my medical records. (And yours of course.)</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dean Procter</title>
		<link>http://e-patients.net/archives/2009/04/part-of-it-is-encoding-information.html/comment-page-1#comment-16654</link>
		<dc:creator>Dean Procter</dc:creator>
		<pubDate>Mon, 13 Apr 2009 12:45:01 +0000</pubDate>
		<guid isPermaLink="false">http://e-patients.net/?p=1839#comment-16654</guid>
		<description>Hi Dave,
In IT we had an expression GIGO - garbage in - garbage out. Clearly medical &#039;records&#039; are not always medical records, rather they&#039;re billing records. Garbage when it comes to treatment.

There are many issues with what google proposes, the chief one being why would you need to give them your records, or create any other copy of them, merely to share them with someone you have authorised to treat you?

Security is a serious issue, not effectively addressed by google or any other proposer of a central storage system.

A central &#039;permission system&#039; is what is required, as part of a medical system which automatically provides only those with a need and your permission, to access your records, wherever they are. This might include insurance, VA, government, employer, doctor, doctor&#039;s receptionist,medical researcher, all with different levels of access, but provided through a central &#039;permission system&#039; with your knowledge and permission.

The core function of the permission system would be authenticating the participants and providing the path to the information, without ever holding the information. It&#039;s fairly obvious that a doctor isn&#039;t interested in the patients billing information, rather the clinical information. 
Role based authentication would make it easier, more efficient and minimise confusion by not drawing conclusions from codes, or bills, and providing less distraction for the particular user.

Moving everyone&#039;s medical data to a central &#039;warehouse&#039; will not improve patient care.

The primary area where we can effect an improvement in treatment is correctly identifying the patient, then we can locate the required records, provide better accountability for treatment costs, reduce fraud and generally provide better outcomes.

Reduction of costs through efficiencies in billing and fraud control will improve patient outcomes. Streamlining and securing payment and claims processes and reducing paperwork for medical personnel will improve patient care.

These are the areas we should be focusing on, not a google-type ad supported medical records warehouse which provides little improvements in patient care whilst significantly increasing the risk of error, loss of data and privacy and additional costs for heathcare providers and consumers.

By all means leave your records where they are, and of course upgrade doctors to electronic systems, but teaching every medical practitioner to speak in codes is a gross waste of education brainpower and resources.
They already speak a language perfectly adequate to provide treatment. Make the system fit them, not the other way around.
Best regards.

DR Procter
deanprocter@transinteract.com</description>
		<content:encoded><![CDATA[<p>Hi Dave,<br />
In IT we had an expression GIGO &#8211; garbage in &#8211; garbage out. Clearly medical &#8216;records&#8217; are not always medical records, rather they&#8217;re billing records. Garbage when it comes to treatment.</p>
<p>There are many issues with what google proposes, the chief one being why would you need to give them your records, or create any other copy of them, merely to share them with someone you have authorised to treat you?</p>
<p>Security is a serious issue, not effectively addressed by google or any other proposer of a central storage system.</p>
<p>A central &#8216;permission system&#8217; is what is required, as part of a medical system which automatically provides only those with a need and your permission, to access your records, wherever they are. This might include insurance, VA, government, employer, doctor, doctor&#8217;s receptionist,medical researcher, all with different levels of access, but provided through a central &#8216;permission system&#8217; with your knowledge and permission.</p>
<p>The core function of the permission system would be authenticating the participants and providing the path to the information, without ever holding the information. It&#8217;s fairly obvious that a doctor isn&#8217;t interested in the patients billing information, rather the clinical information.<br />
Role based authentication would make it easier, more efficient and minimise confusion by not drawing conclusions from codes, or bills, and providing less distraction for the particular user.</p>
<p>Moving everyone&#8217;s medical data to a central &#8216;warehouse&#8217; will not improve patient care.</p>
<p>The primary area where we can effect an improvement in treatment is correctly identifying the patient, then we can locate the required records, provide better accountability for treatment costs, reduce fraud and generally provide better outcomes.</p>
<p>Reduction of costs through efficiencies in billing and fraud control will improve patient outcomes. Streamlining and securing payment and claims processes and reducing paperwork for medical personnel will improve patient care.</p>
<p>These are the areas we should be focusing on, not a google-type ad supported medical records warehouse which provides little improvements in patient care whilst significantly increasing the risk of error, loss of data and privacy and additional costs for heathcare providers and consumers.</p>
<p>By all means leave your records where they are, and of course upgrade doctors to electronic systems, but teaching every medical practitioner to speak in codes is a gross waste of education brainpower and resources.<br />
They already speak a language perfectly adequate to provide treatment. Make the system fit them, not the other way around.<br />
Best regards.</p>
<p>DR Procter<br />
<a href="mailto:deanprocter@transinteract.com">deanprocter@transinteract.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

