<?xml version="1.0" encoding="UTF-8"?>
<rss version="2.0"
	xmlns:content="http://purl.org/rss/1.0/modules/content/"
	xmlns:wfw="http://wellformedweb.org/CommentAPI/"
	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:slash="http://purl.org/rss/1.0/modules/slash/"
	>

<channel>
	<title>MT Exchange &#187; Medical transcriptionist takes a hit for HIPAA</title>
	<atom:link href="http://www.mtexchange.com/medical-transcription-exchange/medical-transcriptionist-takes-a-hit-for-hipaa/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.mtexchange.com</link>
	<description>Medical transcription exchange</description>
	<lastBuildDate>Thu, 03 Nov 2011 14:22:05 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
<xhtml:meta xmlns:xhtml="http://www.w3.org/1999/xhtml" name="robots" content="noindex" />
		<item>
		<title>Medical transcriptionist takes a hit for HIPAA</title>
		<link>http://www.mtexchange.com/medical-transcription-exchange/medical-transcriptionist-takes-a-hit-for-hipaa/</link>
		<comments>http://www.mtexchange.com/medical-transcription-exchange/medical-transcriptionist-takes-a-hit-for-hipaa/#comments</comments>
		<pubDate>Tue, 15 Dec 2009 02:21:18 +0000</pubDate>
		<dc:creator>JulieW8</dc:creator>
				<category><![CDATA[Medical Transcription Exchange]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[EMR]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[HITECH]]></category>
		<category><![CDATA[medical transcription]]></category>
		<category><![CDATA[pay rates]]></category>
		<category><![CDATA[QA]]></category>
		<category><![CDATA[quality]]></category>
		<category><![CDATA[transcription]]></category>

		<guid isPermaLink="false">http://www.mtexchange.com/?p=1050</guid>
		<description><![CDATA[I recently received an e-mail from a transcriptionist who described a situation that I think will surprise most medical transcriptionists. It&#8217;s an issue I found especially interesting in light of a post by Nae at MT Chat, and the responses it got: Yep, my ESP is working real well today doc &#8230; I hadn&#8217;t even [...]]]></description>
			<content:encoded><![CDATA[<p>I recently received an e-mail from a transcriptionist who described a situation that I think will surprise most medical transcriptionists. It&#8217;s an issue I found especially interesting in light of a post by Nae at MT Chat, and the responses it got: <a href="http://www.mtexchange.com/dw6" target="_blank">Yep, my ESP is working real well today doc &#8230;</a></p>
<p>I hadn&#8217;t even discussed this with Nae, so when she posted that thread, she was not aware of this MT&#8217;s e-mail to me.</p>
<p>Let me preface this by saying there are usually 2 sides to a story and I only have one, so my conclusions are going to be based on that. I&#8217;m not going to name names, but if any MTSOs have had a similar experience from their side, or if you&#8217;re in management and you think this is your company, I&#8217;d like to hear the &#8220;other&#8221; side.</p>
<p>In a nutshell, an MT who was being paid a premium line rate because of her experience and skills on multiple accounts, was demoted due to &#8220;potential reportable events&#8221; (PREs) involving privacy and security breaches.</p>
<p>The reason? Selecting the wrong doctor as attending, and sending a copy to the wrong physician. In the first case, the error was noted by the MT, but too late &#8211; the report had already been sent in, at which point it was immediately distributed. Even though the MT sent an e-mail, noting the error, this error was counted in the disciplinary action that was taken against her. In the second instance, the name dictated sounded almost exactly like another name &#8211; and the MT selected the incorrect name.</p>
<p>As amusing as it is to say &#8220;we can&#8217;t read your mind, doc,&#8221; I&#8217;m wondering if some of the people responding to that post at MT Chat want to rethink their answer. Although Nae&#8217;s example is &#8220;send a copy to Dr. Patel,&#8221; in a case where there are multiple doctors with that name, it could have easily been &#8220;send a copy to Dr. Smith,&#8221; where there are not only multiple Dr. Smiths on a list, but Dr. Smyth, Smythe and etc. All it takes is one large university hospital or VA account to realize there are many, many ways to spell names we all thought had a common spelling, for both patients and physicians. With no training and no physician list, it would be obvious to an MT that picking the correct one among a number of Dr. Patels is impossible and needs to be flagged to QA &#8211; but what about Dr. Carter v. Karter? If someone says &#8220;send a copy to John Carter&#8221; and you find a John Carter on the roster &#8211; would you look any further to see if there was also a John Karter and therefore flag the report to someone up the food chain?</p>
<p>In my opinion, there were a couple of errors that occurred prior to the MT making the error.</p>
<ol>
<li>It was a new account and no training was given.</li>
<li>No physician list was provided, including a list of attendings and their fellows or residents.</li>
<li>The MT company has no written policy regarding PREs and how they will be handled.</li>
<li>The MT company has no written policy regarding disciplinary action to be taken in the case of MT errors of this kind.</li>
<li>No software safeguards are in place.</li>
<li>As is usually the case, training for dictators at the facility also appears to be substandard &#8211; GIGO.</li>
</ol>
<p>Some of these seem like no-brainers, don&#8217;t they? I don&#8217;t know how anyone can be expected to perform with minimal errors on a new account without any direction or instructions, regardless of how experienced they are. An experienced MT may be able to pick up and transcribe any dictator at any facility &#8211; but years of experience is going to give an MT the ability to somehow instinctively grasp account specifics.</p>
<p>This is not a small company, this MT is not an independent contractor. The disciplinary action taken cut the MT&#8217;s pay by 20% to 25% <em>yet </em><em>there&#8217;s no written policy in place</em>. No inservice on HIPAA, no training on the account, no written disciplinary policy &#8211; but with no warning, the company takes action that cuts pay 25%.</p>
<p>Hello, MT employees &#8211; have you asked your employer what <strong>the written policy is for <em>your</em> company</strong>? What happens when a mistake like this happens? What are your responsibilities? What disciplinary action may be taken against you? What recourse do you have?</p>
<p>Technology being what it is, why doesn&#8217;t the EMR software &#8211; that same software that immediately routes the transcript to all interested parties upon completion by the MT <em>unless</em> it&#8217;s flagged &#8211; have some safeguards built in? I realize that EMR technology is evolving, but is anyone doing anything to ensure that copies don&#8217;t go to Dr. Carter if he&#8217;s not involved in the patient&#8217;s care and Dr. Karter is? If not, why not? You&#8217;d think that while everyone is out spending money on streamlining the process and reducing labor costs, they&#8217;d also be doing something to ensure security is more automated. Even a delay of a certain number of minutes would be helpful (something like the 7-second delay on newscasts), so if errors are caught shortly after the report is completed, there&#8217;s some hope of rerouting it before it&#8217;s gone out for distribution.</p>
<p>Are MTs paid enough to take on this kind of responsibility? Are <strong>YOU</strong> paid enough to take on this kind of responsibility? What I see happening is that more and more MTs will send every questionable physician name to QA or to the hospital staff to deal with. Then, someone will get mad &#8211; probably at the MTs. Because it seems nobody is willing to hold the dictators responsible. So here&#8217;s a tip for all you working MTs out there &#8211; unless you&#8217;re 100% certain, flag that report. The sooner these questions start piling up on the desks of people who are actually paid enough to deal with PREs, the sooner the problem will be resolved.</p>
<p>This situation was a FAIL of epic proportions, primarily on the part of the transcription service for not having policies in place, by not having in-service sessions for employees to train in HIPAA compliance and on account specifics. Well, shame on management for taking its shortcomings out on the transcriptionist.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtexchange.com/medical-transcription-exchange/medical-transcriptionist-takes-a-hit-for-hipaa/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

