<?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; computers</title>
	<atom:link href="http://www.mtexchange.com/tag/computers/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 transcription offshore</title>
		<link>http://www.mtexchange.com/medical-transcription-exchange/medical-transcription-offshore/</link>
		<comments>http://www.mtexchange.com/medical-transcription-exchange/medical-transcription-offshore/#comments</comments>
		<pubDate>Tue, 19 Apr 2011 03:46:42 +0000</pubDate>
		<dc:creator>JulieW8</dc:creator>
				<category><![CDATA[Medical Transcription Exchange]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[EMR]]></category>
		<category><![CDATA[healthcare IT]]></category>
		<category><![CDATA[HIPAA]]></category>
		<category><![CDATA[HITECH]]></category>
		<category><![CDATA[medical transcription]]></category>
		<category><![CDATA[medical transcriptionists]]></category>
		<category><![CDATA[offshoring]]></category>
		<category><![CDATA[overseas]]></category>
		<category><![CDATA[privacy]]></category>
		<category><![CDATA[security]]></category>

		<guid isPermaLink="false">http://www.mtexchange.com/?p=1389</guid>
		<description><![CDATA[The comments generated by the article on MT Stars&#8217; and offshore ownership got me thinking about the whole sticky wicket that constitutes the anti-offshore sentiment in the US medical transcription community. Donna Littrell questioned the use of my time in addressing the issue. I&#8217;ve been in the discussion forums online for a long, long time [...]]]></description>
			<content:encoded><![CDATA[<p><a href="http://www.mtexchange.com/wp-content/uploads/2011/04/flag.jpg"><img class="alignleft size-full wp-image-1383" style="margin: 5px;" title="big american flag" src="http://www.mtexchange.com/wp-content/uploads/2011/04/flag.jpg" alt="Medical Transcription Exchange" width="300" height="214" /></a>The comments generated by the article on <a href="http://www.mtexchange.com/74z" target="_blank">MT Stars&#8217; and offshore ownership</a> got me thinking about the whole sticky wicket that constitutes the anti-offshore sentiment in the US medical transcription community.</p>
<p>Donna Littrell questioned the use of my time in addressing the issue. I&#8217;ve been in the discussion forums online for a long, long time &#8211; and questioning someone&#8217;s effective use of time in pursuing a line of discussion is intended to stop a conversation, similar to <a href="http://en.wikipedia.org/wiki/Godwin%27s_law" target="_blank"><em>Godwin&#8217;s Law</em></a>:</p>
<blockquote><p>As an online discussion grows longer, the probability of a comparison involving Nazis or Hitler approaches.</p></blockquote>
<p>Were I to posit <em>Julie&#8217;s Law</em> (well, <em>Laws</em>, since there has to be more than one), it would be that as soon as someone reaches the point where they cannot logically defend their position, they will call into question the use of time of (a) the original poster, (b) other participants in the conversation, and then declare THEY don&#8217;t have time for this nonsense, so they&#8217;re done discussing it.</p>
<p>So, I decided to address a topic that is surely dear to the heart of the founder of ATA and its members: anti-offshoring attitudes and policies in the medical transcription community.</p>
<p>Let me start by relating an incident that happened to me many years ago, when offshoring first became an issue. At that time, I was paying for a listing in a publication that listed medical trancription services. (I believe this publication is now defunct, but I have the 2003 and 2004 directories, which is like looking through a registration of gravestones.) I received a solicitation in the mail about listing my service, filled it out and sent a check. I was subsequently contacted by the editor, who told me they would be unable to list my business in the directory because they had a policy against listing companies that were involved with offshoring work and they believed I was sending work overseas. I asked the editor to point out to me where in their contract this policy was stated. She stuttered and stammered a bit before admitting the policy wasn&#8217;t written. She also couldn&#8217;t tell me when the policy had been put into place. Then, I asked her how they were verifying whether or not a company sent work overseas. Signed affadavits? Audit? Not to my surprise, there was no verification process. Obviously, with no verification process and no written policy, the <em>policy</em> was being unevenly applied. In fact, I had the prior year&#8217;s directory and I pointed out to her all the companies that were listed that were sending work overseas and/or doing training overseas. I asked her if she really wanted to go down this road, at which point she decided that maybe, in fact, they would allow my business to be listed in the directory.</p>
<p>The editor admitted that her reason for attempting to deny my listing was based on posts I&#8217;d made in medical transcription forums that she felt were supportive off offshoring. Aside from that, whether or not I was sending work overseas isn&#8217;t  the point. Even if this editor had had a written policy, there was no way to verify the accuracy of any information. And, as I&#8217;m going to discuss, application of any policy is, by its very nature, difficult to impossible to uniformly apply.</p>
<p>How far is someone who is anti-offshore willing to go to stand by their principles and <em>walk the walk</em>? This is where things get sticky.</p>
<p>First of all, how does an individual or organization verify the uniquely <em>nationalist</em> work ethic and policies of a company or individual? Take their word on it? Ask for copies of contracts? Not having a process in place to verify the truthfulness or accuracy of claims is the same as having a contract with no early termination penalty; it&#8217;s a nice framework for working together, but pretty toothless. The organization formerly known as MTIA based its membership categories (and dues) on revenue, and members were required to submit financials. At least they&#8217;re asked to prove a positive &#8211; how do you prove a negative?</p>
<p>In spite of my belief that absent a method of independent verification, these policies are worthless, I&#8217;ll continue&#8230;</p>
<p>How far is an organization or individual willing to go to <em>walk the walk</em> and back up their beliefs and/or policies? Refuse to work for a company that sends work offshore? Boycott publications that accept advertising from companies that send work offshore? Boycott websites that are owned by offshore interests and/or have advertisers that are offshore or send work offshore? Refuse to accept advertising  from companies that are involved with offshore transcription? Boycott vendors that sell their products and services to offshore companies or companies that send work offshore?</p>
<p>The possibilities seem endless, don&#8217;t they?</p>
<p>Over the years, anti-offshore sentiment has evolved to center around privacy and security issues. HIPAA and HITECH have strengthened this argument &#8211; and I believe it is a valid concern. Looking at significant HIPAA breaches over the past year reveals that out of over 260 incidents reported that affect 500 or more individuals, only 3 involved transcription services. For more information, you can read <a href="http://www.mtexchange.com/srh" target="_blank">Brenda Hurley&#8217;s summary</a>. Right now, I&#8217;m feeling like I ought to contact Gair Transcription and offer to do some consulting about their online presence &#8211; aside from their address (in the US), Google search results returned only information about this breach. But here&#8217;s my favorite part &#8211; they exposed PHI on the internet for <strong>over 2 years</strong>! &lt;thud&gt; I don&#8217;t even know if any of these companies are involved with overseas transcription, but since these breaches occurred on their servers, it&#8217;s really a moot point.</p>
<p>Quite frankly, I&#8217;m more concerned about hackers in Russia than I am about transcription contractors in India.</p>
<p>To drive the sticky wicket in even further, we might be able to make an issue over whether or not these companies utilized overseas <em>website maintenance and programming</em>. Whether or not there was a breach, any overseas contractor maintaining the website would have access to the same information a transcriptionist would have &#8211; probably more. Is that something medical transcriptionists object to, or are they leaving that issue for the US programmers? In fact, according to Dr. Ahmed, he worked on the website design and programming for MT Stars. Is anyone concerned that their personal information is being exposed to someone in Pakistan who might do God-knows-what with it, or are they all using fake and throwaway e-mail addresses, so they don&#8217;t care? <img src='http://www.mtexchange.com/wp-includes/images/smilies/icon_wink.gif' alt=';-)' class='wp-smiley' />  Does anyone ever wonder if their company website is programmed overseas? Maybe ATA should add a membership restriction that includes using offshore programmers, since they&#8217;re concerned for the security and privacy of American&#8217;s data.</p>
<p>There are healthcare providers who don&#8217;t have a problem with the privacy and security issues of sending transcription overseas. There are medical transcription companies that feel the privacy and security measures they have in place meet the requirements, even for overseas employees and/or contractors. The fact that there has been no large breaches involving overseas contractors supports the confidence these companies have in their policies and procedures for dealing with offshore workers. Where I <strong>do</strong> feel problems may arise are in situations where a small MTSO or an independent MT may not have adequate measures in place when transmitting PHI to small MTSOs or independent contractors offshore. Ultimately, however, the US entity will be the one on the hook &#8211; and the US entity will have to decide whether or not the risks are worth the benefits.</p>
<p>When I look at the <em>So What Can We Do?</em> recommendations in the ATA&#8217;s <a href="http://www.mtexchange.com/jut" target="_blank">open letter on offshoring</a>, I see an effort that is well-intentioned, but rather naïve. In reality, what Americans (in fact, most people worldwide) are willing to give up in terms of privacy is changing at an incredible rate of speed. You could close your social network and e-mail and all other online accounts and log off the internet permanently &#8211; and there would still be a huge volume of information about you available on the internet. It might even all be contained on servers within the borders of the United States of America. The fact is, you can&#8217;t control what others do and how they conduct their business. Your information is being tracked in hundreds, if not thousands, of different ways. If we limit the conversation to <em>only</em> your medical information, your doctor, the hospital, the laboratory, the pharmacy and your healthcare insurance carrier are only the starting point. The largest reported HIPAA breach so far this year is being reported by <em>HealthNet</em> &#8211; a large insurance carrier.</p>
<p>When we bank online, watch the pharmacist verify our insurance information and medication record on the computer and watch the doctor send our records to the hospital with a push of the button, pay a credit card online, hand a discount card to the cashier at the grocery store &#8211; and a host of other electronic events that have become ubiquitous in our day-to-day lives &#8211; we are relying on the company we&#8217;re entrusting with our personal and financial information and that it has made every effort, even extraordinary efforts, to safeguard that information. Not just because they can be sued, but because their interests in safeguarding that information align with our own. Even though we are aware that there is a possibility that our information could be stolen, we have consciously or unconsciously weighed the risks and decided the benefits are greater than the risk.</p>
<p>Which brings me back to that sticky wicket. It&#8217;s pretty obvious to me  that at some point we have to accept that in the medical transcription  industry, we can&#8217;t possibly boycott everything that touches the offshore  transcription industry. And we can&#8217;t prove a negative. At whatever point a person or organization  comes to that realization, they have to either set limits they can live  with &#8211; or start rationalizing  and defending the  inconsistency between their actions and their stated principles.</p>
<div id="_mcePaste" class="mcePaste" style="position: absolute; left: -10000px; top: 427px; width: 1px; height: 1px; overflow: hidden;">If one has the time to hunt down this type of information, just imagine  what you could do if you focused on a positive issue for the  transcription industry.  Our industry is being battered from all sides.  We need to support each other and keep moving forward. It’s too easy to  sit back and whine and complain about every little thing, because you  will always have people who will commisurate with you – misery loves  company. That’s a reason I do not follow the transcription boards (this  one included). I only found out about this issue because I received an  email. There’s enough negativity in this world. Our energy would be  better spent if we put our heads together and combined our efforts so  the future of our industry, as changing as it is, will be something we  can all live with.<span class="Apple-style-span" style="border-collapse: separate; color: #000000; font-family: 'Times New Roman'; font-style: normal; font-variant: normal; font-weight: normal; letter-spacing: normal; line-height: normal; orphans: 2; text-indent: 0px; text-transform: none; white-space: normal; widows: 2; word-spacing: 0px; font-size: medium;"><span class="Apple-style-span" style="color: #111111; font-family: Arial,'Helvetica Neue',Helvetica,sans-serif; font-size: 13px; line-height: 20px;">&nbsp;</p>
<p style="padding: 0px; margin: 0px 0px 1.538em;">Transcriptionists and Transcription Companies also have the following obligations:</p>
<ul style="padding: 0px; margin: 0px 0px 1.538em 1.538em; list-style-type: square;">
<li style="padding: 0px; margin: 0px;">Must be a 100% U.S. company or individual</li>
<li style="padding: 0px; margin: 0px;">Must perform all transcription work in-house OR subcontract only to U.S. employees/individuals legally working within the U.S.</li>
<li style="padding: 0px; margin: 0px;">Must not subcontract any transcription work overseas</li>
<li style="padding: 0px; margin: 0px;">Must not subcontract any transcription work to companies that subcontract transcription work overseas</li>
</ul>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p>&nbsp;</p>
<p></span></span></div>
]]></content:encoded>
			<wfw:commentRss>http://www.mtexchange.com/medical-transcription-exchange/medical-transcription-offshore/feed/</wfw:commentRss>
		<slash:comments>14</slash:comments>
		</item>
		<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>
		<item>
		<title>I am not a guru</title>
		<link>http://www.mtexchange.com/medical-transcription-exchange/i-am-not-a-guru/</link>
		<comments>http://www.mtexchange.com/medical-transcription-exchange/i-am-not-a-guru/#comments</comments>
		<pubDate>Sat, 24 Jan 2009 21:19:59 +0000</pubDate>
		<dc:creator>JulieW8</dc:creator>
				<category><![CDATA[Medical Transcription Exchange]]></category>
		<category><![CDATA[applications]]></category>
		<category><![CDATA[computers]]></category>
		<category><![CDATA[programs]]></category>
		<category><![CDATA[software]]></category>

		<guid isPermaLink="false">http://www.mtexchange.com/?p=430</guid>
		<description><![CDATA[I had someone gush this week that I&#8217;m a guru. Wanna know why? I read the help file. Yes, that&#8217;s all it took. Someone asked for help with something, I didn&#8217;t know the answer &#8211; so I read the application help file. If that&#8217;s all it takes to be a guru &#8211; and there&#8217;s lots [...]]]></description>
			<content:encoded><![CDATA[<p>I had someone gush this week that I&#8217;m a guru.</p>
<p>Wanna know why?</p>
<p>I read the help file.</p>
<p>Yes, that&#8217;s all it took. Someone asked for help with something, I didn&#8217;t know the answer &#8211; so I read the application help file.</p>
<p>If that&#8217;s all it takes to be a guru &#8211; and there&#8217;s lots of money involved &#8211; count me in.</p>
<p>Folks, if you want to know how to use your computer and the applications on it &#8211; read the messages on the screen, read the help file and be willing to take some time to push a few buttons and see what happens. Don&#8217;t worry &#8211; I could be a professional button-pusher and I haven&#8217;t blown up my computer yet, so you should be pretty safe.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtexchange.com/medical-transcription-exchange/i-am-not-a-guru/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>

