BEGIN:VCALENDAR
VERSION:2.0
PRODID:-//Drummond Group - ECPv6.17.4.1//NONSGML v1.0//EN
CALSCALE:GREGORIAN
METHOD:PUBLISH
X-ORIGINAL-URL:https://www.drummondgroup.com
X-WR-CALDESC:Events for Drummond Group
REFRESH-INTERVAL;VALUE=DURATION:PT1H
X-Robots-Tag:noindex
X-PUBLISHED-TTL:PT1H
BEGIN:VTIMEZONE
TZID:America/Toronto
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20200308T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20201101T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20210314T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20211107T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20220313T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20221106T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20230312T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20231105T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20240310T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20241103T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20250309T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20251102T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20260308T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20261101T060000
END:STANDARD
BEGIN:DAYLIGHT
TZOFFSETFROM:-0500
TZOFFSETTO:-0400
TZNAME:EDT
DTSTART:20270314T070000
END:DAYLIGHT
BEGIN:STANDARD
TZOFFSETFROM:-0400
TZOFFSETTO:-0500
TZNAME:EST
DTSTART:20271107T060000
END:STANDARD
END:VTIMEZONE
BEGIN:VEVENT
DTSTART;TZID=America/Toronto:20260810T083000
DTEND;TZID=America/Toronto:20260811T120000
DTSTAMP:20260727T162445Z
CREATED:20260707T152439Z
LAST-MODIFIED:20260727T162445Z
UID:51444-1786350600-1786449600@www.drummondgroup.com
SUMMARY:WEDI 2026: Prior Authorization & Interoperability Panel
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/wedi-2026-prior-authorization-interoperability-panel/
LOCATION:Corboy Law Center\, 25 East Pearson Street\, 15th Floor\, Chicago\, 60611
CATEGORIES:Conference,FHIR
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/07/WEDI-Summer-Forum-2026.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20260810
DTEND;VALUE=DATE:20261030
DTSTAMP:20260727T162354Z
CREATED:20251230T211542Z
LAST-MODIFIED:20260727T162354Z
UID:47932-1786320000-1793318399@www.drummondgroup.com
SUMMARY:2026 FHIRplace Multi-Party Testing (ePA)
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhirplace-multi-party-testing-epa/
CATEGORIES:FHIR,Test Event
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/FHIRplace-Test-Events.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Toronto:20260805T130000
DTEND;TZID=America/Toronto:20260805T140000
DTSTAMP:20261022T201308Z
CREATED:20260713T193753Z
LAST-MODIFIED:20261022T201308Z
UID:51638-1785934800-1785938400@www.drummondgroup.com
SUMMARY:FHIRplace CRD Interoperability Testing Findings
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhir-interoperability-testing-webinar-drummond/
LOCATION:Virtual
CATEGORIES:FHIR
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/07/FHIRplace-Q2-Sprint-Webinar.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20260714
DTEND;VALUE=DATE:20260717
DTSTAMP:20260727T162257Z
CREATED:20260623T164727Z
LAST-MODIFIED:20260727T162257Z
UID:51270-1783987200-1784246399@www.drummondgroup.com
SUMMARY:FHIRplace at CMS HL7 Connectathon: Virtual Testing
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhirplace-at-cms-hl7-connectathon-virtual-testing/
LOCATION:Virtual
CATEGORIES:Conference,FHIR
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/06/2026-July-CMS-Connectathon-version-3.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Toronto:20260630T130000
DTEND;TZID=America/Toronto:20260630T143000
DTSTAMP:20261022T201559Z
CREATED:20260612T155559Z
LAST-MODIFIED:20261022T201559Z
UID:51068-1782824400-1782829800@www.drummondgroup.com
SUMMARY:FHIR Intermediary Testing: Real-World Transactions and Compliance
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhir-intermediary-testing-real-world-transactions-and-compliance/
LOCATION:Virtual
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/06/Webinar-Featured-Image.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20260504
DTEND;VALUE=DATE:20260725
DTSTAMP:20260727T162357Z
CREATED:20251230T211313Z
LAST-MODIFIED:20260727T162357Z
UID:47929-1777852800-1784937599@www.drummondgroup.com
SUMMARY:2026 FHIRplace Multi-Party Testing (PDEX)
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhirplace-multi-party-testing-pdex/
CATEGORIES:FHIR,Test Event
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/FHIRplace-Test-Events.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Toronto:20260325T130000
DTEND;TZID=America/Toronto:20260325T143000
DTSTAMP:20260727T162324Z
CREATED:20260321T150556Z
LAST-MODIFIED:20260727T162324Z
UID:49445-1774443600-1774449000@www.drummondgroup.com
SUMMARY:Beyond Connectathons: How Scalable FHIR Testing Is Possible with FHIRplace
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/beyond-connectathons-how-scalable-fhir-testing-is-possible-with-fhirplace/
LOCATION:Virtual
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/03/WEDI-Webinar-March2026.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;TZID=America/Toronto:20260319T123000
DTEND;TZID=America/Toronto:20260319T133000
DTSTAMP:20260727T162352Z
CREATED:20260122T190917Z
LAST-MODIFIED:20260727T162352Z
UID:48474-1773923400-1773927000@www.drummondgroup.com
SUMMARY:HTI-4 Certification and FHIR Interoperability Testing
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/hti-4-certification-and-fhir-interoperability-testing/
LOCATION:Virtual
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/01/HT1-4-Webinar-Featured-Image-Website-StreamYard-Event-Name.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20260105
DTEND;VALUE=DATE:20260221
DTSTAMP:20260727T162404Z
CREATED:20251230T205852Z
LAST-MODIFIED:20260727T162404Z
UID:47922-1767571200-1771631999@www.drummondgroup.com
SUMMARY:2026 FHIRplace Multi-Party Testing (HTI-4)
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhirplace-multi-party-testing-hti-4/
CATEGORIES:FHIR,Test Event
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/FHIRplace-Test-Events.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20250821
DTEND;VALUE=DATE:20250822
DTSTAMP:20260727T162516Z
CREATED:20251218T045047Z
LAST-MODIFIED:20260727T162516Z
UID:47616-1755734400-1755820799@www.drummondgroup.com
SUMMARY:Drummond & Shift: Building Tomorrow’s Privacy Interoperability Landscape
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/drummond-shift-building-tomorrows-privacy-interoperability-landscape/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/png:https://www.drummondgroup.com/wp-content/uploads/2025/07/Security-Code-Scanning-Service-Page-1.png
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20240814
DTEND;VALUE=DATE:20240815
DTSTAMP:20260727T162352Z
CREATED:20251230T224641Z
LAST-MODIFIED:20260727T162352Z
UID:48036-1723593600-1723679999@www.drummondgroup.com
SUMMARY:Transforming Healthcare Interoperability Testing with FHIRplace
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/transforming-healthcare-interoperability-testing-with-fhirplace/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2024/05/HTI-2-Highlights.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20240620
DTEND;VALUE=DATE:20240621
DTSTAMP:20260727T162433Z
CREATED:20240710T203132Z
LAST-MODIFIED:20260727T162433Z
UID:47193-1718841600-1718927999@www.drummondgroup.com
SUMMARY:Connecting with Confidence: FHIR® Client App Certification & Integration Pilot Success
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/connecting-with-confidence-fhir-client-app-certification-integration-pilot-success/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/Free-Consulting-Bob-Bryan.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20240123
DTEND;VALUE=DATE:20240124
DTSTAMP:20260727T162519Z
CREATED:20240125T143020Z
LAST-MODIFIED:20260727T162519Z
UID:47161-1705968000-1706054399@www.drummondgroup.com
SUMMARY:Webinar: HTI-1 Final Rule: An In-Depth Analysis of Recent Changes
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/ht1-final-rule-analysis-of-recent-changes/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/HTI-1-Proposed-Rule-to-Final-Rule-e1726072075453.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20231231
DTEND;VALUE=DATE:20240101
DTSTAMP:20260727T162438Z
CREATED:20231011T184836Z
LAST-MODIFIED:20260727T162438Z
UID:47146-1703980800-1704067199@www.drummondgroup.com
SUMMARY:Building Trust with Interoperability: FHIR Client App Testing and Certification Launch Webinar
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/fhir-client-launch-webinar/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2026/01/Solid-Blue-Generic.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20220202
DTEND;VALUE=DATE:20220203
DTSTAMP:20260727T162522Z
CREATED:20220202T193427Z
LAST-MODIFIED:20260727T162522Z
UID:47127-1643760000-1643846399@www.drummondgroup.com
SUMMARY:Roadmap for Compliance to CMS Interoperability and Patient Access Final Rule
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/roadmap-for-compliance-fhir/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2025/12/Generic-Press-Release-Featured-Image-Multiple-e1726072435295.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20210622
DTEND;VALUE=DATE:20210623
DTSTAMP:20260727T162441Z
CREATED:20210622T182736Z
LAST-MODIFIED:20260727T162441Z
UID:47118-1624320000-1624406399@www.drummondgroup.com
SUMMARY:CMS Interoperability Rule Readiness: FHIR Testing & Certification for Payers
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/cms-interoperability-rule-readiness-fhir-testing-certification-for-payers/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2021/06/Generic-Featured-Image-Green-e1726072122819.jpg
END:VEVENT
BEGIN:VEVENT
DTSTART;VALUE=DATE:20210608
DTEND;VALUE=DATE:20210609
DTSTAMP:20260727T162526Z
CREATED:20210622T182545Z
LAST-MODIFIED:20260727T162526Z
UID:47113-1623110400-1623196799@www.drummondgroup.com
SUMMARY:The Role of Testing and Compliance in Testing and Interoperability
DESCRIPTION:On-Demand Webinar				\n				\n				\n				\n					FHIRplace CRD Interoperability Testing Findings				\n				\n				\n				\n									\n					\n						\n									Watch Now\n					\n					\n				\n								\n				\n				\n				\n					\n				\n		\n					\n		\n		\n				\n				\n					Prior Auth Breaks in Production				\n				\n				\n				\n									Coverage Requirements Discovery looks straightforward on paper. In practice\, a payer returns the wrong coverage decision\, or none at all. Authentication fails on a token you thought was valid. These defects rarely show up until a real trading partner hits them\, and by then the fix is expensive and public. 								\n				\n				\n		\n				\n				\n									This session walked through what ten weeks of multi-party CRD testing actually exposed\, and what it means for your own implementation. Learn which CRD failures were most common\, so you can check your system against them first.See how testing partners resolved authentication issues once\, cleanly\, with no production incident.Understand where payer coverage logic and provider prefetch templates drift apart.Get the Q3–Q4 testing roadmap\, including CRD-PAS and intermediary connect.								\n				\n				\n				\n					\n				\n		\n		\n					\n				\n				\n					What You'll Learn				\n				\n				\n				\n									Watch the engaging presentation of the Q2 FHIRplace FHIR interoperability testing results. The full CRD testing picture: 7 organizations\, 9 roles\, 1\,134 test attempts over 10 weeksWhy 56% of all issues traced to rule evaluation and coverage determination\, and what that signals for payersHow 89% of actively executed scenarios reached a resolved or actively remediated state inside the testing windowWhat the two engaged intermediaries\, KONZA and ZeOmega\, mean for real-world data exchange 								\n				\n					\n				\n				\n		\n					\n		\n				\n				\n							\n					\n						\n				\n				\n		\n				\n				\n				\n					FAQs				\n				\n				\n				\n							\n						\n				\n					 I work on the payer side. Is this relevant to me? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									Yes. Most Q2 issues traced to coverage determination logic\, which is a payer-side concern. The session covers both provider and payer findings. 								\n				\n				\n					\n						\n				\n					 What companies participated in the Q2 FHIRplace FHIR Interoperability testing sprint? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The participating members found on the FHIRplace Validated products page. 								\n				\n				\n					\n						\n				\n					 Will I get the full Q2 report? \n							\n			\n			\n		\n\n						\n				\n				\n				\n									The full Q2 report is already available and can be found on the FHIRplace Validated products page.
URL:https://www.drummondgroup.com/event/the-role-of-testing-and-compliance-in-testing-and-interoperability/
LOCATION:On-Demand
CATEGORIES:FHIR,Webinars and Videos
ATTACH;FMTTYPE=image/jpeg:https://www.drummondgroup.com/wp-content/uploads/2021/06/Generic-Featured-Image-1.jpg
END:VEVENT
END:VCALENDAR