Preferred Drug List Requirements Sample Clauses

Preferred Drug List Requirements. The Contractor shall maintain a preferred drug list (PDL). In accordance with IC 12-15- 35-46, State approval of the PDL shall be required prior to Contractor implementation. The Contractor shall submit the proposed PDL to FSSA at least thirty-five (35) calendar days before the intended PDL implementation date. The FSSA shall submit the PDL to the DUR Board for review and recommendation. The Contractor shall be accessible to the DUR Board to respond to any questions regarding the PDL. The DUR Board will provide a recommendation regarding approval of the PDL in accordance with the terms of IC 00-00-00-00. FSSA will approve, disapprove or modify the formulary based on the DUR Board’s recommendation. The Contractor shall comply with the decision within sixty
AutoNDA by SimpleDocs
Preferred Drug List Requirements. The Contractor shall maintain a preferred drug list (PDL). In accordance with IC 12-15- 35-46, State approval of the PDL shall be required prior to Contractor implementation. The Contractor shall submit the proposed PDL to FSSA at least thirty-five (35) calendar days before the intended PDL implementation date. The FSSA shall submit the PDL to the DUR Board for review and recommendation. The Contractor shall be accessible to the DUR Board to respond to any questions regarding the PDL. The DUR Board will provide a recommendation regarding approval of the PDL in accordance with the terms of IC 00-00-00-00. FSSA will approve, disapprove or modify the 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. In accordance with IC 00- 00-00-00, prior to removing one (1) or more drugs from the PDL or placing new restrictions on one (1) or more drugs, the Contractor shall submit the proposed change to FSSA 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 FSSA staff and/or the DUR Board, as directed by FSSA, to answer questions about the clinical rationale for the proposed change. The Contractor is not required to seek approval from the State in order to add a drug to the PDL; however, the Contractor shall notify FSSA of any addition to the PDL within thirty (30) days after making the addition. The Contractor shall maintain an Over-the-Counter (OTC) Drug Formulary which contains, at a minimum, the same items included in the Hoosier Healthwise fee-for- service OTC Formulary and as updated by the DUR Board. Any additions to the Contractor OTC Drug Formulary are required to only be from participating rebating labelers. The PDL shall be made readily available to providers in the Contractor’s network and to members. The PDL shall be updated to reflect all changes in the status of a drug or addition of new drugs. The Contractor shall also support e-Prescribing technologies to communicate the PDL to prescribers through electronic medical records (EMRs) and e- Prescribing applications. Refer to 3.8.5 for additional requirements on e-Prescribing. Notwithstanding the foregoing, the Contractor...
Preferred Drug List Requirements. The Contractor shall maintain a preferred drug list (PDL). In accordance with IC 00-00-00-00, State approval of the PDL shall be required prior to Contractor implementation. The Contractor shall submit the proposed PDL to OMPP at least thirty -five (35) calendar days before the intended PDL implementation date. OMPP shall submit the PDL to the DUR Board for review and recommendation. The Contractor shall be accessible to the DUR Board to respond to any questions regarding the PDL. The DUR Board will provide a recommendation regarding approval of the PDL in accordance with the terms of IC 12-15-35-
Preferred Drug List Requirements. The Contractor shall maintain a preferred drug list (PDL). In accordance with IC 00-00-00-00, State approval of the PDL shall be required prior to Contractor implementation. The Contractor shall submit the proposed PDL to FSSA at least thirty-five (35) calendar days before the intended PDL implementation date. The FSSA shall submit the PDL to the DUR Board for review and recommendation. The Contractor shall be accessible to the DUR Board to respond to any questions regarding the PDL. The DUR Board will provide a recommendation regarding approval of the PDL in accordance with the terms of IC 12-15-35- 46. FSSA will approve, disapprove or modify the 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. Per CFR 438.10(i)(1)-(2), the Contractor shall make available in electronic or paper form, the covered drug list(s) of medications including the reference brand and generic names of each drug as well as what tier each drug is on. The Contractor shall utilize a Pharmacy and Therapeutics Committee which shall meet regularly to make recommendations for changes to the PDL. In accordance with IC 12-15- 35-47, prior to removing one (1) or more drugs from the PDL or placing new restrictions on one (1) or more drugs, the Contractor shall submit the proposed change to FSSA which shall forward the proposal to the DUR Board. Such changes shall be submitted at least thirty-five

Related to Preferred Drug List Requirements

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

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

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

  • System Requirements Apple Software is supported only on Apple-branded hardware that meets specified system requirements as indicated by Apple.

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

  • DRUG/ALCOHOL TESTING Section 33.1 Drug testing may be conducted on employees during their duty hours upon reasonable suspicion or randomly by computer selection. Alcohol testing will be conducted only upon reasonable suspicion. Reasonable suspicion that an employee used or is using a controlled substance or alcohol in an unlawful or abusive manner may be based upon, but not limited to: A. Observable phenomena, such as direct observation of drug or alcohol use or possession and/or the physical symptoms of being under the influence of a drug or alcohol; B. A pattern or abnormal conduct or erratic behavior, including abnormal leave patterns; C. Arrest or conviction for a drug or alcohol-related offense, or the identification of an employee as the focus of a criminal investigation into illegal drug or alcohol possession, use, or trafficking; D. Information provided either by reliable and credible sources or independently corroborated; E. Evidence that an employee has tampered with a previous drug test; F. Facts or circumstances developed in the course of an authorized investigation of an accident or unsafe working practices. Section 33.2 Drug/alcohol testing shall be conducted solely for administrative purposes and the results obtained shall not be used in criminal proceedings. Under no circumstances may the results of drug/alcohol screening or testing be released to a third party for use in a criminal prosecution against the affected employee. The following procedure shall not preclude the Employer from other administrative action but such actions shall not be based solely upon the initial reagent testing results alone. Section 33.3 All drug screening tests shall be conducted by laboratories meeting the standards of the Substance Abuse and Mental Health Service Administration. No test shall be considered positive until it has been confirmed by a Gas Chromatography/Mass Spectrometry. The procedures utilized by the Employer and testing laboratory shall include an evidentiary chain of custody control and split sample testing. All procedures shall be outlined in writing and this outline shall be followed in all situations arising under this article. Section 33.4 Alcohol testing shall be done in accordance with the law of the State of Ohio to detect drivers operating a motor vehicle under the influence. A positive result shall entitle the Employer to proceed with sanctions as set forth in this Article. Section 33.5 The results of the testing shall be delivered to a specified employee of the Employer with command responsibility and the employee tested. An employee whose confirmatory test result is positive shall have the right to request a certified copy of the testing results in which the vendor shall affirm that the test results were obtained using the approved protocol methods. The employee shall provide a signed release for disclosure of the testing results to the Employer. A representative for the bargaining unit shall have a right of access to the results upon request to the Employer, with the employee’s written consent. Refusal to submit to the testing provided for under this Agreement may be grounds for discipline. A. If a drug screening test is positive, a confirmatory test shall be conducted utilizing the fluid from the primary sample. B. In the event that any confirmation drug test results are positive, the employee is entitled to have the split sample tested by another DHHS-certified lab in the manner prescribed above at the employee’s expense. The employee must request the split sample test within seventy-two (72) hours of being notified of a positive result. The results of this test, whether positive or negative, shall be determinative. Section 33.7 A list of three (3) testing laboratories shall be maintained by the Employer. These laboratories shall conduct any testing directed by the Employer. The Employer shall obtain the approval of the bargaining unit representative as to any laboratories put on this list, which approval shall not be unreasonably withheld. Section 33.8 If after the testing required above has produced a positive result the Employer may require the employee to participate in any rehabilitation or detoxification program that is covered by the employee’s health insurance. Discipline allowed by the positive findings provided for above shall be deferred pending rehabilitation of the employee within a reasonable period. An employee who participates in a rehabilitation or detoxification program shall be allowed to use sick time and vacation leave for the period of the rehabilitation or detoxification program. If no such leave credits are available, the employee shall be placed on medical leave of absence without pay for the period of the rehabilitation or detoxification program. Upon completion of such program and upon receiving results from a retest demonstrating that the employee is no longer abusing a controlled substance/alcohol, the employee shall be returned to his/her former position. Such employee may be subject to periodic retesting upon his/her return to his/her position for a period of one (1) year from the date of his/her return to work. Any employee in a rehabilitation or detoxification program in accordance with this Article will not lose any seniority or benefits, should it be necessary for the employee to be placed on medical leave of absence without pay, for a period not to exceed ninety (90) days. Section 33.9 If the employee refuses to undergo rehabilitation or detoxification, or if he/she tests positive during a retesting within one (1) year after his/her return to work from such a program, the employee shall be subject to disciplinary action, including removal from his/her position and termination of his/her employment. Section 33.10 Costs of all drug screening tests and confirmatory tests shall be borne by the Employer except that any test initiated at the request of the employee shall be at the employee’s expense. Section 33.11 The Employer may conduct four (4) tests of an employee during the one (1) year period after the employee has completed a rehabilitation or detoxification program as provided above. Section 33.12 The provisions of this Article shall not require the Employer to offer a rehabilitation/detoxification program to any employee more than once.

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

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

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

  • Basic Requirements To be eligible for PayPal’s Seller Protection program, all of the following basic requirements must be met, as well as any applicable additional requirements: • The primary address for your PayPal account must be in the United States. • The item must be a physical, tangible good that can be shipped, except for items subject to the Intangible Goods Additional Requirements. Transactions involving items that you deliver in person in connection with payment made in your physical store, may also be eligible for PayPal’s Seller Protection program so long as the buyer paid for the transaction in person by using a PayPal goods and services QR code. • You must ship the item to the shipping address on the Transaction Details page in your PayPal account for the transaction. If you originally ship the item to the recipient’s shipping address on the Transaction Details page but the item is later redirected to a different address, you will not be eligible for PayPal’s Seller Protection program. We therefore recommend not using a shipping service that is arranged by the buyer, so that you will be able to provide valid proof of shipping and delivery. • The shipping requirement does not apply to eligible transactions involving items that you deliver in person; provided, however, that you agree to provide us with alternative evidence of delivery or such additional documentation or information relating to the transaction that we may request. • You must respond to PayPal’s requests for documentation and other information in a timely manner as requested in our email correspondence with you or in our correspondence with you through the Resolution Center. If you do not respond to PayPal’s request for documentation and other information in the time requested, you may not be eligible for PayPal’s Seller Protection program. • If the sale involves pre-ordered or made-to-order goods, you must ship within the timeframe you specified in the listing. Otherwise, it is recommended that you ship all items within 7 days after receipt of payment. • You provide us with valid proof of shipment or delivery. • The payment must be marked “eligible” or “partially eligible” in the case of Unauthorized Transaction claims, or “eligible” in the case of Item Not Received claims, for PayPal’s Seller Protection program on the Transaction Details page. • In the case of an Unauthorized Transaction claim, you must provide valid proof of shipment or proof of delivery that demonstrates that the item was shipped or provided to the buyer no later than two days after PayPal notified you of the dispute or reversal. For example, if PayPal notifies you of an Unauthorized Transaction claim on September 1, the valid proof of shipment must indicate that the item was shipped to the buyer no later than September 3 to be eligible for PayPal’s Seller Protection program. PayPal determines, in its sole discretion, whether your claim is eligible for PayPal’s Seller Protection program. PayPal will make a decision, in its sole discretion, based on the eligibility requirements, any information or documentation provided during the resolution process, or any other information PayPal deems relevant and appropriate under the circumstances. To be eligible for PayPal’s Seller Protection program for a buyer’s Item Not Received claim, you must meet both the basic requirements and the additional requirements listed below: • Where a buyer files a chargeback with the issuer for a card-funded transaction, the payment must be marked “eligible” for PayPal’s Seller Protection on the Transaction Details page. • You must provide proof of delivery as described below.

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