Data and Interface Sample Clauses

Data and Interface. AR-23 The Contractor shall be fully capable of accepting and implementing enrollment and other data files via a secure file transfer protocol (SFTP) on or before October 30, 2022. AR-24 The Contractor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. AR-25 Enrollment File Transfers from the Department a. Maintain enrollment records for all Participants based on the Department’s enrollment files submitted to the Contractor. b. Maintain enrollment records in compliance with the required HIPAA standards. c. Not overwrite, update or in any way change the enrollment information without direction from the Department. The Department’s enrollment file shall be the official system of record. d. Accept the enrollment files in a format and frequency as required by the Department. The current enrollment file format and delivery schedule is in Attachment 5: Enrollment File Layout and Schedule, of the Contract. e. Accept routine enrollment files and an annual Open Enrollment file (generally provided at the end of November following Open Enrollment) for the purpose of generating ID cards for distribution prior to each Plan Year. The Open Enrollment file shall not be loaded into production by the Contractor. f. Process the enrollment files as required in PG-14 of Attachment 3: Performance Guarantees, of the Contract.
Sample 1Sample 2Sample 3
AutoNDA by SimpleDocs
Data and Interface. 24 Service Provider shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 30, 2014. 25 The Vendor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract.
Sample 1Sample 2
Data and Interface. AR-12 In the performance of the post payment claims audit, the Contractor shall use the data from the Department's HIMIS system as the official record. The Contractor shall be provided access to the Department's HIMIS system for retrieval of claims data. AR-13 Contractor must exchange weekly and monthly data and file transfers between the Contractor and third parties and/or the Department using asecure method, format, and frequency required by the Department. AR-14 The Contractor or any of its Subcontractors shall notify the Department immediately in the event of lost data or security breach. Notice to the Department may be made by phone or email. AR-15 Contractor shall be responsible for recreating or retrieving such lost data ina manner and schedule determined by the Department. AR-16 The Contractor is required to ensure confidential information is completely protected from unauthorized access. AR-17 The Contractor shall ensure that their equipment will not compromise the Department's data.
Sample 1
Data and Interface. The Contractor shall be fully capable of accepting and implementing enrollment and other data files via secure portal on or before December 1, 2022 or another date mutually agreed upon between the Contractor and the Department. The Contractor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. The Contractor shall maintain an information system capable of electronically receiving and updating Participant enrollment information (e.g., eligibility, name, address, coverage code). The Contractor shall accurately convert and load the Department’s enrollment files. The Contractor shall also: a. Maintain enrollment records for all Participants based on the Department’s enrollment files submitted to the Contractor. b. Maintain enrollment records in compliance with the required HIPAA standards. c. Not overwrite, update or in any way change the enrollment information without direction from the Department. The Department’s enrollment file shall be the official system of record. d. Accept the enrollment files in a format and frequency as required by the Department. The current enrollment file format and delivery schedule is in Attachment D of the RFP. e. Accept routine enrollment files and an Open Enrollment file (generally provided at the end of December following Open Enrollment) for the purpose of generating ID cards for distribution prior to the coverage Implementation Date. The Open Enrollment file shall not be loaded into production by the Contractor. f. Process the enrollment files as required in PG-14 of Attachment 3: Performance Guarantees, of the Contract. File transfers with other entities shall be exchanged in a secure method and approved by the Department.
Sample 1
Data and Interface. Contractor shall be fully capable of accepting and implementing eligibility and other data files via a secure file transfer protocol (sFTP) on or before October 30, 2017.
Sample 1
Data and Interface. 19. Contractor shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 1, 2015. 20. Contractor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. 21. Contractor shall maintain an information system capable of electronically receiving and updating Participant eligibility information (e.g., eligibility, name, address, coverage code). Contractor shall accurately convert and load the Department’s eligibility files. Contractor shall maintain eligibility records for all Participants based on the Department’s eligibility files submitted to Contractor. The maintenance of eligibility records shall be compliant with the required Xxxxx-Xxxxx-Xxxxxx Act standards. The Department’s eligibility file shall be the official system of record and Contractor shall not overwrite, update or in any way change the eligibility information without express direction from the Department. Contractor may update member addresses if Contractor is made aware of a more recent address than the address listed on the eligibility file. Contractor shall accept the eligibility files in a format and frequency as required by the Department. The current eligibility file format and delivery schedule is in Attachment D: Enrollment and Eligibility File, which may be subject to change in the future. The eligibility files shall be processed as required in PG-11 of Attachment B: Performance Guarantees. 22. Contractor shall develop, implement and maintain a Disaster Recovery Plan, a summary of which shall be reviewed by the Department on or before the effective date of the Contract. At a minimum, Contractor shall maintain backup of State files/data and shall provide services to Participants within 24 hours of a disaster.
Sample 1
Data and Interface. The Contractor shall not use, or otherwise disseminate, sell, copy, or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract. a. Contractor shall maintain an information system capable of electronically receiving and updating Participant eligibility information (e.g., name, mailing address, email address). Contractor shall accurately convert and load the Department’s eligibility files. b. Contractor shall maintain eligibility records in compliance with the required HIPAA standards. 7.1 Contractor shall assign a Contract Manager as the primary contact for the Department. 7.2 Contractor shall assign an Account Management Team to the Contract. Account Management Team will consist of individuals employed by the Contractor who will have primary responsibility for the Department’s account. Contractor shall provide a written list of its Account Management Team members within ten (10) Calendar Days of contract execution. All changes to the individuals listed shall be sent to the Department in writing, within ten (10) Calendar Days of the change. The Account Management Team shall include, but will not be limited to, an executive sponsor and a Contract Manager. 7.3 The Contractor shall meet with the Department quarterly. Contractor shall provide for Department approval a draft agenda five (5) Business Days in advance of a meeting, allowing changes to the agenda and a reasonable opportunity to prepare for the meeting. During each quarterly meeting, Contractor and Department will discuss Contractor's quarterly reports and other issues such as: performance guarantees, quality assurance, operations, benefit and program changes or enhancements, audits, trends utilization, program outcomes, customer service issues, and other issues reasonably related to the Contract. 7.4 Within five (5) Business Days after any meeting, Contractor shall provide the Department draft meeting minutes. The Department will review and may revise the draft minutes as appropriate and return to Contractor. 7.5 Progress meetings, issue meetings and emergency meetings shall be held as needed. Either Party may call such a meeting, subject to reasonable notice. Any meeting held in person shall be at the State offices in Tallahassee, Florida. Contractor shall not be entitled to additional compensation for meeting preparation or attendance. Wh...
Sample 1
AutoNDA by SimpleDocs
Data and Interface. Service Provider shall be fully capable of accepting and implementing eligibility and other data files via FTP on or before October 30, 2014. The Vendor shall not use, or otherwise disseminate, sell, copy or make available to any person or entity, data relating to any aspect of performance of the Services, without prior written authorization of the Department. This requirement shall survive the termination of the Contract.
Sample 1

Related to Data and Interface

  • Data Access Access to Contract and State Data The Contractor shall provide to the Client Agency access to any data, as defined in Conn. Gen Stat. Sec. 4e-1, concerning the Contract and the Client Agency that are in the possession or control of the Contractor upon demand and shall provide the data to the Client Agency in a format prescribed by the Client Agency and the State Auditors of Public Accounts at no additional cost.

  • System and Data Access Services a. System. Subject to the terms and conditions of this Addendum and solely for the purpose of providing access to Fund Data as set forth herein, State Street hereby agrees to provide the Fund, or certain third parties approved by State Street that serve as the Fund`s investment advisors, investment managers or fund accountants (the "Fund Accountants") or as the Fund`s independent auditors (the "Auditor"), with access to State Street`s Multicurrency HORIZONR Accounting System and the other information systems described in Attachment A (collectively, the "System") on a remote basis solely on the computer hardware, system software and telecommunication links described in Attachment B (the "Designated Configuration") or on any designated substitute or back-up equipment configuration consented to in writing by State Street, such consent not to be unreasonably withheld.

  • Data Access Services State Street agrees to make available to the Fund the Data Access Services subject to the terms and conditions of this Addendum and such data access operating standards and procedures as may be issued by State Street from time to time. The Fund shall be able to access the System to (i) originate electronic instructions to State Street in order to (a) effect the transfer or movement of cash or securities held under custody by State Street or (b) transmit accounting or other information (the transactions described in (i)(a) and (i)(b) above are referred to herein as “Client Originated Electronic Financial Instructions”), and (ii) access data for the purpose of reporting and analysis, which shall all be deemed to be Data Access Services for purposes of this Addendum.

  • Interface A defined set of transmission facilities that separate Load Zones and that separate the NYCA from adjacent Control Areas. Investor-Owned Transmission Owners. A Transmission Owner that is owned by private investors. At the present time these include: Central Xxxxxx Gas & Electric Corporation, Consolidated Edison Company of New York, Inc., New York State Electric & Gas Corporation, Niagara Mohawk Power Corporation, Orange and Rockland Utilities, Inc., and Rochester Gas and Electric Corporation.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Network Interface Device 4.1 The NID is defined as any means of interconnection of end-user customer premises wiring to BellSouth’s distribution plant, such as a cross-connect device used for that purpose. The NID is a single-line termination device or that portion of a multiple-line termination device required to terminate a single line or circuit at the premises. The NID features two independent xxxxxxxx or divisions that separate the service provider’s network from the End User’s on-premises wiring. Each chamber or division contains the appropriate connection points or posts to which the service provider and the End User each make their connections. The NID provides a protective ground connection and is capable of terminating cables such as twisted pair cable. 4.1.1 BellSouth shall permit Al-Call to connect Al-Call ’s loop facilities to on-premises wiring through the BellSouth NID or at any other technically feasible point.

  • Network Interconnection Architecture Each Party will plan, design, construct and maintain the facilities within their respective systems as are necessary and proper for the provision of traffic covered by this Agreement. These facilities include but are not limited to, a sufficient number of trunks to the point of interconnection with the tandem company, and sufficient interoffice and interexchange facilities and trunks between its own central offices to adequately handle traffic between all central offices within the service areas at a P.01 grade of service or better. The provisioning and engineering of such services and facilities will comply with generally accepted industry methods and practices, and will observe the rules and regulations of the lawfully established tariffs applicable to the services provided.

  • Interfaces GTE provides the CLECs with choices for access to OSS pre-ordering, ordering, maintenance and repair systems. Availability of the interfaces is fundamental to the CLEC being able to effectively do business with GTE. Additionally, in many instances, CLEC personnel must work with the service personnel of GTE. Measurements in this category assess the availability to the CLECs of systems and personnel at GTE work centers.

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

  • Network Access TENANT may find it necessary to purchase a network interface card, wireless PC card or other hardware in order to connect to the internet service. LANDLORD is not responsible for the purchase of these items and LANDLORD cannot guarantee compatibility with any device TENANT may have. The computer and network card must have software installed that supports the Internet Protocol commonly referred to as TCP/IP. Any conflicts between the software compatibility of the network and the TENANT’S computer operating system or any other feature will be the responsibility of the TENANT to resolve. LANDLORD will not be responsible for software issues related to the user’s personal computer.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!