<?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:media="http://search.yahoo.com/mrss/"
	>
<channel>
	<title>Comments on: Jump-Starting Health IT: Best $20 Billion You’ll Ever Spend</title>
	<atom:link href="http://ehrdecisions.com/2009/01/16/jump-starting-health-it-best-20-billion-you%e2%80%99ll-ever-spend/feed/" rel="self" type="application/rss+xml" />
	<link>http://ehrdecisions.com/2009/01/16/jump-starting-health-it-best-20-billion-you%e2%80%99ll-ever-spend/</link>
	<description>Electronic Health Record (EHR) information and news</description>
	<lastBuildDate>Wed, 23 Jun 2010 06:22:33 -0700</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.0</generator>
	<item>
		<title>By: James Wyckoff</title>
		<link>http://ehrdecisions.com/2009/01/16/jump-starting-health-it-best-20-billion-you%e2%80%99ll-ever-spend/comment-page-1/#comment-194</link>
		<dc:creator>James Wyckoff</dc:creator>
		<pubDate>Fri, 06 Feb 2009 20:50:07 +0000</pubDate>
		<guid isPermaLink="false">http://ehrdecisions.com/?p=188#comment-194</guid>
		<description>How long will this take? Former HHS chief Tommy Thompson announce a 10-year plan in 2004, and are we nearly halfway there? I doubt it...</description>
		<content:encoded><![CDATA[<p>How long will this take? Former HHS chief Tommy Thompson announce a 10-year plan in 2004, and are we nearly halfway there? I doubt it&#8230;</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: RDGelzer</title>
		<link>http://ehrdecisions.com/2009/01/16/jump-starting-health-it-best-20-billion-you%e2%80%99ll-ever-spend/comment-page-1/#comment-178</link>
		<dc:creator>RDGelzer</dc:creator>
		<pubDate>Thu, 29 Jan 2009 22:23:37 +0000</pubDate>
		<guid isPermaLink="false">http://ehrdecisions.com/?p=188#comment-178</guid>
		<description>So much progress, such immense promise, such and exciting time ahead for health care and for our country&#039;s citizens&#039; many windfalls from a more efficient and effective industry.  Still, many problems remain among them is making sure that the point of care record is trustworthy according to existing rules, regulations, and standards for medical records and for business records.  As that is accomplished we discover the need to adapt old rules and generate new ones specific to assuring data quality in EHRs.   Perhaps we should at least make sure EHRs conform to existing rules for electronic records before we implement them everywhere for everyone?  These are roadmapped requirements for future  CCHIT Certification requirements, but they are not comprehensively present yet, with stepwise improvements mapped out to 2010 and beyond.  Today, though, even retaining the original version of an amended record (certainly a very basic authenticity requirement) is not due to become a Certification requirement (for Ambulatory) until this calendar year.

We&#039;re making huge leaps forward, let&#039;s make sure these systems are at least built capable of trustworthiness before we subsidize further acceleration of their implementation.   Since we cannot yet assure a trustworthy record today, we gain a huge additional increment in national value by making sure that foundational requirement is met before we push forward to hard, too fast.   Before we &quot;wed&quot; ourselves too irreversibly to the EHR vision, let&#039;s contemplate that old saw, &quot;Marry in Haste, Repent at Leisure&quot;.

RDGelzer, MD, MPH, CHCC
Advocates for Documentation Integrity and Compliance
Volunteer-CCHIT Privacy and Compliance WG
Volunteer-HL7 EHR-S Functional Model WG on the Records Management-Evidentiary Support Profile</description>
		<content:encoded><![CDATA[<p>So much progress, such immense promise, such and exciting time ahead for health care and for our country&#8217;s citizens&#8217; many windfalls from a more efficient and effective industry.  Still, many problems remain among them is making sure that the point of care record is trustworthy according to existing rules, regulations, and standards for medical records and for business records.  As that is accomplished we discover the need to adapt old rules and generate new ones specific to assuring data quality in EHRs.   Perhaps we should at least make sure EHRs conform to existing rules for electronic records before we implement them everywhere for everyone?  These are roadmapped requirements for future  CCHIT Certification requirements, but they are not comprehensively present yet, with stepwise improvements mapped out to 2010 and beyond.  Today, though, even retaining the original version of an amended record (certainly a very basic authenticity requirement) is not due to become a Certification requirement (for Ambulatory) until this calendar year.</p>
<p>We&#8217;re making huge leaps forward, let&#8217;s make sure these systems are at least built capable of trustworthiness before we subsidize further acceleration of their implementation.   Since we cannot yet assure a trustworthy record today, we gain a huge additional increment in national value by making sure that foundational requirement is met before we push forward to hard, too fast.   Before we &#8220;wed&#8221; ourselves too irreversibly to the EHR vision, let&#8217;s contemplate that old saw, &#8220;Marry in Haste, Repent at Leisure&#8221;.</p>
<p>RDGelzer, MD, MPH, CHCC<br />
Advocates for Documentation Integrity and Compliance<br />
Volunteer-CCHIT Privacy and Compliance WG<br />
Volunteer-HL7 EHR-S Functional Model WG on the Records Management-Evidentiary Support Profile</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Stephen Wilson</title>
		<link>http://ehrdecisions.com/2009/01/16/jump-starting-health-it-best-20-billion-you%e2%80%99ll-ever-spend/comment-page-1/#comment-175</link>
		<dc:creator>Stephen Wilson</dc:creator>
		<pubDate>Thu, 29 Jan 2009 05:22:31 +0000</pubDate>
		<guid isPermaLink="false">http://ehrdecisions.com/?p=188#comment-175</guid>
		<description>Dr Leavitt&#039;s letter captures the terrific energy that should properly go with President Obama&#039;s pronouncements. 

I would like to add an observation as a practitioner of security in e-health systems.  In embracing Personal Health Records, and planning their security and privacy, we need to take special care with Health Identifiers.  

The current state of user authentication and Health ID management puts patients accessing their own PHRs at enormous risk.  Conventional username-and-password log on leaves users utterly vulnerable to ID theft, phishing and pharming (where users are drawn to what appears to be a legitimate EHR website but which is in fact a criminal enterprise trying to elicit the user&#039;s personal details). 

Health IDs (and PHR user account details) need to be treated with the utmost care; they must be safeguarded against unauthorised usage, especially theft and replay.  The replay of stolen identity data now is rife in the payments system; at least $5billion of Card Not Present payment fraud happens every year, fueled by a thriving black market in stolen account details.  Witness the recent highly organised attacks on Heartland Payment Systems and the TJX department stores, which netted organised criminals tens of millions of ID records.  

The lesson for healthcare systems is to pay attention not only to access control mechanisms but also the &lt;i&gt;pedigree&lt;/i&gt; of identifiers.  How do we know that a given Health ID really pertains to a singular individual? And that it has been provided willfully to a carer or an information system? And how can we be sure without invading the patient&#039;s privacy by having them play &quot;Twenty Questions&quot; every time they want access? 

Simple password access to internet banking services is already widely superseded in the finance sector. The health sector needs to go one step better than banking, for the perils are so much greater.  In e-health we must adopt uniform two factor and &lt;i&gt;non replayable&lt;/i&gt; authentication of users accessing their own EHRs.  The US federal government&#039;s authentication guidelines expressly address these issues; NIST SP800-63 &quot;Electronic Authentication Guideline&quot; is very useful.  It sets the bar higher than we&#039;re accustomed to in personal internet security, but I think there is no room for error when it comes to PHRs. 

If we think that PHRs are crucial to the future of healthcare, then we&#039;re going to have to treat them as part of the national infrastructure, and invest in personal safety measures accordingly. 

Stephen Wilson
Lockstep Technologies.</description>
		<content:encoded><![CDATA[<p>Dr Leavitt&#8217;s letter captures the terrific energy that should properly go with President Obama&#8217;s pronouncements. </p>
<p>I would like to add an observation as a practitioner of security in e-health systems.  In embracing Personal Health Records, and planning their security and privacy, we need to take special care with Health Identifiers.  </p>
<p>The current state of user authentication and Health ID management puts patients accessing their own PHRs at enormous risk.  Conventional username-and-password log on leaves users utterly vulnerable to ID theft, phishing and pharming (where users are drawn to what appears to be a legitimate EHR website but which is in fact a criminal enterprise trying to elicit the user&#8217;s personal details). </p>
<p>Health IDs (and PHR user account details) need to be treated with the utmost care; they must be safeguarded against unauthorised usage, especially theft and replay.  The replay of stolen identity data now is rife in the payments system; at least $5billion of Card Not Present payment fraud happens every year, fueled by a thriving black market in stolen account details.  Witness the recent highly organised attacks on Heartland Payment Systems and the TJX department stores, which netted organised criminals tens of millions of ID records.  </p>
<p>The lesson for healthcare systems is to pay attention not only to access control mechanisms but also the <i>pedigree</i> of identifiers.  How do we know that a given Health ID really pertains to a singular individual? And that it has been provided willfully to a carer or an information system? And how can we be sure without invading the patient&#8217;s privacy by having them play &#8220;Twenty Questions&#8221; every time they want access? </p>
<p>Simple password access to internet banking services is already widely superseded in the finance sector. The health sector needs to go one step better than banking, for the perils are so much greater.  In e-health we must adopt uniform two factor and <i>non replayable</i> authentication of users accessing their own EHRs.  The US federal government&#8217;s authentication guidelines expressly address these issues; NIST SP800-63 &#8220;Electronic Authentication Guideline&#8221; is very useful.  It sets the bar higher than we&#8217;re accustomed to in personal internet security, but I think there is no room for error when it comes to PHRs. </p>
<p>If we think that PHRs are crucial to the future of healthcare, then we&#8217;re going to have to treat them as part of the national infrastructure, and invest in personal safety measures accordingly. </p>
<p>Stephen Wilson<br />
Lockstep Technologies.</p>
]]></content:encoded>
	</item>
</channel>
</rss>
