Payments for Provider-Preventable Conditions Sample Clauses

Payments for Provider-Preventable Conditions. Section 2702(a) of the Affordable Care Act prohibits Federal financial participation (FFP) payments to States for any amounts expended for providing medical assistance for Provider Preventable Conditions (PPCs), including health care-acquired conditions (HCACs) and other provider-preventable conditions (OPPCs). PPCs are hospital-acquired conditions not present on hospital admission, the wrong procedure performed on a patient, and procedures performed on a wrong patient or body part. The MCO may not make payments for PPCs as defined by the federal regulations and BMS policy in accordance with 42 CFR 438.6. The MCO will track PPC data and make it available to BMS upon request.
Sample 1Sample 2Sample 3See All (9)
AutoNDA by SimpleDocs
Payments for Provider-Preventable Conditions. Section 2702(a) of the Affordable Care Act (ACA) prohibits federal financial participation (FFP) payments to States for any amounts expended for providing medical assistance for Provider Preventable Conditions (PPCs), including health care-acquired conditions (HCACs) and other provider-preventable conditions (OPPCs). PPCs are hospital-acquired conditions not present on hospital admission, the wrong procedure performed on a patient, and procedures performed on a wrong patient or body part. The MCO may not make payments for PPCs as defined by the federal regulations and DHHR policy in accordance with 42 CFR §438.6 and 42 CFR §447.26. The MCO will track PPC data and make it available to DHHR upon request. Other provider-preventable condition means a condition occurring in any health care setting that meets the following criteria:
Sample 1Sample 2Sample 3See All (7)
Payments for Provider-Preventable Conditions. The Contractor may not make payments for Provider-preventable conditions as defined by the Federal regulations and the Mississippi State Plan in accordance with 42 C.F.R. § 438.6. In accordance with the Mississippi State Plan, the Contractor shall identify and deny Never Events, which are a type of Provider-preventable condition. The Contractor shall track data and submit a report quarterly, in a format to be specified by the Division.
Sample 1Sample 2
Payments for Provider-Preventable Conditions. The Contractor may not make payments for Provider-preventable conditions as defined by the Federal regulations and the Mississippi State Plan in accordance with 42 C.F.R. § 438.6. In accordance with the Mississippi State Plan, the Contractor shall identify and deny Never Events, which are a type of Provider-preventable condition. The Contractor shall track data and submit a report quarterly, in a format to be specified by the Division. Section 2702(a) of the Affordable Care Act prohibits Federal financial participation (FFP) payments to States for any amounts expended for providing medical assistance for health care-acquired conditions (HCACs) and other Provider-Preventable Conditions (PPCs). PPCs are hospital-acquired conditions not present on hospital admission, the wrong procedure performed on a patient, and procedures performed on a wrong patient or body part. The Contractor may not make payments for PPCs as defined by the federal regulations in accordance with 42 C.F.R. § 438.6. The Contractor will track PPC data and make it available to the Division upon request.
Sample 1

Related to Payments for Provider-Preventable Conditions

  • Service Conditions Customer acknowledges that in the event of a service issue, Customer is responsible for on-site cooperative testing with LightEdge Technical Support to assist in the diagnosis of the trouble. Customer agrees to be bound to current terms of LightEdge Acceptable Use Policy. Terms of the Acceptable Use Policy are subject to change without notice. Current Acceptable Use Policy can be found here: xxxx://xxx.xxxxxxxxx.xxx/legal Customer agrees that any service complaints including concerns regarding level of support, products, service reliability, or any other concerns related to LightEdge or Services being provided by LIghtEdge will be communicated to LightEdge by sending an email to xx@xxxxxxxxx.xxx.

  • Forecasting Requirements for Trunk Provisioning Within ninety (90) days of executing this Agreement, Reconex shall provide Verizon a two (2) year traffic forecast. This initial forecast will provide the amount of traffic to be delivered to and from Verizon over each of the Local Interconnection Trunk groups over the next eight (8) quarters. The forecast shall be updated and provided to Verizon on an as-needed basis but no less frequently than semiannually. All forecasts shall comply with the Verizon CLEC Interconnection Trunking Forecast Guide and shall include, at a minimum, Access Carrier Terminal Location (“ACTL”), traffic type (Local Traffic/Toll Traffic, Operator Services, 911, etc.), code (identifies trunk group), A location/Z location (CLLI codes for Reconex-IPs and Verizon-IPs), interface type (e.g., DS1), and trunks in service each year (cumulative).

  • Contract Conditions This section contains conditions which shall be complied with during the performance of this contract. The conditions come in two parts, general conditions and special contract requirements.

  • ADDITIONAL SPECIAL CONTRACT CONDITIONS A. Special Contract Conditions revisions: the corresponding subsections of the Special Contract Conditions referenced below are replaced in their entirety with the following:

  • Unbundled Loop Modifications (Line Conditioning 2.5.1 Line Conditioning is defined as routine network modification that BellSouth regularly undertakes to provide xDSL services to its own customers. This may include the removal of any device, from a copper Loop or copper Sub-loop that may diminish the capability of the Loop or Sub-loop to deliver high-speed switched wireline telecommunications capability, including xDSL service. Such devices include, but are not limited to, load coils, excessive bridged taps, low pass filters, and range extenders. Excessive bridged taps are bridged taps that serves no network design purpose and that are beyond the limits set according to industry standards and/or the XxxxXxxxx XX 00000.

  • Safe Conditions Whenever an employee reports a condition which the employee feels represents a violation of safety or health rules and regulations or which is an unreasonable hazard to persons or property, such conditions shall be promptly investigated. The appropriate administrator shall reply to the concern, in writing, if the employee's concern is communicated in writing.

  • Unsafe Conditions In accordance with 29 CFR § 1977, occasions might arise when an employee is confronted with a choice between not performing assigned tasks or subjecting himself/herself to serious injury or death arising from a hazardous condition at the workplace. If the employee, with no reasonable alternative, refuses in good faith to expose himself/herself to the dangerous condition, he/she would be protected against subsequent discrimination. The condition causing the employee's apprehension of death or injury must be of such a nature that a reasonable person, under the circumstances then confronting the employee, would conclude that there is a real danger of death or serious injury and that there is insufficient time, due to the urgency of the situation, to eliminate the danger by resorting to regular statutory enforcement channels. In addition, in such circumstances, the employee, where possible, must also have sought from his Employer, and been unable to obtain, a correction of the dangerous condition.

  • SUSPENSIVE CONDITIONS 18.1 The Contract is subject to the suspensive condition that the Purchaser obtains a loan in the amount reflected in clause 7 of the SCHEDULE, forming part of the Purchase price payable by the Purchaser to the Seller for the Property, from a bank or other financial institution, against the security of a first mortgage bond over the Property in favour of such bank or financial institution, such loan to be approved in writing by such bank or financial institution within the period stipulated in clause 9 of the SCHEDULE.

  • Supplemental JBoss Software Conditions Software Access and Software Maintenance for Supplemental JBoss Software is intended and available for Development Purposes only and for up to 25 users for each 16 Core Band Subscription of Red Hat JBoss Middleware Software that you purchased. If you deploy or use the Supplemental JBoss Software for Production Purposes or for more than 25 users, you agree to purchase the appropriate Software Subscriptions for each Unit that you deploy or use. Red Hat’s Open Source Assurance Program applies only to the Red Hat JBoss Middleware Software Subscription that you purchased (such as Red Hat JBoss Enterprise Application Platform in the example above) and does not apply to Supplemental JBoss Software. JBoss xPaaS Subscriptions (defined below) are not considered Supplemental JBoss Software. Each installation and use of JBoss xPaaS Subscriptions Software for either Development Purposes or Production Purposes is a Unit and requires a paid Software Subscription.

  • Commercial Operation Date Testing and Modifications Prior to the Commercial Operation Date, the Connecting Transmission Owner shall test the Connecting Transmission Owner’s Attachment Facilities and System Upgrade Facilities and System Deliverability Upgrades and Developer shall test the Large Generating Facility and the Developer Attachment Facilities to ensure their safe and reliable operation. Similar testing may be required after initial operation. Developer and Connecting Transmission Owner shall each make any modifications to its facilities that are found to be necessary as a result of such testing. Developer shall bear the cost of all such testing and modifications. Developer shall generate test energy at the Large Generating Facility only if it has arranged for the injection of such test energy in accordance with NYISO procedures.

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