Data Sharing The GRANTEE BENEFICIARY agrees to share data with the AGENCY as deemed necessary by AGENCY, in its sole discretion, for expenditure validation, trend review, and performance monitoring.
Traffic Management 9.2.1 During the Operating Period, Developer shall be responsible for the general management of traffic on the Project. Developer shall manage traffic so as to preserve and protect safety of traffic on the Project and Related Transportation Facilities and, to the maximum extent practicable, to avoid disruption, interruption or other adverse effects on traffic flow, throughput or level of service on the Project and Related Transportation Facilities. Developer shall conduct traffic management in accordance with all applicable Technical Provisions, Technical Documents, Laws and Governmental Approvals, and in accordance with the Traffic Management Plan.
9.2.2 Developer shall prepare and submit to TxDOT and the Independent Engineer for TxDOT approval a Traffic Management Plan for managing traffic on the Project and Related Transportation Facilities after the commencement of traffic operations on any portion of the Project, addressing (a) orderly and safe movement and diversion of traffic on Related Transportation Facilities during Project construction, (b) orderly and safe movement of traffic on the Project and (c) orderly and safe diversion of traffic on the Project and Related Transportation Facilities necessary in connection with field maintenance and repair work or Renewal Work or in response to Incidents, Emergencies and lane closures. Developer shall prepare the Traffic Management Plan according to the schedule set forth in the Technical Provisions. The Traffic Management Plan shall comply with the Technical Provisions and Technical Documents concerning traffic management and traffic operations. Developer shall carry out all traffic management during the Term in accordance with the approved Traffic Management Plan.
9.2.3 Developer shall implement the Traffic Management Plan to promote safe and efficient operation of the Project and Related Transportation Facilities at all times during the course of any construction or operation of the Project and during the Utility Adjustment Work.
9.2.4 TxDOT shall have at all times, without obligation or liability to Developer, the right
9.2.4.1 Issue Directive Letters to Developer regarding traffic management
9.2.4.2 Provide on the Project, via message signs or other means consistent with Good Industry Practice, non-Discriminatory traveler and driver information, and other public information (e.g. amber alerts), provided that the means to disseminate such information does not materially interfere with the functioning of the ETCS.
Information Management Information and Records
Account Management 15.1 The Contractor is required to provide a dedicated Strategic Account Manager who will be the main point of contact for the Authority. The Strategic Account Manager will: Attend quarterly, or as otherwise agreed, review meetings with the Authority, in person at the Authority’s premises or other locations as determined by the Authority Attend regular catch-up meetings with the Authority, in person or by telephone/videoconference Resolve any on-going operational issues which have not been resolved by the Contractor or Account Manager(s) and therefore require escalation Ensure that the costs involved in delivering the Framework are as low as possible, whilst always meeting the required standards of service and quality.
15.2 The Contractor is also required to provide a dedicated Account Manager for every Framework Public Body using the Framework, if required by the Framework Public Body. The service to be provided will be agreed with each Framework Public Body and may include: regular review meetings, which may be in person at the Framework Public Bodies’ premises, by video-conference, webinar or telephone Regular catch-up meetings/telephone calls to discuss current and on-going issues Work with the Framework Public Bodies Contract Manager to resolve any on-going operational issues Work with the Framework Public Body ’s Contract Manager to pro-actively introduce initiatives to: Create efficiencies in processes Improve the environmental performance of the contract.
15.3 It is expected that end users will contact the Contractor in the first instance to resolve any operational issues. The Account Manager will act as a point of escalation to be contacted either by end users or by the Framework Public Body’s Contract Manager should there be issues that the Contractor needs to resolve.
15.4 Further details of the roles and responsibilities of the Contractor, Authority and Framework Public Bodies are provided in Schedule 4 – Management Arrangements
Data Storage Where required by applicable law, Student Data shall be stored within the United States. Upon request of the LEA, Provider will provide a list of the locations where Student Data is stored.
Virus Management DST shall maintain a malware protection program designed to deter malware infections, detect the presence of malware within DST environment.
Patch Management All workstations, laptops and other systems that process and/or 20 store PHI COUNTY discloses to CONTRACTOR or CONTRACTOR creates, receives, maintains, or 21 transmits on behalf of COUNTY must have critical security patches applied, with system reboot if 22 necessary. There must be a documented patch management process which determines installation 23 timeframe based on risk assessment and vendor recommendations. At a maximum, all applicable 24 patches must be installed within thirty (30) calendar or business days of vendor release. Applications 25 and systems that cannot be patched due to operational reasons must have compensatory controls 26 implemented to minimize risk, where possible.
Information Sharing (a) HHSC will provide the MA Dual SNP with resources regarding the LTSS covered by Medicaid in accordance with this section.
(b) Texas Medicaid benefits are described in Attachment B, Texas Medicaid Summary of Benefits. The MA Dual SNP must include the Texas Medicaid Summary of Benefits in its Member Handbook for the MA Product.
(c) HHSC and the MA Dual SNP will identify and share information, such as the following:
(1) HHSC will provide the MA Dual SNP with links to online Medicaid LTSS provider information for the traditional fee-for-service and STAR+PLUS programs. Within thirty (30) business days after receiving such information, the MA Dual SNP must post a link to this information on its website.
(2) The MA Dual SNP must:
A) Notify Dual Eligible Members and Other Dual SNP Members, via its member communication materials that information concerning Medicaid provider participation is available on the MA Dual SNP’s website; and
B) Notify Dual Eligible Members and Other Dual SNP Members that they may request written copies of Medicaid Provider directories by contacting their STAR+PLUS MCO,
C) Assist the Dual Eligible Members and Other Dual SNP Members in obtaining printed copies of Medicaid Provider directories from their STAR+PLUS MCO, and
D) Verify that the Dual Eligible Members and Other Dual SNP Member received the requested directory.
(3) The MA Dual SNP must notify Network Providers that information concerning Medicaid provider participation is available on the MA Dual SNP’s website. The MA Dual SNP must provide this notice in the Network Provider agreement, Network Provider manuals, bulletins, faxes, policies and procedures, provider manual updates, or other contractual documents.
(4) The MA Dual SNP must have written procedures for ensuring that Dual Eligible Members and Other Dual SNP Members have access to the services identified in the MA Product, including policies regarding network adequacy that are consistent with the requirements of the MA Agreement. The MA Dual SNP must provide HHSC with a copy of these policies no later than 5 business days after a request.
(d) The MA Dual SNP must encourage Network Provider SNF to electronically submit to the HHSC Medicaid claims administrator a resident transaction notice within 72 hours after a Dual Eligible Member’s admission or discharge from the nursing facility, in accordance with 40 Tex. Admin. Code § 19.2615.
(e) The MA Dual SNP is required to notify HHSC of significant changes to the terms of its CMS contract within 10 business days of such changes, which may include but is not limited to the following: changes in the services areas; plan benefit package (PBP) changes; non-renewal; terminations or deficiencies of the contract; notices of intent to deny; and any novation agreements. Plans must submit any CMS warning letters or corrective action plans within 10 business days of receipt to the HHSC point-of- contact identified in Section 9.06.
(f) The MA Dual SNP is required to notify HHSC in the event the Plan receives less than a 3.0 star Medicare rating on either its Part C or Part D scores. The Plan must provide an outline of the steps proposed or implemented to improve the low score.
(g) The MA Dual SNP must participate in meetings with HHSC, telephonic or in person, relating to the health care provided under this Agreement and their compliance with this Agreement's terms, and to timely provide any necessary information and data upon HHSC's request.
(h) The MA Dual SNP, upon request from HHSC, must provide all documents it provides to and receives from CMS, within 30 days of the HHSC request, unless an extension is granted by HHSC.
Union Management Relations Any changes deemed necessary in this Agreement may be made by mutual agreement of the parties at any time during the life of this Agreement.
Asset Management Supplier will: i) maintain an asset inventory of all media and equipment where Accenture Data is stored. Access to such media and equipment will be restricted to authorized Personnel; ii) classify Accenture Data so that it is properly identified and access to it is appropriately restricted; iii) maintain an acceptable use policy with restrictions on printing Accenture Data and procedures for appropriately disposing of printed materials that contain Accenture Data when such data is no longer needed under the Agreement; iv) maintain an appropriate approval process whereby Supplier’s approval is required prior to its Personnel storing Accenture Data on portable devices, remotely accessing Accenture Data, or processing such data outside of Supplier facilities. If remote access is approved, Personnel will use multi-factor authentication, which may include the use of smart cards with certificates, One Time Password (OTP) tokens, and biometrics.
