Deprecated: Creation of dynamic property Tribe__Events__Pro__Integrations__WPML__Event_Listener::$wpml is deprecated in /sites/staging.digitalinsights.supremeclients.com/files/wp-content/plugins/events-calendar-pro/src/Tribe/Integrations/WPML/Event_Listener.php on line 52

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the sitepress-multilingual-cms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the OxyPowerPack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the aryo-activity-log domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookiebot domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tribe-events-calendar-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the functions domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the limit-login-attempts-reloaded domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the oxyextras domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the oxygen domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qdiwebchat domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qiacareers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qiaeloqua domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redirection domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the related-posts-for-wp-1 domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the safe-svg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the spinupwp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tribe-events-filter-view domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the the-events-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tinymce-advanced domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the use-any-font domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-all-export-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-all-import-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-debugging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-smtp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-search-with-algolia domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpae-acf-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpai-acf-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpai-user-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpml-import domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpml-string-translation domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Deprecated: Creation of dynamic property Tribe__Events__Filterbar__View::$pluginUrl is deprecated in /sites/staging.digitalinsights.supremeclients.com/files/wp-content/plugins/the-events-calendar-filterbar/src/Tribe/View.php on line 145

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the sitepress-multilingual-cms domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the OxyPowerPack domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the acf domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the aryo-activity-log domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the cookiebot domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tribe-events-calendar-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the functions domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the insert-headers-and-footers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the limit-login-attempts-reloaded domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the oxyextras domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the oxygen domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qdiwebchat domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qiacareers domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the qiaeloqua domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the redirection domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the related-posts-for-wp-1 domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the safe-svg domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the spinupwp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tribe-events-filter-view domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the the-events-calendar domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the tinymce-advanced domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the use-any-font domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wordpress-seo domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-all-export-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-all-import-pro domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-debugging domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-mail-smtp domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wp-search-with-algolia domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpae-acf-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpai-acf-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpai-user-add-on domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpml-import domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Notice: Function _load_textdomain_just_in_time was called incorrectly. Translation loading for the wpml-string-translation domain was triggered too early. This is usually an indicator for some code in the plugin or theme running too early. Translations should be loaded at the init action or later. Please see Debugging in WordPress for more information. (This message was added in version 6.7.0.) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php on line 6114

Deprecated: Creation of dynamic property Tribe__Events__Filterbar__PUE::$pue_instance is deprecated in /sites/staging.digitalinsights.supremeclients.com/files/wp-content/plugins/the-events-calendar-filterbar/src/Tribe/PUE.php on line 45

Deprecated: explode(): Passing null to parameter #2 ($string) of type string is deprecated in /sites/staging.digitalinsights.supremeclients.com/files/wp-content/plugins/oxygen/component-framework/api/oxygen.element-helper.class.php on line 72

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893

Warning: Cannot modify header information - headers already sent by (output started at /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/functions.php:6114) in /sites/staging.digitalinsights.supremeclients.com/files/wp-includes/rest-api/class-wp-rest-server.php on line 1893
{"id":84275,"date":"2023-02-07T21:34:31","date_gmt":"2023-02-07T21:34:31","guid":{"rendered":"https:\/\/digitalinsights.qiagen.com\/?p=84275"},"modified":"2024-10-05T02:19:20","modified_gmt":"2024-10-05T02:19:20","slug":"every-clinical-cancer-genetics-professional-needs-this-tool-in-2023","status":"publish","type":"post","link":"https:\/\/staging.digitalinsights.supremeclients.com\/news\/blog\/clinical\/every-clinical-cancer-genetics-professional-needs-this-tool-in-2023\/","title":{"rendered":"Every clinical cancer genetics professional needs this tool in 2023"},"content":{"rendered":"\n
A new balancing act: How do clinical cancer geneticists and genetic counselors manage more patients with less time?<\/h5>\n\n\n\n

The COVID-19 pandemic marked a turning point across the healthcare landscape. And like many professions, clincal cancer genetics is shifting in unexpected ways.<\/p>\n\n\n\n

From changes to delivery models and the genetic testing landscape, to emerging new technologies and greater access, clinical genetics is at an inflection point. The demand for services is growing, patient cases are becoming more complex, and professional burnout is at an all-time high.<\/p>\n\n\n\n

 <\/p>\n\n\n\n

\n
\n

The COVID-19 pandemic marked a turning point across the healthcare landscape. And like many professions, clincal cancer genetics is shifting in unexpected ways.<\/p>\n\n\n\n

From changes to delivery models and the genetic testing landscape, to emerging new technologies and greater access, clinical genetics is at an inflection point. The demand for services is growing, patient cases are becoming more complex, and professional burnout is at an all-time high.<\/p>\n<\/div>\n\n\n\n

\n \n \"\"\n <\/a>\n
\n\tOn-Demand Webinar How to simplify somatic NGS analysis and reduce literature review time by 90% <\/h6>\n \n \n WATCH NOW <\/a>\n <\/div><\/div>\n<\/div>\n\n\n\n


<\/a><\/p>\n\n\n

\n
\nWarning<\/b>: foreach() argument must be of type array|object, bool given in \/sites\/staging.digitalinsights.supremeclients.com\/files\/wp-content\/plugins\/functions\/block\/accordion-red-arrow.php<\/b> on line 6<\/b>
\n <\/div>\n\n\n
\n
\nWarning<\/b>: foreach() argument must be of type array|object, bool given in \/sites\/staging.digitalinsights.supremeclients.com\/files\/wp-content\/plugins\/functions\/block\/accordion-red-arrow.php<\/b> on line 6<\/b>
\n <\/div>\n\n\n\n

<\/p>\n\n\n\n

What\u2019s the common denominator?<\/h5>\n\n\n\n

There\u2019s a catalyzing culprit to these three challenges. Time<\/em>. Across the industry, clinical geneticists and genetic counselors report time as the biggest bottleneck in their ability to provide services efficiently.<\/p>\n\n\n\n

In a survey<\/a> of cancer genetic counselors, 92% report not having enough time to properly prepare for new patient meetings.<\/p>\n\n\n\n

This statistic gains greater impact when considering these five cause-and-effects:<\/p>\n\n\n

\n
\n
\n
\n \n \n <\/svg>\n <\/div>\n
Demand for clinical cancer genetics is soaring.<\/h6>\n <\/div>\n
\n

According to the\u00a0U.S. Bureau of Labor Statistics<\/a>, the field is projected to grow by 27% between 2018 and 2028, compared to just 5% across all professions.<\/p>\n <\/div>\n <\/div>\n

\n
\n
\n \n \n <\/svg>\n <\/div>\n
Rapid growth in demand for clinical cancer genetics professionals has led to a workforce shortage.<\/h6>\n <\/div>\n
\n

There is approximately 1 clinical cancer genetics professional per 300,000 individuals in the United States (Pal et a. (2013)<\/a>).<\/p>\n <\/div>\n <\/div>\n

\n
\n
\n \n \n <\/svg>\n <\/div>\n
A workforce shortage places greater caseload pressure on genetic counselors.<\/h6>\n <\/div>\n
\n

According to the National Society of Genetic Counselors (NSGC) Professional Status Survey, 62% of clinical genetic counselors report an increase in patient volume in just two years (Patel et al. (2018)<\/a>).<\/p>\n <\/div>\n <\/div>\n

\n
\n
\n \n \n <\/svg>\n <\/div>\n
Case complexity is increasing.<\/h6>\n <\/div>\n
\n

A survey found that genetic counselors spend an average of 4-6 hours per patient working on case-prep, follow-up, and administrative tasks (Attard et al. (2018)<\/a>).<\/p>\n <\/div>\n <\/div>\n

\n
\n
\n \n \n <\/svg>\n <\/div>\n
Clinical geneticists are overwhelmed.<\/h6>\n <\/div>\n
\n

Up to three-quarters of clinical geneticists are found to be at moderate to high risk for burnout and compassion fatigue (Injeyan et al. 2011; Lee et al. 2015; Udipi et al. 2008).<\/p>\n <\/div>\n <\/div>\n <\/div>\n\n\n\n

<\/div>\n\n\n\n
Pinpointing the problem<\/h5>\n\n\n\n

Clinical geneticists and genetic counselors are experiencing compounded challenges. However, a closer look at a typical clinical cancer genetics workflow illuminates the main problem.<\/p>\n\n\n\n

In a 2018 survey<\/a>, 17 genetic counselors indicate that 64% of their time is spent on patient-related activities (PRA) versus face-to-face patient interaction. This equates to 3 hours of PRA time per patient. And, the most time-consuming part of the PRA was writing letters, which involves summarizing the genetic test results, providing detailed information, and recommending next steps\u2014which all must be cited and supported by evidence.<\/p>\n\n\n\n

Similarly, Heald et al.<\/a> found that the most time-intensive part of a clinical geneticist\u2019s and genetic counselor's workflow is literature review and exploring testing options.  And, a recent study by Williams et al.<\/a> found that clinical cancer genetics professionals spend an average of 420 minutes (7 hours) reviewing all available medical literature before presenting to physicians and their patients.<\/p>\n\n\n\n

Clinical cancer geneticists and genetic counselors need a way to shorten the literature review process of their workflow without jeopardizing patient outcomes. They need a workflow that allows them to spend more time interacting with patients and less time behind a computer screen. They need a workflow that supports an increase in billing and reimbursement activities and decreases fatigue and burnout.<\/p>\n\n\n\n

While some studies<\/a> recommend improving efficiency by hiring a clinical genetics assistant\u2014a \u201csolution\u201d that incurs substantial annual resources and costs\u2014there\u2019s an easier way forward.<\/p>\n\n\n\n

A simple solution<\/h5>\n\n\n\n

The Human Somatic Mutation Database (HSMD)<\/a> is the most time-efficient and cost-effective way cancer genetic counselors can scale caseload volume.<\/p>\n\n\n\n

\n
\n

An easy-to-use, somatic database from QIAGEN, HSMD contains extensive genomic content relevant to solid tumors and hematological malignancies. Pulling content from over 419,000 real-world clinical oncology cases and 40+ databases contained in the QIAGEN Knowledge Base, HSMD gives genetic counselors access to over 1.5 million somatic variants characterized in over 1,400 cancer-related genes.<\/p>\n<\/div>\n\n\n\n


\nWarning<\/b>: Trying to access array offset on value of type null in \/sites\/staging.digitalinsights.supremeclients.com\/files\/wp-content\/plugins\/functions\/block\/cta-without-image-left.php<\/b> on line 18<\/b>
\n
\nWarning<\/b>: Trying to access array offset on value of type null in \/sites\/staging.digitalinsights.supremeclients.com\/files\/wp-content\/plugins\/functions\/block\/cta-without-image-left.php<\/b> on line 19<\/b>
\n
\n
\n
HSMD vs. HGMD<\/h5>\n
For genetic counselors and clinical geneticists who need access to both hereditary and somatic cases, you can combine content from HSMD and the Human Genetic Mutation Database (HGMD) Professional for full coverage.<\/h6>\n LEARN MORE HERE<\/a>\n <\/div>\n<\/div><\/div>\n<\/div>\n\n\n\n

<\/a><\/h5>\n\n\n\n
HSMD allows you to search by:<\/h6>\n\n\n\n