Data Requestor Sample Clauses

Data Requestor. The term “Data Requestor” means the person submitting a Patient Count Query, Feasibility Query, or Research Project. Such researcher shall only be a Qualified Faculty or Affiliate Investigator.
AutoNDA by SimpleDocs

Related to Data Requestor

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

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

  • Identity Verification In the case that the Subscriber provides telecommunication services to any Subscriber’s Customers pursuant to Section 8.1, the Subscriber is responsible for performing and shall perform personal identification of Subscriber’s Customer. SORACOM shall not bear any responsibility in relation to dealing with such matters.

  • CONTRACT EXHIBIT I PREFERRED PRICING AFFIDAVIT This preferred-pricing affidavit is entered into in accordance with section 216.0113, F.S., and as required by Contract No. 80101507-21-STC-ITSA (“Contract”) between (“Contractor”) and the Department of Management Services. As the person authorized by Contractor to sign this affidavit, I attest that the Contractor is in full compliance with the preferred-pricing clause of the Contract. Contractor’s Name: By: Signature Printed Name/Title Date: STATE OF COUNTY OF Sworn to (or affirmed) and subscribed before me this day of , by . Signature of Notary Vendor Name: FEIN# Vendor’s Authorized Representative Name and Title: Address: City, State, and Zip code: Phone Number: ( ) - E-mail: CORPORATE SEAL (IF APPLICABLE) (Print, Type, or Stamp Commissioned Name of Notary Public) [Check One] Personally Known OR Produced the following I.D.

  • CONTRACTOR NAME CHANGE An amendment is required to change the Contractor's name as listed on this Agreement. Upon receipt of legal documentation of the name change the State will process the amendment. Payment of invoices presented with a new name cannot be paid prior to approval of said amendment.

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

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

  • Contract Exhibit J Quarterly Sales Report If a conflict exists among any of the Contract documents, the documents shall have priority in the order listed below:

  • _CheckoutDate_ _CheckoutTime_ Rental $_Rental_ Fees $_Fees_ Taxes $_AreaTax_ Total $_NetAmount_ Security Deposit $_RefundableSecurityDeposit_ Deposit $_DepositAmount_ (due _DepositDueDate_) Balance $_BalanceAmount_ (due _BalanceDueDate_) AGREEMENT Whistler Prime Vacation Properties (WPVP), the Agent of the Owners, and Tenant agree as follows: Above Tenant is at least twenty-five (25) years of age (an "adult") and will be an occupant of the vacation property listed above during the entire reserved dates. In addition to Tenant, other authorized occupants may be family members or friends of Tenant. Use of the premises will be denied to persons not falling within the foregoing categories. Should any unauthorized persons occupy or use the Premises, Tenant will be required to vacate the premises immediately without the possibility of a refund. Premises keys will not be issued to anyone who is not an adult. RESERVATIONS Reservations may be placed up to two (1) year in advance, but are subject to the rates in effect for the year said reservations are placed. All times are Pacific Standard Time and currency is CAD unless otherwise noted. While every effort will be made to have the property available for check in at 4pm CheckinTime, during high season, a cleaning crew may require additional cleaning time and check in may be delayed up to 6:00 pm. RESERVATION DEPOSIT A deposit totaling 35% of the agreed upon total amount is due with acceptance of rental agreement. Payment of deposit shall be deemed as acceptance of this rental agreement. Payment may be made by major credit card service offered by WPVP at time of reservation. We accept VISA or MASTERCARD.

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