<?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: Electronic Medical Records, Loss of Privacy and Cost Savings</title>
	<atom:link href="http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/</link>
	<description></description>
	<lastBuildDate>Fri, 30 Nov 2012 06:36:35 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
		<item>
		<title>By: Melody Warbington (rwm52)</title>
		<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/#comment-87</link>
		<dc:creator>Melody Warbington (rwm52)</dc:creator>
		<pubDate>Wed, 04 Jul 2012 05:29:17 +0000</pubDate>
		<guid isPermaLink="false">http://www.redstate.com/halsted/?p=76#comment-87</guid>
		<description><![CDATA[I almost posted a &quot;where&#039;s lineholder?&quot; comment because I knew you&#039;d want to respond to this.

Thanks for the input (and check your email).]]></description>
		<content:encoded><![CDATA[<p>I almost posted a &#8220;where&#8217;s lineholder?&#8221; comment because I knew you&#8217;d want to respond to this.</p>
<p>Thanks for the input (and check your email).</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: lineholder</title>
		<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/#comment-86</link>
		<dc:creator>lineholder</dc:creator>
		<pubDate>Wed, 04 Jul 2012 05:20:34 +0000</pubDate>
		<guid isPermaLink="false">http://www.redstate.com/halsted/?p=76#comment-86</guid>
		<description><![CDATA[The provider has to keep a record accessible for patient service, legal and auditing reasons, but backups could be outsourced.  I think the plan is to have records centrally located via Regional Health Information Organizations (RHIOs) along with the possibility of one main centralized database.  

RHIOs is one of the provisions that was included in HITECH when the ONC-HIT was established.  

As to the standards halsted mentions in the diary...those have already been established via HL7, IEEE, and ASTM.  

Some of the information gathered in a hybrid EMRs can&#039;t be accessed via SQL even if the record was included in a centralized database.  Part of the information is entered via computer systems and part of it is simply scanned into an electronic format (like vanghossister describes below).  

Even with large providers, they&#039;ve been hesitant about investing significant funds into setting up a broad scale system that could be used until the transition to ICD-10 takes place because it will alter the data sets that will be used and change user screen formats (along with changing cost centers)  

SMART cards are another option, with patients having downloadable medical records on WORM devices. 

But even if we get to the point of having totally electronic systems, unless CMS changes their rules, there will still be information that doesn&#039;t get recorded in the centralized system.]]></description>
		<content:encoded><![CDATA[<p>The provider has to keep a record accessible for patient service, legal and auditing reasons, but backups could be outsourced.  I think the plan is to have records centrally located via Regional Health Information Organizations (RHIOs) along with the possibility of one main centralized database.  </p>
<p>RHIOs is one of the provisions that was included in HITECH when the ONC-HIT was established.  </p>
<p>As to the standards halsted mentions in the diary&#8230;those have already been established via HL7, IEEE, and ASTM.  </p>
<p>Some of the information gathered in a hybrid EMRs can&#8217;t be accessed via SQL even if the record was included in a centralized database.  Part of the information is entered via computer systems and part of it is simply scanned into an electronic format (like vanghossister describes below).  </p>
<p>Even with large providers, they&#8217;ve been hesitant about investing significant funds into setting up a broad scale system that could be used until the transition to ICD-10 takes place because it will alter the data sets that will be used and change user screen formats (along with changing cost centers)  </p>
<p>SMART cards are another option, with patients having downloadable medical records on WORM devices. </p>
<p>But even if we get to the point of having totally electronic systems, unless CMS changes their rules, there will still be information that doesn&#8217;t get recorded in the centralized system.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: vangoghssister</title>
		<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/#comment-85</link>
		<dc:creator>vangoghssister</dc:creator>
		<pubDate>Wed, 04 Jul 2012 03:11:07 +0000</pubDate>
		<guid isPermaLink="false">http://www.redstate.com/halsted/?p=76#comment-85</guid>
		<description><![CDATA[I work for a large healthcare system in Oklahoma as a transcriptionist. We&#039;ve been working on converting over entirely to EMR (electronic medical record) since before 2008. I have no idea when it will be completed,  but I&#039;m not going to hold my breath in 2014!

My understanding of how an EMR works is within one healthcare system, such as the one I work for, patient records will be available for any physician or their proxy to view immediately. Upon receipt of a release of information request from a healthcare provider outside our system, I believe the pertinent records will be sent as an encrypted file via an e-mail type program. I am not positive about how that works.

As for creating lots of high paying jobs, while that might be true for those involved in the software part of conversion, it is not true after implementation is near completion. All of our old records have been scanned and converted to an electronic format. We have now entered the phase of physician order sets being entered electronically rather than handwritten and scanned in later. We have also entered into the phase of any &quot;real&quot; paper documents being scanned in by unit clerks or nurses on each floor. Our department head is now trying to find enough positions to fill with those who used to scan in paper documents all day so no one loses their job. The more efficient you become, the fewer people are needed. 

I can&#039;t think of anything worse than a centralized bank of medical records &quot;guarded&quot; by our government! What a disaster that would be. 

I would suggest anyone reading this should obtain copies of their personal records and go over them carefully, with your family physician if necessary, to make sure there are no mistakes. The advent of speech &quot;wreckognition&quot; makes this especially important! Mistakes can live in your record for a very long time unless someone thinks to question an entry.]]></description>
		<content:encoded><![CDATA[<p>I work for a large healthcare system in Oklahoma as a transcriptionist. We&#8217;ve been working on converting over entirely to EMR (electronic medical record) since before 2008. I have no idea when it will be completed,  but I&#8217;m not going to hold my breath in 2014!</p>
<p>My understanding of how an EMR works is within one healthcare system, such as the one I work for, patient records will be available for any physician or their proxy to view immediately. Upon receipt of a release of information request from a healthcare provider outside our system, I believe the pertinent records will be sent as an encrypted file via an e-mail type program. I am not positive about how that works.</p>
<p>As for creating lots of high paying jobs, while that might be true for those involved in the software part of conversion, it is not true after implementation is near completion. All of our old records have been scanned and converted to an electronic format. We have now entered the phase of physician order sets being entered electronically rather than handwritten and scanned in later. We have also entered into the phase of any &#8220;real&#8221; paper documents being scanned in by unit clerks or nurses on each floor. Our department head is now trying to find enough positions to fill with those who used to scan in paper documents all day so no one loses their job. The more efficient you become, the fewer people are needed. </p>
<p>I can&#8217;t think of anything worse than a centralized bank of medical records &#8220;guarded&#8221; by our government! What a disaster that would be. </p>
<p>I would suggest anyone reading this should obtain copies of their personal records and go over them carefully, with your family physician if necessary, to make sure there are no mistakes. The advent of speech &#8220;wreckognition&#8221; makes this especially important! Mistakes can live in your record for a very long time unless someone thinks to question an entry.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: acat</title>
		<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/#comment-84</link>
		<dc:creator>acat</dc:creator>
		<pubDate>Wed, 04 Jul 2012 02:22:18 +0000</pubDate>
		<guid isPermaLink="false">http://www.redstate.com/halsted/?p=76#comment-84</guid>
		<description><![CDATA[doesn&#039;t already have that ...

The problem with distributed is the latency.

Let&#039;s suppose Dave Average, who we&#039;ll say lives in Bucks County PA, receives a minor injury.  Let&#039;s suppose Dave Average steps on a rusty nail while cleaning out the garage.  

Dave doesn&#039;t remember his last tetanus shot so the hospital looks it up while they&#039;re cleaning out his foot.  Dave&#039;s last shot was at his physician&#039;s office 3 years ago, Dave&#039;s physician is on the same network service provider as the hospital - since this is all in Bucks County - so the E.R. tells Dave he&#039;s good very quickly.

Now, let&#039;s introduce some latency.  Suppose that, instead of Dave&#039;s garage, it&#039;s his friend Bill&#039;s garage .. and further suppose the garage isn&#039;t in Bucks County, but Hershey.

The Hershey ER sends the query, but they&#039;re on a different network that only send queries to Dave&#039;s physicians&#039; network in batches, 4 times a day.  The last batch just completed when Dave came in, so now Dave has to wait around for 6 hours to find out that he doesn&#039;t need a tetanus shot.

Okay, let&#039;s introduce even more latency.  Dave is now outside the U.S., specifically he&#039;s on vacation in Ixtapa, Mexico.  Now, Ixtapa is a resort town, and their doctors are pretty darn good, but the local E.R. subscribes to a data service that sends their queries in batches, and receives  answers the next day.  Most days.  Dave now has to wait over 24 hours to find out he doesn&#039;t need a tetanus shot.

This is the problem with distributed .. while it&#039;s possible to do the whole thing in realtime, that&#039;s much less efficient, especially as the distance increases and international borders get in the way... so the inevitable service providers.

Yes, hospitals and medical groups and even some doctors offices have an I.T. staff but if the ones near me are an example, they do largely break/fix for the specialized hardware needed, as well as common Windows desktop issues.  

Like businesses with EDI, they&#039;re much more likely to contract this kind of data storage and retrieval out ... and the service provider is going to do whatever they can to lower their costs.

Mew]]></description>
		<content:encoded><![CDATA[<p>doesn&#8217;t already have that &#8230;</p>
<p>The problem with distributed is the latency.</p>
<p>Let&#8217;s suppose Dave Average, who we&#8217;ll say lives in Bucks County PA, receives a minor injury.  Let&#8217;s suppose Dave Average steps on a rusty nail while cleaning out the garage.  </p>
<p>Dave doesn&#8217;t remember his last tetanus shot so the hospital looks it up while they&#8217;re cleaning out his foot.  Dave&#8217;s last shot was at his physician&#8217;s office 3 years ago, Dave&#8217;s physician is on the same network service provider as the hospital &#8211; since this is all in Bucks County &#8211; so the E.R. tells Dave he&#8217;s good very quickly.</p>
<p>Now, let&#8217;s introduce some latency.  Suppose that, instead of Dave&#8217;s garage, it&#8217;s his friend Bill&#8217;s garage .. and further suppose the garage isn&#8217;t in Bucks County, but Hershey.</p>
<p>The Hershey ER sends the query, but they&#8217;re on a different network that only send queries to Dave&#8217;s physicians&#8217; network in batches, 4 times a day.  The last batch just completed when Dave came in, so now Dave has to wait around for 6 hours to find out that he doesn&#8217;t need a tetanus shot.</p>
<p>Okay, let&#8217;s introduce even more latency.  Dave is now outside the U.S., specifically he&#8217;s on vacation in Ixtapa, Mexico.  Now, Ixtapa is a resort town, and their doctors are pretty darn good, but the local E.R. subscribes to a data service that sends their queries in batches, and receives  answers the next day.  Most days.  Dave now has to wait over 24 hours to find out he doesn&#8217;t need a tetanus shot.</p>
<p>This is the problem with distributed .. while it&#8217;s possible to do the whole thing in realtime, that&#8217;s much less efficient, especially as the distance increases and international borders get in the way&#8230; so the inevitable service providers.</p>
<p>Yes, hospitals and medical groups and even some doctors offices have an I.T. staff but if the ones near me are an example, they do largely break/fix for the specialized hardware needed, as well as common Windows desktop issues.  </p>
<p>Like businesses with EDI, they&#8217;re much more likely to contract this kind of data storage and retrieval out &#8230; and the service provider is going to do whatever they can to lower their costs.</p>
<p>Mew</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Dave_A</title>
		<link>http://www.redstate.com/halsted/2012/07/02/electronic-medical-records-loss-of-privacy-and-cost-savings/#comment-83</link>
		<dc:creator>Dave_A</dc:creator>
		<pubDate>Wed, 04 Jul 2012 01:58:58 +0000</pubDate>
		<guid isPermaLink="false">http://www.redstate.com/halsted/?p=76#comment-83</guid>
		<description><![CDATA[The problem with AHLTA is that it&#039;s a unified, centralized database.

The RIGHT way to do it, is to standardize a file-format for health-records, and then make each person&#039;s records transmittable or request-able between medical facilities.

Think something similar to the Web, but for health records, not a centralized database...]]></description>
		<content:encoded><![CDATA[<p>The problem with AHLTA is that it&#8217;s a unified, centralized database.</p>
<p>The RIGHT way to do it, is to standardize a file-format for health-records, and then make each person&#8217;s records transmittable or request-able between medical facilities.</p>
<p>Think something similar to the Web, but for health records, not a centralized database&#8230;</p>
]]></content:encoded>
	</item>
</channel>
</rss>
