
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>MyChart messages for non-English speaking patients</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1692343</link>
<description></description>
<lastBuildDate>Fri, 12 Jun 2026 12:42:37 GMT</lastBuildDate>
<pubDate>Tue, 18 Jul 2023 20:46:35 GMT</pubDate>
<copyright>Copyright &#xA9; 2023 National Association of Healthcare Access Management</copyright>
<atom:link href="https://www.naham.org/forums/topic_rss.asp?id=1692343" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>MyChart messages for non-English speaking patients</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1692343</link>
<guid>https://www.naham.org/forums/posts.aspx?topic=1692343</guid>
<description><![CDATA[Does anyone have any strategies for managing patient messages in MyChart in languages other than English? For instance, if you receive a message written in Spanish from a patient with limited English proficiency, how do you translate it and how do you message back? Do you use Google translate? An interpreter? A staff person with Spanish fluency? We're looking for any innovations or solutions to offer equity in access for these patients. Thank&nbsp; you]]></description>
<pubDate>Mon, 25 Apr 2022 22:31:55 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://www.naham.org/forums/posts.aspx?topic=1745788</link>
<guid>https://www.naham.org/forums/posts.aspx?topic=1745788</guid>
<description><![CDATA[The healthcare standard is that interactions with patients whose first language isn't English should be through a certified interpreter. This is to make sure that the person relaying the information has the correct terminology for medical terms and you know will provide true and accurate information. With messages, it might be easiest to just have the employee call an interpreter and complete any needs over the phone instead of trying to find someone to interpreter and respond to each message. ]]></description>
<pubDate>Tue, 18 Jul 2023 21:46:35 GMT</pubDate>
</item>
</channel>
</rss>
