
<rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom">
<channel>
<title>Authorization Workflow</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1721082</link>
<description></description>
<lastBuildDate>Fri, 12 Jun 2026 12:18:01 GMT</lastBuildDate>
<pubDate>Wed, 4 Jan 2023 19:06:30 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=1721082" rel="self" type="application/rss+xml"></atom:link>
<item>
<title>Authorization Workflow</title>
<link>https://www.naham.org/forums/posts.aspx?topic=1721082</link>
<guid>https://www.naham.org/forums/posts.aspx?topic=1721082</guid>
<description><![CDATA[<p>Good Afternoon:</p><p>&nbsp;</p><p>I am looking to talk with someone who has successfully implemented authorization requirements at the payer level based on CPT codes for their health care system.&nbsp; I am looking to learn about the benefits and risks associated with such a build and how this can be accomplished and maintained.&nbsp; You can reach me at balakr@amc.edu.</p><p>&nbsp;</p><p>Many thanks</p><p>ReBecca Balak, MBA, CHAM, CRCR</p><p>Epic Analyst I</p><p>Cadence/Prelude/Referrals/Auth and RTE</p>]]></description>
<pubDate>Wed, 4 Jan 2023 20:06:30 GMT</pubDate>
</item>
</channel>
</rss>
