By WaMu Sample Clauses

By WaMu. WaMu represents that as of the Agreement Date: (A) WaMu is a corporation duly incorporated, validly existing and in good standing under the Laws of Washington; (B) WaMu has all requisite corporate power and authority to execute, deliver and perform its obligations under this Agreement; (C) the execution, delivery and performance of this Agreement by WaMu (1) has been duly authorized by WaMu and (2) will not conflict with, result in a breach of or constitute a default under any other agreement to which WaMu is a party or by which WaMu is bound; (D) WaMu is duly licensed, authorized or qualified to do business and is in good standing in every jurisdiction in which a license, authorization or qualification is required for the ownership or leasing of its assets or the transaction of business of the character transacted by it, except where the failure to be so licensed, authorized or qualified would not have a material adverse effect on WaMu’s ability to fulfill its obligations under this Agreement; and (E) there is no outstanding litigation, arbitrated matter or other dispute to which WaMu is a party which, if decided unfavorably to WaMu, would reasonably be expected to have a material adverse effect on Supplier’s or WaMu’s ability to fulfill their respective obligations under this Agreement.
AutoNDA by SimpleDocs
By WaMu. WaMu warrants to and covenants with Supplier that during the Term and the Termination Assistance Period: (A) WaMu will comply with all Laws applicable to it in connection with its obligations under this Agreement; (B) WaMu will be responsible for any fines and penalties arising from any noncompliance by WaMu or WaMu Agents with any Law relating to WaMu’s use of the Services unless (1) such noncompliance was caused by Supplier or (2) such noncompliance was related to a change in such Law and Supplier failed to notify WaMu in a timely manner of such change in accordance with subsection (C) of Section 19.2 (By Supplier); (C) WaMu will ensure that no viruses or similar items are coded or introduced into the Supplier Systems from the WaMu Systems. WaMu agrees that, in the event a virus or similar item is found to have been introduced into the Supplier Systems from the WaMu Systems, WaMu will assist Supplier in reducing the effects of the virus or similar item and, if the virus or similar item causes a loss of operational efficiency or loss of data or creates a security risk, to assist Supplier to the same extent to mitigate and restore such losses and mitigate such risk; and (D) except as otherwise provided in this Agreement, WaMu will obtain all applicable permits and licenses, including the WaMu Governmental Approvals and the WaMu Consents, required of WaMu in connection with its obligations under this Agreement.

Related to By WaMu

  • Logging The ISP will require the maintenance of network and application logs as part of BNY Mellon’s security information and event management processes. Logs are retained in accordance with law applicable to BNY Mellon’s provision of the services as well as BNY Mellon’s applicable policies. BNY Mellon uses various tools in conjunction with such logs, which may include behavioral analytics, security monitoring case management, network traffic monitoring and analysis, IP address management and full packet capture.

  • 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.

  • Health Requirements A. Provider shall remain in compliance with all applicable federal, state, county, and municipal, statutes, laws, ordinances, regulations, and guidelines, as well as any Board guidelines, policies, and rules in effect now or later, and as amended from time to time related to COVID-19. B. Provider shall comply with evolving requirements to protect the health and safety of Student Participants and staff, as expressed in local, and state guidance from various government agencies. This includes, but is not limited to, adhering to all health and safety guidelines issued by CPS, IDPH, and CDPH related to COVID-19. Provider acknowledges these health and safety guidelines are subject to change. C. Required health and safety practices may vary across age groups and settings. Provider shall comply, at a minimum, with all health and safety mandates issued by the State of Illinois and the City of Chicago and guidance from the Illinois State Board of Education (“ISBE”). D. Under Chicago’s March 19 Public Health Order, congregate facilities (such as long-term care facilities, childcare settings, correctional facilities, etc.) must immediately report to CDPH clusters of COVID-19 patients, defined as two or more confirmed cases of COVID-19 occurring within 14 calendar days of each other at a facility. To report positive cases, Provider must complete the COVID-19 Online Case Report Form found at the following website: xxxxx://xxxxxx.xxx.xxxxxxxx.xxx/surveys/?s=FR7MAJAY84. A copy of the current COVID-19 Online Case Report Form is attached and incorporated into this Supplemental Scope as Attachment A. Provider must also comply with additional operational, reporting and tracing requirements established by CPS. E. As of July 13, 2020, interim guidance issued by CDPH encourages notification for every COVID-19 case. For more information, see CDPH Interim Guidance on Management of COVID 19 Cases in Childcare Settings (“CDPH Guidance”) at the following link: https://xxx.xxxxxxx.xxx/content/dam/city/depts/cdph/HealthProtectionandResponse/Interim% 20Guidance%20on%20Management%20of%20COVID 19%20Cases%20in%20Childcare%20Settings%2007.13.

  • Contractor Requirements The Firm shall be construed, during the entire term of this contract, to be an independent contractor. Nothing in this contract is intended to nor shall be construed to create an employer- employee relationship, or a joint venture relationship. The Firm represents that it is qualified to perform the duties to be performed under this contract and that it has, or will secure, if needed, at its own expense, applicable personnel who are qualified to perform the duties required under this contract. Such personnel shall not be deemed in any way, directly or indirectly, expressly or by implication, to be employees of the District. Any person assigned by the firm to perform the services hereunder shall be the employee or a subcontractor of the Firm, who shall have the sole right to hire and discharge its employee or subcontractors. The Firm or its subcontractors shall pay, when due, all salaries and wages of their employees and accepts exclusive responsibility for the payment of federal income tax, social security, unemployment compensation and any other withholdings that may be required. Neither the Firm, its subcontractors nor their employees are entitled to state retirement or leave benefits. It is further understood that the consideration expressed herein constitutes full and complete compensation for all services and performance hereunder, and that any sum due and payable to the Firm shall be paid as a gross sum with no withholdings or deductions being made by the District for any purpose from said contract sum, except as permitted in paragraphs 16, 17 and 18.

  • System Logging The system must maintain an automated audit trail which can 20 identify the user or system process which initiates a request for PHI COUNTY discloses to 21 CONTRACTOR or CONTRACTOR creates, receives, maintains, or transmits on behalf of COUNTY, 22 or which alters such PHI. The audit trail must be date and time stamped, must log both successful and 23 failed accesses, must be read only, and must be restricted to authorized users. If such PHI is stored in a 24 database, database logging functionality must be enabled. Audit trail data must be archived for at least 3 25 years after occurrence.

  • NETWORK INTERCONNECTION METHODS 3.1 The Interconnection provided herein may not be used solely for the purpose of originating a Party’s own interexchange traffic.

  • Minimum Vendor Legal Requirements Vendor shall remain aware of and comply with this Agreement and all local, state, and federal laws governing the sale of products/services offered by Vendor under this contract. Such applicable laws, ordinances, and policies must be complied with even if not specified herein.

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

  • Subcontractor Requirements The Supplier must ensure that any subcontract entered into for the purpose of this Agreement contains an equivalent clause granting the rights specified in this clause.

  • Construction Methods 3.1 The Contractor shall provide all tools, equipment, materials, labor and work for the excavation and removal of the unsuitable subgrade soils and their subsequent replacement with the specified backfill soils as directed by the Owner’s representative. All work under this item shall be performed in a safe and workmanlike manner. 3.2 All work shall be performed in accordance with DelDOT Standard Specifications Section 821. 3.3 Following the removal of existing pavements, the Owner’s representative will review the exposed subgrade and provide recommendations for the undercutting of unsuitable subgrade materials as required. The depth and extent of undercut excavation, if required, will be determined by the Owner’s representative at the time of excavation. 3.4 All excavated materials shall become the property of the Contractor and be removed from the site at the completion of the project at no additional expense to the Owner. 3.5 Undercut excavations should be backfilled with graded aggregate. Backfill shall be placed in loose lifts not exceeding 8 inches thick. Each lift should be compacted with at least 3 passes of a minimum 5-ton, walk-behind or self-propelled vibratory roller when the size of the area permits, or with a vibrating plate mechanical compactor for smaller areas. Lift thickness shall be reduced to 6 inch loose lift when using a vibratory plate compactor. 3.6 The Contractor shall take precautions as necessary to minimize the potential for disturbance or softening of the pavement subgrade materials from inclement weather or construction traffic. As a minimum, this shall include the placement of backfill on the same day as the excavation. Any soft areas which develop shall be undercut and replaced with graded aggregate at no additional cost to the Owner. 3.7 Where undercutting is performed, the geotextile fabric shall be installed. The fabric should be pulled tight and lapped a minimum of 12 inches.

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