
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Patient wrist banding with self-service devices</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1750067</link>
<description></description>
<lastBuildDate>Fri, 12 Jun 2026 12:19:44 GMT</lastBuildDate>
<pubDate>Sun, 31 Dec 2023 18:59:12 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=1750067" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Patient wrist banding with self-service devices</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1750067</link>
<guid>https://www.naham.org/forums/posts.aspx?topic=1750067</guid>
<description><![CDATA[<div id="ctl00_PageContent_rptPosts_ctl00_pnlVideo" style="color: #666666;">&nbsp;</div><p style="color: #666666;">Hello,</p><p style="color: #666666;">&nbsp;</p><p style="color: #666666;">My organization is working to standardize our patient wrist banding process. Our registration experience is in the process of being transformed, modernized, and simplified in order to meet consumer expectations, reduce expense, and stabilize the workforce. We have rolled out many self-service check-in options for our patients such as Epic Welcome on tablets, Kiosks and the use of Hello Patient. With this shift, we need to look at opportunities to make changes to other areas of work that were historically owned by a staff member at a desk on our patient access team. How are other organizations with self-service check-in devices handling patient wrist banding?</p>]]></description>
<pubDate>Tue, 29 Aug 2023 21:44:28 GMT</pubDate>
</item>
<item>
<title></title>
<link>https://www.naham.org/forums/posts.aspx?topic=1763592</link>
<guid>https://www.naham.org/forums/posts.aspx?topic=1763592</guid>
<description><![CDATA[Following as we will be moving to Hello Patient and Epic Welcome soon in the ED which I manage.  Anxious to see how other organizations handle this as well.]]></description>
<pubDate>Sun, 31 Dec 2023 19:59:12 GMT</pubDate>
</item>
</channel>
</rss>
