BEGIN:VCALENDAR VERSION:2.0 PRODID:-//ChamberMaster//Event Calendar 2.0//EN METHOD:PUBLISH X-PUBLISHED-TTL:P1H REFRESH-INTERVAL:P1H CALSCALE:GREGORIAN BEGIN:VTIMEZONE TZID:America/New_York BEGIN:DAYLIGHT RRULE:FREQ=YEARLY;BYMONTH=3;BYDAY=2SU DTSTART:20070101T000000 TZOFFSETFROM:-0500 TZOFFSETTO:-0400 TZNAME:Eastern Daylight Time END:DAYLIGHT BEGIN:STANDARD RRULE:FREQ=YEARLY;BYMONTH=11;BYDAY=1SU DTSTART:20070101T000000 TZOFFSETFROM:-0400 TZOFFSETTO:-0500 TZNAME:Eastern Standard Time END:STANDARD END:VTIMEZONE BEGIN:VEVENT DTSTART;TZID=America/New_York:20261001T130000 DTEND;TZID=America/New_York:20261001T140000 X-MICROSOFT-CDO-ALLDAYEVENT:FALSE SUMMARY:Prior Authorization Policy Digitization\, presented by Drummond & Itiliti Health DESCRIPTION:Your health plan's prior authorization policies are being digitized. But digitization alone doesn't prove that the automated workflows will work at scale\, across different EHR systems\, in production conditions.\n\nThis is where testing enters. And testing for policy digitization across multiple EHRs is harder than it looks.\n\nItiliti Health has spent years working directly with health plan customers on policy digitization. They've seen where the automation breaks\, where EHR vendors interpret policies differently\, and where documentation gaps trip up workflows. Drummond has conducted extensive testing on the Clinical Request for Documentation (CRD) standard\, and now faces the next phase: testing digitized policies themselves.\n\nThis webinar brings those two perspectives together. You'll hear from Itiliti Health about the real challenges their customers face when testing policies across vendor systems. Then you'll see how Drummond's FHIRplace testing framework addresses those gaps.\n\nThis is grounded in customer experience\, not specification theory.\n\n\nWHAT YOU'LL LEARN\n\nThe State of CRD Testing and What It RevealedDrummond has completed extensive testing on how EHRs and payers handle Clinical Request for Documentation requests. Timothy Bennett and Lisa Palmer share what that data shows:What scope of participants and testing conditions Key findings on policy digitization from the CRD request/response cycleWhere EHRs and payers interpret digitized policies differentlyWhy clean data models matter for accurate authorization decisionsPatterns that emerged across different EHR vendors and provider workflows\nThis foundation explains why the next phase of testing is critical.\n\nReal-World Implementation ChallengesItiliti Health brings direct experience. Michael Lunzer shares firsthand what his health plan customers encounter when they try to test digitized policies:Variability in how different EHR systems read and apply policy dataDocumentation and template requirements that cause automation to failHow policy complexity translates into testing complexity Real examples from customer implementations (anonymized)Why this testing matters for meeting the CMS deadline and building internal confidence in the rollout\nYou'll hear the specific friction points that policy models alone don't reveal.\n\nFrom Challenges to Testing Strategy\n\nWith those challenges mapped\, the webinar connects them to testing solutions. How does FHIRplace testing address what you just heard?How FHIRplace's approach tackles policy digitization across vendor environmentsWhy continuous testing matters as policies change and EHR versions updateHow Drummond helps health plans de-risk policy digitization rollouts Timeline and process for certificationNext steps for plans and payers ready to test\nQ&AOpen-floor discussion. Expect questions about EHR integration challenges\, typical testing cycles\, cost and timeline\, and how to start.\n\n________________________________________\nWHY THIS MATTERSDigitization is not a one-time event.Plans change. Vendors update systems. Providers introduce new workflows. Continuous testing keeps the automation aligned with change. A policy that works in testing in month one may have issues when an EHR releases a new version in month three.Policy digitization requires testing across the systems that will actually use it.Data models alone don't tell you what will happen in production. You need to see how EHRs consume the policy data\, apply it to real clinical scenarios\, and generate responses. Gaps in that testing don't surface until go-live.Customer experience informs better testing.Itiliti Health's on-the-ground work with health plans reveals gaps that pure specification reviews miss. Specification compliance and real-world usability are not the same thing. That's why this conversation matters.Drummond's role is to provide the infrastructure to close that gap.FHIRplace provides the testing framework health plans need to go live with confidence. You test against policy data modeled as it will be\, across EHRs that will consume it\, in conditions that simulate production.\n\n\nYOUR PRESENTERS:Timothy Bennett\, DrummondLisa Palmer\, DrummondMichael Lunzer\, Itiliti Health\n\n\nWHO SHOULD ATTENDHealth plan operations and compliance leaders managing prior authorization digitizationIT and clinical policy teams overseeing policy digitization testingEHR platform teams supporting health plan policy implementationPayers evaluating their policy digitization readiness for CMS deadlinesAnyone responsible for prior authorization automation testing\nWHAT'S NEXTRegister & WEDI will send a calendar invite. After the session\, all attendees will receive a recording and the slide deck. Health plans interested in FHIRplace testing can schedule a free consultation with Drummond to discuss your specific testing needs and timeline. X-ALT-DESC;FMTTYPE=text/html:

Your health plan'\;s prior authorization policies are being digitized. But digitization alone doesn'\;t prove that the automated workflows will work at scale\, across different EHR systems\, in production conditions.

This is where testing enters. And testing for policy digitization across multiple EHRs is harder than it looks.

Itiliti Health has spent years working directly with health plan customers on policy digitization. They'\;ve seen where the automation breaks\, where EHR vendors interpret policies differently\, and where documentation gaps trip up workflows. Drummond has conducted extensive testing on the Clinical Request for Documentation (CRD) standard\, and now faces the next phase: testing digitized policies themselves.

This webinar brings those two perspectives together. You'\;ll hear from Itiliti Health about the real challenges their customers face when testing policies across vendor systems. Then you'\;ll see how Drummond'\;s FHIRplace testing framework addresses those gaps.

This is grounded in customer experience\, not specification theory.


WHAT YOU'\;LL LEARN

The State of CRD Testing and What It Revealed

Drummond has completed extensive testing on how EHRs and payers handle Clinical Request for Documentation requests. Timothy Bennett and Lisa Palmer share what that data shows:


This foundation explains why the next phase of testing is critical.

Real-World Implementation Challenges

Itiliti Health brings direct experience. Michael Lunzer shares firsthand what his health plan customers encounter when they try to test digitized policies:


You'\;ll hear the specific friction points that policy models alone don'\;t reveal.

From Challenges to Testing Strategy

With those challenges mapped\, the webinar connects them to testing solutions. How does FHIRplace testing address what you just heard?


Q&\;A

Open-floor discussion. Expect questions about EHR integration challenges\, typical testing cycles\, cost and timeline\, and how to start.

________________________________________


WHY THIS MATTERS

Digitization is not a one-time event.

Plans change. Vendors update systems. Providers introduce new workflows. Continuous testing keeps the automation aligned with change. A policy that works in testing in month one may have issues when an EHR releases a new version in month three.

Policy digitization requires testing across the systems that will actually use it.

Data models alone don'\;t tell you what will happen in production. You need to see how EHRs consume the policy data\, apply it to real clinical scenarios\, and generate responses. Gaps in that testing don'\;t surface until go-live.

Customer experience informs better testing.

Itiliti Health'\;s on-the-ground work with health plans reveals gaps that pure specification reviews miss. Specification compliance and real-world usability are not the same thing. That'\;s why this conversation matters.

Drummond'\;s role is to provide the infrastructure to close that gap.

FHIRplace provides the testing framework health plans need to go live with confidence. You test against policy data modeled as it will be\, across EHRs that will consume it\, in conditions that simulate production.


YOUR PRESENTERS:

Timothy Bennett\, Drummond

Lisa Palmer\, Drummond

Michael Lunzer\, Itiliti Health


WHO SHOULD ATTEND


WHAT'\;S NEXT

Register &\; WEDI will send a calendar invite. After the session\, all attendees will receive a recording and the slide deck. Health plans interested in FHIRplace testing can schedule a free consultation with Drummond to discuss your specific testing needs and timeline.

LOCATION: UID:e.1359.1627627 SEQUENCE:3 DTSTAMP:20260910T183652Z URL:https://wedi.growthzoneapp.com/event-calendar/Details/prior-authorization-policy-digitization-presented-by-drummond-itiliti-health-1915070?sourceTypeId=Hub END:VEVENT END:VCALENDAR