Agency Data and Certification
Agency Data and Certification Sample Clauses
Related to Agency Data and Certification
COMPLIANCE AND CERTIFICATION 25.1 Each Party shall comply at its own expense with all Applicable Laws that relate to that Party’s obligations to the other Party under this Agreement. Nothing in this Agreement shall be construed as requiring or permitting either Party to contravene any mandatory requirement of Applicable Law.
Licensing and Certification The Grantee shall ensure that all licensed and/or certified staff maintain a current license and/or certification if the programs and services associated with State Aid Commitment Diversion funds require professional licensure or certification.
Audits and Certifications The parties agree that the audits described in Clause 5(f) and Clause 12(2) of the Standard Contractual Clauses shall be carried out in accordance with the following specifications: Upon Customer’s request, and subject to the confidentiality obligations set forth in the Agreement, Qubole shall make available to Customer that is not a competitor of Qubole (or Customer’s independent, third-party auditor that is not a competitor of Qubole) information regarding the Qubole’s compliance with the obligations set forth in this DPA in the form of the third-party certifications and audits set forth in the Security and Privacy Documentation to the extent Qubole makes them generally available to its customers. Customer may contact Qubole in accordance with the “Notices” Section of the Agreement to request an on-site audit of the procedures relevant to the protection of Personal Data. Customer shall reimburse Qubole for any time expended for any such on- site audit at the Qubole’s then-current professional services rates, which shall be made available to Customer upon request. Before the commencement of any such on-site audit, Customer and Qubole shall mutually agree upon the scope, timing, and duration of the audit in addition to the reimbursement rate for which Customer shall be responsible. All reimbursement rates shall be reasonable, taking into account the resources expended by Qubole. Customer shall promptly notify Qubole with information regarding any non- compliance discovered during the course of an audit.
LEED Certification Landlord may, in Landlord’s sole and absolute discretion, elect to apply to obtain or maintain a LEED certification for the Project (or portion thereof), or other applicable certification in connection with Landlord’s sustainability practices for the Project (as such sustainability practices are to be determined by Landlord, in its sole and absolute discretion, from time to time). In the event that Landlord elects to pursue such an aforementioned certification, Tenant shall, at Tenant’s sole cost and expense, promptly cooperate with the Landlord’s efforts in connection therewith and provide Landlord with any documentation it may need in order to obtain or maintain the aforementioned certification (which cooperation may include, but shall not be limited to, Tenant complying with certain standards pertaining to the purchase of materials used in connection with any Alterations or improvements undertaken by the Tenant in the Project, the sharing of documentation pertaining to any Alterations or improvements undertaken by Tenant in the Project with Landlord, and the sharing of Tenant’s billing information pertaining to trash removal and recycling related to Tenant’s operations in the Project).
Licenses and Certifications Where required by law, PROVIDER must, at all times, be licensed or certified by either the State or County as a qualified provider of the services purchased hereby. PROVIDER shall fully cooperate with licensing and certification authorities. PROVIDER shall submit copies of the required licenses or certifications upon request by COUNTY. PROVIDER shall promptly notify COUNTY in writing of any citation PROVIDER receives from any licensing or certification authority, including all responses and correction plans.
CERTIFICATION REGARDING DRUG-FREE WORKPLACE REQUIREMENTS The undersigned (authorized official signing for the contracting organization) certifies that the contractor will, or will continue to, provide a drug-free workplace in accordance with 45 CFR Part 76 by:
Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.
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.
Implementation Report Within 150 days after the Effective Date, Extendicare shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include:
CHILD SUPPORT CERTIFICATION Under Section 231.006, Texas Family Code, the Engineer certifies that the individual or business entity named in this contract, bid, or application is not ineligible to receive the specified grant, loan, or payment and acknowledges that this contract may be terminated and payment may be withheld if this certification is inaccurate. If the above certification is shown to be false, the Engineer is liable to the state for attorney’s fees, the cost necessary to complete the contract, including the cost of advertising and awarding a second contract, and any other damages provided by law or the contract. A child support obligor or business entity ineligible to receive payments because of a payment delinquency of more than thirty (30) days remains ineligible until: all arrearages have been paid; the obligor is in compliance with a written repayment agreement or court order as to any existing delinquency; or the court of continuing jurisdiction over the child support order has granted the obligor an exemption from Subsection (a) of Section 231.006, Texas Family Code, as part of a court- supervised effort to improve earnings and child support payments.
