Encounter Data Submission Requirements Sample Clauses

Encounter Data Submission Requirements i. The MCOP shall collect data on services furnished to members through a claims system and shall report encounter data electronically to ODM as specified in Appendix L.
AutoNDA by SimpleDocs
Encounter Data Submission Requirements. 4.16.3.1 The Georgia Families program utilizes encounter data to determine the adequacy of medical services and to evaluate the quality of care rendered to members. DCH will use the following requirements to establish the standards for the submission of data and to measure the compliance of the Contractor to provide timely and accurate information. Encounter data from the Contractor also allows DCH to budget available resources, set contractor capitation rates, monitor utilization, follow public health trends and detect potential fraud. Most importantly, it allows the Division of Managed Care and Quality to make recommendations that can lead to the improvement of healthcare outcomes.
Encounter Data Submission Requirements. General Requirements Each MCP must collect data on services furnished to members through an encounter data system and must report encounter data to the ODJFS. MCPs are required to submit this data electronically to ODJFS on a monthly basis in the following standard formats: · Institutional Claims - UB92 flat file · Noninstitutional Claims - National standard format · Prescription Drug Claims - NCPDP ODJFS relies heavily on encounter data for monitoring MCP performance. The ODJFS uses encounter data to measure clinical performance, conduct access and utilization reviews, reimburse MCPs for newborn deliveries and aid in setting MCP capitation rates. For these reasons, it is important that encounter data is timely, accurate, and complete. Data quality, performance measures and standards are described in the Agreement. An encounter represents all of the services, including medical supplies and medications, provided to a member of the MCP by a particular provider, regardless of the payment arrangement between the MCP and the provider. For example, if a member had an emergency department visit and was examined by a physician, this would constitute two encounters, one related to the hospital provider and one related to the physician provider. However, for the purposes of calculating a utilization measure, this would be counted as a single emergency department visit. If a member visits their PCP and the PCP examines the member and has laboratory procedures done within the office, then this is one encounter between the member and their PCP. If the PCP sends the member to a lab to have procedures performed, then this is two encounters; one with the PCP and another with the lab. For pharmacy encounters, each prescription filled is a separate encounter. Appendix C Covered Families and Children (CFC) population Encounters include services paid for retrospectively through fee-for-service payment arrangements, and prospectively through capitated arrangements. Only encounters with services (line items) that are paid by the MCP, fully or in part, and for which no further payment is anticipated, are acceptable encounter data submissions, except for immunization services. Immunization services submitted to the MCP must be submitted to ODJFS if these services were paid for by another entity (e.g., free vaccine program). All other services that are unpaid or paid in part and for which the MCP anticipates further payment (e.g., unpaid services rendered during a delivery of a ne...
Encounter Data Submission Requirements 

Related to Encounter Data Submission Requirements

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

  • Information Requirements (a) The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder of Registrable Securities and take such further reasonable action as any Holder of Registrable Securities may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder of Registrable Securities, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company's most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

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

  • Compliance with Information Requests Notwithstanding any other provision of the Deposit Agreement or any ADR(s), each Holder and Beneficial Owner agrees to comply with requests from the Company pursuant to applicable law, the rules and requirements of any stock exchange on which the Shares or ADSs are, or will be, registered, traded or listed or the Articles of Association of the Company, which are made to provide information, inter alia, as to the capacity in which such Holder or Beneficial Owner owns ADSs (and Shares as the case may be) and regarding the identity of any other person(s) interested in such ADSs and the nature of such interest and various other matters, whether or not they are Holders and/or Beneficial Owners at the time of such request. The Depositary agrees to use its reasonable efforts to forward, upon the request of the Company and at the Company’s expense, any such request from the Company to the Holders and to forward to the Company any such responses to such requests received by the Depositary.

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