Encounter Data Submission and Processing Sample Clauses

Encounter Data Submission and Processing. (1) Contractor shall submit valid Encounter Data at least once per calendar month, on forms or formats specified by OHA and in accordance with OAR 410-141-3430 and OAR 943- 120-0100 through 943-120-0200. The Encounter Data submitted must represent 50 percent of all Encounter claim types received and adjudicated by Contractor during that calendar month, including the paid amounts regardless of whether the Provider is paid on a fee-for-service or capitated basis, or whether the Provider is in network (participating) or out of network (non-participating). (2) Contractor shall correct errors in Encounter Data if the Encounter Data cannot be processed because of missing or erroneous information. Corrective Action may be initiated if more than 10% of any Encounter Data submission cannot be processed because of missing or erroneous information. (3) To prevent Corrective Action, Contractor may submit documentation to OHA citing specific circumstances that delay Contractor’s timely submittal of Valid Encounter Data. OHA will review the documentation and make a determination within 30 days on whether the circumstances cited are Acceptable. These “Acceptable” circumstances may include, but are not limited to:
AutoNDA by SimpleDocs
Encounter Data Submission and Processing a. (1) Contractor shall submit Valid Encounter Data at least once per calendar month, including Encounter Pharmacy Data, in accordance with the AP Standard not later than the last day of the Final Submission Month. (2) Contractor shall submit valid Encounter Data on forms or formats specified by OHA and in accordance with OAR 410-141-3430 and OAR 943-120-0100 through 943-120-0200. (3) The Encounter Data submitted must represent no less than 50 percent of all Encounter claim types received and adjudicated by Contractor during that calendar month, including the paid amounts regardless of whether the Provider is paid on a fee-for-service or capitated basis, or whether the Provider is in network (participating) or out of network (non-participating). (4) Contractor shall correct errors in Encounter Data if the Encounter Data cannot be processed because of missing or erroneous information. Corrective Action will be initiated if more than 5% of any Encounter Data submission cannot be processed because of missing or erroneous information. (5) For purposes of this section, the AP Standard allows for Contractor delay of no more than 5% of non-pharmacy encounter claims for the Subject Month with prior notification to OHA. Contractor may submit documentation to OHA citing specific circumstances that will result in a delay to Contractor’s timely submittal of Valid Encounter Data. (6) If Contractor submits documentation of a delay in encounter claims submission, OHA will review the documentation and make a determination within 30 days on whether the circumstances cited are Acceptable and that a Corrective Action Plan is not necessary to remedy the deficiency. g. (7) These “Acceptable” circumstances may include, but are not limited to: (a) Member's failure to give the Provider necessary claim information;

Related to Encounter Data Submission and Processing

  • Encounter Data Party shall provide encounter data to the Agency of Human Services and/or its departments and ensure further that the data and services provided can be linked to and supported by enrollee eligibility files maintained by the State.

  • 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: Xxxxx Xxxxxxxxxx, 0000 XX 00xx Xxxxxx, Xxxxxxxx 000, Xxxxx, Xxxxxxx 00000, E-Mail: xxxxxxxxxxx@xxxxxxx.xxx.

  • Proposed Policies and Procedures Regarding New Online Content and Functionality By October 31, 2017, the School will submit to OCR for its review and approval proposed policies and procedures (“the Plan for New Content”) to ensure that all new, newly-added, or modified online content and functionality will be accessible to people with disabilities as measured by conformance to the Benchmarks for Measuring Accessibility set forth above, except where doing so would impose a fundamental alteration or undue burden. a) When fundamental alteration or undue burden defenses apply, the Plan for New Content will require the School to provide equally effective alternative access. The Plan for New Content will require the School, in providing equally effective alternate access, to take any actions that do not result in a fundamental alteration or undue financial and administrative burdens, but nevertheless ensure that, to the maximum extent possible, individuals with disabilities receive the same benefits or services as their nondisabled peers. To provide equally effective alternate access, alternates are not required to produce the identical result or level of achievement for persons with and without disabilities, but must afford persons with disabilities equal opportunity to obtain the same result, to gain the same benefit, or to reach the same level of achievement, in the most integrated setting appropriate to the person’s needs. b) The Plan for New Content must include sufficient quality assurance procedures, backed by adequate personnel and financial resources, for full implementation. This provision also applies to the School’s online content and functionality developed by, maintained by, or offered through a third-party vendor or by using open sources. c) Within thirty (30) days of receiving OCR’s approval of the Plan for New Content, the School will officially adopt, and fully implement the amended policies and procedures.

  • Details of Data Processing (a) Subject matter: The subject matter of the data processing under this DPA is the Customer Data.

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

  • Ordering Guidelines and Processes 1.13.1 For information regarding Ordering Guidelines and Processes for various Network Elements, Combinations and Other Services, PLI should refer to the “Guides” section of the BellSouth Interconnection Web site, which is incorporated herein by reference, as amended from time to time. The Web site address is: http//xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/. 1.13.2 Additional information may also be found in the individual CLEC Information Packages, which are incorporated herein by reference, as amended from time to time, located at the “CLEC UNE Products” Web site address: xxxx://xxx.xxxxxxxxxxxxxxx.xxxxxxxxx.xxx/guides/html/unes.html. 1.13.3 The provisioning of Network Elements, Combinations and Other Services to PLI’s Collocation Space will require cross-connections within the central office to connect the Network Element, Combinations or Other Services to the demarcation point associated with PLI’s Collocation Space. These cross-connects are separate components that are not considered a part of the Network Element, Combinations or Other Services and, thus, have a separate charge pursuant to this Agreement.

  • Problem Statement School bus fleets are aging, and our communities have poor air quality. Replacing school buses with zero emission school buses will address both of these issues.

  • Errors, Questions, and Complaints a. In case of errors or questions about your transactions, you should as soon as possible contact us as set forth in Section 6 of the General Terms above. b. If you think your periodic statement for your account is incorrect or you need more information about a transaction listed in the periodic statement for your account, we must hear from you no later than sixty (60) days after we send you the applicable periodic statement for your account that identifies the error. You must: 1. Tell us your name; 2. Describe the error or the transaction in question, and explain as clearly as possible why you believe it is an error or why you need more information; and, 3. Tell us the dollar amount of the suspected error. c. If you tell us orally, we may require that you send your complaint in writing within ten (10) Business Days after your oral notification. Except as described below, we will determine whether an error occurred within ten (10) Business Days after you notify us of the error. We will tell you the results of our investigation within three (3) Business Days after we complete our investigation of the error, and will correct any error promptly. However, if we require more time to confirm the nature of your complaint or question, we reserve the right to take up to forty-five (45) days to complete our investigation. If we decide to do this, we will provisionally credit your Eligible Transaction Account within ten (10) Business Days for the amount you think is in error. If we ask you to submit your complaint or question in writing and we do not receive it within ten (10) Business Days, we may not provisionally credit your Eligible Transaction Account. If it is determined there was no error we will mail you a written explanation within three (3) Business Days after completion of our investigation. You may ask for copies of documents used in our investigation. We may revoke any provisional credit provided to you if we find an error did not occur.

  • Claims Submission Unless otherwise prohibited by federal or state law, Provider will submit Clean Claims for all Covered Services to BCBSM within one hundred eighty (180) days of the date of service.

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

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