DATA MANAGEMENT REQUIREMENTS. A. The definitions contained in this Section are derived from state law. Should there be any conflict between the meanings assigned in this Agreement and the meanings defined in applicable state law (even in the event of future amendments to law that create such conflict), the definitions found in state law will prevail.

DATA MANAGEMENT REQUIREMENTS. Quest shall telephone the Investigators to notify them of lab assay values which must be made known immediately to the Investigator (and any medical monitors designated in the Addendum) for proper patient care and which are defined in the relevant CLW (hereinafter "ALERTS"). In addition, Quest shall immediately provide notification to the Investigator and medical monitor of lab assay values which would exclude the patient from the Study and which are defined in each clinical protocol if requested in the relevant CLW. Quest shall notify Investigator sites within one working day (limited to Monday through Friday) of the completion of testing, or as specified in the CLW. If Quest is unable to reach the Investigator after Quest has made a minimum of two attempts, Quest shall promptly notify the SB Clinical Study Leader, medical monitor or other designated SB contact. All Alerts shall be automatically flagged on the hard copy laboratory report.

DATA MANAGEMENT REQUIREMENTS. All Participants agree to make data available when it is necessary for state, federal or grant reporting, provided it does not conflict with confidentiality law. Each Participant agrees to defend and indemnify the other Participant’s, their directors, officers, agents, and employees, from any and all claims, demands, damages, and other liability, including costs and attorney fees, resulting from or arising out of its performance and/or non-performance under this Agreement; performance and/or non-performance of its duties and responsibilities under this Agreement; and any other negligent act or omission of its directors, officers, agents, or employees. After the implementation period and the term of this agreement, additional Participants can be added as they are identified in the community. Additional Participants must fall under a category, which already exist, in the Delineation of Responsibilities and agree to the all aspects of those responsibilities and all terms of this agreement as written. Additional Participants must sign a signature addendum and an oath of confidentiality. The decision to include Additional Participants will be made at the Homeless and Xxxxxx Youth Advisory Committee.

DATA MANAGEMENT REQUIREMENTS. In most cases, data generated by IHCC Projects (e.g. genotype, phenotype, demographics, health information, etc.) will be securely stored and managed by participating cohorts using a federated model of data storage and access. No identifying information (e.g. names, medical record numbers) should be shared or made publicly available without complying with local data protection legislation, ethics approval and adequate safeguards to protect against individual identity disclosure. It is possible that for specific projects some data types (e.g. sequencing data) may be stored on another data platform at the request of the Scientific Projects Sub-Committee, and as agreed upon by participating Cohort Members. In such circumstances, equivalent Data Management Requirements will be respected and will be made transparent to IHCC members via project description and pending Scientific Projects Sub-Committee approval. As per data protection laws, Cohort Members retain the right to withdraw data from individual participants from IHCC Projects, should those participants request it.

DATA MANAGEMENT REQUIREMENTS. 1. Quest shall perform edit checks on patient demographic data (consistent with privacy laws and regulations) on the day that the sample is received. If Quest detects errors or omissions, including an invalid Study number, an invalid Investigator number, an invalid Investigator site number, an invalid patient number, an improper visit sequencing, or patient demographics that changed from a previous visit, then Quest shall contact the Investigators by telephone (or other mutually acceptable method of communication) for resolution. A record of all such changes shall be maintained by Quest. If Quest is unable to contact the Investigators or has been unable to reach a resolution within five business days (or within two business days if after the last patient visit), then Quest shall notify the designated GSK contact. 2. Quest shall telephone the Investigators to notify them of lab assay values which must be made known immediately to the Investigator (and any medical monitors designated in the Task Description) for proper patient care and which are defined in the relevant CLW (hereinafter "Alerts"). In addition, Quest shall immediately provide notification to the Investigator and medical monitor of lab assay values which would exclude the patient from the Study and which are defined in each clinical protocol if requested in the relevant CLW. Quest shall notify Investigator sites within one working day (limited to Monday through Friday) of the completion of testing, or as specified in the CLW. If Quest is unable to reach the Investigator after Quest has made a minimum of two attempts, Quest shall promptly notify the GSK Clinical Study Leader, medical monitor or other designated GSK contact. All Alerts shall be automatically flagged on the hard copy laboratory report. 3. Quest shall provide to GSK a support service for queries or resolving errors related to Quest, with such queries or errors to be resolved within three days (or within 24 hours if after the last patient visit). Quest also shall provide guidance for any general lab questions and shall ensure the complete resolution of all data issues at the completion of the Study (ensuring satisfactory completion of the relevant Study). Quest shall track all queries raised in each Study, provided that GSK has entered such queries in the relevant database established by GSK. 4. Quest will retain all patient records and test results from any Study for five years following the termination of each Study or for such lo...

Related to DATA MANAGEMENT REQUIREMENTS

Equipment Requirements No Equipment is provided to Customer as part of this Service.
Agreement Requirements This agreement will be issued to cover the Janitorial Service requirements for all State Agencies and shall be accessible to any School District, Political Subdivision, or Volunteer Fire Company.
Project Requirements 1. Project must conform to regulations under 24 CFR Part 92, commonly known as the HOME Regulations.
Vehicle Requirements The following shall be considered minimum Vehicle requirements. The Authorized User shall include supplemental required specifications for Vehicles specified in a Mini-Bid. Unless otherwise indicated, all items specified which are listed on the OEM Pricelist as standard or optional equipment shall be factory installed and operative. Vehicles delivered to an Authorized User in a condition considered to be below retail customer acceptance levels will not be accepted. Items which determine this acceptance level shall include, but not be limited to, the general appearance of the interior and exterior of the vehicle for completeness and quality of workmanship, lubrication and fluid levels, with any leaks corrected, mechanical operation of the vehicle and all electrical components operational. Product specified to be furnished and installed which is not available through the OEM shall conform to the standards known to that particular industry, both product and installation.
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.
Subcontract Requirements As required by Section 6.22(e)(5) of the Administrative Code, Contractor shall insert in every subcontract or other arrangement, which it may make for the performance of Covered Services under this Agreement, a provision that said subcontractor shall pay to all persons performing labor in connection with Covered Services under said subcontract or other arrangement not less than the highest general prevailing rate of wages as fixed and determined by the Board of Supervisors for such labor or services.
Support Requirements If there is a dispute between the awarded vendor and TIPS Member, TIPS or its representatives may assist, at TIPS sole discretion, in conflict resolution or third party (mandatory mediation), if requested by either party. TIPS, or its representatives, reserves the right to inspect any project and audit the awarded vendors TIPS project files, documentation and correspondence. TIPS Members stand in the place of TIPS as related to this agreement and have the same access to the proposal information and all related documents. TIPS Members have all the same rights under the awarded Agreement as TIPS.
Payment Requirements ‌ A. Contract Amount: It is expressly agreed and understood that the total amount to be paid by County under this Contract shall not exceed the total County funding as set forth in Attachment B-Payment/Compensation to Subrecipient attached hereto and incorporated herein by reference. B. County will reclaim any unused balance of funds for reallocation to other County approved projects.
Technical Requirements 4.5.3.1 Tandem Switching shall have the same capabilities or equivalent capabilities as those described in Telcordia TR-TSY-000540 Issue 2R2, Tandem Supplement, June 1, 1990. The requirements for Tandem Switching include but are not limited to the following: 4.5.3.1.1 Tandem Switching shall provide signaling to establish a tandem connection; 4.5.3.1.2 Tandem Switching will provide screening as jointly agreed to by <<customer_short_name>> and BellSouth; 4.5.3.1.3 Where applicable, Tandem Switching shall provide AIN triggers supporting AIN features where such routing is not available from the originating end office switch, to the extent such Tandem switch has such capability; 4.5.3.1.4 Where applicable, Tandem Switching shall provide access to Toll Free number database; 4.5.3.1.5 Tandem Switching shall provide connectivity to Public Safety Answering Point (PSAP)s where 911 solutions are deployed and the tandem is used for 911; and 4.5.3.1.6 Where appropriate, Tandem Switching shall provide connectivity for the purpose of routing transit traffic to and from other carriers. 4.5.3.2 BellSouth may perform testing and fault isolation on the underlying switch that is providing Tandem Switching. Such testing shall be testing routinely performed by BellSouth. The results and reports of the testing shall be made available to <<customer_short_name>>. 4.5.3.3 BellSouth shall control congestion points and network abnormalities. All traffic will be restricted in a non-discriminatory manner. 4.5.3.4 Tandem Switching shall process originating toll free traffic received from <<customer_short_name>>’s local switch. 4.5.3.5 In support of AIN triggers and features, Tandem Switching shall provide SSP capabilities when these capabilities are not available from the Local Switching Network Element to the extent such Tandem Switch has such capability.
Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

DATA MANAGEMENT REQUIREMENTS Sample Clauses

Filter & Search

Related Clauses

Sub-Clauses

Related to DATA MANAGEMENT REQUIREMENTS