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: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;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;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
END:VCALENDAR