Reporting Format and Batch Submission Schedule Sample Clauses

Reporting Format and Batch Submission Schedule. The Contractor shall submit institutional, pharmacy, dental, vision, transportation and other professional encounter claims in an electronic format that adheres to the data specifications in the Companion Guides and any other state or federally mandated electronic claims submission standards, or be subject to liquidated damages. A diagnosis code and DRG, as applicable, is a required data field and must be included on all encounter claims. The Contractor’s encounter claims must include the National Drug Codes (NDCs) when an encounter involves products or services with NDCs, including medical and institutional claims where medications with NDCs are included and billed separately. An indication of claim payment status and an identification of claim type (i.e., original, void or replacement) is also required, in the form designated by FSSA. The Contractor shall submit via secure FTP at least one batch of encounter data for paid and denied institutional, pharmacy and professional claims before 5 p.m. Eastern on Wednesday each week, or other date and time as specified by the State. OMPP will use an overall average of calendar month submissions to assess compliance with this encounter claim submission requirement. The State shall require the Contractor to submit a corrective action plan and shall assess liquidated damages for failure to comply with the encounter claims submission requirements. See Exhibit 3 for a schedule of liquidated damages OMPP shall assess for non-compliance with this requirement. Only data and information accepted by the data warehouse by June 30 shall be considered for the next year’s capitation rate adjustments.
Sample 1
AutoNDA by SimpleDocs

Related to Reporting Format and Batch Submission Schedule

  • Implementation Schedule TIME IS OF THE ESSENCE with regard to all dates and time periods set forth and/or incorporated herein. Any material modification or deviation from an approved schedule described in this Agreement shall occur only upon approval of the City and RDA, with any such approvals required to be in writing as an amendment to this Agreement, and which approvals shall not be unreasonably withheld. City shall cooperate and act promptly with respect to any and all permits or approvals necessary for completion of the Project. Notwithstanding the above, this Agreement shall not limit the discretion of the City, or any of its duly appointed and authorized governing bodies, boards or entities, in approving or rejecting any aspect of the Project or improvements contemplated on or about the Property.

  • Escrow Format Specification 3.1. Deposit’s Format. Registry objects, such as domains, contacts, name servers, registrars, etc. will be compiled into a file constructed as described in draft-xxxxx-xxxxxxx-registry-data-escrow, see Part A, Section 9, reference 1 of this Specification and draft-xxxxx-xxxxxxx-dnrd-objects-mapping, see Part A, Section 9, reference 2 of this Specification (collectively, the “DNDE Specification”). The DNDE Specification describes some elements as optional; Registry Operator will include those elements in the Deposits if they are available. If not already an RFC, Registry Operator will use the most recent draft version of the DNDE Specification available at the Effective Date. Registry Operator may at its election use newer versions of the DNDE Specification after the Effective Date. Once the DNDE Specification is published as an RFC, Registry Operator will implement that version of the DNDE Specification, no later than one hundred eighty (180) calendar days after. UTF-8 character encoding will be used.

  • Evaluation Schedule CLIENT REFERENCES The Tenderer shall provide details of his performance on each of the previous projects listed in the “Relevant Experience” returnable schedule. “Client Reference Scorecards” will be completed by each of the respective Clients for the projects listed in the “Relevant Experience” returnable schedule. The following are to be completed by the Client and Principal Agent and is to be supported in each case by a letter of award and the works completion certificate. Both Client and Principal Agent must sign and stamp the documents, failure to obtain both signatures and stamps will result in no allocation of points. PROJECT NAME and SCOPE OF WORK: Principal agent: ................................................................................................................................. Client: .. ..............................................................................................................................................

  • Billing Specifications 55.6.1 The Parties agree that billing requirements and outputs will be consistent with the Ordering & Billing Form (OBF) and also with Telcordia Technologies Billing Output Specifications (BOS).

  • EODUF Packing Specifications 7.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • ODUF Packing Specifications 6.3.1 The data will be packed using ATIS EMI records. A pack will contain a minimum of one (1) message record or a maximum of ninety-nine thousand nine hundred and ninety-nine (99,999) message records plus a pack header record and a pack trailer record. One transmission can contain a maximum of ninety-nine (99) packs and a minimum of one (1) pack.

  • TIMELINESS OF BILLING SUBMISSION The parties agree that timeliness of billing is of the essence to this Contract and recognize that the City is on a fiscal year. All xxxxxxxx for dates of service prior to July 1 must be submitted to the City no later that the first Friday in August of the same year.

  • Project Plan Development of Project Plan Upon the Authorized User’s request, the Contractor must develop a Project Plan. This Project Plan may include Implementation personnel, installation timeframes, escalation procedures and an acceptance plan as appropriate for the Services requested. Specific requirements of the plan will be defined in the RFQ. In response to the RFQ, the Contractor must agree to furnish all labor and supervision necessary to successfully perform Services procured from this Lot. Project Plan Document The Contractor will provide to the Authorized User, a Project Plan that may contain the following items: • Name of the Project Manager, Contact Phone Numbers and E-Mail Address; • Names of the Project Team Members, Contact Phone Numbers and E-Mail Address; • A list of Implementation milestones based on the Authorized User’s desired installation date; • A list of responsibilities of the Authorized User during system Implementation; • A list of designated Contractor Authorized Personnel; • Escalation procedures including management personnel contact numbers; • Full and complete documentation of all Implementation work; • Samples of knowledge transfer documentation; and • When applicable, a list of all materials and supplies required to complete the Implementation described in the RFQ. Materials and Supplies Required to Complete Implementation In the event that there are items required to complete an Implementation, the Contractor may request the items be added to its Contract if the items meet the scope of the Contract. Negotiation of Final Project Plan If the Authorized User chooses to require a full Project Plan, the State further reserves the right for Authorized Users to negotiate the final Project Plan with the apparent RFQ awardee. Such negotiation must not substantively change the scope of the RFQ plan, but can alter timeframes or other incidental factors of the final Project Plan. The Authorized User will provide the Contractor a minimum of five (5) business days’ notice of the final negotiation date. The Authorized User reserves the right to move to the next responsible and responsive bidder if Contractor negotiations are unsuccessful.

  • Updated Information Submission by Interconnection Customer The updated information submission by the Interconnection Customer, including manufacturer information, shall occur no later than one hundred eighty (180) Calendar Days prior to the Trial Operation. The Interconnection Customer shall submit a completed copy of the Electric Generating Unit data requirements contained in Appendix 1 to the LGIP. It shall also include any additional information provided to the Participating TO and the CAISO for the Interconnection Studies. Information in this submission shall be the most current Electric Generating Unit design or expected performance data. Information submitted for stability models shall be compatible with the Participating TO and CAISO standard models. If there is no compatible model, the Interconnection Customer will work with a consultant mutually agreed to by the Parties to develop and supply a standard model and associated information. If the Interconnection Customer's data is materially different from what was originally provided to the Participating TO and the CAISO for the Interconnection Studies, then the Participating TO and the CAISO will conduct appropriate studies pursuant to the LGIP to determine the impact on the Participating TO’s Transmission System and affected portions of the CAISO Controlled Grid based on the actual data submitted pursuant to this Article 24.3. The Interconnection Customer shall not begin Trial Operation until such studies are completed and all other requirements of this LGIA are satisfied.

  • Statement of Work The Contractor shall provide the services and staff, and otherwise do all things necessary for or incidental to the performance of work, as set forth below:

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