<?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>Medical Claims and Billing &#187; claims</title>
	<atom:link href="http://medicalclaimsandbilling.com/tag/claims/feed/" rel="self" type="application/rss+xml" />
	<link>http://medicalclaimsandbilling.com</link>
	<description>Expert Practice Management Information</description>
	<lastBuildDate>Tue, 23 Feb 2010 18:38:36 +0000</lastBuildDate>
	<generator>http://wordpress.org/?v=2.9.1</generator>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
			<item>
		<title>How to Bill: Facial and Dental Nerve Blocks</title>
		<link>http://medicalclaimsandbilling.com/how-to-bill-facial-and-dental-nerve-blocks/</link>
		<comments>http://medicalclaimsandbilling.com/how-to-bill-facial-and-dental-nerve-blocks/#comments</comments>
		<pubDate>Fri, 12 Feb 2010 07:17:38 +0000</pubDate>
		<dc:creator>Coder</dc:creator>
				<category><![CDATA[How To Bill]]></category>
		<category><![CDATA[claims]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[dental]]></category>

		<guid isPermaLink="false">http://medicalclaimsandbilling.com/?p=29</guid>
		<description><![CDATA[When you have a procedure that can cover two close but distinctly different areas such as a facial and a dental nerve block, you need to make sure that your claim encompasses exactly the procedure that was done or you may wind up with a denial of your claim.
A common situation would be if the [...]]]></description>
			<content:encoded><![CDATA[<p>When you have a procedure that can cover two close but distinctly different areas such as a facial and a dental nerve block, you need to make sure that your claim encompasses exactly the procedure that was done or you may wind up with a denial of your claim.</p>
<p>A common situation would be if the ED physician performed a diagnostic nerve block on a patient complaining of pain in the floor of her mouth and her bottom set of teeth. You would want to be certain that you chose 64402 (Injection, anesthetic agent; facial nerve) for facial nerve blocks, not blocks in the mouth or jaw. The determining factor is that the surgeon treated a branch of the trigeminal nerve, not the facial nerve.  <span id="more-29"></span></p>
<p>On the claim, report 64400 (&#8230; trigeminal nerve, any division or branch) for the nerve block. Other 64400 scenarios: Areas affected by the trigeminal nerve and its branches, and therefore coded with 64400 for nerve blocks, include:</p>
<ul>
<li>the body of the mandible and the lower portion of the ramus</li>
<li>upper and lower teeth</li>
<li>floor of the mouth</li>
<li>anterior two-thirds of the tongue</li>
<li>gingiva on the lingual surface of the mandible</li>
<li>gingiva on the labial surface of the mandible</li>
<li>mucosa and skin of the lower lip and chin.</li>
</ul>
<p>To ensure proper payment, back up your medical billing claim with the proper documentation to show the reason for the facial or dental block and that will allow the carrier to see why this code was chosen along with the necessity of the procedure. This will enable you to realize reimbursements instead of rejections on these type of claims.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalclaimsandbilling.com/how-to-bill-facial-and-dental-nerve-blocks/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Avoid Rejected Claims</title>
		<link>http://medicalclaimsandbilling.com/avoid-rejected-claims/</link>
		<comments>http://medicalclaimsandbilling.com/avoid-rejected-claims/#comments</comments>
		<pubDate>Wed, 06 Jan 2010 08:57:43 +0000</pubDate>
		<dc:creator>Coder</dc:creator>
				<category><![CDATA[Coding Tips]]></category>
		<category><![CDATA[claims]]></category>
		<category><![CDATA[coding]]></category>
		<category><![CDATA[medical billing]]></category>

		<guid isPermaLink="false">http://medicalclaimsandbilling.com/?p=8</guid>
		<description><![CDATA[When your medical billing claims get rejected, one claim can put your staff behind on everything they are supposed to be doing.  The patient&#8217;s folder will have to be pulled, the notes will have to be re-read and researched, the claim will have to be compiled again and the coding will need to be double [...]]]></description>
			<content:encoded><![CDATA[<p>When your medical billing claims get rejected, one claim can put your staff behind on everything they are supposed to be doing.  The patient&#8217;s folder will have to be pulled, the notes will have to be re-read and researched, the claim will have to be compiled again and the coding will need to be double checked again to make sure you are using the latest codings and modifiers for the claim. In some cases the carrier will need to be contacted which is more time lost from servicing your practice and the claim will have to be submitted once again and the will take more time away from your day to day servicing of patients.  <span id="more-8"></span></p>
<p>If you&#8217;re ready to get rid of the hassles that a rejected claim or multiple claims can cause, it might be time to consider outsourcing your medical billing claims to a third party partner that can get your claims submitted, double check your billing and get your reimbursements.</p>
<p>The beautiful thing about outsourcing your medical billing claims is the average return rate due to errors is less than 1%. Plus you&#8217;ll see up to 25% of your reimbursements increased due to your claims being handled in an efficient manner. Best of all, your staff will be free to help you run your practice instead of chasing paperwork for medical billing claims.</p>
]]></content:encoded>
			<wfw:commentRss>http://medicalclaimsandbilling.com/avoid-rejected-claims/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
	</channel>
</rss>
