<?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; Visible black character &#8211; cracks in the concrete</title>
	<atom:link href="http://www.mtexchange.com/medical-transcription-exchange/visible-black-character-cracks-in-the-concrete/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>Visible black character &#8211; cracks in the concrete</title>
		<link>http://www.mtexchange.com/medical-transcription-exchange/visible-black-character-cracks-in-the-concrete/</link>
		<comments>http://www.mtexchange.com/medical-transcription-exchange/visible-black-character-cracks-in-the-concrete/#comments</comments>
		<pubDate>Mon, 17 Aug 2009 23:11:16 +0000</pubDate>
		<dc:creator>JulieW8</dc:creator>
				<category><![CDATA[Medical Transcription Exchange]]></category>
		<category><![CDATA[AHDI]]></category>
		<category><![CDATA[AHIMA]]></category>
		<category><![CDATA[Joint Committee]]></category>
		<category><![CDATA[MTIA]]></category>
		<category><![CDATA[VBC]]></category>
		<category><![CDATA[visible black character]]></category>

		<guid isPermaLink="false">http://www.mtexchange.com/?p=841</guid>
		<description><![CDATA[Ask me if I am at all surprised to hear there are some issues &#8211; and lots of questions and disagreements &#8211; with the visible black character &#8220;standard&#8221; that was concocted by a joint task force a couple years back. In addition to my first post about this at the old MT Exchange site, I [...]]]></description>
			<content:encoded><![CDATA[<p><img class="alignleft size-full wp-image-842" style="margin: 4px;" title="vbc_cracked" src="http://www.mtexchange.com/wp-content/uploads/2009/08/vbc_cracked.jpg" alt="vbc_cracked" width="210" height="139" />Ask me if I am at all surprised to hear there are some issues &#8211; and lots of questions and disagreements &#8211; with the <a href="http://visibleblackcharacter.com" target="_blank"><strong>visible black character</strong></a> &#8220;<a href="http://www.mtexchange.com/s8k" target="_blank">standard</a>&#8221; that was concocted by a joint task force a couple years back. In addition to <a href="http://www.mtexchange.com/s8k" target="_blank">my first post</a> about this at the old MT Exchange site, I posted a followup earlier this year: <a href="http://www.mtexchange.com/gll" target="_blank">Visible black character, revisited</a>. In addition, I put a web site dedicated to an explanation of the various methods of billing, including the <a href="http://visibleblackcharacter.com" target="_blank">visible black character</a>.</p>
<p>As I had predicted &#8211; there&#8217;s no method that can&#8217;t be manipulated.</p>
<p>Whether the issues arise from manipulation or from the fact that the &#8220;Joint Task Force on Standards Development&#8221; issued a white paper, not a standard, and failed to use actual standard-setting methodology, is debatable. But &#8211; I was catching up on my reading and came across <a href="http://fortherecordmag.com" target="_blank">For the Record</a>&#8216;s article: &#8220;<a href="http://www.fortherecordmag.com/archives/072009p16.shtml" target="_blank">Buyer be Aware</a>.&#8221; I&#8217;m sending a great big thank you to them for putting this online so everyone can read it.</p>
<p>My first bone of contention in this article is some of the quotes attributed to Dale Kivi, director of business development at FutureNet Technologies.</p>
<blockquote><p>While many companies such as SPi say they prefer that providers adopt the VBC method, Kivi suggests that a good deal of the resistance has come from transcriptionists themselves. “Whereas HIM directors have been coming up to speed on adopting VBC, the understanding and acceptance at the MT [medical transcriptionist] level has not progressed as rapidly,” he says. “Some transcriptionists are wary of changing because there have already been so many changes to their compensation. They see any change as something that could reduce their pay for the same volume of work. And because the VBC method eliminates payment for spaces, they worry it will eliminate something from their salary as well, which of course it does not.”</p></blockquote>
<p>Dale, obviously you don&#8217;t work in the trenches. Let&#8217;s count the number of MTs who comment on this and tell me that they were asked to convert to the VBC and either  (a) didn&#8217;t get an increase in line rate to compensate for the lost characters, (b) weren&#8217;t advised that a change to the VBC without a compensatory increase in the rate paid per line would result in reduced pay for more work and/or (c) weren&#8217;t even advised that their company&#8217;s line counting software was being changed to the VBC.</p>
<p>And here we have a promotion of the biggest lie perpetuated by those promoting the VBC:</p>
<blockquote><p>One of the most important benefits of converting to the VBC method is that it allows documents to be easily verifiable. With previous methods, there was room for improper billing practices to take place.</p></blockquote>
<p>I have to keep beating this drum:</p>
<ul>
<li>There are no methods that can&#8217;t be manipulated</li>
<li>Unless someone is counting &#8211; manually &#8211; all the <strong>visible</strong> black characters (note the importance of the word in bold), this method is no more accurate than any other method that uses software to count the billable units.</li>
</ul>
<p>The assertion made by Kivi and others is that the VBC is much easier to audit because &#8220;what you see is what you pay for.&#8221; I would like to know from the industry leaders how many companies are auditing by actually counting the visible characters with no software. Because the bottom line is &#8211; the VBC is only more accurate if you actually sit and count each visible character on the document you are auditing and only easier if you were using an abacus to verify your invoices prior to going to the VBC.</p>
<p>Oh &#8211; but wait! Read on in the article and you see where the cracks are starting to show in the stressed-out &#8220;standard.&#8221;</p>
<blockquote><p>Of course, nothing is ever 100% foolproof, and there are  some bones of contention even when using VBCs.</p></blockquote>
<p>Do tell!</p>
<blockquote><p>“Headers and footers are one issue,” says Cohen [president of SPi Healthcare]. “Some clients are OK with counting headers and footers across all pages, since they are visual characters, while others may insist on counting the first page only.”</p></blockquote>
<p>What a surprise &#8211; some people want to have their cake and eat it, too! Look, folks &#8211; either you pay for all the characters you see on each and every page &#8211; or this &#8220;standard&#8221; starts on that slippery slope to join the calculated line. It seems the demographics are joining the headers and footers on that slippery slope. It doesn&#8217;t at all surprise me that this issue has come up. There were reasons why the calculated line was abused and those reasons still exist in the industry. Those reasons didn&#8217;t go anywhere just because a joint committee got together and came up with a new way of counting billable units. At fault are both parties involved in the transaction (you know who you are).</p>
<p>Now here&#8217;s what I find to be the real kicker in the whole article:</p>
<blockquote><p>Kivi agrees that it’s important for both parties to be clear about these types of details to avoid the perception that the transcription service is attempting to sneak something under the radar. In that regard, he considers communication to be a key to better billing.</p></blockquote>
<p>No s***, Sherlock. And if this was the case across the board, there wouldn&#8217;t be a need for the VBC.</p>
<p>Back to my bottom line: you can use any method of calculating a billable unit as long as it is transparent and verifiable.</p>
<p>Oh yeah &#8211; and I&#8217;m just never going to understand how any of these people can claim the VBC is easier to verify. I&#8217;m begging Kivi or anyone else to explain it to me.</p>
]]></content:encoded>
			<wfw:commentRss>http://www.mtexchange.com/medical-transcription-exchange/visible-black-character-cracks-in-the-concrete/feed/</wfw:commentRss>
		<slash:comments>9</slash:comments>
		</item>
	</channel>
</rss>

