Data Use Each party may use Connected Account Data in accordance with this Agreement and the consent (if any) each obtains from each Connected Account. This consent includes, as to Stripe, consent it receives via the Connected Account Agreement.
Data Mining 4.1. Provider agrees not to use GLO Data for unrelated commercial purposes, advertising or advertising-related services, or for any other purpose not explicitly authorized by the GLO in this Contract or any document related thereto. 4.2. Provider agrees to take all reasonably feasible physical, technical, administrative, and procedural measures to ensure that no unauthorized use of GLO Data occurs.
Malicious Use of Orphan Glue Records Registry Operator shall take action to remove orphan glue records (as defined at xxxx://xxx.xxxxx.xxx/en/committees/security/sac048.pdf) when provided with evidence in written form that such records are present in connection with malicious conduct.
Data Location 1.1. The CONTRACTOR shall not store or transfer non-public COUNTY data outside of the United States. This includes backup data and Disaster Recovery locations. The CONTRACTOR will permit its personnel and contractors to access COUNTY data remotely only as required to provide technical support. (Remote access to data from outside the continental United States is prohibited unless approved in advance and in writing by the County.) 1.2. The CONTRACTOR must notify the COUNTY in advance and in writing of any location changes to CONTRACTOR’s data center(s) that will process or store County data.
Data Rights User retains all rights over any data and other information that User may provide, upload, transfer or make available in relation to, or which is collected from User’s devices or equipment by, the Software, including, without limitation, information pertaining to how the Software obtains, uses, and respond to inputs, location, ambient conditions, and other information related to use and operation of the Software with Honeywell or third-party products, software or websites (“Usage Data”). Honeywell has the right to retain, transfer, disclose, duplicate, analyze, modify, and otherwise use Usage Data to protect, improve, or develop its products, services, and related offerings. All information, analysis, insights, inventions, and algorithms derived from Usage Data by Honeywell (but excluding the Usage Data itself) and any intellectual property rights obtained related thereto, are owned exclusively and solely by Xxxxxxxxx.
Certain Additional Actions Regarding Intellectual Property If any Event of Default shall have occurred and be continuing, upon the written demand of the Collateral Agent, each Pledgor shall execute and deliver to the Collateral Agent an assignment or assignments of the registered Patents, Trademarks and/or Copyrights and Goodwill and such other documents as are necessary or appropriate to carry out the intent and purposes hereof. Within five (5) Business Days of written notice thereafter from the Collateral Agent, each Pledgor shall make available to the Collateral Agent, to the extent within such Pledgor’s power and authority, such personnel in such Pledgor’s employ on the date of the Event of Default as the Collateral Agent may reasonably designate to permit such Pledgor to continue, directly or indirectly, to produce, advertise and sell the products and services sold by such Pledgor under the registered Patents, Trademarks and/or Copyrights, and such persons shall be available to perform their prior functions on the Collateral Agent’s behalf.
Project or Building Name and Signage Landlord shall have the right at any time to change the name of the Project or Building and to install, affix and maintain any and all signs on the exterior and on the interior of the Project or Building as Landlord may, in Landlord’s sole discretion, desire. Tenant shall not use the name of the Project or Building or use pictures or illustrations of the Project or Building in advertising or other publicity or for any purpose other than as the address of the business to be conducted by Tenant in the Premises, without the prior written consent of Landlord.
Insurance and Fingerprint Requirements Information Insurance If applicable and your staff will be on TIPS member premises for delivery, training or installation etc. and/or with an automobile, you must carry automobile insurance as required by law. You may be asked to provide proof of insurance. Fingerprint It is possible that a vendor may be subject to Chapter 22 of the Texas Education Code. The Texas Education Code, Chapter 22, Section 22.0834. Statutory language may be found at: xxxx://xxx.xxxxxxxx.xxxxx.xxxxx.xx.xx/ If the vendor has staff that meet both of these criterion: (1) will have continuing duties related to the contracted services; and (2) has or will have direct contact with students Then you have ”covered” employees for purposes of completing the attached form. TIPS recommends all vendors consult their legal counsel for guidance in compliance with this law. If you have questions on how to comply, see below. If you have questions on compliance with this code section, contact the Texas Department of Public Safety Non-Criminal Justice Unit, Access and Dissemination Bureau, FAST-FACT at XXXX@xxxxx.xxxxx.xx.xx and you should send an email identifying you as a contractor to a Texas Independent School District or ESC Region 8 and TIPS. Texas DPS phone number is (000) 000-0000. See form in the next attribute to complete entitled: Texas Education Code Chapter 22 Contractor Certification for Contractor Employees
Data Requirements • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.
GENERAL SERVICE DESCRIPTION Service Provider currently provides active medical, pharmacy(Rx) and dental administration for coverages provided through Empire and Anthem (medical), Medco(Rx), MetLife(dental) and SHPS (FSA) (Empire, Anthem, Medco, MetLife and SHPS collectively, the “Vendors”) for its U.S. Active, Salaried, Eligible Employees (“Covered Employees”). Service Provider shall keep the current contracts with the Vendors and the ITT CORPORATION SALARIED MEDICAL AND DENTAL PLAN (PLAN NUMBER 502 EIN 00-0000000) and the ITT Salaried Medical Plan and Salaried Dental Plan General Plan Terms (collectively, the “Plans”) and all coverage thereunder in full force through December 31, 2011 for Service Recipient’s Covered Employees. All claims of Service Recipient’s Covered Employees made under the Plans and incurred on or prior to December 31, 2011 the (“2011 Plan Year”) will be adjudicated in accordance with the current contract and Service Provider will continue to take such actions on behalf of Service Recipient’s Covered Employees as if such employees are employees of Service Provider. All medical, dental, pharmacy and FSA claims of Service Recipient’s Covered Employees made under the Plans (the “Claims”) will be paid by the Vendors on behalf of the Service Provider. Service Recipient will pay Service Provider for coverage based on 2011 budget premium rates previously set for the calendar year 2011 and described in the “Pricing” section below. Service Recipient will pay Service Provider monthly premium payments for this service, for any full or partial months, based on actual enrollment for the months covered post-spin using enrollments as of the first (1st) calendar day of the month, commencing on the day after the Distribution Date. Service Recipient will prepare and deliver to Service Provider a monthly self xxxx containing cost breakdown by business unit and plan tier as set forth on Attachment A, within five (5) Business Days after the beginning of each calendar month. The Service Recipient will be required to pay the Service Provider the monthly premium payments within ten (10) Business Days after the beginning of each calendar month. A detailed listing of Service Recipient’s employees covered, including the Plans and enrollment tier in which they are enrolled, will be made available to Service Provider upon its reasonable request. Service Provider will retain responsibility for executing funding of Claim payments and eligibility management with Vendors through December 31, 2013. Service Provider will conduct a Headcount True-Up (as defined below) of the monthly premiums and establish an Incurred But Not Reported (“IBNR”) claims reserve for Claims incurred prior to December 31, 2011 date, but paid after that date, and conduct a reconciliation of such reserve. See “Headcount True-Up” and “IBNR Reconciliation” sections under Additional Pricing for details.
