Encounter Data Submittal Sample Clauses

Encounter Data Submittal. A. Contractor shall implement policies and procedures for ensuring the complete, accurate, and timely submission of Encounter Data for all services for which Contractor has incurred any financial liability, whether directly or through Subcontracts or other arrangements. B. Contractor shall require subcontractors and non-contracting providers to provide encounter data to Contractor, which allows the Contractor to meet its administrative functions and the requirements set forth in this section. Contractor shall have in place mechanisms, including edits and reporting systems sufficient to assure encounter data is complete and accurate prior to submission to DHCS. C. Contractor shall submit complete, timely, reasonable, and accurate Encounter Data within six (6) business days of the end of each month following the month of payment, under this contract or as otherwise agreed upon by DHCS and in the format specified by DHCS.‌‌‌‌‌ D. DHCS will measure the quality of the Encounter Data for completeness, timeliness, reasonability, and accuracy. E. If DHCS find deficiencies regarding Encounter Data or the quality of Encounter Data, DHCS may notify Contractor in writing of the deficiency and request correction and resubmission of the relevant Encounter Data. Contractor shall ensure that corrected Encounter Data is resubmitted within 15 calendar days of the date of DHCS' notice. Upon Contractor's written request, DHCS may grant an extension for submission of corrected Encounter Data.
AutoNDA by SimpleDocs
Encounter Data Submittal. Contractor shall implement policies and procedures for ensuring the complete, accurate, and timely submission of Encounter level data for all services which Contractor incurred any financial liability whether directly or through Subcontracts or other arrangements. Contractor shall submit Encounter-level data to DHS and to LHD on a monthly basis, no later than 90 calendar days following the end of the reporting month in which the Encounter occurred in the form and manner specified in the DHS’ most recent Managed Care Data Element Dictionary, hereby incorporated by reference. Encounter-level data shall include data elements as specified in DHS’ most recent Managed Care Data Manual Element Dictionary. .1 MIS/Data Correspondence Upon written notice by DHS of any problems related to the submittal of data to DHS as required under this Contract, or upon written notice by DHS of concerns regarding any other changes or clarifications made by Contractor to its MIS system, Contractor shall submit Corrective Actions with measurable benchmarks within five working days from the date of DHS’ facsimile notice to Contractor. Within 30 days of DHS’ receipt of Contractor’s Corrective Action plan, DHS shall approve the Corrective Action plan or request revisions. Within 15 days after receipt of a request for revisions to the Corrective Action plan, Contractor shall submit a revised Corrective Action plan for DHS approval. .2 Timely, Complete and Accurate Data Submission Contractor shall ensure that the Encounter-level data submitted to DHS are timely, complete and accurate and in compliance with the requirements of DHS’ most recent Managed Care Data Element Dictionary. Upon written notice by DHS that Encounter data is insufficient or inaccurate, Contractor shall ensure that corrected data is submitted within 15 calendar days.
Encounter Data Submittal. Contractor shall implement policies and procedures for ensuring the complete, accurate, and timely submission of Encounter-level data for all services for which Contractor has incurred any financial liability, whether directly or through Subcontracts or other arrangements. As a condition of payment, Contractor may require subcontractors and out-of-plan providers to provide Encounter-level data to Contractor that meets the same standards required for Contractor to comply with this section. Contractor shall submit Encounter-level data to DHS on a monthly basis, no later than ninety (90) days following the end of the reporting month in which the Encounter occurred, in the form and manner specified in DHS' most recent Managed Care Data Element Dictionary. Encounter-level data received and processed by Contractor too late to be submitted timely, shall be submitted to DHS with the next monthly submission. Encounter-level data shall include data elements specified in DHS' most recent Managed Care Data Element Dictionary. XXXXXX MEDICAL CENTERS, INC. 95-23637-A03
Encounter Data Submittal. Contractor shall implement policies and procedures for ensuring the complete, accurate, and timely submission of encounter data for all services for which Contractor has incurred any financial liability, whether directly or through Subcontracts or other arrangements. Encounter data shall include data elements specified in CDHS’ most recent Managed Care Data Element Dictionary and all existing Policy Letters related to encounter data reporting. Contractor shall require subcontractors and non-contracting providers to provide encounter data to Contractor, which allows the Contractor to meet their administrative functions and the requirements set forth in this section. Contractor shall have in place mechanisms, including edits and reporting systems sufficient to assure encounter data is complete and accurate prior to submission to CDHS. Contractor shall submit encounter data to CDHS on a monthly basis in the form and manner specified in CDHS’ most recent Managed Care Data Element Dictionary and all existing Policy Letters related to encounter data reporting. Upon written notice by CDHS that the encounter data is insufficient or inaccurate, Contractor shall ensure that corrected data is resubmitted within 15 calendar days of receipt of CDHS’ notice. Upon Contractor’s written request, CDHS may provide a written extension for submission of corrected encounter data.
Encounter Data Submittal. The Contractor will submit Encounter data to DHS on a monthly basis 90 days following the end of the reporting month in which the Encounter occurred as specified in the Managed Care Encounter Data Reporting Manual. Encounter data will include the data elements as outlined in Attachment 9.4-B, Managed Care Encounter Data Reporting Elements of the RFA.

Related to Encounter Data Submittal

  • Invoice Submission All invoices submitted by Contractor shall include the City Contract Number, an assigned Invoice Number, and an Invoice Date. Contractor shall be provided with a cover sheet for invoicing. This cover sheet must be filled out correctly and submitted with each invoice. Contractor shall submit the original invoice through the responsible City Project Manager at: City of Ocala Engineer’s Office, Attn: Xxxx Xxxxxxxxx, 0000 XX 00xx Xxxxxx, Xxxxxxxx 000, Xxxxx, Xxxxxxx 00000, E-Mail: xxxxxxxxxx@xxxxxxx.xxx.

  • Submittals Submittals required by the Contract Documents shall be prepared specifically for the Work by the Contractor to illustrate some portion of the Work. Submittals are not Contract Documents.

  • Data Subject Requests To the extent legally permitted, Okta shall promptly notify Customer if Okta receives a request from a Data Subject to exercise the Data Subject's right of access, right to rectification, restriction of Processing, erasure (“right to be forgotten”), data portability, object to the Processing, or its right not to be subject to an automated individual decision making (“Data Subject Request”). Factoring into account the nature of the Processing, Okta shall assist Customer by appropriate organizational and technical measures, insofar as this is possible, for the fulfilment of Customer’s obligation to respond to a Data Subject Request under Data Protection Laws and Regulations. In addition, to the extent Customer, in its use of the Service, does not have the ability to address a Data Subject Request, Okta shall, upon Customer’s request, provide commercially- reasonable efforts to assist Customer in responding to such Data Subject Request, to the extent that Okta is legally authorized to do so, and the response to such Data Subject Request is required under Data Protection Laws and Regulations. To the extent legally permitted, Customer shall be responsible for any costs arising from Okta’s provision of such assistance.

  • DATA REQUESTS Upon the written request of the District, the State Auditor’s Office, the Appraisal District, or the Comptroller during the term of this Agreement, the Applicant, the District or any other entity on behalf of the District shall provide the requesting party with all information reasonably necessary for the requesting party to determine whether the Applicant is in compliance with its rights, obligations or responsibilities, including, but not limited to, any employment obligations which may arise under this Agreement.

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