Product Schedules
The following additional terms and conditions apply only and to the extent Customer has subscribed to the applicable Riskonnect Applications as set forth in a Subscription Order. These terms are required by Riskonnect’s Licensors and may not be amended or modified.
A. Salesforce Products
The terms and conditions of this Article A of the Product Schedule shall apply only if Customer’s Subscription Order includes the following Riskonnect Applications:
- Integrated Risk Management Services (IRMS)
- Risk Management Information System (RMIS)
- OSHA Management
- Values Collection & Renewals
- Certificate Management
- Claim Audit
- Health & Safety (H&S)
- HealthCare
- Enterprise Risk Management
- Internal Audit
- Corporate Policy Management
- Regulatory & Compliance Management
- Internal Controls
- IT Risk Management
- Third Party Risk Management Bundle
- ESG Risk Management; and/or
- AI Governance
Additional Definitions:
“Data Infrastructure” means the data processing resources within the Riskonnect Service, including but not limited to, data and file storage, within Customer’s account configured in the Riskonnect Service platform.
“Platform Provider” means Salesforce.com, Inc.
“Platform Service” means the online, web-based service provided by Platform Provider to Riskonnect in connection with Riskonnect’s provision of the Riskonnect Service.
“System Administrator” means a User designated by Customer who is authorized to create User accounts, to purchase subscriptions by executing a Subscription Order, and to otherwise administer Customer’s use of the Riskonnect Service.
Additional Terms and Conditions:
- Notwithstanding any access Customer’s Users may have to the services of Riskonnect’s Licensors via the Customer’s configuration of the Riskonnect Service, Riskonnect is the sole provider of the Riskonnect Service and Customer is entering into a contractual relationship solely with Riskonnect. In the event that Riskonnect ceases operations or otherwise ceases or fails to provide the Riskonnect Service, Riskonnect’s Licensors have no obligation to refund Customer any fees paid by Customer to Riskonnect or to provide Customer the Riskonnect Service.
- Any configuration, development, or data integration services to the Customer’s instance of the Riskonnect Service that is performed by Customer or Customer’s third parties is not covered by Software Support and Riskonnect shall have no liability whatsoever for such services. However, Customer may request Riskonnect to render support services for configurations and modifications performed by Customer provided that such Annual Services shall be billable to Customer at Riskonnect’s then current hourly rate.
- Customer’s subscriptions include a specific quantity of Data Infrastructure, as reflected in Customer’s Riskonnect Application. If Customer exceeds the amount of Data Infrastructure, upon 30 days’ notice, Customer shall be charged for any additional Data Infrastructure used and pay additional subscription fees.
- NOTHING IN THIS SCHEDULE A, SECTION 2.4 SHALL LIMIT RISKONNECT’S WARRANTIES OR INDEMNIFICATION OBLIGATIONS UNDER THIS AGREEMENT, INCLUDING THOSE THAT RISKONNECT MAKES AND/OR PROVIDES ON BEHALF OF RISKONNECT’S LICENSORS. Notwithstanding the foregoing, to the maximum extent permitted by law, Riskonnect’s Licensors make no, and disclaim all, warranties of any kind, whether express, implied, statutory, or otherwise, including, without limitation, any implied warranty of merchantability, fitness for a particular purpose, or non-infringement of third-party rights with respect to the Platform Service, and/or the Riskonnect Service, or any of the products and services offered by Riskonnect’s Licensors. Riskonnect’s Licensors make no representation, warranty, or guarantee as to the reliability, timeliness, quality, suitability, availability, accuracy or completeness of the Riskonnect Service. Riskonnect’s Licensors do not represent or warrant that the Riskonnect Service will be available, secure, timely, uninterrupted or error-free; the Riskonnect Service or any of the products and services offered by Riskonnect’s Licensors will meet Customer’s requirements or expectations; any data stored using the Riskonnect Service will be accurate, reliable, or secure; errors or defects in the Riskonnect Service will be corrected; or the Riskonnect Service or the Data Infrastructure used by Riskonnect to make the Riskonnect Service available are free of Disabling Code, viruses or other harmful components.
- There are no third-party beneficiaries to this Agreement, except that Platform Provider shall be a third-party beneficiary to this Agreement solely as it relates to the provisions herein that relate to the use of the Platform Service.
- At any time during the Term of this Agreement, Customer will have access to and the ability to extract the Customer Data. Customer may schedule a weekly data export from within the Riskonnect Service for Customer’s own backup purposes.
- It is Customer’s responsibility to designate the applicable access to be granted to each User. Customer assumes full legal and financial responsibility for all instructions of any nature that are reasonably accepted and acted upon by Riskonnect in accordance with such designation. Customer shall promptly notify Riskonnect if it becomes aware that the security of its designations has been compromised. Users shall only access, use, and/or configure those modules and features associated with the applicable Riskonnect Application(s) to which Customer subscribes under this Agreement. If a User accesses, uses, configures, and/or replicates a Riskonnect Application module or feature within the Riskonnect Service other than those to which Customer has subscribed, then Riskonnect shall notify Customer of the unauthorized access or use. If such unauthorized access or use by the User is not discontinued within 10 days, then Riskonnect will adjust Customer’s subscriptions and invoice Customer for the additional Riskonnect Application, module or feature being accessed or used.
- Riskonnect Insights Terms of Use. Riskonnect provides Customer’s Users a subscription to use Insights solely for risk-related data.
- Riskonnect eSignature Terms of Use. If Customer implements Adobe eSignature (powered by Adobe Acrobat Sign or related Adobe signature products or services, hereinafter “Adobe Sign”) in its Riskonnect Service, as set forth in a Statement of Work and/or Subscription Order, the following terms apply to Adobe Sign:
- As a condition of using Adobe Sign, Customer accepts and agrees to comply with Adobe’s then-current Enterprise Licensing Terms, Product Specific Licensing Terms, data protection terms, documentation, usage restrictions, and other terms applicable to Adobe Sign as made available by Adobe from time to time (collectively, the “Adobe Terms”), solely as they apply to Customer’s use of Adobe Sign through the Riskonnect Service. Customer shall not use Adobe Sign in any manner that would cause Riskonnect to violate the Adobe Terms. Except for the express limited rights granted under the Agreement, this Exhibit, and the Adobe Terms, no right, title, or interest in or to any Adobe intellectual property, technology, products, or services is granted, transferred, or otherwise provided to Customer.
- Customer acknowledges that Riskonnect, and not Adobe, is the provider of the Riskonnect Service to Customer. Adobe is not responsible for providing the Riskonnect Service to Customer, refunding any fees paid by Customer to Riskonnect, or providing support directly to Customer, except to the extent expressly required under the Adobe Terms or applicable law.
- Unless otherwise stated in the applicable Subscription Order, Customer’s subscription includes up to two thousand (2,000) Adobe Sign transactions annually. For this purpose, a “Transaction” means each Electronic Document, or collection of related Electronic Documents up to 100 pages or 10 MB, sent through Adobe Sign. Any usage above the included transaction quantity may be subject to additional fees.
- By using Adobe Sign, Customer agrees to conduct the applicable transaction using electronic documents and electronic signatures instead of paper-based documents and wet ink signatures. Customer is not required to use Adobe Sign and remains responsible for determining whether electronic signatures are appropriate for its intended transaction.
- Riskonnect does not verify the identity, authority, capacity, or intent of any signer or other recipient of an Electronic Document submitted through Adobe Sign. Customer is solely responsible for verifying the identity and authority of each signer and for determining the validity, completeness, legal effect, enforceability, and suitability of any Electronic Document, workflow, consent, disclosure, record retention process, or signature process used with Adobe Sign.
- Customer is solely responsible for determining whether its use of Adobe Sign complies with all laws, regulations, industry requirements, internal policies, record retention obligations, consent requirements, and electronic signature requirements applicable to Customer, its Users, its documents, its transactions, its industry, and the jurisdictions in which it operates.
- Customer acknowledges that Customer Data, Electronic Documents, usage information, and related information may be processed by Adobe and its affiliates in connection with the provision, operation, support, protection, improvement, development, and enforcement of Adobe Sign and related services, as further described in the Adobe Terms and applicable data protection terms. Customer is responsible for ensuring that it has all rights, notices, consents, authorizations, and legal bases required for Customer Data and Electronic Documents submitted to or processed through Adobe Sign. Unless expressly authorized by Riskonnect in writing, Customer shall not submit to Adobe Sign any Sensitive Personal Data or other categories of data that are prohibited or restricted under the Adobe Terms, applicable documentation, or applicable law.
- Customer acknowledges that Adobe may use technologies or processes to screen for certain illegal or abusive content or behavior, and Adobe or Riskonnect may suspend access to Adobe Sign, remove unlawful content, or disclose information relating to Customer’s or Users’ use of Adobe Sign where required by law, regulation, subpoena, court order, or other valid legal process.
- Customer shall not, and shall not permit any User or third party to: (a) use Adobe Sign in violation of applicable law or regulation, or in connection with unlawful, infringing, defamatory, harassing, privacy-invasive, or otherwise unlawful content; (b) use Adobe Sign in a manner that could create a material risk to the security, availability, integrity, or normal operation of Adobe, Riskonnect, the Riskonnect Service, Adobe Sign, or any customer of Adobe or Riskonnect; (c) copy, distribute, republish, download, display, transmit, sell, rent, lease, host, sublicense, resell, or otherwise make Adobe Sign available as a standalone product or service; (d) use Adobe Sign except through Customer’s authorized configuration of the Riskonnect Service; (e) reverse engineer, decompile, disassemble, monitor inputs or outputs for the purpose of discovering underlying algorithms or methods, or otherwise attempt to discover source code, data representations, processes, methods, or other non-public aspects of Adobe Sign or Adobe technology; (f) remove, obscure, or alter any proprietary notices associated with Adobe Sign or any reports generated through Adobe Sign; (g) use any Adobe software component, module, service, or functionality that is not included in Customer’s subscription or otherwise made available by Riskonnect; (h) share login IDs or passwords, permit simultaneous use of the same login credentials by more than one User, or permit unauthorized access to Adobe Sign; or (i) use Adobe Sign in any Restricted Country or other location where Adobe does not make Adobe Sign available or where access or use is restricted by applicable law or the Adobe Terms.
- Riskonnect may limit, suspend, or terminate Customer’s access to Adobe Sign if Customer or any User violates these eSignature Terms, the Adobe Terms, or applicable law. Where commercially reasonable, Riskonnect will provide notice and an opportunity to discontinue the prohibited activity. However, Riskonnect may suspend or terminate access immediately where Riskonnect or Adobe reasonably determines that continued use may violate applicable law, create a security or operational risk, impair the normal operation of Adobe Sign or the Riskonnect Service, involve unlawful content, involve use in a Restricted Country, or otherwise expose Riskonnect, Adobe, or their customers to material risk.
- Customer acknowledges that data and Electronic Documents processed through Adobe Sign may be retained, deleted, exported, or made available in accordance with the Adobe Terms, applicable Product Specific Licensing Terms, and Adobe’s then-current functionality. Customer Data stored within Adobe Sign may be available for a limited period following termination or expiration and may be accessible only in the format then available through the applicable Adobe Sign reporting or export interface. Riskonnect will use commercially reasonable efforts to assist Customer with retrieval of Customer Data from Adobe Sign, subject to the availability of such data from Adobe, the Adobe Terms, the Agreement, and Riskonnect’s then-current data transfer protocols.
- Except as otherwise required by a court of competent jurisdiction, Riskonnect has no obligation to become involved in any dispute between Customer and any third party arising from or relating to Customer’s use of Adobe Sign. If Riskonnect becomes involved in any such dispute as a party, witness, custodian, or otherwise as a result of Customer’s use of Adobe Sign, Customer shall defend, indemnify, and hold harmless Riskonnect from and against any third-party claim, suit, proceeding, cost, expense, or liability arising from Customer’s or its Users’ acts or omissions relating to Adobe Sign. The preceding sentence does not apply to disputes concerning the scope of Riskonnect’s authority to make Adobe Sign available through the Riskonnect Service or intellectual property disputes related to Adobe Sign, which shall be handled in accordance with the Agreement.
- Except for any express warranties provided by Riskonnect under the Agreement, Adobe Sign is provided “as is” and “as available.” To the maximum extent permitted by law, Riskonnect and its licensors disclaim all warranties, representations, and conditions regarding Adobe Sign, whether express, implied, statutory, or otherwise, including warranties of merchantability, fitness for a particular purpose, title, non-infringement, accuracy, availability, security, timeliness, uninterrupted operation, or error-free operation.
- Riskonnect Alerts Service Terms of Use. NOTWITHSTANDING RELATED PROVISIONS IN THE AGREEMENT, RISKONNECT NEITHER MAKES ANY WARRANTY NOR ACCEPTS ANY LIABILITY WITH REGARD TO THE TIMELINESS AND ACCURACY OF THE THIRD-PARTY DATA DELIVERED THROUGH THE RISKONNECT ALERTS SERVICE. FURTHERMORE, THE PARTIES EXPRESSLY AGREE THAT ANY NON-CONFORMITY OR FAILURE OF THE RISKONNECT ALERTS SERVICE SHALL NOT GIVE REASON TO TERMINATE THE AGREEMENT FOR CAUSE.
B. Resilience Products
The terms and conditions of this Article B of the Product Schedule shall apply only if Customer’s Subscription Order include the following Riskonnect Applications:
- Resilience Software
- Threat Intelligence Software
- Notifications Software
- Crisis Management
- Operational Resilience
Additional Definitions:
“Communication Platform Provider” means Twilio (phone, text and email delivery).
“Communication Service” means the online, web-based service provided by Communication Platform Provider to Riskonnect in connection with Riskonnect’s provision of the Riskonnect Service
“Customer Contacts” means Users who access and use the Riskonnect Service to perform plan creation (based on existing templates), update, view and approval.
“Internal Contacts” means those personnel designated by Customer to receive notifications via the Notifications Module.
“Platform Provider” means Amazon Web Services and/or Microsoft Azure.
“Platform Service” means the online, web-based service provided by Platform Provider (as defined below) to Riskonnect in connection with Riskonnect’s provision of the Riskonnect Service.
Additional Terms and Conditions:
- The Platform Provider shall be a third-party beneficiary of this Agreement solely as it relates to the disclosure and use of any confidential or proprietary information of the Platform Provider that Riskonnect may disclose to Customer.
- Customer shall take no action that would cause Riskonnect to be in violation of Luzmo’s terms and conditions found at https://www.luzmo.com/information-pages/terms-and-conditions.
- Only if Customer’s subscription includes Threat Intelligence, such feature is licensed to Customer by Riskonnect as an authorized reseller, OnSolve, LLC (“OnSolve”) under the applicable Order. OnSolve products are subject to OnSolve’s end user subscription agreement located at https://www.onsolve.com/company/legal/enterprise-terms-and-conditions/ as may be updated from time to time by OnSolve.
- Only if the Customer’s subscription include the Notification Software, the following terms and conditions shall apply:
- Use of the Notifications Software notification tool is limited to organizational incidents. This includes messages as part of a crisis and ten tests per year (total test messages will not exceed ten times the number of internal contacts within the Riskonnect Service). Additional non-incident-based use may incur additional charges at Riskonnect’s sole discretion, up to $0.25 per message sent. Lastly, the Notifications Software is not to be used for internal operational communications among first responders, nor is for use with any third-party customer, supplier, or local population for status update purposes. Customer must only use the Notifications Software for internal communications during an operational disruptive incident or for an exercise to evaluate internal crisis communications-related purposes.
- Customer, on behalf of itself and all Users, agrees to comply with Communication Platform Provider’s Acceptable Use Policy available at the following web site: https://www.twilio.com/legal/aup (as updated from time to time, “Use Policy”). Should Customer or any of its Users materially breach or should Riskonnect in good faith believe Customer or any of its Users have materially breached, any of the terms of the Use Policy, Riskonnect may suspend the Communication Service upon notice to Customer.
- Riskonnect may suspend the Communication Service if there is an unusual and material spike or increase in Customer’s use of the Communication Service and if Riskonnect suspects that such traffic or use is fraudulent or materially and negatively impacting the operating capability of the Communication Services or if provision of the Communication Service is prohibited by applicable law or regulation
- If any Updates to the Communication Service that are not backward compatible become necessary, Riskonnect will use commercially reasonable efforts to notify Customer at least thirty (30) days prior to implementation.
- Customer agrees to assign any intellectual property in feedback and suggestions regarding the Communication Service to the Communication Platform Provider.
- NOTHING CONTAINED IN THIS SCHEDULE SHALL LIMIT RISKONNECT’S WARRANTIES OR INDEMNIFICATION OBLIGATIONS UNDER THIS AGREEMENT, INCLUDING THOSE THAT RISKONNECT MAKES AND/OR PROVIDES ON BEHALF OF RISKONNECT’S LICENSORS. NOTWITHSTANDING THE FOREGOING, TO THE MAXIMUM EXTENT PERMITTED BY LAW, , THE COMMUNICATION PLATFORM PROVIDER MAKES NO WARRANTY OF ANY KIND, WHETHER EXPRESS, IMPLIED, STATUTORY, OR OTHERWISE, AND SPECIFICALLY DISCLAIMS ALL IMPLIED WARRANTIES, INCLUDING ANY IMPLIED WARRANTY OF MERCHANTABILITY, FITNESS FOR A PARTICULAR PURPOSE, OR NON-INFRINGEMENT TO THE FULLEST EXTENT PERMITTED BY LAW. COMMUNICATION PLATFORM PROVIDER ADDITIONALLY DISCLAIMS ALL WARRANTIES RELATED TO THIRD PARTY TELECOMMUNICATIONS PROVIDERS. CUSTOMER ACKNOWLEDGES THE INTERNET AND TELECOMMUNICATIONS PROVIDERS’ NETWORKS ARE INHERENTLY INSECURE AND THAT NEITHER COMMUNICATION PLATFORM PROVIDER NOR RISKONNECT WILL HAVE ANY LIABILITY FOR ANY CHANGES TO, INTERCEPTION OF, OR LOSS OF CUSTOMER DATA WHILE IN TRANSIT VIA THE INTERNET OR A TELECOMMUNICATIONS PROVIDER’S NETWORK.
- Customer shall defend Riskonnect, the Communication Platform Provider and the Communication Platform Provider’s directors, officers, employees, and Affiliates (collectively, “Indemnified Parties”) from and against any claim, demand, suit, or proceeding made or brought against an Indemnified Party by a third party alleging or arising out of Customer’s breach of the Use Policy. Customer will indemnify the Indemnified Parties from any damages, fines or penalties imposed by a government or regulatory body, attorneys’ fees, and costs awarded against an Indemnified Party or for settlement amounts approved by Customer for a claim under this Section. No limitation of liability shall apply to this Section.
C. Active Risk Products
The terms and conditions of this Article C of this Product Schedule shall apply only if Customer’s Subscription Order include the following Riskonnect Applications:
- Active Risk Platform
- Active Risk Manager (ARM)
- Active Risk Compliance Manager (ARCM)
- Active Risk Operational Risk Manager (ARORM)
- Active Risk Audit Manager (ARAM)
- Active Risk Quality Manager (ARQM)
- Active Risk Policy Manager (ARPM)
Additional and Amended Definitions
“Platform Provider” means Amazon Web Services or Microsoft Azure.
“Platform Service” means the online, web-based service provided by Platform Provider to Riskonnect in connection with Riskonnect’s provision of the Riskonnect Service.
Additional Terms and Conditions
- Any configuration, development, or data integration services to Customer’s instance of the Riskonnect Service that is performed by Customer or Customer’s third parties is not covered by Software Support, and Riskonnect shall have no liability whatsoever for such services. However, Customer may request Riskonnect to render support services for configurations and modifications performed by Customer provided that such Annual Services shall be billable to Customer at Riskonnect’s then current hourly rate.
- The Platform Provider shall be a third-party beneficiary of this Agreement solely as it relates to the disclosure and use of any confidential or proprietary information of the Platform Provider that Riskonnect may disclose to Customer.
D. Camms Products
The terms and conditions of this Article D of this Product Schedule shall apply only if Customer’s Subscription Order include the following Riskonnect Applications:
- Camms Application
- GSP Platform
- GRC Compliance
- GRC Incident
- Connect
- GRC Business Process Toolkit
- GRC Health and Safety
- Third Party Risk Management
- Disclosures Management
- Community Voices Management
Additional Definitions:
“Hosting Region” means the hosting country (or countries) specified in the Subscription Order.
“Platform Provider” means Microsoft Azure or Macquarie.
“Platform Service” means the online, web-based service provided by Platform Provider (as defined above) to Riskonnect in connection with Riskonnect’s provision of the Riskonnect Service.
“Riskonnect Locations” means Australia, the United States, the United Kingdom, India, Sri Lanka, the Philippines and/or such other countries as Riskonnect may specify from time to time on reasonable notice.
“User Information” means the name, position, position description, location, email address, phone number and reporting officer of each User.
Additional Terms and Conditions:
- Riskonnect may remotely monitor Customer’s usage of the Riskonnect Applications to audit and verify Customer’s compliance with the Agreement and any applicable usage restrictions. If an audit determines that Customer is not compliant with the Agreement, Customer shall reimburse Riskonnect, within thirty (30) days of the date of written notification of the audit results pay the additional fees for any usage in excess of Customer’s rights under the Agreement (for which Riskonnect may immediately issue an invoice) and otherwise rectify the non-compliance to Riskonnect’s reasonable satisfaction.
- Riskonnect agrees to restrict geographic access to Customer Data as follows: (a) where the Subscription Order specifies that Customer is purchasing a ‘Region Restricted’ infrastructure security offering (which, as of the Effective Date, comprises Riskonnect’s Secure+, Protected+ or Dedicated options) then only Riskonnect personnel based in the Hosting Region specified in the Subscription Order may access Customer Data, and Riskonnect must not disclose, store, export or transfer Customer Data to a country outside the Hosting Region, except that Riskonnect may disclose User Information to employees and contractors of Riskonnect and its Affiliates who are based in Riskonnect Locations, solely for the purposes of providing the Riskonnect Service and Professional Services (and Customer acknowledges that Riskonnect personnel outside the Hosting Region may use the User Information to contact Users); (b) where the Subscription Order does not specify that Customer is purchasing a ‘Region Restricted’ infrastructure security offering, then Riskonnect may disclose, store, export or transfer Customer Data to a country outside the Hosting Region: (i) by giving remote access to Customer Data to employees and contractors of Riskonnect and its Affiliates who are based in Riskonnect Locations, solely for the purposes of providing the Riskonnect Service and Professional Services; or (ii) with Customer’s prior written consent.
E. ClearSight Products
The terms and conditions of this Article E shall apply only if Customer’s Subscription Order include the following Riskonnect Applications
- ClearSight Integrated Risk Management
- Claims Administration
- Claims Management
- WC Claims Administration
- Incident Management
- Insurance Management
- Physician Administration
- Risk Identification
- Risk Mitigation
- Enterprise
- Values Collection & Renewals
Additional and Amended Definitions:
“Supplemental Materials” shall also include the Riskonnect ClearSight Exhibits for the EDI solution, Medicare Section 111 Solution (CMS Solution), and Work Cover / Comcare Submissions (Applicable to Australia only).
“Data Infrastructure” means the data processing resources within the Riskonnect Service, including but not limited to, data and file storage, within Customer’s account configured in the Riskonnect Service platform
Additional Terms and Conditions:
- Customer’s subscriptions include a specific quantity of Data Infrastructure, as reflected in Customer’s Riskonnect Application. If Customer exceeds the amount of Data Infrastructure, upon 30 days’ notice, Customer shall be charged for any additional Data Infrastructure used and pay additional subscription fees
- Customer Data is available for download at all times through reporting capabilities included in the Application(s). Further, at any time during the Term of this Agreement, upon written request by Customer upon payment of applicable fees or use of Annual Service hours, Riskonnect shall make the Customer Data available to Customer in the Riskonnect format and layout.
- Only if Customer’s subscriptions include EDI, the following terms shall apply: Riskonnect ClearSight Enterprise Edition supports IAIABC standards EDI releases 1, 2 and 3, as required by the applicable state. EDI States included for Customer are set forth in the applicable Statement(s) of Work. Configuration of additional states may require additional fees and/or erode the Annual Service hours. Riskonnect is not responsible for maintaining claim and payment data in compliance with state requirements. SaaS Application will provide basic functionality that will allow Customer to transmit EDI data to jurisdictions via the Riskonnect ClearSight Data Router or a third-party clearinghouse/data router. Riskonnect is not responsible for accuracy of Customer Data contained in submissions or for the initiation of the transmission processes. Riskonnect will not provide services/EDI transmission related to proof of coverage.States limit acceptance of EDI transmissions through particular vendors or through particular mechanisms. If Customer will be using the SaaS Application EDI functionality for states that accept EDI transmissions only from particular vendors other than Riskonnect or through mechanisms other than those offered by Riskonnect, Customer will be responsible for establishing and maintaining a relationship with such vendors or otherwise arranging for transmission from the SaaS Application through such mechanisms. In these cases, Riskonnect shall not have responsibility for transmissions to or from the state. SaaS Application functionality will then be configured to permit transmission to and from such vendors or through such mechanism. Riskonnect shall have no responsibility for the services or products, or transmission provided by such vendors.If EDI transmissions are made through a third-party vendor, Customer is responsible for providing Riskonnect with necessary third-party authorizations and the user ID and password to access the Customer’s account to permit for delivery and receipt of files to that vendor from the SaaS Application.As part of the initial setup, Riskonnect will deploy and configure the standard EDI (FROI/SROI) module, set up the transmission method (according to state requirements) and set up the transmission schedule. Riskonnect will assist Customer during state acceptance testing period but is not responsible for training Customer on state requirements or for creating test plans based on state requirements. Customer will be required to establish trading partner agreements with all jurisdictions prior to state testing.The data elements of the FROI/SROI EDI transmission will reside in a holding table in the SaaS Application database until the data is sent (as set forth below) to the state’s EDI data warehouse.Customer is responsible for:
- entry and accuracy of all EDI data entered in the system and for meeting state requirements; marking EDI transmissions in the SaaS Application with a status of “Mark to Send” when transmissions are ready to be submitted to the state; and
- understanding the timing originally set up at the time of implementation related to when EDI transmissions will be processed and sent to the State(s).Riskonnect requires Customer to maintain remote access to streamline the testing process and allow Riskonnect to perform services related to EDI under this Exhibit. If Customer disables remote assess, Customer will incur additional remote and/or telephonic assistance hours and will be responsible for additional fees incurred as a result of such additional assistance hours.Riskonnect recommends that Customer transmits claims daily. Riskonnect shall not be responsible for any state, Customer or third-party system failures or connectivity issues which may result in failures to transmit Customer’s transactions within the state’s required time frames.Customer is responsible for:
- claims administration, claims decisions and business decisions related to data that is tracked in the SaaS Application and transmitted to the state; and
- ensuring that data is populated in the SaaS Application in accordance with state rules, including ensuring that data is available for all data elements/fields required by the state.All changes to setup of this feature after completion of state acceptance testing will be applied against ongoing service hours.Riskonnect is not responsible for any third-party fees or state penalties related to state EDI requirements.
- Only if Customer’s subscriptions include a Medicare Section 111 Solution (CMS Solution), the following terms shall apply:Solution Options:The Medicare Section 111 Solution (the “Solution”) provided by Riskonnect includes several options to aid Customer in compliance with The Medicare, Medicaid, and SCHIP Extension Act of 2007 (“SCHIP”):
- Option 1 (Comprehensive Solution): A comprehensive solution wherein Riskonnect and a Strategic Service Provider (SSP) will facilitate the full cycle of reporting Medicare beneficiary data to Centers for Medicare and Medicaid Services (CMS).
- Option 2 (Claims/Eligibility Data Export): A solution for Customers who prefer to work with their own Reporting Agent (RA) or method for reporting Medicare beneficiary data to CMS and can choose to receive a standard data export from Riskonnect ClearSight applications.
- Alternate Reporting Agent Option: A solution wherein Riskonnect and a Strategic Service Provider (SSP) will facilitate exporting CMS data and receiving responses from an Alternate Reporting Agent who will serve as the Reporting Agent (RA) for the Customer. The Alternate Reporting Agent (not Riskonnect or the SSP) will facilitate reporting Medicare beneficiary data to Centers for Medicare and Medicaid Services (CMS). Neither Riskonnect nor SSP shall be responsible for any actions or omissions of the Alternate Reporting Agent.Unless specified otherwise, the Medicare Section 111 Solution Elements as defined in Section 1.1 of this Appendix apply to all options.The Solution is only supported by the following Riskonnect ClearSight proprietary software packages and versions (the “Supported Software”):
- Riskonnect ClearSight EnterpriseIn the event that Customer is not currently licensing the Supported Software, Customer will not be able to use the Solution without upgrading or migrating to the Supported Software. Any such upgrade or migration is not included in the scope of the Solution.CMS has identified data element requirements for the purpose of standardizing the process of mandatory reporting under Section 111 of SCHIP (the “CMS Data Elements”). This includes standardized data fields, history and response elements as outlined in the MMSEA Section 111 Medicare Secondary Payer Mandatory Reporting Liability Insurance (Including Self-Insurance), No-Fault Insurance, and Workers’ Compensation USER GUIDE (the “CMS User Manual”), as supplemented and amended by CMS.The CMS User Manual is available at the following link:
http://www.cms.gov/Medicare/Coordination-of-Benefits-and-Recovery/Mandatory-Insurer-Reporting-For-Non-Group-Health-Plans/NGHP-User-Guide/NGHP-User-Guide.htmlRiskonnect shall provide a repository within the Supported Software to store the CMS Data Elements. This repository shall house CMS Data Elements that Customer cannot accommodate within core tables in the Supported Software. In order to capture this data in the CMS Data Elements repository, workflow changes may be required by Customer. Capabilities to assign default data element values and handle data element modifications such as parsing Claimant Name into first name / last name and eliminating dashes in Social Security Numbers will be available within the Section 111 Data Mapping Tool (described below).Customer may wish to define multiple Responsible Reporting Entity (RRE) IDs within the Solution. Customers may define RRE IDs at the following levels only:
- Customer, Coverage, Location, Policy
- The following combinations only are supported for RRE ID definition:
- Customer
- Customer, Coverage
- Customer, Coverage, Policy
- Customer, Coverage, Location
- Claim LevelAssumptions:
- RRE ID definition at levels other than those identified above will require customization at an additional feeRiskonnect shall provide a data mapping tool to map both data elements and codes to the CMS Data Elements.
- Mapping for Customers who use Professional Edition and Riskonnect ClearSight Enterprise – Mapping will be limited to data elements that reside in the following core tables: Claim (including extended tables), Location, Rolodex / Contact, and Policy for each RRE identified by Customer.The Riskonnect ClearSight Medicare Section 111 Solution Module includes a claim user interface (“Standard Section 111 Tab”), data structure, and logic processes required to capture and manage mapped CMS Data Elements for export to CMS. The Riskonnect ClearSight Section 111 Solution Module includes all CMS Data Elements as defined by CMS.During implementation, Riskonnect and/or Customer will deploy and configure the Solution as described in the corresponding Statement of Work. Duration and effort for implementation will vary depending on the specific implementation requirements of Customer, as reflected in specifications mutually agreed to by the parties. Riskonnect will work with Customer to deploy the Standard Section 111 Tab to Customer’s licensed version of the Supported Software and will provide a process to map any existing fields and codes in Customer’s licensed version of the Supported Software to the CMS Data Elements as provided for in the corresponding Statement of Work. Riskonnect is not responsible for any of Customer’s obligations to CMS under the requirements of SCHIP or for any failure of the Customer to provide the data elements required by CMS.Any system configuration services or changes required to comply with any CMS guidance issued under SCHIP (“CMS Section 111 requirements”) will be billed as incurred at Riskonnect’s then current rates or erode existing Annual Service hours. Examples of system configuration services or changes that are not included in the scope of the Solution include, but are not limited to, the following:
- Modifications to existing system configuration, codes, and screen design
- Creation of or modification to event notifications or validations for workflow purposes
- Changes to system security as a result of CMS Section 111 requirements
- Future configuration changes resulting from modifications to the existing CMS Section 111 requirements
- Modifications to data conversions occurring as a result of CMS Section 111 requirements
- Working meetings or project management efforts by Riskonnect staff to coordinate modification to existing configuration
- Changes required to transfer data to or from third-party sources
- Custom programming work or changes to existing custom programming or reports
- Assistance from Riskonnect with any Customer testing required by CMS under SCHIPImplementation will be considered complete once the Solution has been deployed, configured, tested and moved into production with SSP.Option 1 (Comprehensive Solution) Specific InformationStrategic Service ProviderExamWorks Clinical Solutions, LLC, as successor in interest to Gould & Lamb, LLC (“ExamWorks”) is Riskonnect’s designated Strategic Service Provider (SSP) for the Solution. More information about the SSP may be found at www.examworks-cs.com. Customer acknowledges and agrees that Customer shall designate ExamWorks as its Reporting Agent at the time of RRE Registration with CMS as required by SCHIP. In the event that Customer is not an RRE, Customer shall ensure that its customers that are RREs (the “Customer’s RREs”) are registered as such on the CMS Coordination of Benefits Secure Website (COBSW) and designate ExamWorks as RA at RRE Registration with CMS as required by SCHIP. Customer acknowledges and agrees that Customer shall deliver to SSP the required reporting information and CMS-defined reporting date as provided by CMS during the registration process.In the event Customer enters into a SOW after RRE registration, Customer will take all necessary steps required by CMS, such as designating ExamWorks as the Customer’s RA with CMS as required by SCHIP.SSP shall assign Customer a Single Point of Contact (SPOC) as well as an Account Manager to facilitate the reporting process to CMS. Responsibilities include, but are not limited to, issue resolution and training.Customer acknowledges and agrees that ExamWorks shall be solely responsible for submitting any required information to CMS received from Customer or Customer’s RRE. As the SSP will submit to CMS all data provided by or on behalf of the Customer to Riskonnect via the Solution, Customer acknowledges and agrees that the SSP will require access to Customer Data made available to Riskonnect by, or on behalf of, Customer and consents to the disclosure of such Customer Data to SSP by Riskonnect.
The SSP may, upon Customer’s consent, offer additional services to Customer. Customer shall enter into a separate agreement with the SSP for any such additional services. Riskonnect shall not be responsible for any obligations in connection with such separate agreement between Customer and the SSP.
In the event that the SSP services provided under the applicable Statement of Work are terminated either because the SSP designated in this Appendix has ceased supporting CMS reporting or for other reasons, Riskonnect shall provide to Customer the option of entering into a new or amended Statement of Work for the performance of Claims/Eligibility Data Export Services (Option 2) and shall use commercially reasonable best efforts to find an alternative SSP. Unless Customer elects to enter into a new or amended Statement of Work for Claims/Eligibility Data Export Services, Customer acknowledges and agrees that it shall designate an alternative SSP provided by Riskonnect as its RA and that such alternative SSP shall be solely responsible for submitting any required information to CMS received from Customer or Customer’s RREs. In the event Customer enters into a new or amended Statement of Work for Claims/Eligibility Data Export Services, Riskonnect shall have the right to terminate the services for the Option 1 (Comprehensive Solution).
Customer may elect to utilize a Customer Data Provider as its data provider for CMS Data Elements and may also elect to utilize the Solution to submit data to CMS on behalf of its Customer Data Provider. Customer shall be responsible for all CMS data element data quality and exchange of information with Customer Data Provider related to CMS data elements; Riskonnect bears no responsibility for data transfer to Customer Data Provider or quality of data received from Customer Data Provider. Riskonnect recommends that Customer increase frequency of data updates from Customer Data Provider to a minimum of weekly to best facilitate data transfer to the SSP where Customer will utilize Riskonnect ClearSight’s Comprehensive Solution (Option 1) to submit data to CMS on behalf of their Customer Data Provider.
Riskonnect ClearSight Medicare Section 111 Solution Module for Option 1
In addition to the elements defined above, the Section 111 Module for Option 1 includes the following:
- Response codes from the SSP processing / result files
- All data required to facilitate exports to and imports from SSPPost-Implementation Functionality / WorkflowRiskonnect shall submit CMS Data Elements provided by Customer or Customer’s Data Provider to the SSP on a scheduled weekly basis. Riskonnect is not responsible for the accuracy of any CMS Data Elements or for ensuring that such CMS Data Elements comply with CMS Section 111 requirements.SSP shall submit the Claim Input file transmissions provided by Customer (consisting of all CMS Data Elements provided by Customer or Customer Data Provider to Riskonnect) to CMS on a quarterly basis within Customer’s CMS-assigned quarterly submission.CMS shall submit a response regarding the quarterly Claim Input file transmission to SSP. The response from CMS shall be processed by the SSP and submitted to Riskonnect. SSP shall also notify Customer by e-mail that a response has been submitted to Riskonnect. Such results shall be available for Customer’s review within the Supported Software, and Customer is responsible for review of and required action on all such results within five (5) business days of receipt of the e-mail notification from SSP.SSP shall submit Medicare Eligibility queries to CMS on a monthly basis in order to verify whether injured parties reported in the CMS Data Elements are eligible for Medicare coverage.CMS shall submit a response regarding the monthly Medicare eligibility check to SSP. Response shall be processed by the SSP and supplied back to Riskonnect via the weekly transmission process between Riskonnect and SSP.Customer must respond to and correct all errors received in response files from the SSP within five (5) business days of receipt of the e-mail notification from SSP.
Data Transmissions from Riskonnect to SSP for ASP Customers:
Data transmissions to SSP for ASP Customers include weekly Claim Input file transmission and weekly Medicare Eligibility file transmission for each RRE for which Customer sets up mapping in the Riskonnect ClearSight Medicare Section 111 Solution Module of Supported Software as described in this Exhibit.
The Claim Input file is based on Section 111 specifications. The claim detail, auxiliary, and TIN reference records are denormalized into a single claim record with additional fields required by SSP to manage system administration and compliance. The Medicare Eligibility file is used for submitting claims to test for Medicare eligibility. It includes injured party information required to check Medicare eligibility with CMS.
Receipt of Data Imports by Riskonnect from SSP for ASP Customers:
Data imports from SSP include a Claim Result file, a Claim Status file, and a Section 111 Response file for each RRE as identified in the RRE Appendix. Relevant results are imported into the Supported Software and available for Customer’s review within the Riskonnect ClearSight Medicare Section 111 Solution Module.
This deliverable includes weekly transmission from SSP to Riskonnect of the Claim Result file and Claim Status file, as well as quarterly transmission from SSP to Riskonnect of the Section 111 Response file. A Claim Result file is created automatically for each weekly submission to SSP. This file contains records that were not processed by the SSP due to errors. A Claim Status file is provided weekly by SSP for each RRE and contains claim validation, eligibility, and compliance updates for all claims currently in the SSP’s application for the Customer. The Section 111 Response file is provided by CMS for each RRE within forty-five (45) days of receipt of a Section 111 required submission and TIN Reference file. CMS Claim Response data are provided to Customer in the Section 111 Response File received from SSP.
Option 2 (Claims/Eligibility Data Export) Specific Information:
Riskonnect shall submit CMS Data Elements provided by Customer or Customer Data Provider to the Customer or to Reporting Agent designated by Customer on a scheduled weekly basis. Riskonnect is not responsible for the accuracy of any CMS Data Elements or for ensuring that such CMS Data Elements comply with the Section 111 requirements issued by CMS.
Customer may elect to utilize a Customer Data Provider as their data provider for CMS Data Elements, and may also elect to utilize the Solution to submit data to CMS on behalf of their Customer Data Provider. Customer must maintain all responsibility for CMS data element data quality and exchange of information with Customer Data Provider related to CMS data elements; Riskonnect bears no responsibility for data transfer to Customer Data Provider or quality of data received from Customer Data Provider. Riskonnect recommends that Customer increase frequency of data updates from Customer Data Provider to a minimum of weekly to best facilitate data transfer to CMS on behalf of their Customer Data Provider.
Assumptions:
- Riskonnect will not make changes to the standard export file layouts. Changes to the layout that are not initiated by Riskonnect will require an additional fee.
- Option 2 is export only and does not include an import of Section 111 Response file or Medicare Eligibility Response file.
- Customer is responsible for data in the Supported Software, including identification and resolution of all claim data errors related to the Section 111 reporting process.
- Customer is responsible for any fees levied by CMS due to data errors in the Supported Software.
- Where Riskonnect needs to participate in error resolution, time spent on those activities will be billed as incurred at Riskonnect then current rates or erode existing Annual Service hours.
- Riskonnect will make changes to the file layout as needed to support changes to the CMS reporting requirements. Riskonnect will provide advance warning of those changes to Customer. Customer is responsible for coordinating change management with Customer’s Solution or Customer’s Reporting Agent.Data Transmissions from Riskonnect to Customer’s Solution or Customer’s Reporting Agent for ASP CustomersRiskonnect will transmit export file(s) in the Riskonnect ClearSight standard export layout to Customer’s Solution or Customer Agent’s FTP site via Secure FTP.Export files include:
- Weekly claim detail, including TIN reference data file which includes claims with (a) non-closed status, (b) financial activity within the last quarter, or (c) are Medicare eligible, will be included in this file export.
- (OPTIONAL) Weekly Medicare Eligibility Query data file. Eligibility determination must be manually entered into the claims database. Standard layout definition will be made available to customers selecting this option.
- Alternate Reporting Agent Delivery Option – Specific InformationStrategic Service ProviderExamWorks Clinical Solutions, LLC, as successor in interest to Gould & Lamb, LLC (“ExamWorks”) is Riskonnect’s designated Strategic Service Provider (SSP) for the Solution. More information about the SSP may be found at www.examworks-cs.com. Customer acknowledges and agrees that Customer shall notify Riskonnect and the SSP with the identity of its Alternate Reporting Agent or the Alternate Reporting Agent for its customers that are RREs (the “Customer’s RREs”).SSP shall assign Customer a Single Point of Contact (SPOC) as well as an Account Manager to facilitate the reporting process to the Alternate Reporting Agent. Responsibilities include, but are not limited to, issue resolution and training.Customer acknowledges and agrees that ExamWorks shall be solely responsible for submitting any required information to Alternate Reporting Agent received from Customer or Customer’s RRE and that Alternate Reporting Agent shall be solely responsible for submitting any required information to CMS. As the SSP will submit to Alternate Reporting Agent all data provided by or on behalf of the Customer to Riskonnect via the Solution, Customer acknowledges and agrees that the SSP will require access to Customer Data made available to Riskonnect by, or on behalf of, Customer and consents to the disclosure of such Customer Data to SSP by Riskonnect.The SSP may, upon Customer’s consent, offer additional services to Customer. Customer shall enter into a separate agreement with the SSP for any such additional services. Riskonnect shall not be responsible for any obligations in connection with such separate agreement between Customer and the SSP.In the event that the SSP services provided under the applicable Statement of Work are terminated either because the SSP designated in this Exhibit has ceased supporting CMS reporting or for other reasons, Riskonnect shall provide to Customer the option of entering into a new or amended Statement of Work for the performance of Claims/Eligibility Data Export Services (Option) and shall use commercially reasonable best efforts to find an alternative SSP. In the event Customer enters into a new or amended Statement of Work for Claims/Eligibility Data Export Services, Riskonnect shall have the right to terminate the services for the Alternate Reporting Agent Solution.Customer may elect to utilize a Customer Data Provider as its data provider for CMS Data Elements and may also elect to utilize the Solution to submit data to CMS on behalf of its Customer Data Provider. Customer shall be responsible for all CMS data element data quality and exchange of information with Customer Data Provider related to CMS data elements; Riskonnect bears no responsibility for data transfer to Customer Data Provider or quality of data received from Customer Data Provider. Riskonnect recommends that Customer increase frequency of data updates from Customer Data Provider to a minimum of weekly to best facilitate data transfer to the SSP where Customer will utilize Riskonnect ClearSight’s Alternate Reporting Agent Solution to submit data to Alternate Reporting Agent on behalf of their Customer Data Provider.
In addition to the elements defined above, the Section 111 Module for Alternate Reporting Agent includes the following:
- Response codes from the SSP processing / result files
- All data required to facilitate exports to and imports from SSPPost-Implementation Functionality / Workflow:Riskonnect shall submit CMS Data Elements provided by Customer or Customer’s Data Provider to the SSP on a scheduled weekly basis. Riskonnect is not responsible for the accuracy of any CMS Data Elements or for ensuring that such CMS Data Elements comply with CMS Section 111 requirements.SSP shall submit the Claim Input file transmissions provided by Customer (consisting of all CMS Data Elements provided by Customer or Customer Data Provider to Riskonnect) to Alternate Reporting Agent upon receipt from Riskonnect.Neither Riskonnect nor SSP are responsible for submitting Claim Input file transmissions to CMS within Customer’s CMS-assigned quarterly submission or receiving and processing CMS response files.The response received by SSP from Alternate Reporting Agent shall be processed by the SSP and submitted to Riskonnect. Such results shall be available for Customer’s review within the Supported Software.Customer acknowledges and agrees that it is solely responsible for ensuring that: (1) Alternate Reporting Agent submits Medicare Eligibility queries to CMS in order to verify whether injured parties reported in the CMS Data Elements are eligible for Medicare coverage; and (2) Alternate Reporting Agent acknowledges receipt of and processes responses from CMS regarding the Medicare eligibility check.Responses received by SSP from Alternate Reporting Agent shall be processed by the SSP and supplied back to Riskonnect via the weekly transmission process between Riskonnect and SSP.
Data Transmissions from Riskonnect to SSP for ASP Customers:
Data transmissions to SSP for ASP Customers include weekly Claim Input file transmission and weekly Medicare Eligibility file transmission for each RRE for which Customer sets up mapping in the Riskonnect ClearSight Medicare Section 111 Solution Module of Supported Software as described in this Exhibit.
The Claim Input file is based on Section 111 specifications. The claim detail, auxiliary, and TIN reference records are denormalized into a single claim record with additional fields required by SSP to manage system administration and compliance. The Medicare Eligibility file is used for submitting claims to test for Medicare eligibility. It includes injured party information required to check Medicare eligibility with CMS.
Receipt of Data Imports by Riskonnect from SSP for ASP Customers:
Data imports from SSP include data provided to SSP by the Alternative Reporting Agent (which may include a Claim Result file, a Claim Status file, and a Section 111 Response file for each identified RRE). The Alternative Reporting Agent may provide additional details regarding the data it shall provide to SSP. Relevant results are imported into the Supported Software and available for Customer’s review within the Riskonnect ClearSight Medicare Section 111 Solution Module.
This deliverable includes weekly transmission from SSP to Riskonnect of the Claim Result file and Claim Status file, as well as quarterly transmission from SSP to Riskonnect of the Section 111 Response file returned by Alternate Reporting Agent. A Claim Result file is created automatically for each weekly submission to SSP. This file contains records that were not processed by the SSP due to errors. A Claim Status file is provided weekly by SSP for each RRE and contains claim validation, eligibility information received from Alternate Reporting Agent, and compliance updates for all claims currently in the SSP’s application for the Customer. Riskonnect and SSP are not responsible for the Section 111 Response file provided by CMS to Alternative Reporting Agent for each RRE within forty-five (45) days of receipt of a Section 111 required submission and TIN Reference file. CMS Claim Response data is provided to Customer in the Section 111 Response File returned to SSP by Alternate Reporting Agent.
Customer Responsibilities:
If Customer is an RRE under CMS guidelines, Customer shall register as such on the COBSW as required by SCHIP and/or coordinate registration of their customers which may be RREs as required by SCHIP (the “RRE Registration”). Compliance with the requirements of the COBSW (and all CMS Mandatory Insurer Reporting, or Section 111, obligations generally) is solely Customer’s responsibility. To ascertain its Section 111 obligations and determine whether it is an RRE, Customer should consult the CMS Section 111 website at www.cms.hhs.gov/MandatoryInsRep or such other website as CMS might provide.
In the event Customer enters into a Statement of Work for the CMS Solution after RRE Registration, Customer shall provide proof of its registration as an RRE on the COBSW to Riskonnect upon the effective date of such Statement of Work and shall take all necessary steps required or provided by CMS.
Customer is responsible for registration with the COBSW and designation of the applicable organization as Reporting Agent (RA) or making any changes to the designated RA as may be required by Riskonnect. Customer is responsible for providing RRE ID information to Riskonnect.
Data Elements:
Customer must ensure that injured party data elements and the Medicare eligibility flag contained within the CMS Data are properly captured on the base claim table for Professional Edition (“PE”) and Riskonnect ClearSight Enterprise (on EI records for Workers Comp claims and CI records for non-WC claims).
The Solution will NOT automate the management of RRE ID assignments based on claim takeovers, deductible limits, re-insurance, stop loss insurance, excess insurance, umbrella insurance, guaranty funds, patient compensation funds, etc. Modification of data within Supported Software will be the sole responsibility of Customer to accommodate these types of business decisions. Customer will be responsible for manual entry and management of RRE assignments/changes, TPOC (Total Payment Obligation of Claimant) data, and ORM (On-going Responsibility for Medicals) data. Customer will also be responsible for correcting any data entry errors pertaining to this data entry.
Customer may elect to utilize a Customer Data Provider as their data provider for CMS Data Elements and may also elect to utilize a Riskonnect ClearSight Medicare Section 111 Solution to submit data to CMS on behalf of their Customer Data Provider. Customer must maintain all responsibility for CMS data element data quality and exchange of information with Customer Data Provider related to CMS data elements; Riskonnect bears no responsibility for data transfer to Customer Data Provider. Riskonnect recommends that Customer increase frequency of data updates from Customer Data Provider to a minimum of weekly to best facilitate data transfer to CMS on behalf of their Customer Data Provider.
User Acceptance Testing:
Customer User Acceptance Testing is required for approval of all deliverables outlined herein. If Customer does not provide Riskonnect with feedback, the deliverable will be deemed accepted thirty (30) days after delivery.
Upon implementation of the Solution, Customer shall be solely responsible for:
- Accuracy of data required by and submitted to CMS and any damages of any nature resulting from the transmission of incorrect information
- Timely entry and update of data required by CMS in the appropriate fields within the Medicare Section 111 Module
- Identification and resolution of all errors in the CMS Data Elements and ensuring that the CMS Data Elements comply with the Section 111 requirements issued by CMS
- Ensuring that the CMS Data Elements have been provided by Customer or Customer Data Provider for all data elements/fields required by the CMS Section 111 guidelines in a timely manner for accurate reporting to CMS
- Claims administration, claims decisions and business decisions related to CMS Data ElementsAdditional Terms and Conditions:Riskonnect shall not be responsible for any CMS, Customer, Customer Data Provider, SSP, Alternate Reporting Agent or other third-party system failures or connectivity issues which may result in failures to transmit Customer’s transactions within the CMS required time frames. Riskonnect shall not be responsible for errors or omissions, negligence of, or connectivity issues or delays by SSP or the Alternate Reporting Agent. Notwithstanding anything to the contrary in the Agreement, Riskonnect shall in no event be liable for any indirect, special, punitive, incidental or consequential damages in any action arising from or related to any software provided or services performed in connection with the Solution, whether based in contract, tort, intended conduct or otherwise. The maximum aggregate liability of Riskonnect in connection with the Solution shall in no event exceed the fees actually paid by Customer to Riskonnect solely for the Medicare Section 111 Solution in the twelve (12) month period immediately preceding the date on which such claim is made.In the event that the SSP changes its fees to Riskonnect, Riskonnect shall notify Customer in writing within thirty (30) days of Riskonnect receipt of notice regarding SSP’s fee increase. Customer agrees that Riskonnect shall have the right to adjust the annual fee by the amount set forth in such notice to Customer.
- Only if Customer’s subscriptions include Work Cover/Comcare Submissions (applicable in Australia only), the following terms shall apply:As new versions of the EDT specifications are released, Riskonnect will upgrade the Enterprise and ClearSight systems to include the new specifications and will release WorkCover and Comcare specific interim upgrades outside of the standard core Enterprise and ClearSight product release cycles, as required.Notwithstanding anything to the contrary in the Agreement or any Statement(s) of Work entered into by Riskonnect and Customer, Riskonnect does not represent or warrant that any of its or its Affiliates’ proprietary software products licensed by Customer are intended to assure compliance with any legal or regulatory requirements. The parties acknowledge and agree that compliance with any legal and regulatory requirements applicable to the Customer is solely the responsibility of the Customer. Riskonnect or its Affiliates may provide to Customer information and services related to regulatory issues relating to Customer’s risk management program. Any reports or advice provided by Riskonnect or its Affiliates will be based on publicly available information and Riskonnect’s or its Affiliates’ experience as a risk management information systems provider in dealing with such matters for other Customers and should not be relied upon as accounting, regulatory or tax advice. In all instances, Riskonnect and its Affiliates recommend that Customer seek its own advice on accounting, regulatory and tax matters from professional legal and tax advisers.