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.
Rights of Data Subjects 5.1 You control access to Your Services environment that holds Personal Information about Your end users, and Your end users should direct any requests related to their rights under Applicable Data Protection Law to You.
5.2 To the extent such access is not available to You, Oracle will provide assistance with requests from individuals to access, delete or erase, restrict, rectify, receive and transmit, block access to or object to processing related to Personal Information held in Your Services environment on Oracle systems, insofar as reasonably and technically possible.
5.3 If Oracle directly receives any requests or inquiries from Your end users that have identified You as the Controller, it will promptly pass on such requests to You without responding to the end user.
Cost Sharing a) With respect to the funding in C6.1a), should there be an amount of employee co-pay, the Trust shall advise boards what that amount shall be. Unless advised otherwise, there will be no deductions upon the Participation Date.
b) Any further cost sharing or funding arrangements as per previous local collective agreements in effect as of August 31, 2014 remain status quo.
Pro Rata Sharing 63 32. Severability.........................................................64 33. Counterparts.........................................................64 34. Notices..............................................................64 35. Language.............................................................66 36. Jurisdiction.........................................................66 37.
Data shared with Subcontractors If DSHS Data provided under this Contract is to be shared with a subcontractor, the Contract with the subcontractor must include all of the data security provisions within this Contract and within any amendments, attachments, or exhibits within this Contract. If the Contractor cannot protect the Data as articulated within this Contract, then the contract with the sub- Contractor must be submitted to the DSHS Contact specified for this contract for review and approval.
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.
Line Sharing 4.1 ‘Line Sharing’ is an arrangement by which Verizon facilitates ICG’s provision of ADSL (in accordance with T1.413), Splitterless ADSL (in accordance with T1.419), RADSL (in accordance with TR # 59), Multiple Virtual Line (MVL (a proprietary technology)), or any other xDSL technology that is presumed to be acceptable for shared line deployment in accordance with FCC rules, to a particular Customer location over an existing copper Loop that is being used simultaneously by Verizon to provide analog circuit-switched voice grade service to that Customer by making available to ICG, solely for ICG’s own use, the frequency range above the voice band on the same copper Loop required by ICG to provide such services. This Section 4 addresses Line Sharing over loops that are entirely copper loops.
4.2 In accordance with, but only to the extent required by Applicable Law, Verizon shall provide Line Sharing to ICG for ICG’s provision of ADSL (in accordance with T1.413), Splitterless ADSL (in accordance with T1.419), RADSL (in accordance with TR # 59), MVL (a proprietary technology), or any other xDSL technology that is presumed to be acceptable for shared line deployment in accordance with FCC rules, on the terms and conditions set forth herein. In order for a Loop to be eligible for Line Sharing, the following conditions must be satisfied for the duration of the Line Sharing arrangement: (i) the Loop must consist of a copper loop compatible with an xDSL service that is presumed to be acceptable for shared-line deployment in accordance with FCC rules; (ii) Verizon must be providing simultaneous circuit-switched analog voice grade service to the Customer served by the Loop in question; (iii) the Verizon Customer’s dial tone must originate from a Verizon End Office Switch in the Wire Center where the Line Sharing arrangement is being requested; and (iv) the xDSL technology to be deployed by ICG on that Loop must not significantly degrade the performance of other services provided on that Loop.
4.3 Verizon shall make Line Sharing available to ICG at the rates set forth in the Pricing Attachment. In addition to the recurring and nonrecurring charges shown in the Pricing Attachment for Line Sharing itself, the following rates shown in the Pricing Attachment and in Verizon ’s applicable Tariffs are among those that may apply to a Line Sharing arrangement: (i) prequalification charges to determine whether a Loop is xDSL compatible (i.e., compatible with an xDSL service that is presumed to be acceptable for shared-line deployment in accordance with FCC rules); (ii) engineering query charges, engineering work order charges, or Loop conditioning (Digital Designed Loop) charges; (iii) charges associated with Collocation activities requested by ICG; and (iv) misdirected dispatch charges, charges for installation or repair, manual intervention surcharges, trouble isolation charges, and pair swap/line and station transfer charges.
4.4 The following ordering procedures shall apply to Line Sharing:
4.4.1 To determine whether a Loop qualifies for Line Sharing, the Loop must first be prequalified to determine if it is xDSL compatible. ICG must utilize the mechanized or manual Loop qualification processes described in the terms applicable to xDSL and Digital Designed Loops to make this determination.
4.4.2 ICG shall place orders for Line Sharing by delivering to Verizon a valid electronic transmittal service order or other mutually agreed upon type of service order. Such service order shall be provided in accordance with industry format and specifications or such format and specifications as may be agreed to by the Parties.
4.4.3 If the Loop is prequalified by ICG through the Loop prequalification database, and if a positive response is received and followed by receipt of ICG’s valid, accurate and pre-qualified service order for Line Sharing, Verizon will return an LSR confirmation within twenty-four
Network Security and Privacy Liability Insurance During the term of this Contract, Supplier will maintain coverage for network security and privacy liability. The coverage may be endorsed on another form of liability coverage or written on a standalone policy. The insurance must cover claims which may arise from failure of Supplier’s security resulting in, but not limited to, computer attacks, unauthorized access, disclosure of not public data – including but not limited to, confidential or private information, transmission of a computer virus, or denial of service. Minimum limits: $2,000,000 per occurrence $2,000,000 annual aggregate Failure of Supplier to maintain the required insurance will constitute a material breach entitling Sourcewell to immediately terminate this Contract for default.
Loss of Data In the event of loss of any State data or records where such loss is due to the intentional act, omission, or negligence of the Contractor or any of its subcontractors or agents, the Contractor shall be responsible for recreating such lost data in the manner and on the schedule set by the Contract Manager. The Contractor shall ensure that all data is backed up and is recoverable by the Contractor.
Data Subjects The categories of Data Subjects who we may collect Personal Data about may include the following where they are a natural person: the Customer, the directors and ultimate beneficial owner(s) of the Customer, your customers, employees and contractors, payers and payees. You may share with Airwallex some or all of the following types of Personal Data regarding Data Subjects: • full name; • email address; • phone number and other contact information; • date of birth; • nationality; • public information about the data subject; • other relevant verification or due diligence documentation as required under these terms; and • any other data that is necessary or relevant to carry out the Agreed Purposes.
