Data recorder Sample Clauses

Data recorder. For the competitors of the CN category, a data recorder with sensors, homologated by the promoter, must be installed in all cars and for all events. There are of the responsibility of every team, to get itself this recorder of data, as well as the sensors, to install them, and to make sure that they work correctly. The promoter will indicate later the homologated system. Cars without data recorder, without all the necessary sensors or with a recorder out of service, will be not in conformity with the regulation and could be declared to stewards.
AutoNDA by SimpleDocs
Data recorder. 23.1 For purposes of this chapter, the term

Related to Data recorder

  • PAYEE DATA RECORD FORM STD 204: This form must be completed by all contractors that are not another state agency or other governmental entity.

  • MARC Records When applicable to the Licensed Materials, at Licensee’s request, Licensor shall provide full OCLC-quality batched sets of MARC records incorporating Licensee specifications at no additional cost by the date of the execution of this License Agreement. Updates to existing records and new title records, matching the schedule of release and delivery of new publications, will be provided on a mutually agreed-upon schedule and in a format that renders them useful to the Licensee and/or the Participating Institutions.

  • Data Reporting 1. Maintain and adhere to data system software and encrypted portable computer device updates, and interface capability requirements for each computer located within the facility, and as specified in the Contract and required by County.

  • J4 Records The Contractor and any Sub-contractors appointed by it shall maintain the records referred to in clause E9.1 and such other documents as the Authority may reasonably require throughout the period of this Contract; and the Contractor and any Sub-contractors appointed by it shall maintain such records and documents until at least 31 December 2022.

  • Public Records Taxpayer acknowledges that GO-Biz is subject to the California Public Records Act (PRA) (Gov. Code, § 6250 et seq.). This Agreement and materials submitted by Taxpayer to GO-Biz may be subject to a PRA request. In such an event, GO-Biz will notify Taxpayer, as soon as practicable that a PRA request for Taxpayer’s information has been received, but not less than five (5) business days prior to the release of the requested information to allow Taxpayer to seek an injunction. GO-Biz will work in good faith with Taxpayer to protect the information to the extent an exemption is provided by law, including, but not limited to, notes, drafts, proprietary information, financial information, and trade secret information. GO-Biz will also apply the “balancing test” as provided for under Government Code section 6255, to the extent applicable. Notwithstanding the foregoing, GO-Biz agrees that any information provided to GO-Biz by the FTB, in connection with this Agreement will be treated as confidential tax information protected by Article 2 (commencing with Section 19542) of Chapter 7 of Part 10.2 of the RTC, assuming that FTB can rely on such a section and shall not be disclosed to any party, other than personnel of GO-Biz or the Committee, without Taxpayer’s prior written consent. Taxpayer acknowledges that this Agreement in whole or in part will be made available to the public at least ten (10) calendar days prior to the Committee hearing. Pursuant to RTC sections 17059.2 and 23689, in the event of approval by the Committee of this Agreement, Taxpayer acknowledges and agrees that GO-Biz will post on its website the following information:

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

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

  • Access to Records; Contractor Financial Records Contractor agrees that District and its authorized representatives are entitled to review all Contractor books, documents, papers, plans, and records, electronic or otherwise (“Records”), directly pertinent to this Contract for the purpose of making audit, examination, excerpts, and transcripts. Contractor shall maintain all Records, fiscal and otherwise, directly relating to this Contract in accordance with generally accepted accounting principles so as to document clearly Contractor's performance. Following final payment and termination of this Contract, Contractor shall retain and keep accessible all Records for a minimum of three years, or such longer period as may be required by law, or until the conclusion of any audit, controversy, or litigation arising out of or related to this Contract, whichever date is later.

  • Medical Records Medical records relating to Trial Subjects that are not submitted to Sponsor may include some of the same information as is included in Trial Data; however, Sponsor makes no claim of ownership to those documents or the information they contain. c.

  • Data Retention The Company will hold and use the Data only as long as is necessary to implement, administer and manage the Grantee’s participation in the Plan, or as required to comply with legal or regulatory obligations, including under tax and security laws.

Time is Money Join Law Insider Premium to draft better contracts faster.