Date of Issue of Enrollee Materials Sample Clauses

Date of Issue of Enrollee Materials. The MCO shall submit to the STATE, upon request, written confirmation of the dates on which the MCO issues all new Enrollee materials required by section 3.6.6. The MCO must notify the STATE and provide a brief explanation in writing within two (2) working days if the MCO cannot comply with the time frame specified in section 3.6.6.
AutoNDA by SimpleDocs
Date of Issue of Enrollee Materials. The HEALTH PLAN shall submit to the STATE upon request, written confirmation of the dates on which the HEALTH PLAN issues all new Enrollee materials required by Section 3.2.3. The HEALTH PLAN must notify the STATE and provide a brief explanation in writing within two working days if the HEALTH PLAN cannot comply with the time frame specified in Section 3.2.3.

Related to Date of Issue of Enrollee Materials

  • RELEASE OF BID EVALUATION MATERIALS Requests concerning the evaluation of Bids may be submitted under the Freedom of Information Law. Information, other than statistical or factual tabulations or data such as the Bid Tabulation, shall only be released as required by law after Contract award. Bid Tabulations are not maintained for all procurements. Names of Bidders may be disclosed after Bid opening upon request. Written requests should be directed to the Commissioner.

  • Data Security and Unauthorized Data Release The Requester and Approved Users, including the Requester’s IT Director, acknowledge NIH’s expectation that they have reviewed and agree to manage the requested controlled-access dataset(s) and any Data Derivatives of controlled-access datasets according to NIH’s expectations set forth in the current NIH Security Best Practices for Controlled-Access Data Subject to the GDS Policy and the Requester’s IT security requirements and policies. The Requester, including the Requester’s IT Director, agree that the Requester’s IT security requirements and policies are sufficient to protect the confidentiality and integrity of the NIH controlled-access data entrusted to the Requester. If approved by NIH to use cloud computing for the proposed research project, as outlined in the Research and Cloud Computing Use Statements of the Data Access Request, the Requester acknowledges that the IT Director has reviewed and understands the cloud computing guidelines in the NIH Security Best Practices for Controlled-Access Data Subject to the NIH GDS Policy. The Requester and PI agree to notify the appropriate DAC(s) of any unauthorized data sharing, breaches of data security, or inadvertent data releases that may compromise data confidentiality within 24 hours of when the incident is identified. As permitted by law, notifications should include any known information regarding the incident and a general description of the activities or process in place to define and remediate the situation fully. Within 3 business days of the DAC notification, the Requester agrees to submit to the DAC(s) a detailed written report including the date and nature of the event, actions taken or to be taken to remediate the issue(s), and plans or processes developed to prevent further problems, including specific information on timelines anticipated for action. The Requester agrees to provide documentation verifying that the remediation plans have been implemented. Repeated violations or unresponsiveness to NIH requests may result in further compliance measures affecting the Requester. All notifications and written reports of data security incidents and policy compliance violations should be sent to the DAC(s) indicated in the Addendum to this Agreement. NIH, or another entity designated by NIH may, as permitted by law, also investigate any data security incident or policy violation. Approved Users and their associates agree to support such investigations and provide information, within the limits of applicable local, state, tribal, and federal laws and regulations. In addition, Requester and Approved Users agree to work with the NIH to assure that plans and procedures that are developed to address identified problems are mutually acceptable and consistent with applicable law.

  • Delivery and Content of Monthly Bills/Supplementary Bills 10.2.1 The SPD shall issue to SECI hard copy of a signed Monthly Xxxx/Supplementary Xxxx for the immediately preceding Month/relevant period based on the issuance of Energy Accounts along with all relevant documents (payments made by SPD for drawal of power, payment of reactive energy charges, Metering charges or any other charges as per guidelines of SERC/CERC, if applicable. Each Monthly Xxxx shall include all charges as per this Agreement for the energy supplied for the relevant Month based on Energy Accounts issued by RPC or any other competent authority which shall be binding on both the Parties. The Monthly Xxxx amount shall be the product of the energy as per Energy Accounts and the Applicable Tariff. Energy drawn from the grid will be regulated as per the regulations of respective State the Project is located in.

  • CHILD AND DEPENDENT ADULT/ELDER ABUSE REPORTING CONTRACTOR shall establish a procedure acceptable to ADMINISTRATOR to ensure that all employees, agents, subcontractors, and all other individuals performing services under this Agreement report child abuse or neglect to one of the agencies specified in Penal Code Section 11165.9 and dependent adult or elder abuse as defined in Section 15610.07 of the WIC to one of the agencies specified in WIC Section 15630. CONTRACTOR shall require such employees, agents, subcontractors, and all other individuals performing services under this Agreement to sign a statement acknowledging the child abuse reporting requirements set forth in Sections 11166 and 11166.05 of the Penal Code and the dependent adult and elder abuse reporting requirements, as set forth in Section 15630 of the WIC, and shall comply with the provisions of these code sections, as they now exist or as they may hereafter be amended.

  • ECR Number Environmental Commitment Record Requirements Description of ADOT Responsibilities TMP-3 The following measures will be implemented for the Selected Alternative: • All equipment exhaust systems will be in good working order. Properly designed engine enclosures and intake silencers will be used. • Equipment will be maintained on a regular basis. New equipment will be subject to new product emission standards. • Stationary equipment will be located as far away from sensitive receivers as possible. • Construction-related noise generators will be shielded from noise receivers (e.g., use temporary enclosures to shield generators or crushers, take advantage of site conditions to provide topographic separation). • Construction alerts will be distributed to keep the public informed of construction activities, and a toll-free number for construction-related complaints will be provided. • During the design phase, hours of operation will be evaluated to minimize disruptions during construction. ADOT to oversee for compliance TMP-4 Congestion from construction-related traffic will create temporary impacts in the project vicinity. The magnitude of these impacts will vary depending on the location of the sources of the fill material and of the disposition sites for surplus material, the land uses along the routes, the duration of hauling operations, staging locations, and the construction phasing. To identify acceptable routes and times of operation, ADOT, or its representative, will prepare an agreement with local agencies regarding hauling of construction materials on public streets. ADOT to oversee for compliance TP Attachment 000-0 Xxxxx Xxxxxxxx Xxxxxxx Project Record of Decision (ROD) Developer’s Environmental Commitment Requirements The following table includes the Project-specific environmental commitments as written in the ROD, with minor modifications for clarification purposes. As it relates to these Technical Provisions, references to freeway, project, South Mountain Freeway, proposed action, proposed freeway, and Selected Alternative mean the Project, and references to contractor mean Developer. Developer shall comply with and perform all of the contractor and ADOT requirements, including the ADOT obligations, commitments, and responsibilities, identified in the following table, except to the extent of those requirements that are specifically identified in the third column, entitled “Description of ADOT Responsibilities,” which are not delegated to Developer.

  • Texas Education Code Chapter 22 Contractor Certification for Contractor Employees Introduction Texas Education Code Chapter 22 requires entities that contract with school districts to provide service s to obtain criminal history record information regarding covered employees. Contractors must certify to the district t hat they have complied. Covered employees with disqualifying criminal histories are prohibited from serving at a sch ool district. Definitions: Covered employees: Employees of a contractor or subcontractor who have or will have continuing dutie s related to the service to be performed at the District and have or will have direct contact with students. The District will be the final arbiter of what constitutes direct contact with students. Disqualifying criminal history: Any conviction or other criminal history information designated by the District, or one of the following offenses, if at the time of the o ffense, the victim was under 18 or enrolled in a public school: (a) a felony offense under Title 5, Texas Penal Code; (b) an offense for which a defendant is required to register as a sex offender under Chapter 62, Texas Code of Criminal Procedure; or (c) an equivalent offense under federal law or the laws of another state. I certify that: NONE (Section A) of the employees of Contractor and any subcontractors are covered employees, as defined abo ve. If this box is checked, I further certify that Contractor has taken precautions or imposed conditions to ensure tha t the employees of Contractor and any subcontractor will not become covered employees. Contractor will maintain t hese precautions or conditions throughout the time the contracted services are provided. OR SOME (Section B) or all of the employees of Contractor and any subcontractor are covered employees. If this box is checked, I further certify that: (1) Contractor has obtained all required criminal history record information regarding its covered employees. None of the covered employees has a disqualifying criminal history. (2) If Contractor receives information that a covered employee subsequently has a reported criminal history, Contra ctor will immediately remove the covered employee from contract duties and notify the District in writing within 3 busi ness days. (3) Upon request, Contractor will provide the District with the name and any other requested information of covered employees so that the District may obtain criminal history record information on the covered employees. (4) If the District objects to the assignment of a covered employee on the basis of the covered employee's criminal h istory record information, Contractor agrees to discontinue using that covered employee to provide services at the District. Noncompliance or misrepresentation regarding this certification may be grounds for contract termination. None Texas Business and Commerce Code § 272 Requirements as of 9-1-2017 SB 807 prohibits construction contracts to have provisions requiring the contract to be subject to the laws of anothe r state, to be required to litigate the contract in another state, or to require arbitration in another state. A contract wit h such provisions is voidable. Under this new statute, a “construction contract” includes contracts, subcontracts, or agreements with (among others) architects, engineers, contractors, construction managers, equipment lessors, or materials suppliers. “Construction contracts” are for the design, construction, alteration, renovation, remodeling, or repair of any building or improvement to real property, or for furnishing materials or equipment for the project. The t erm also includes moving, demolition, or excavation. BY RESPONDING TO THIS SOLICITATION, AND WHEN APPLI CABLE, THE PROPOSER AGREES TO COMPLY WITH THE TEXAS BUSINESS AND COMMERCE CODE § 272 WH EN EXECUTING CONTRACTS WITH TIPS MEMBERS THAT ARE TEXAS GOVERNMENT ENTITIES. 7 5 Texas Government Code 2270 Verification Form Texas Government Code 2270 Verification Form Texas 2017 House Xxxx 89 has been signed into law by the governor and as of September 1, 2017 will be codified as Texas Government Code § 2270 and 808 et seq. The relevant section addressed by this form reads as follows: Texas Government Code Sec. 2270.002. PROVISION REQUIRED IN CONTRACT. A governmental entity may not ent er into a contract with a company for goods or services unless the contract contains a written verification from the c ompany that it: (1) does not boycott Israel; and (2) will not boycott Israel during the term of the contract.engaged by ESC Region 8/The Interlocal Purchasing System (TIPS) 0000 Xxxxxxx 000 Xxxxx Xxxxxxxxx,XX,00000 verify by this writing that the above-named company affirms that it (1) does not boycott Israel; and (2) will not boycot t Israel during the term of this contract, or any contract with the above-named Texas governmental entity in the futur e. I further affirm that if our company’s position on this issue is reversed and this affirmation is no longer valid, that t he above-named Texas governmental entity will be notified in writing within one (1) business day and we understand that our company’s failure to affirm and comply with the requirements of Texas Government Code 2270 et seq. shall be grounds for immediate contract termination without penalty to the above-named Texas governmental entity. AND our company is not listed on and we do not do business with companies that are on the the Texas Comptroller of Pu blic Accounts list of Designated Foreign Terrorists Organizations per Texas Gov't Code 2270.0153 found at xxxxx://x xxxxxxxxxx.xxxxx.xxx/xxxxxxxxxx/xxxx/xxxxxxx-xxxxxxxxx.xxx I swear and affirm that the above is true and correct. YES

  • How to File an Appeal of a Prescription Drug Denial For denials of a prescription drug claim based on our determination that the service was not medically necessary or appropriate, or that the service was experimental or investigational, you may request an appeal without first submitting a request for reconsideration. You or your physician may file a written or verbal prescription drug appeal with our pharmacy benefits manager (PBM). The prescription drug appeal must be submitted to us within one hundred and eighty (180) calendar days of the initial determination letter. You will receive written notification of our determination within thirty (30) calendar days from the receipt of your appeal. How to File an Expedited Appeal Your appeal may require immediate action if a delay in treatment could seriously jeopardize your health or your ability to regain maximum function, or would cause you severe pain. To request an expedited appeal of a denial related to services that have not yet been rendered (a preauthorization review) or for on-going services (a concurrent review), you or your healthcare provider should call: • our Grievance and Appeals Unit; or • our pharmacy benefits manager for a prescription drug appeal. Please see Section 9 for contact information. You will be notified of our decision no later than seventy-two (72) hours after our receipt of the request. You may not request an expedited review of covered healthcare services already received.

  • Privacy and User Information You acknowledge that in connection with your use of Mobile Banking, First Resource Bank and its affiliates and service providers, including Fiserv, Inc. and its affiliates, may receive names, domain names, addresses, passwords, telephone and device numbers, the content of messages, data files, data about your usage of the service (such as session length, number of transactions and geolocation), and other data and information provided by you or from other sources in connection with Mobile Banking or the Software (collectively “User Information”). First Resource Bank and its affiliates and service providers will maintain reasonable safeguards to protect the information from unauthorized disclosure or use, but reserve the right to use and disclose this information as reasonably necessary to deliver Mobile Banking, perform analytics to improve the service, and as otherwise permitted by law, including compliance with court orders or lawful instructions from a government agency, to protect the personal safety of subscribers or the public, to defend claims, and as otherwise authorized by you. First Resource Bank and its affiliates and service providers also reserve the right to monitor use of Mobile Banking and the Software for purposes of verifying compliance with the law, these terms and conditions and any applicable license, but disclaim any obligation to monitor, filter, or edit any content. Restrictions on Use. You agree not to use Mobile Banking or the Software in or for any illegal, fraudulent, unauthorized or improper manner or purpose and will only be used in compliance with all applicable laws, rules and regulations, including all applicable state, federal, and international Internet, data, telecommunications, telemarketing, “spam,” and import/export laws and regulations, including the U.S. Export Administration Regulations. Without limiting the foregoing, you agree that you will not use Mobile Banking or the Software to transmit or disseminate: (i) junk mail, spam, or unsolicited material to persons or entities that have not agreed to receive such material or to whom you do not otherwise have a legal right to send such material; (ii) material that infringes or violates any third party’s intellectual property rights, rights of publicity, privacy, or confidentiality, or the rights or legal obligations of any wireless service provider or any of its clients or subscribers; (iii) material or data, that is illegal, or material or data, as determined by First Resource Bank (in its sole discretion), that is harassing, coercive, defamatory, libelous, abusive, threatening, obscene, or otherwise objectionable, materials that are harmful to minors or excessive in quantity, or materials the transmission of which could diminish or harm the reputation of First Resource Bank or any third-party service provider involved in the provision of Mobile Banking; (iv) material or data that is alcoholic beverage-related (e.g., beer, wine, or liquor), tobacco-related (e.g., cigarettes, cigars, pipes, chewing tobacco), guns or weapons-related (e.g., firearms, bullets), illegal drugs- related (e.g., marijuana, cocaine), pornographic-related (e.g., adult themes, sexual content), crime-related (e.g., organized crime, notorious characters), violence-related (e.g., violent games), death-related (e.g., funeral homes, mortuaries), hate-related (e.g. racist organizations), gambling-related (e.g., casinos, lotteries), specifically mentions any wireless carrier or copies or parodies the products or services of any wireless carrier; (v) viruses, Trojan horses, worms, time bombs, cancelbots, or other computer programming routines that are intended to damage, detrimentally interfere with, surreptitiously intercept or expropriate any system, data, or personal information; (vi) any material or information that is false, misleading, or inaccurate; (vii) any material that would expose First Resource Bank, any third-party service provider involved in providing Mobile Banking, or any other third party to liability; or (viii) any signal or impulse that could cause electrical, magnetic, optical, or other technical harm to the equipment or facilities of Fiserv or any third party. You agree that you will not attempt to: (a) access any software or services for which your use has not been authorized; or (b) use or attempt to use a third party’s account; or (c) interfere in any manner with the provision of Mobile Banking or the Software, the security of Mobile Banking or the Software, or other customers of Mobile Banking or the Software; or (d) otherwise abuse Mobile Banking or the Software.

  • Contractor Sales Reporting Vendor Management Fee Contractor Reports Master Contract Sales Reporting. Contractor shall report total Master Contract sales quarterly to Enterprise Services, as set forth below. Master Contract Sales Reporting System. Contractor shall report quarterly Master Contract sales in Enterprise Services’ Master Contract Sales Reporting System. Enterprise Services will provide Contractor with a login password and a vendor number. The password and vendor number will be provided to the Sales Reporting Representative(s) listed on Contractor’s Bidder Profile. Data. Each sales report must identify every authorized Purchaser by name as it is known to Enterprise Services and its total combined sales amount invoiced during the reporting period (i.e., sales of an entire agency or political subdivision, not its individual subsections). The “Miscellaneous” option may be used only with prior approval by Enterprise Services. Upon request, Contractor shall provide contact information for all authorized purchasers specified herein during the term of the Master Contract. If there are no Master Contract sales during the reporting period, Contractor must report zero sales. Due dates for Master Contract Sales Reporting. Quarterly Master Contract Sales Reports must be submitted electronically by the following deadlines for all sales invoiced during the applicable calendar quarter: For Calendar Quarter Ending Master Contract Sales Report Due March 31: April 30 June 30: July 31 September 30: October 31 December 31: January 31 Vendor Management Fee. Contractor shall pay to Enterprise Services a vendor management fee (“VMF”) of 0.74 percent on the purchase price for all Master Contract sales (the purchase price is the total invoice price less applicable sales tax). The sum owed by Contractor to Enterprise Services as a result of the VMF is calculated as follows: Amount owed to Enterprise Services = Total Master Contract sales invoiced (not including sales tax) x .0074. The VMF must be rolled into Contractor’s current pricing. The VMF must not be shown as a separate line item on any invoice unless specifically requested and approved by Enterprise Services. Enterprise Services will invoice Contractor quarterly based on Master Contract sales reported by Contractor. Contractors are not to remit payment until they receive an invoice from Enterprise Services. Contractor’s VMF payment to Enterprise Services must reference this Master Contract number, work request number (if applicable), the year and quarter for which the VMF is being remitted, and the Contractor’s name as set forth in this Master Contract, if not already included on the face of the check. Failure to accurately report total net sales, to submit a timely usage report, or remit timely payment of the VMF, may be cause for Master Contract termination or the exercise of other remedies provided by law. Without limiting any other available remedies, the Parties agree that Contractor’s failure to remit to Enterprise Services timely payment of the VMF shall obligate Contractor to pay to Enterprise Services, to offset the administrative and transaction costs incurred by the State to identify, process, and collect such sums. the sum of $200.00 or twenty-five percent (25%) of the outstanding amount, whichever is greater, or the maximum allowed by law, if less. Enterprise Services reserves the right, upon thirty (30) days advance written notice, to increase, reduce, or eliminate the VMF for subsequent purchases, and reserves the right to renegotiate Master Contract pricing with Contractor when any subsequent adjustment of the VMF might justify a change in pricing.

  • Authorized User Overview and Mini-Bid Process Project Based IT Consulting Services Contracts enable Authorized Users to use a competitive Mini-bid Process to acquire Services on an as-needed basis, for qualified IT Projects. Project Based IT Consulting Services may include, but will not be limited to projects requiring: analysis, data classification, design, development, testing, quality assurance, security and associated training for Information Technology based applications. See section 1.3 Out of Scope Work for a listing of projects expressly excluded from the scope of this Contract. An Authorized User Agreement for Project Based IT Consulting Services will be governed first by the terms and conditions specified in the OGS Centralized Contract and second by terms and conditions added to the Authorized User Statement of Work. Additional terms and conditions shall not conflict with or modify the terms and conditions of the OGS Centralized Contract. NYS Executive Agencies must adhere to all internal processes and approvals including, as required, approval from NYS Office of Information Technology Services. Other Authorized Users must adhere to their own internal processes and approvals. In accordance with Appendix B, section 28, Modification of Contract Terms, an Authorized User may add additional required terms and conditions to this Mini-Bid and resultant Authorized User Agreement only if such terms and conditions (1) are more favorable to the Authorized User and (2) do not conflict with or supersede the OGS Centralized Contract terms and conditions. Examples of additional terms and conditions include: • Expedited delivery timeframe; • Additional incentives, such as discount for expedited payment/Procurement Card use; and • Any additional requirements imposed by the funding source or Federal law.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!