<?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: Another experience at the ER</title>
	<atom:link href="http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/feed/" rel="self" type="application/rss+xml" />
	<link>http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/</link>
	<description>eHealth, innovation, and health care</description>
	<lastBuildDate>Sat, 21 Jan 2012 14:04:34 +0000</lastBuildDate>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
	<item>
		<title>By: Hans</title>
		<link>http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/comment-page-1/#comment-2177</link>
		<dc:creator>Hans</dc:creator>
		<pubDate>Fri, 16 Jan 2009 16:33:29 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/#comment-2177</guid>
		<description>Hi Betsy,
Thanks for the well thought out comment. Not much to say except that things need to get better, especially if the goal of an EHR in five years is to be realized (Obama/Bush).
Hans.</description>
		<content:encoded><![CDATA[<p>Hi Betsy,<br />
Thanks for the well thought out comment. Not much to say except that things need to get better, especially if the goal of an EHR in five years is to be realized (Obama/Bush).<br />
Hans.</p>
]]></content:encoded>
	</item>
	<item>
		<title>By: Betsy</title>
		<link>http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/comment-page-1/#comment-2041</link>
		<dc:creator>Betsy</dc:creator>
		<pubDate>Thu, 20 Nov 2008 20:23:51 +0000</pubDate>
		<guid isPermaLink="false">http://blog.hansoh.com/2008/11/18/another-experience-at-the-er/#comment-2041</guid>
		<description>What has to be done to get clinicians to adopt ehealth is to have clinicians involved in developing the programs. And then to deveop programs that work. That can lessen the workload, not increase it.  The program writers should be on the floor, shadowing the docs, nurses, social workers, therapists, etc, while they work with sick people, in all areas of care.  Then they can create programs which flow with the clinical work, not against it.  Where documenting in the e chart is easier than writing on the piece of paper.  There is always the assumption that the clinical staff is rigid, hates change, just won&#039;t cooperate with moving forward.  This as opposed to the possibility that they are given a pep talk by people who have no idea how to do what they do, and then left alone to struggle with cumbersome, unintelligent programs that begin to feel like another ailing patient to be assessed, diagnosed, and treated. 
 I recently communicated with a clinician whose hospital&#039;s new &#039;echart&#039; was going to be read from oldest to newest.  Anyone in healthcare knows that we have always had the most recent entries first-because in an emergency, that&#039;s how we need to review the record for efficiency and accuracy.  The person who decided to design the flow &#039;backwards&#039; had never had to use a medical record for clinical care, I&#039;m here to tell you!  
We should be creating a record that is, first of all things, a clinical tool, and then make certain that the clinical tool incorporates all regulatory elements. There is always a clinical reason behind any regulation.  Whether the legal department or the accreditation department or the IRB wrote the reg, there was a clinical situation that necessitated that reg.  I hate hearing staff say: &quot;oh, that&#039;s just a document.  That&#039;s just paperwork for xyz.&quot;  And, I think it&#039;s demoralizing for people who do such important work to feel that the extensive documenting and  reporting they do is just wasted space. While people who love to heal, to be around people and interact with them in a therapeutic way may never fall in love with charting,  I think we can teach clinicians how to make recording a vital part of what they do, to own it and see it&#039;s worth (beyond I&#039;ll get fired if I don&#039;t...) even be made to feel as proud of their documentation as they are of their clinical work.  In order for this miracle to occur, though, I think that the front-line clinicians, the ones who actually care for  the patients, day in and day out must be a much greater part of designing the system we use. What if, for example, you could use the same documentation you created on mrs. X in rm 3455 to e-mail the order for her non-contrast MRI?  What if you could auto-fill the discharge instructions?  What if you could instant message the on-call doc, and so perform the communication and the documentation of the communication in one action?  Then, when the Doc orders a new drug during that communication, you could email or efax the order to the pharmacy?  And then, from the same computer, download and print out patient information leaflet on the medicine to help with teaching?  These are the kinds of things that take so much of a nurses or therapists or social workers time.  We have to go from one computer to another, close one program open another, then track down the paper chart to write it all down in...if you could see the 4 different e-record systems in my institution that we must work from simultaneously, you would cry.  At the incredible redundancy, except for some very primary but very minimal types of data that can&#039;t be gotten from one to another program.  And how the incalulable potential for increasing utility-for research, for administration, for quality assurance-is completely dashed by the design of these systems.  I know there has to be someone who can do it-who can design a truly elegant system that meets the needs of the staff using it and, ultimately, the patients whose care depends on it, while providing the regulators all the documentation they need to assure that the care is excellent.  We have to aim higher, and we have to include the front-line staff in the process from the start-not just as a marketing afterthought, to hand to a couple of day-shift nurses to &#039;try out&#039; for a week and then supply commentary.  Or worse, fill out an evaluation questionnaire!</description>
		<content:encoded><![CDATA[<p>What has to be done to get clinicians to adopt ehealth is to have clinicians involved in developing the programs. And then to deveop programs that work. That can lessen the workload, not increase it.  The program writers should be on the floor, shadowing the docs, nurses, social workers, therapists, etc, while they work with sick people, in all areas of care.  Then they can create programs which flow with the clinical work, not against it.  Where documenting in the e chart is easier than writing on the piece of paper.  There is always the assumption that the clinical staff is rigid, hates change, just won&#8217;t cooperate with moving forward.  This as opposed to the possibility that they are given a pep talk by people who have no idea how to do what they do, and then left alone to struggle with cumbersome, unintelligent programs that begin to feel like another ailing patient to be assessed, diagnosed, and treated.<br />
 I recently communicated with a clinician whose hospital&#8217;s new &#8216;echart&#8217; was going to be read from oldest to newest.  Anyone in healthcare knows that we have always had the most recent entries first-because in an emergency, that&#8217;s how we need to review the record for efficiency and accuracy.  The person who decided to design the flow &#8216;backwards&#8217; had never had to use a medical record for clinical care, I&#8217;m here to tell you!<br />
We should be creating a record that is, first of all things, a clinical tool, and then make certain that the clinical tool incorporates all regulatory elements. There is always a clinical reason behind any regulation.  Whether the legal department or the accreditation department or the IRB wrote the reg, there was a clinical situation that necessitated that reg.  I hate hearing staff say: &#8220;oh, that&#8217;s just a document.  That&#8217;s just paperwork for xyz.&#8221;  And, I think it&#8217;s demoralizing for people who do such important work to feel that the extensive documenting and  reporting they do is just wasted space. While people who love to heal, to be around people and interact with them in a therapeutic way may never fall in love with charting,  I think we can teach clinicians how to make recording a vital part of what they do, to own it and see it&#8217;s worth (beyond I&#8217;ll get fired if I don&#8217;t&#8230;) even be made to feel as proud of their documentation as they are of their clinical work.  In order for this miracle to occur, though, I think that the front-line clinicians, the ones who actually care for  the patients, day in and day out must be a much greater part of designing the system we use. What if, for example, you could use the same documentation you created on mrs. X in rm 3455 to e-mail the order for her non-contrast MRI?  What if you could auto-fill the discharge instructions?  What if you could instant message the on-call doc, and so perform the communication and the documentation of the communication in one action?  Then, when the Doc orders a new drug during that communication, you could email or efax the order to the pharmacy?  And then, from the same computer, download and print out patient information leaflet on the medicine to help with teaching?  These are the kinds of things that take so much of a nurses or therapists or social workers time.  We have to go from one computer to another, close one program open another, then track down the paper chart to write it all down in&#8230;if you could see the 4 different e-record systems in my institution that we must work from simultaneously, you would cry.  At the incredible redundancy, except for some very primary but very minimal types of data that can&#8217;t be gotten from one to another program.  And how the incalulable potential for increasing utility-for research, for administration, for quality assurance-is completely dashed by the design of these systems.  I know there has to be someone who can do it-who can design a truly elegant system that meets the needs of the staff using it and, ultimately, the patients whose care depends on it, while providing the regulators all the documentation they need to assure that the care is excellent.  We have to aim higher, and we have to include the front-line staff in the process from the start-not just as a marketing afterthought, to hand to a couple of day-shift nurses to &#8216;try out&#8217; for a week and then supply commentary.  Or worse, fill out an evaluation questionnaire!</p>
]]></content:encoded>
	</item>
</channel>
</rss>

