{"id":955,"date":"2015-03-24T21:00:19","date_gmt":"2015-03-25T01:00:19","guid":{"rendered":"https:\/\/cms.basys.com\/customer-cms\/?page_id=955"},"modified":"2022-10-25T14:33:02","modified_gmt":"2022-10-25T18:33:02","slug":"regulatory-2","status":"publish","type":"page","link":"https:\/\/cms.basys.com\/customer-cms\/regulatory-2\/","title":{"rendered":"Regulatory"},"content":{"rendered":"<p>Bridgeway Benefit Technologies monitors a number of legislative \/ regulatory topics and requirements in Healthcare, Pension\/Retirement and other benefits that could potentially impact the basys software systems of both our U.S. and Canadian customers. As your software provider, we are committed to keeping our software current in accordance with regulatory requirements and imposed timelines to the extent that we are aware of these regulations through our research and as identified by our customers. We are equally committed to maintain software stability and to minimize ongoing costs and disruption to our customers\u2019 operations.<\/p>\n<p>With the best interests of our customers in mind, and the ultimate goal of software standardization, in 2011 Bridgeway implemented a new policy, designed with customer input, with the following objectives:<\/p>\n<ul>\n<li>Ensure timely availability of software revisions in response to new and changing regulatory requirements.<\/li>\n<li>Ensure high quality software is delivered in the most cost effective manner possible for our customers by minimizing software variations across our customer base.<\/li>\n<li>Avoid issues that could impact customer costs and business practices by providing customers visibility into the scope of software changes planned, with the ability to comment, prior to software availability.<\/li>\n<\/ul>\n<p>With these objectives in mind, the policy documented in the table below addresses three key aspects of managing regulatory changes.<\/p>\n<table class=\" alignleft\" cellspacing=\"2\" cellpadding=\"4\">\n<tbody>\n<tr>\n<td style=\"text-align: left; vertical-align: top;\"><strong>Monitoring &amp; Impact Assessment<\/strong><\/td>\n<td style=\"text-align: left; vertical-align: top;\">\n<ul>\n<li>Bridgeway will monitor credible industry resources to identify U.S. and Canadian regulatory requirements that could impact our software. Bridgeway will maintain, and update monthly, on our Customer Website a list of \u201cCurrent Regulatory Topics\u201d being monitored with status so customers may be aware and validate that appropriate topics are being monitored. Bridgeway will notify customers when changes are made to the Regulatory Topics list by sending an email to the primary contacts designated for each customer.<\/li>\n<li>Bridgeway expects that U.S. and Canadian customers notify us in a timely manner of regulatory topics that are omitted from the \u201cCurrent Regulatory Topics\u201d list and that they believe necessitate Bridgeway monitoring or impact assessment. Bridgeway will take customer recommendations on additional topics under consideration and will add topics to monitoring and impact assessment activities and update the \u201cCurrent Regulatory Topics\u201d list and notify customers accordingly.<\/li>\n<li>Timed in accordance with imposed regulatory requirements and timelines, Bridgeway will conduct an impact assessment on a regulatory topic and identify requirements that have implications to our software. The impact assessment will identify requirements planned as in scope for revisions to basys software and our software approach (the scope of software changes planned).<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left; vertical-align: top;\"><strong>Customer Comment Period<\/strong><\/td>\n<td style=\"text-align: left; vertical-align: top;\">\n<ul>\n<li>Upon completion of each impact assessment for a regulatory topic, Bridgeway will issue a memorandum to our customers enabling a customer comment period. The memorandum will communicate the results of the impact assessment, Bridgeway\u2019s preliminary plans for implementation, and a date when the comment period will end. The comment period memorandum will be sent via email to the primary contacts designated for each customer. Your Account Manager can provide you with the list of primary contacts for your office, if needed, and modify the contacts as appropriate.<\/li>\n<li>It is each customer\u2019s responsibility to ensure that the appropriate resource in their office review the information contained in the comment period memorandum and to conduct the due diligence necessary to ensure that the scope of software changes planned by Bridgeway meets their business needs and is appropriate to ensure their compliance with regulatory requirements.<\/li>\n<li>As a guideline, the duration of a comment period will range from 15 to 30 business days depending on the volume, complexity and urgency of the revisions. Bridgeway may extend the duration of a comment period at the request of our customers when a strong business rationale is communicated for more time.<\/li>\n<li>It is each customer\u2019s responsibility to respond with comments or concerns in accordance with the timeline established for the comment period. Responses may be provided to Bridgeway via phone or email. At the request of customers, Bridgeway may host a webinar for customers who prefer to provide input in a group setting where discussion with other customers can occur. A non-response from a customer will indicate that there are no concerns and that the customer concurs with Bridgeway\u2019s plans.<\/li>\n<li>Upon completion of the comment period, Bridgeway will assess comments received across customers and adjust our plans if and where appropriate. In situations where conflicting information is received from customers (for example conflicting information between CMS regional offices and CMS Central office), Bridgeway will facilitate a process to resolve conflicting information, working collaboratively with impacted customers.<\/li>\n<li>Bridgeway will issue a post-comment period memorandum to our customers to inform them of the results of the comment period and any revisions to the scope of changes planned for our software.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<tr>\n<td style=\"text-align: left; vertical-align: top;\"><strong>Software Release &amp; Upgrades <\/strong><\/td>\n<td style=\"text-align: left; vertical-align: top;\">\n<ul>\n<li>Bridgeway will make available to customers a software release that complies with required changes, and establish a timeframe for customer deployment. Bridgeway will communicate in advance to customers the date software will be available for implementation, the deployment timeline established by Bridgeway and associated deployment costs so customers can plan and budget accordingly. As always, Bridgeway will work with each customer on a deployment timeline that works best for them.<\/li>\n<li>Customers who choose to implement the software release will have the assurance of software compliance and will realize benefits associated with keeping software versions current. Ensuring software is up to date with the most current version is in alignment with software release best practices, better positions the customer for future software releases, helps ensure software stability in the customer\u2019s environment, and enhances Bridgeway\u2019s ability to support and service the customer in the most efficient manner possible.<\/li>\n<li>Customers who choose not to implement the software release will be at risk of noncompliance and will compromise Bridgeway\u2019s ability to support and service the customer in the most cost effective manner going forward.<\/li>\n<li>Customers who complete the deployment of software during the deployment timeline established by Bridgeway will be assured of the lowest deployment costs possible and will benefit from savings resulting from a Bridgeway project team allocated across multiple customers. Customers who choose to complete the deployment of software at a later time may experience an increase in deployment costs as a new Bridgeway project team will need to be engaged specifically for the customer. Customers who choose not to implement the release at any time may compromise their ability to take future regulatory releases without requiring a special project to address their specific situation.<\/li>\n<li>Customers will be responsible for software deployment costs (service fees for Bridgeway to install the software in the customer\u2019s environment and to support acceptance testing of software and subsequent migration\/installation of the software to the customer\u2019s production environment). Bridgeway will execute basys software development and quality assurance testing work resulting from regulatory changes as part of yearly software maintenance. Exceptions may occur that necessitate additional customer fees for regulatory changes that impose a major development effort and\/or a significant level of complexity that is beyond standard software maintenance or impact a subset of Bridgeway customers.<\/li>\n<\/ul>\n<\/td>\n<\/tr>\n<\/tbody>\n<\/table>\n<p>As a valued customer, we hope that you recognize that Bridgeway established this policy with the best interests of our customers in mind. We continually seek ways to enhance the discipline of our processes and quality of our software and service. Please direct all comments and questions regarding this communication to <a href=\"mailto:%20deniser@basys.com\" target=\"_blank\" rel=\"noopener noreferrer\">Denise Richards,<\/a>\u00a0Senior Director, Enterprise Solutions.<\/p>\n<p>&nbsp;<\/p>\n","protected":false},"excerpt":{"rendered":"<p>Bridgeway Benefit Technologies monitors a number of legislative \/ regulatory topics and requirements in Healthcare, Pension\/Retirement and other benefits that could potentially impact the basys software systems of both our U.S. and Canadian customers. As your software provider, we are committed to keeping our software current in accordance with regulatory requirements and imposed timelines to [&hellip;]<\/p>\n","protected":false},"author":2,"featured_media":0,"parent":0,"menu_order":0,"comment_status":"open","ping_status":"open","template":"","meta":{"_acf_changed":false,"_bbp_topic_count":0,"_bbp_reply_count":0,"_bbp_total_topic_count":0,"_bbp_total_reply_count":0,"_bbp_voice_count":0,"_bbp_anonymous_reply_count":0,"_bbp_topic_count_hidden":0,"_bbp_reply_count_hidden":0,"_bbp_forum_subforum_count":0,"_monsterinsights_skip_tracking":false,"_monsterinsights_sitenote_active":false,"_monsterinsights_sitenote_note":"","_monsterinsights_sitenote_category":0,"_genesis_hide_title":false,"_genesis_hide_breadcrumbs":false,"_genesis_hide_singular_image":false,"_genesis_hide_footer_widgets":false,"_genesis_custom_body_class":"","_genesis_custom_post_class":"","_genesis_layout":"","footnotes":""},"class_list":{"0":"post-955","1":"page","2":"type-page","3":"status-publish","5":"entry"},"acf":[],"_links":{"self":[{"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/pages\/955","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/pages"}],"about":[{"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/types\/page"}],"author":[{"embeddable":true,"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/users\/2"}],"replies":[{"embeddable":true,"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/comments?post=955"}],"version-history":[{"count":10,"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/pages\/955\/revisions"}],"predecessor-version":[{"id":8024,"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/pages\/955\/revisions\/8024"}],"wp:attachment":[{"href":"https:\/\/cms.basys.com\/customer-cms\/wp-json\/wp\/v2\/media?parent=955"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}