<?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:georss="http://www.georss.org/georss" xmlns:geo="http://www.w3.org/2003/01/geo/wgs84_pos#" xmlns:media="http://search.yahoo.com/mrss/"
		>
<channel>
	<title>Comments on: Bad Data &amp; PHR Adoption</title>
	<atom:link href="http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/feed/" rel="self" type="application/rss+xml" />
	<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/</link>
	<description>Providing perspective on key IT trends in the healthcare sector</description>
	<lastBuildDate>Mon, 04 Jun 2012 23:53:02 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.com/</generator>
	<item>
		<title>By: Nathan Lake</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-6711</link>
		<dc:creator><![CDATA[Nathan Lake]]></dc:creator>
		<pubDate>Fri, 24 Dec 2010 15:47:01 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-6711</guid>
		<description><![CDATA[I like the CHR approach, but would argue that the PHR/EHR divisions are still relevant...at least in the eyes of the providers. Unfortunately, it is the physicians that  seem to be hesitant to accept a close PHR/EHR integration. There is a widely held belief among many healthcare providers that patients can modify/edit data in the PHR in such a way that future recipients of that data will be unaware of the changes. While this may not be true with many of the PHRs, it is a reasonable fear considering the number of PHRs that have sprung up. With no standards to control their operation, there is nothing to prevent a PHR vendor form allowing it.

In my opinion, proper certification of PHRs is essential to alleviate those fears. It is the healthcare providers that will eventually make the PHR part of a true CHR...and right now, they are not universally on board.

There are widely accepted standards for EHRs being developed, but PHR stardards still lag behind...but we are working on them.]]></description>
		<content:encoded><![CDATA[<p>I like the CHR approach, but would argue that the PHR/EHR divisions are still relevant&#8230;at least in the eyes of the providers. Unfortunately, it is the physicians that  seem to be hesitant to accept a close PHR/EHR integration. There is a widely held belief among many healthcare providers that patients can modify/edit data in the PHR in such a way that future recipients of that data will be unaware of the changes. While this may not be true with many of the PHRs, it is a reasonable fear considering the number of PHRs that have sprung up. With no standards to control their operation, there is nothing to prevent a PHR vendor form allowing it.</p>
<p>In my opinion, proper certification of PHRs is essential to alleviate those fears. It is the healthcare providers that will eventually make the PHR part of a true CHR&#8230;and right now, they are not universally on board.</p>
<p>There are widely accepted standards for EHRs being developed, but PHR stardards still lag behind&#8230;but we are working on them.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: John</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-6710</link>
		<dc:creator><![CDATA[John]]></dc:creator>
		<pubDate>Fri, 24 Dec 2010 15:02:35 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-6710</guid>
		<description><![CDATA[Nathan,
Thanks for your comment and you are correct, knowing where the data comes from and whether or not it has been altered is critical for trust, not only clinician trust in the data but patient/consumer trust as well.

While I have not been a big fan of certification initiatives, such as CCHIT&#039;s for PHRs, there is a need for PHRs to clearly identify the source of PHI in a given PHR - is it clinician derived, patient derived, loved one etc. Such clear data tagging will help build trust on both sides of the current divide.

But more broadly speaking, believe the terms EHR, PHR, etc are artificial. THere is only one record, which we have begun calling a CHR, collaborative health record. Terms such as PHR, EHR create artificial divisions and are no longer relevant.]]></description>
		<content:encoded><![CDATA[<p>Nathan,<br />
Thanks for your comment and you are correct, knowing where the data comes from and whether or not it has been altered is critical for trust, not only clinician trust in the data but patient/consumer trust as well.</p>
<p>While I have not been a big fan of certification initiatives, such as CCHIT&#8217;s for PHRs, there is a need for PHRs to clearly identify the source of PHI in a given PHR &#8211; is it clinician derived, patient derived, loved one etc. Such clear data tagging will help build trust on both sides of the current divide.</p>
<p>But more broadly speaking, believe the terms EHR, PHR, etc are artificial. THere is only one record, which we have begun calling a CHR, collaborative health record. Terms such as PHR, EHR create artificial divisions and are no longer relevant.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Nathan Lake</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-6708</link>
		<dc:creator><![CDATA[Nathan Lake]]></dc:creator>
		<pubDate>Thu, 23 Dec 2010 03:48:35 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-6708</guid>
		<description><![CDATA[I am a member of the HL7 EHR, PHR and RM-ES (Records Management and Evidentiary Support) workgroups. Discussions there are now focusing less on accuracy and more on source control. There will always be inaccurate information in a patient&#039;s EHR and PHR. Of course we need to do what we can to minimize inaccuracy, but it will always be  there. What is more important (in my opinion and that of others) is that the source of the information be known to any reader/recipient. Mistrust by clinicians of PHR data is more closely tied to uncertainly of the data source than it is to questions of its accuracy. 

If the recipient is able to reliably identify the source of the data, he/she is able to make a decision about how much trust they put on the data. Without knowing the source, the accuracy is a moot point since it almost certainly will not be trusted.]]></description>
		<content:encoded><![CDATA[<p>I am a member of the HL7 EHR, PHR and RM-ES (Records Management and Evidentiary Support) workgroups. Discussions there are now focusing less on accuracy and more on source control. There will always be inaccurate information in a patient&#8217;s EHR and PHR. Of course we need to do what we can to minimize inaccuracy, but it will always be  there. What is more important (in my opinion and that of others) is that the source of the information be known to any reader/recipient. Mistrust by clinicians of PHR data is more closely tied to uncertainly of the data source than it is to questions of its accuracy. </p>
<p>If the recipient is able to reliably identify the source of the data, he/she is able to make a decision about how much trust they put on the data. Without knowing the source, the accuracy is a moot point since it almost certainly will not be trusted.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: PHR Package &#38; Reconcile &#124; Beacon 16</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-5507</link>
		<dc:creator><![CDATA[PHR Package &#38; Reconcile &#124; Beacon 16]]></dc:creator>
		<pubDate>Wed, 28 Jul 2010 21:13:29 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-5507</guid>
		<description><![CDATA[[...] Bad Data &amp; PHR Adoption « Chilmark Research. [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Bad Data &amp; PHR Adoption « Chilmark Research. [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: sanjaygidwani.net &#187; Consider The Source</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-4140</link>
		<dc:creator><![CDATA[sanjaygidwani.net &#187; Consider The Source]]></dc:creator>
		<pubDate>Sat, 12 Dec 2009 19:16:03 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-4140</guid>
		<description><![CDATA[[...] addition, as John Chilmark points out ICD-9 is &#8220;limited&#8221; (full article). Problem is, claims data is based on limited code sets (ICD-9) that physicians use for [...]]]></description>
		<content:encoded><![CDATA[<p>[...] addition, as John Chilmark points out ICD-9 is &#8220;limited&#8221; (full article). Problem is, claims data is based on limited code sets (ICD-9) that physicians use for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Consider the Source</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-3659</link>
		<dc:creator><![CDATA[Consider the Source]]></dc:creator>
		<pubDate>Mon, 21 Sep 2009 19:04:27 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-3659</guid>
		<description><![CDATA[[...] the PHR, if only billing data was used.In addition, as John Chilmark points out ICD-9 is &quot;limited&quot; (full article). Problem is, claims data is based on limited code sets (ICD-9) that physicians use for [...]]]></description>
		<content:encoded><![CDATA[<p>[...] the PHR, if only billing data was used.In addition, as John Chilmark points out ICD-9 is &quot;limited&quot; (full article). Problem is, claims data is based on limited code sets (ICD-9) that physicians use for [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Tethered PHRs: Cutting the Umbilical Cord &#171; Chilmark Research</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-2805</link>
		<dc:creator><![CDATA[Tethered PHRs: Cutting the Umbilical Cord &#171; Chilmark Research]]></dc:creator>
		<pubDate>Wed, 13 May 2009 21:51:36 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-2805</guid>
		<description><![CDATA[[...] While there has been some recent publicity on bad data that may exist in even a provider sponsored PHR, by and large the data therein is better and certainly more useful than what you&#8217;ll find in [...]]]></description>
		<content:encoded><![CDATA[<p>[...] While there has been some recent publicity on bad data that may exist in even a provider sponsored PHR, by and large the data therein is better and certainly more useful than what you&#8217;ll find in [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Health 2.0: A lot of Hot Air in This Balloon &#171; Chilmark Research</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-2685</link>
		<dc:creator><![CDATA[Health 2.0: A lot of Hot Air in This Balloon &#171; Chilmark Research]]></dc:creator>
		<pubDate>Mon, 27 Apr 2009 23:05:15 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-2685</guid>
		<description><![CDATA[[...] Halamka and Roni Zeiger were very open and transparent as to what went wrong when e-Patient Dave tried to move his Personal Health Information (PHI) into Google Health.  Halamka stated that it was a mistake to allow transfer of admin data, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] Halamka and Roni Zeiger were very open and transparent as to what went wrong when e-Patient Dave tried to move his Personal Health Information (PHI) into Google Health.  Halamka stated that it was a mistake to allow transfer of admin data, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Bad Data Saga Continues &#171; Chilmark Research</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-2622</link>
		<dc:creator><![CDATA[Bad Data Saga Continues &#171; Chilmark Research]]></dc:creator>
		<pubDate>Wed, 15 Apr 2009 16:10:19 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-2622</guid>
		<description><![CDATA[[...] 15, 2009 by John    Since our post on Monday, where we highlighted the potential impact to PHR adoption of the Boston Globe story on one consumer&#8217;s less than ideal experience with Google Health, [...]]]></description>
		<content:encoded><![CDATA[<p>[...] 15, 2009 by John    Since our post on Monday, where we highlighted the potential impact to PHR adoption of the Boston Globe story on one consumer&#8217;s less than ideal experience with Google Health, [...]</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Jim</title>
		<link>http://chilmarkresearch.com/2009/04/13/bad-data-amp-phr-adoption/#comment-2601</link>
		<dc:creator><![CDATA[Jim]]></dc:creator>
		<pubDate>Tue, 14 Apr 2009 15:26:06 +0000</pubDate>
		<guid isPermaLink="false">http://chilmarkresearch.com/?p=1504#comment-2601</guid>
		<description><![CDATA[Added to &lt;a href=&quot;http://EHRLinks.com&quot; rel=&quot;nofollow&quot;&gt;EHRLinks.com&lt;/a&gt;]]></description>
		<content:encoded><![CDATA[<p>Added to <a href="http://EHRLinks.com" rel="nofollow">EHRLinks.com</a></p>
]]></content:encoded>
	</item>
</channel>
</rss>

