Use Special Submission Requirements Sample Clauses

Use Special Submission Requirements. O = Original Original Initial submission of the claim No special requirements A = Amendment Correction To correct, update, add missing data elements values of a claim previously loaded in MH DW. Example: an incorrect data mapping to an Encounter field was remediated and impacted claim lines are now resubmitted to the MHDW with an “Amendment” Record Type and the correct value. Submitted with the Original Claim Number and Suffix Nothing should be entered in Former Claim / Suffix Number fields unless the amendment is for a previously adjusted claim, in which case the amendment record would inherit the former claim number/suffix from the claim it is amending. V = Void or Back Out Void To remove a claim line that was previously loaded in MH DW. Example: A paid claim was later denied. All previously submitted claim lines would be resubmitted with a “Void” Record Type. Submitted with new Claim Number/Suffix. Claim Number/Suffix of the claim to be voided must be placed in Former Claim Number/Suffix fields R = Replacement Adjustment To replace a claim that was previously loaded in the MH DW with one that has a new claim number. Example: the provider has resubmitted a claim under a new claim number. All previously submitted claim lines must be resubmitted with the new claim number and a “Replacement” Record Type. Submitted with new Claim Number/Suffix. Claim Number/Suffix of the claim that has to be replaced must be placed in Former Claim Number/Suffix fields. All claim lines need to be replaced with the new claim number. If there are more claim lines in the replacement claim than the original, submit the additional claim as an Original. Visa versa, if there are fewer claim lines in the replacement than the original, void the extra claim lines.
AutoNDA by SimpleDocs

Related to Use Special Submission Requirements

  • Data Submission Requirements As part of its registration and sponsorship of Registered Names in the Registry TLD, Registrar shall submit to the Registry System complete data as required by technical specifications of the Registry System that are made available to Registrar from time to time. Registrar hereby grants Registry Operator a non-exclusive, royalty free, non-transferable, limited license to such data for propagation of and the provision of authorized access to the TLD zone files and as otherwise required for Registry Operator to meet its obligations to ICANN and/or for Registry Operator’s operation of the Registry TLD.

  • Submission Requirements The Contractor shall submit inventory disposal schedules to the Plant Clearance Officer no later than—

  • Admission Requirements USERs and Participants are subject to the administrative and technical supervision and control of CONTRACTOR; and will comply with all applicable rules of CONTRACTOR and DOE with regard to admission to and use of the User Facility, including safety, operating and health- physics procedures, environment protection, access to information, hours of work, and conduct. Participants shall execute any and all documents required by CONTRACTOR acknowledging and agreeing to comply with such applicable rules of CONTRACTOR. Participants will not be considered employees of CONTRACTOR for any purpose.

  • Installation requirements 7.8 We (if we install the System) or our contractor (if we procure a contractor to install the System) must:

  • Application Requirements This application shall contain, as a minimum, a sketch showing the location of proposed facilities; a description, sketch, manufacturer’s brochure, etc. of the proposed facilities; and a description of the operation proposed. (11-28-90) 101. -- 199. (RESERVED)‌ 200. OPERATIONAL AGREEMENT.‌‌

  • Construction Requirements a) All Life and Safety and applicable Building Codes will be strictly enforced (i.e., tempered glass, fire dampers, exit signs, smoke detectors, alarms, etc.). Prior coordination with the Building Manager is required.

  • Notification Requirements 1. If the Family Leave is foreseeable, the employee must provide the agency/department with thirty (30) calendar days notice of his or her intent to take Family Leave.

  • Notification Requirement Through and up to the conclusion of the Non-Competition Period, Executive shall give notice to the Company of each new business activity he plans to undertake, at least seven (7) days prior to beginning any such activity. Such notice shall state the name and address of the Person for whom such activity is undertaken and the nature of Executive’s business relationship(s) and position(s) with such Person.

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

  • Design Requirements 9.2.1. Metal liner The compressive stress in the liner at zero pressure and 15 °C shall not cause the liner to buckle or crease.

Time is Money Join Law Insider Premium to draft better contracts faster.