By Microsoft Microsoft will defend Customer against any third-party claim to the extent it alleges that a Product or Fix made available by Microsoft for a fee and used within the scope of the license granted under this agreement (unmodified from the form provided by Microsoft and not combined with anything else), misappropriates a trade secret or directly infringes a patent, copyright, trademark or other proprietary right of a third party. If Microsoft is unable to resolve a claim of infringement under commercially reasonable terms, it may, as its option, either: (1) modify or replace the Product or fix with a functional equivalent; or (2) terminate Customer’s license and refund any prepaid license fees (less depreciation on a five-year, straight-line basis) for perpetual licenses and any amount paid for Online Services for any usage period after the termination date. Microsoft will not be liable for any claims or damages due to Customer’s continued use of a Product or Fix after being notified to stop due to a third- party claim.
By Contractor Should the Contractor be liable for any payments to the State hereunder, interest, late payment charges and collection fee charges will be determined and assessed pursuant to Section 18 of the State Finance Law.
Checkoff A. In conformity with Section 2 of the Act, 39 U.S.C. 1205, without cost to the Union, the Employer shall deduct and remit to the Union the regular and periodic Union dues from the pay of employees who are members of the Union, provided that the Employer has received a written assignment which shall be irrevo- cable for a period of not more than one year, from each employee on whose account such deductions are to be made. The Employer agrees to remit to the Union all deductions to which it is entitled fourteen (14) days after the end of the pay period for which such deductions are made. Deductions shall be in such amounts as are designated to the Employer in writing by the Union.
B. The authorization of such deductions shall be in the fol- lowing form: I hereby assign to the National Association of Letter Carriers, AFL- CIO, from any salary or wages earned or to be earned by me as your employee (in my present or any future employment by you) such regular and peri- odic membership dues as the Union may certify as due and owing from me, as may be established from time to time by said Union. I authorize and direct you to deduct such amounts from my pay and to remit same to said Union at such times and in such manner as may be agreed upon between you and the Union at any time while this authori- zation is in effect, which includes a $8.00 yearly subscrip- tion to the Postal Record as part of the membership dues. Notice: Contributions or gifts to the National Association of Letter Carriers, AFL-CIO are not tax deductible as charitable contributions for Federal income tax purposes. However, they may be tax deductible under other provi- sions of the Internal Revenue Code. This assignment, authorization and direction shall be irrevocable for a period of one (1) year from the date of delivery hereof to you, and I agree and direct that this assignment, authorization and direction shall be automatically renewed, and shall be irrevocable for suc- cessive periods of one (1) year, unless written notice is given by me to you and the Union not more than twenty
Loop A transmission path that extends from a Main Distribution Frame or functionally comparable piece of equipment in a Customer's serving End Office, to the Rate Demarcation Point (or NID if installed at the Rate Demarcation Point) in or at the Customer's premises. The actual transmission facilities used to provide a Loop may utilize any of several technologies.
FIPPA The HSP acknowledges that the LHIN is bound by FIPPA and that any information provided to the LHIN in connection with this Agreement may be subject to disclosure in accordance with FIPPA.
BY PARTIES The parties are entering into this Agreement for the allotment of an Apartment with the full knowledge of all laws, rules, regulations, notifications applicable to the Project.
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.
By Seller Subject to the terms and conditions of this Article IX, Seller covenants and agrees to defend, indemnify and hold harmless Buyer, its officers, directors, employees, agents, advisers, representatives and Affiliates (collectively, the "Buyer Indemnitees") from and against, and pay or reimburse Buyer Indemnitees for, any and all claims, liabilities, obligations, losses, fines, costs, proceedings, deficiencies or damages (whether absolute, accrued, conditional or otherwise and whether or not resulting from third party claims), including out-of-pocket expenses and reasonable attorneys' fees incurred in the investigation or defense of any of the same or in asserting any of their respective rights hereunder (collectively, "Losses"), resulting from or arising out of:
(i) Any misrepresentation or breach of any warranty of Seller contained in this Agreement; provided that any claim for indemnification by Buyer under this clause (i) may be made no later than 18 months from and after the Closing Date, excepting only that any claim for misrepresentation or breach of warranty under Sections 3.6, 3.10(a), 3.18(a), 3.19 and 3.21 may be made no later than a date thirty days from and after the expiration of the period of the applicable statute of limitations;
(ii) any failure of Seller to perform any covenant or agreement made or contained in this Agreement or fulfill any obligation in respect thereof;
(iii) any Excluded Liabilities;
(iv) any and all Benefit Liabilities in respect of Employees except, with respect to Transferred Employees, to the extent assumed by Buyer pursuant to Article VII; and
(v) any product liability claim with respect to products manufactured by Seller and sold prior to the Closing. Seller shall not be required to indemnify Buyer Indemnitees with respect to any claim for indemnification resulting from or arising out of matters described in clauses (i) and (v) above pursuant to this Section unless and until the aggregate amount of all claims against Seller exceeds $270,000 and then only to the extent such aggregate amount exceeds $270,000. Claims thereafter may be asserted regardless of amount. Seller's maximum liability to Buyer Indemnitees under clauses (i) and (v) of this Section shall not exceed $13,750,000.
By Sellers Sellers covenant and agree to defend, indemnify and hold harmless Purchaser, its Affiliates and the officers, directors, employees, agents, advisers and representatives of each such Person (collectively, the "Purchaser Indemnitees") from and against, and pay or reimburse the Purchaser Indemnitees for, any and all claims, liabilities, obligations, losses, fines, costs, royalties, proceedings, deficiencies or damages (whether absolute, accrued, conditional or otherwise and whether or not resulting from third party claims), including out-of-pocket expenses and reasonable attorneys' and accountants' fees incurred in the investigation or defense of any of the same or in asserting any of their respective rights hereunder (collectively, "Losses"), resulting from or arising out of:
(i) any inaccuracy of any representation or warranty made by any Seller herein, or in any certificate delivered by an officer of any Seller pursuant hereto (a "Seller Certificate") or in any Collateral Agreement or in connection herewith or therewith;
(ii) any failure of any Seller to perform any covenant or agreement hereunder or under any Collateral Agreement or fulfill any other obligation in respect hereof or of any Collateral Agreement;
(iii) any and all Retained Liabilities or Retained Assets;
(iv) any and all Taxes (other than payroll Taxes) of any Seller and all Affiliates thereof relating to or arising out of the Business accruing, or with respect to any event or time period occurring, at or prior to Closing; and
(v) any and all liabilities in respect of employees of Seller or its Affiliates or Plans except to the extent assumed by Purchaser pursuant to Section 4.3. Cap on Sellers' Indemnification Obligations. Sellers' obligation to indemnify Purchaser Indemnitees pursuant to this Agreement, any Seller Certificate or any Collateral Agreement for breaches or inaccuracies of representations or warranties, and for breaches or failures to perform covenants or agreements or to fulfill any other obligations set forth in this Agreement (except for (x) the Seller Surviving Covenants, and (y) solely to the extent expressly contemplated by this Section 8.9(a), the Environmental Covenants (as defined in this Section 8.9(a))), in any Seller Certificate or in any Collateral Agreement, shall not exceed the amount of funds held in the Escrow Account at the time such claims
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.
