Incomplete Data For Last Menstrual Period Sample Clauses

Incomplete Data For Last Menstrual Period. As outlined in ODJFS Encounter Data Specifications, the last menstrual period (LMP) field is a required encounter data field. It is discussed in Item 14 of the “HCFA 1500 Billing Instructions.” The date of the LMP is essential for calculating the clinical performance measures and allows the ODJFS to adjust performance expectations for the length of a pregnancy. The occurrence code and date fields on the UB-92, which are “optional” fields, can also be used to submit the date of the LMP. These fields are described in Items 32a & b, 33a & b, 34a & b, 35a & b of the “Inpatient Hospital” and “Outpatient Hospital UB-92 Claim Form Instructions.” An occurrence code value of ‘10’ indicates that a LMP date was provided. The actual date of the LMP would be given in the ‘Occurrence Date’ field.
Sample 1Sample 2Sample 3See All (4)
AutoNDA by SimpleDocs

Related to Incomplete Data For Last Menstrual Period

  • Complete Portfolio Holdings From Shareholder Reports Containing a Summary Schedule of Investments; and

  • Venue Limitation for TIPS Sales Vendor agrees that if any "Venue" provision is included in any TIPS Sale Agreement/contract between Vendor and a TIPS Member, that clause must provide that the "Venue" for any litigation or alternative dispute resolution shall be in the state and county where the TIPS Member operates unless the TIPS Member expressly agrees otherwise. Any TIPS Sale Supplemental Agreement containing a “Venue” clause that conflicts with these terms is rendered void and unenforceable.

  • SUBMISSION OF THE MONTHLY MI REPORT 4.1 The completed MI Report shall be completed electronically and returned to the Authority by uploading the electronic MI Report computer file to MISO in accordance with the instructions provided in MISO. 4.2 The Authority reserves the right (acting reasonably) to specify that the MI Report be submitted by the Supplier using an alternative communication to that specified in paragraph 4.1 above such as email. The Supplier agrees to comply with any such instructions provided they do not materially increase the burden on the Supplier.

  • How Do I Correct an Excess Contribution? If you make a contribution in excess of your allowable maximum, you may correct the excess contribution and avoid the 6% penalty tax under Section 4973 of the Internal Revenue Code for that year by withdrawing the excess contribution and its earnings on or before the due date, including extensions, of the tax return for the tax year for which the contribution was made (generally October 15th). Any earnings on the withdrawn excess contribution may be subject to a 10% early distribution penalty tax if you are under age 59½. In addition, in certain cases an excess contribution may be withdrawn after the time for filing your tax return. Finally, excess contributions for one year may be carried forward and applied against the contribution limitation in succeeding years.

  • In the Event of Forecasted Surpluses If the HSP is forecasting a surplus, the Funder may take one or more of the following actions: adjust the amount of Funding to be paid under Schedule A, require the repayment of excess Funding; adjust the amount of any future funding installments accordingly.

  • Distribution of UDP and TCP queries DNS probes will send UDP or TCP “DNS test” approximating the distribution of these queries.

  • Carry Forward to a Subsequent Year If you do not withdraw the excess contribution, you may carry forward the contribution for a subsequent tax year. To do so, you under-contribute for that tax year and carry the excess contribution amount forward to that year on your tax return. The six percent excess contribution penalty tax will be imposed on the excess amount for each year that it remains as an excess contribution at the end of the year. You must file IRS Form 5329 along with your income tax return to report and remit any additional taxes to the IRS.

  • Monthly Progress Reports During the Construction Period, the Concessionaire shall, no later than 7 (seven) days after the close of each month, furnish to the Authority and the Independent Engineer a monthly report on progress of the Construction Works and shall promptly give such other relevant information as may be required by the Independent Engineer.

  • Available Relief for a Force Majeure Event 11.7.1 Subject to this Article 11: (a) no Party shall be in breach of its obligations pursuant to this Agreement except to the extent that the performance of its obligations was prevented, hindered or delayed due to a Force Majeure Event; (b) every Party shall be entitled to claim relief in relation to a Force Majeure Event in regard to its obligations, including but not limited to those specified under Article 4.5; (c) For avoidance of doubt, neither Party’s obligation to make payments of money due and payable prior to occurrence of Force Majeure events under this Agreement shall be suspended or excused due to the occurrence of a Force Majeure Event in respect of such Party. (d) Provided that no payments shall be made by either Party affected by a Force Majeure Event for the period of such event on account of its inability to perform its obligations due to such Force Majeure Event.

  • Clean-Up Period (a) Notwithstanding anything to the contrary set forth herein or in any other Loan Document, during the Clean-Up Period, the occurrence of any breach of a representation, covenant or an Event of Default (other than an Event of Default set out in Section 9.1(a)) will be deemed not to be a breach of a representation or warranty or a breach of a covenant or an Event of Default, as the case may be, if it would have been (if it were not for this provision) a breach of representation or warranty or a breach of a covenant or an Event of Default only by reason of circumstances relating exclusively to, with respect to any Permitted Acquisition or other Permitted Clean-Up Investment (or the subsidiaries of such target), the target of such Permitted Acquisition or Permitted Clean-Up Investment, and provided that such breach or Event of Default: (i) is capable of being remedied within the Clean-Up Period and the Loan Parties are taking appropriate steps to remedy such breach or Event of Default; (ii) does not have and is not reasonably likely to have a Material Adverse Effect; and (iii) was not procured by or approved by Holdings or the Borrowers. (b) Notwithstanding Section 9.6(a), if the relevant circumstances are continuing on or after the expiry of the Clean-Up Period, there shall be a breach of representation or warranty, breach of covenant or Event of Default, as the case may be, notwithstanding the above (and without prejudice to the rights and remedies of the Agents and the Lenders). (c) For the avoidance of doubt, if any breach of representation or warranty, breach of covenant or Event of Default shall be deemed to not exist due to Section 9.6(a) during the Clean-Up Period, then such breach of representation or warranty, breach of covenant or Event of Default shall be deemed not to exist for purposes of Section 5.2 for so long as (but in no event later than the end of the Clean-Up Period) such breach of representation or warranty, breach of covenant or Event of Default shall be deemed not to exist due to the provisions of Section 9.6(a).

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