DATA ESCROW REQUIREMENTS Registry Operator will engage an independent entity to act as data escrow agent (“Escrow Agent”) for the provision of data escrow services related to the Registry Agreement. The following Technical Specifications set forth in Part A, and Legal Requirements set forth in Part B, will be included in any data escrow agreement between Registry Operator and the Escrow Agent, under which ICANN must be named a third-‐party beneficiary. In addition to the following requirements, the data escrow agreement may contain other provisions that are not contradictory or intended to subvert the required terms provided below.
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.
TITLE VI REQUIREMENTS H-GAC in accordance with the provisions of Title VI of the Civil Rights Act of 1964 (78 Xxxx. 000, 00 X.X.X. §§ 0000x to 2000d-4) and the Regulations, hereby notifies all bidders that it will affirmatively ensure that any disadvantaged business enterprises will be afforded full and fair opportunity to submit in response to this Agreement and will not be discriminated against on the grounds of race, color, or national origin in consideration for an award.
Organizational Power; Authorization The execution, delivery and performance by each Loan Party of the Loan Documents to which it is a party are within such Loan Party’s organizational powers and have been duly authorized by all necessary organizational, and if required, shareholder, partner or member, action. This Agreement has been duly executed and delivered by the Borrower, and constitutes, and each other Loan Document to which any Loan Party is a party, when executed and delivered by such Loan Party, will constitute, valid and binding obligations of the Borrower or such Loan Party (as the case may be), enforceable against it in accordance with their respective terms, except as may be limited by applicable bankruptcy, insolvency, reorganization, moratorium, or similar laws affecting the enforcement of creditors’ rights generally and by general principles of equity.
Operations Prior to the Closing Date (a) Seller shall use its commercially reasonable efforts to, and to cause the Companies to, operate and carry on the Business in the ordinary course and substantially as operated immediately prior to the date of this Agreement. Consistent with the foregoing, Seller shall use its commercially reasonable efforts, and shall cause the Companies to use their commercially reasonable efforts, consistent with good business practice, to preserve the goodwill of the suppliers, contractors, licensors, employees, customers, distributors and others having business relations with the Business.
Technical Requirements 2.7.4.1 The NID shall provide an accessible point of interconnection and shall maintain a connection to ground.
Organization; Power; Qualification Each of the Borrower, the other Loan Parties and the other Subsidiaries is a corporation, partnership or other legal entity, duly organized or formed, validly existing and in good standing under the jurisdiction of its incorporation or formation, has the power and authority to own or lease its respective properties and to carry on its respective business as now being and hereafter proposed to be conducted and is duly qualified and is in good standing as a foreign corporation, partnership or other legal entity, and authorized to do business, in each jurisdiction in which the character of its properties or the nature of its business requires such qualification or authorization and where the failure to be so qualified or authorized could reasonably be expected to have, in each instance, a Material Adverse Effect.
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.
Power, Authority, Consents The Borrower has the power to execute, deliver and perform this Loan Agreement, the Promissory Note and Pledge Agreement, all of which have been duly authorized by all necessary and proper corporate or other action.
Organization; Power (a) Buyer is a corporation duly organized, validly existing and in good standing under the laws of Delaware.
