Preferred Drug List and Formulary Requirements Sample Clauses

Preferred Drug List and Formulary Requirements. The Contractor shall maintain a preferred drug list (PDL) for the Contractor’s Hoosier Healthwise packages. The Hoosier Healthwise formulary shall support the coverage and non-coverage requirements for legend and non-legend drugs by Indiana Medicaid. More information can be found in 000 XXX 0-00-0, 405 IAC 5-24-4, 405 IAC 5-24-5 and 407 IAC 3-10-1. Prior to implementing a PDL or formulary, the Contractor shall: (i) submit the PDL or formulary to OMPP for submission to the Drug Utilization and Review (DUR) Board; and (ii) receive approval from OMPP in accordance with IC 00-00-00-00. At least thirty-five (35) days before the intended implementation date of the PDL and formulary, the Contractor shall submit its proposed PDL and formulary to OMPP. The OMPP shall submit the PDL and formulary to the Drug Utilization Review (DUR) Board for review and recommendation. The Contractor shall be accessible to the DUR Board to respond to any questions regarding the PDL and formulary. The DUR Board will provide a recommendation regarding approval of the PDL and formulary in accordance with the terms of IC 00-00-00-00. OMPP will approve, disapprove or modify the PDL and/or formulary based on the DUR Board’s recommendation. The Contractor shall comply with the decision within sixty (60) days after receiving notice of the decision. The Contractor shall utilize a Pharmacy and Therapeutics Committee which shall meet regularly to make recommendations for changes to the PDL and/or formulary. In accordance with IC 00-00-00-00, prior to removing one (1) or more drugs from the PDL and/or formulary or otherwise placing new PA criteria on one (1) or more drugs, the Contractor shall submit the proposed change to the OMPP which shall forward the proposal to the DUR Board. Such changes shall be submitted at least thirty-five (35) calendar days in advance of the proposed change. The Contractor shall also meet with OMPP staff, as directed by OMPP, to answer questions about the clinical rationale for the proposed change. The DUR Board will provide a recommendation regarding approval of the proposed change to the PDL and/or formulary in accordance with the terms of IC 12-15-35-
Sample 1Sample 2Sample 3See All (23)
AutoNDA by SimpleDocs
Preferred Drug List and Formulary Requirements. The Contractor shall maintain a preferred drug list (PDL) for the Contractor’s Hoosier Healthwise packages. The Hoosier Healthwise formulary shall support the coverage and non-coverage requirements for legend and non-legend drugs by Indiana Medicaid. More information can be found in 000 XXX 0-00-0, 405 IAC 5-24-4, 405 IAC 5-24-5 and 407 IAC 3-10-1. Prior to implementing a PDL or formulary, the Contractor shall: (i) submit the PDL or formulary to OMPP for submission to the Drug Utilization and Review (DUR) Board; and
Sample 1Sample 2Sample 3See All (7)
Preferred Drug List and Formulary Requirements. The Contractor shall maintain a preferred drug list (PDL) for the Contractor’s Hoosier Healthwise packages. The Hoosier Healthwise formulary shall support the coverage and non-coverage requirements for legend and non-legend drugs by Indiana Medicaid. More information can be found in 000 XXX 0-00-0, 405 IAC 5-24-4, 405 IAC 5-24-5 and 407 IAC 3-10-1. In accordance with CMS-2390-F, the Contractor shall demonstrate prescription drug coverage consistent with the amount, duration, and scope of the fee-for-service program. The Contractor shall
Sample 1Sample 2Sample 3See All (4)
Preferred Drug List and Formulary Requirements. The Contractor shall maintain a preferred drug list (PDL) for the Contractor’s HIP program. The HIP formulary shall support the coverage and non-coverage requirements for legend drugs by Indiana Medicaid, found in 405 IAC 5-24-3. In accordance with CMS- 2390-F, the Contractor shall demonstrate prescription drug coverage consistent with the amount, duration, and scope of the fee-for-service program. The Contractor shall engage with the State process to develop universal medically necessary prior authorization criteria for IHCP. The Contractor shall implement the universal IHCP criteria into their program and may not utilize more restrictive criteria. While the underlying drug formulary for the HIP Plus and the HIP Basic plans will be identical, additional pharmacy services will differ between the plans in order to align the benefits with the overall program goals aimed at encouraging member participation in HIP Plus. Therefore, the HIP Basic pharmacy benefit may have more restrictions than the HIP plus benefit, such as limiting prescription supplies to 30 days. Also, prescriptions obtained by a HIP Basic or HIP State Plan Basic member that are not otherwise exempt on the basis of being preventive, family planning, or maternity, are subject to the copayment amounts set forth in Section 4.1.2. Copayments assessed to the HIP Basic or HIP State Plan Basic member at the point of sale may not exceed the total cost of the drug. Similarly, the HIP Plus pharmacy benefit shall provide additional enhanced pharmacy services including the following: (i) ninety (90) day prescription supplies of routine maintenance medications, when requested by the member; (ii) mail order pharmacy benefit;
Sample 1Sample 2Sample 3See All (4)
Preferred Drug List and Formulary Requirements. The Contractor shall maintain a preferred drug list (PDL) for the Contractor’s HIP program. The HIP formulary shall support the coverage and non-coverage requirements for legend drugs by Indiana Medicaid, found in 405 IAC 5-24- 3. While the underlying drug formulary for the HIP Plus and the HIP Basic plans will be identical, additional pharmacy services will differ between the plans in order to align the benefits with the overall program goals aimed at encouraging member participation in HIP Plus. Therefore, the HIP Basic pharmacy benefit may have more restrictions than the HIP plus benefit, such as limiting prescription supplies to 30 days. Also, prescriptions obtained by a HIP Basic or HIP State Plan Basic member that are not otherwise exempt on the basis of being preventive, family planning, or maternity, are subject to the copayment amounts set forth in Section 4.1.2. Copayments assessed to the HIP Basic or HIP State Plan Basic member at the point of sale may not exceed the total cost of the drug. Similarly, the HIP Plus pharmacy benefit shall provide additional enhanced pharmacy services including the following: (i) ninety (90) day prescription supplies of routine maintenance medications, when requested by the member;
Sample 1Sample 2Sample 3

Related to Preferred Drug List and Formulary Requirements

  • Alcohol and Drug Testing Employee agrees to comply with and submit to any Company program or policy for testing for alcohol abuse or use of drugs and, in the absence of such a program or policy, to submit to such testing as may be required by Company and administered in accordance with applicable law and regulations.

  • Random Drug Testing All employees covered by this Agreement shall be subject to random drug testing in accordance with Appendix D.

  • Federal Medicaid System Security Requirements Compliance Party shall provide a security plan, risk assessment, and security controls review document within three months of the start date of this Agreement (and update it annually thereafter) in order to support audit compliance with 45 CFR 95.621 subpart F, ADP System Security Requirements and Review Process.

  • Prescription Drug Plan Retail and mail order prescription drug copays for bargaining unit employees shall be as follows:

  • Prescription Drugs The agreement may impose a variety of limits affecting the scope or duration of benefits that are not expressed numerically. An example of these types of treatments limit is preauthorization. Preauthorization is applied to behavioral health services in the same way as medical benefits. The only exception is except where clinically appropriate standards of care may permit a difference. Mental disorders are covered under Section A. Mental Health Services. Substance abuse disorders are covered under

  • Safety Requirements The Contractor shall comply with all Federal, State, and local safety laws and regulations applicable to the Work performed under this Agreement.

  • Program Requirements The parties shall comply with the Disadvantaged Business Enterprise Program requirements established in 49 CFR Part 26.

  • New Hampshire Specific Data Security Requirements The Provider agrees to the following privacy and security standards from “the Minimum Standards for Privacy and Security of Student and Employee Data” from the New Hampshire Department of Education. Specifically, the Provider agrees to: (1) Limit system access to the types of transactions and functions that authorized users, such as students, parents, and LEA are permitted to execute; (2) Limit unsuccessful logon attempts; (3) Employ cryptographic mechanisms to protect the confidentiality of remote access sessions; (4) Authorize wireless access prior to allowing such connections; (5) Create and retain system audit logs and records to the extent needed to enable the monitoring, analysis, investigation, and reporting of unlawful or unauthorized system activity; (6) Ensure that the actions of individual system users can be uniquely traced to those users so they can be held accountable for their actions; (7) Establish and maintain baseline configurations and inventories of organizational systems (including hardware, software, firmware, and documentation) throughout the respective system development life cycles; (8) Restrict, disable, or prevent the use of nonessential programs, functions, ports, protocols, and services; (9) Enforce a minimum password complexity and change of characters when new passwords are created; (10) Perform maintenance on organizational systems; (11) Provide controls on the tools, techniques, mechanisms, and personnel used to conduct system maintenance; (12) Ensure equipment removed for off-site maintenance is sanitized of any Student Data in accordance with NIST SP 800-88 Revision 1; (13) Protect (i.e., physically control and securely store) system media containing Student Data, both paper and digital; (14) Sanitize or destroy system media containing Student Data in accordance with NIST SP 800-88 Revision 1 before disposal or release for reuse; (15) Control access to media containing Student Data and maintain accountability for media during transport outside of controlled areas; (16) Periodically assess the security controls in organizational systems to determine if the controls are effective in their application and develop and implement plans of action designed to correct deficiencies and reduce or eliminate vulnerabilities in organizational systems; (17) Monitor, control, and protect communications (i.e., information transmitted or received by organizational systems) at the external boundaries and key internal boundaries of organizational systems; (18) Deny network communications traffic by default and allow network communications traffic by exception (i.e., deny all, permit by exception); (19) Protect the confidentiality of Student Data at rest; (20) Identify, report, and correct system flaws in a timely manner; (21) Provide protection from malicious code (i.e. Antivirus and Antimalware) at designated locations within organizational systems; (22) Monitor system security alerts and advisories and take action in response; and (23) Update malicious code protection mechanisms when new releases are available.

  • Food Service Waste Reduction Requirements Contractor shall comply with the Food Service Waste Reduction Ordinance, as set forth in San Francisco Environment Code Chapter 16, including but not limited to the remedies for noncompliance provided therein.

  • Export Requirements The Program, Documentation and all related technical information or materials are subject to export controls and U.S. Government export regulations. You will comply strictly with all legal requirements established under these controls and will not, in connection with its limited evaluation rights hereunder, export, re-export, divert, transfer or disclose, directly or indirectly the Program, Documentation and any related technical information or materials without the prior approval of the U.S.

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