<?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>Translation Guy &#187; Medicaid</title>
	<atom:link href="http://www.1-800-translate.com/TranslationBlog/tag/medicaid/feed/" rel="self" type="application/rss+xml" />
	<link>http://www.1-800-translate.com/TranslationBlog</link>
	<description>With all the new translation technologies, things have gotten easier, and more complicated.</description>
	<lastBuildDate>Wed, 08 Feb 2012 02:02:16 +0000</lastBuildDate>
	<language>en</language>
	<sy:updatePeriod>hourly</sy:updatePeriod>
	<sy:updateFrequency>1</sy:updateFrequency>
	<generator>http://wordpress.org/?v=3.3.1</generator>
		<item>
		<title>Multilingual Medicaid (Part 3)&#8230; not my fault</title>
		<link>http://www.1-800-translate.com/TranslationBlog/translation/how-multilingual-is-medicare3/</link>
		<comments>http://www.1-800-translate.com/TranslationBlog/translation/how-multilingual-is-medicare3/#comments</comments>
		<pubDate>Fri, 05 Feb 2010 17:23:24 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Translation]]></category>
		<category><![CDATA[bilingual]]></category>
		<category><![CDATA[CSR]]></category>
		<category><![CDATA[interpreters]]></category>
		<category><![CDATA[LEP]]></category>
		<category><![CDATA[LEP caller]]></category>
		<category><![CDATA[Medicaid]]></category>
		<category><![CDATA[medicare]]></category>
		<category><![CDATA[Multilingual]]></category>
		<category><![CDATA[Night Shift]]></category>
		<category><![CDATA[TranslationGuy]]></category>

		<guid isPermaLink="false">http://www.1-800-translate.com/TranslationBlog/?p=518</guid>
		<description><![CDATA[Legislative lip service talks multilingual medical care, for Medicare beneficiaries. But the best intentions of regulators still leaves lots of LEP (Limited English Proficient) patients  in the lurch. According to The California Medicare Part D Language Access Coalition report “Please Hold”, subtitled &#8220;Medicare Plans Leave Limited English Proficient Beneficiaries Waiting for Access,&#8221; getting help when you don&#8217;t [...]]]></description>
		<wfw:commentRss>http://www.1-800-translate.com/TranslationBlog/translation/how-multilingual-is-medicare3/feed/</wfw:commentRss>
		<slash:comments>0</slash:comments>
		</item>
		<item>
		<title>Multilingual Medicaid (Part 2)&#8230; it gets worse</title>
		<link>http://www.1-800-translate.com/TranslationBlog/language/how-multilingual-is-medicare2/</link>
		<comments>http://www.1-800-translate.com/TranslationBlog/language/how-multilingual-is-medicare2/#comments</comments>
		<pubDate>Wed, 03 Feb 2010 21:53:20 +0000</pubDate>
		<dc:creator>Ken</dc:creator>
				<category><![CDATA[Language]]></category>
		<category><![CDATA[bilingual]]></category>
		<category><![CDATA[CSR]]></category>
		<category><![CDATA[interpreters]]></category>
		<category><![CDATA[LEP]]></category>
		<category><![CDATA[LEP caller]]></category>
		<category><![CDATA[Medicaid]]></category>
		<category><![CDATA[Multilingual]]></category>
		<category><![CDATA[Night Shift]]></category>
		<category><![CDATA[TranslationGuy]]></category>

		<guid isPermaLink="false">http://www.1-800-translate.com/TranslationBlog/?p=513</guid>
		<description><![CDATA[How will changes to Medicaid provisions affect care for Limited English Proficient (LEP) beneficiaries? Probably not much, despite considerable room for improvement. Click here for Part 1, where an advocacy group tried to reach out for medical help in languages other than English. The chief finding: Its&#8217; not so easy to find someone who speaks [...]]]></description>
		<wfw:commentRss>http://www.1-800-translate.com/TranslationBlog/language/how-multilingual-is-medicare2/feed/</wfw:commentRss>
		<slash:comments>10</slash:comments>
		</item>
	</channel>
</rss>

