Encounter Data Reporting Requirements Sample Clauses

Encounter Data Reporting Requirements. All Providers of A&D 83 Services funded through this Agreement must submit Individual-level, Service delivery activity (encounter data) within 30 calendar days following the end of each month. Encounter data must be submitted electronically utilizing the HIPAA approved “837” format. Prior to submitting data, each encounter claim, must be documented in the clinical record and must include the date of the encounter Service, type of Service delivered, time of Service, length of Service, setting of Service, personnel rendering Service (including their name, credentials and signature), and a clinical note including a description of the session.
AutoNDA by SimpleDocs
Encounter Data Reporting Requirements. All Providers of A&D 83 Services funded through this Agreement must submit Individual-level, Service delivery activity (encounter data) within 30 calendar days following the end of each month. Encounter data must be submitted electronically utilizing the HIPAA approved “837” format. Files to be transferred over non-secure web or Internet must be encrypted utilizing an encryption format approved by OHA. The subject line for each electronic transmission of data must include the program name, the month covered by the submission (i.e. August 2020), and the words “Gambling Encounter Data.” Counties with secure web services may post the data to their server, using the same naming convention described above, provided that OHA has access and receives timely notification. Prior to submitting data, each encounter claim, must be documented in the clinical record and must include the date of the encounter Service, type of Service rendered, time of Service, length of Service, setting of Service, personnel rendering Services (including their name, credentials and signature), and a clinical note that includes a description of the session.
Encounter Data Reporting Requirements. All Providers of A&D 82 Services funded through this Agreement must submit Individual-level, Service delivery activity (encounter data) within 30 calendar days following the end of each month. Encounter data must be submitted electronically utilizing the HIPAA approved “837” format. Files transferred over non-secure web or Internet must be encrypted utilizing an encryption format approved by OHA. The subject line for each electronic transmission of data must include the program name, the month covered by the submission (i.e. August 2020) and the words “Gambling Encounter Data.” Counties with secure web services may post the data to their server, using the same naming convention described above, provided that OHA has access and receives timely notification. Prior to submitting data, each encounter claim must be documented in the clinical record and must include the date of the encounter Service, type of Service rendered, time of Service, length of Service, setting of Service, personnel rendering Service (including their name, credentials and signature), and a clinical note that includes a description of the session. Providers are expected to reconcile encounter data reports and correct any errors within 30 calendar days of receipt of encounter data report from OHA’s management information system provider. Discrepancies must include apparent cause and remedy. Adjustments will be carried forward to the next month within the effective period of this Agreement.
Encounter Data Reporting Requirements. In order to efficiently implement the disbursement of financial assistance, it is necessary for all Providers of A&D 81 Services funded through this Agreement to submit individual-level service delivery activity (encounter data) within 45 days following the end of each month. Data shall be electronically submitted utilizing the HIPAA approved “837” format. Files to be transferred over non-secure web or internet facilities must be encrypted utilizing an encryption format approved by OHA. The subject line for each electronic transmission of data must include the program name, the month covered by the submission (e.g. August 2015) and the words “Gambling Encounter Data.” Counties with secure web services may post the data to their server as long as access and timely notification is provided to OHA. Prior to submitting an encounter claim, each claimed encounter must be documented in the clinical record. Encounter claim documentation placed in the clinical record must include the date of the encounter Service, the type of Service delivered, the length of Service, and a clinical note describing data from the session, the clinician’s signature and date the note was completed.
Encounter Data Reporting Requirements. All Providers of A&D 81 Services funded through this Agreement must submit Individual-level, Service delivery activity (encounter data) within 45 calendar days following the end of each month. Encounter data must be submitted electronically utilizing the HIPAA approved “837” format. Files transferred over non-secure web or Internet must be encrypted utilizing an encryption format approved by OHA. The subject line for each electronic transmission of data must include the program name, the month covered by the submission (e.g. August 2020), and the words “Gambling Encounter Data.” Counties with secure web services may post the data to their server, using the same naming convention described above, provided that OHA has access and receives timely notification. Prior to submitting data, each encounter claim must be documented in the clinical record and must include the date of the encounter Service, type of Service delivered, length of Service, and a clinical note that includes a description of the session, the clinician’s signature, and date the clinical note was completed.
Encounter Data Reporting Requirements. All HMOs that contract with the Department to provide Medicaid services must submit monthly encounter data files according to the specifications and submission protocols published in the Wisconsin Medicaid HMO Encounter Data User Manual. HMO Contract for February 1, 2006 - December 31, 2007

Related to Encounter Data Reporting Requirements

  • Meteorological Data Reporting Requirement (Applicable to wind generation facilities only)

  • Child Abuse Reporting Requirements A. Grantees shall comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • Data Requirements ‌ • The data referred to in this document are encounter data – a record of health care services, health conditions and products delivered for Massachusetts Medicaid managed care beneficiaries. An encounter is defined as a visit with a unique set of services/procedures performed for an eligible recipient. Each service should be documented on a separate encounter claim detail line completed with all the data elements including date of service, revenue and/or procedure code and/or NDC number, units, and MCE payments/cost of care for a service or product. • All encounter claim information must be for the member identified on the claim by Medicaid ID. Claims must not be submitted with another member’s identification (e.g., xxxxxxx claims must not be submitted under the Mom’s ID). • All claims should reflect the final status of the claim on the date it is pulled from the MCE’s Data Warehouse. • For MassHealth, only the latest version of the claim line submitted to MassHealth is “active”. Previously submitted versions of claim lines get offset (no longer “active” with MassHealth) and payments are not netted. • An encounter is a fully adjudicated service (with all associated claim lines) where the MCE incurred the cost either through direct payment or sub-contracted payment. Generally, at least one line would be adjudicated as “paid”. All adjudicated claims must have a complete set of billing codes. There may also be fully adjudicated claims where the MCE did not incur a cost but would otherwise like to inform MassHealth of covered services provided to Enrollees/Members, such as for quality measure reporting (e.g., CPT category 2 codes for A1c lab tests and care/patient management). • All claim lines should be submitted for each Paid claim, including zero paid claim lines (e.g., bundled services paid at an encounter level and patient copays that exceeded the fee schedule). Denied lines should not be included in the Paid submission. Submit one encounter record/claim line for each service performed (i.e., if a claim consisted of five services or products, each service should have a separate encounter record). Pursuant to contract, an encounter record must be submitted for all covered services provided to all enrollees. Payment amounts must be greater than or equal to zero. There should not be negative payments, including on voided claim lines. • Records/services of the same encounter claim must be submitted with same claim number. There should not be more than one active claim number for the same encounter. All paid claim lines within an encounter must share the same active claim number. If there is a replacement claim with a new version of the claim number, all former claim lines must be replaced by the new claim number or be voided. The claim number, which creates the encounter, and all replacement encounters must retain the same billing provider ID or be completely voided. • Plans are expected to use current MassHealth MCE enrollment assignments to attribute Members to the MassHealth assigned MCE. The integrity of the family of claims should be maintained when submitting claims for multiple MCEs (ACOs/MCO). Entity PIDSL, New Member ID, and the claim number should be consistent across all lines of the same claim. • Data should conform to the Record Layout specified in Section 3.0 of this document. Any deviations from this format will result in claim line or file rejections. Each row in a submitted file should have a unique Claim Number + Suffix combination. • A feed should consist of new (Original) claims, Amendments, Replacements (a.k.a. Adjustments) and/or Voids. The replacements and voids should have a former claim number and former suffix to associate them with the claim + suffix they are voiding or replacing. See Section 2.0, Data Element Clarifications, for more information. • While processing a submission, MassHealth scans the files for the errors. Rejected records are sent back to the MCEs in error reports in a format of the input files with two additional columns to indicate an error code and the field with the error. • Unless otherwise directed or allowed by XxxxXxxxxx, all routine monthly encounter submissions must be successfully loaded to the MH DW on or before the last day of each month with corrected rejections successfully loaded within 5 business days of the subsequent month for that routine monthly encounter submission to be considered timely and included in downstream MassHealth processes. Routine monthly encounter submissions should contain claims with paid/transaction dates through the end of the previous month.

  • Reporting Requirements The Company, during the period when the Prospectus is required to be delivered under the 1933 Act or the 1934 Act, will file all documents required to be filed with the Commission pursuant to the 1934 Act within the time periods required by the 1934 Act and the 1934 Act Regulations.

  • Child Abuse Reporting Requirement Grantee will: a. comply with child abuse and neglect reporting requirements in Texas Family Code Chapter 261. This section is in addition to and does not supersede any other legal obligation of the Grantee to report child abuse. b. develop, implement and enforce a written policy that includes at a minimum the System Agency’s Child Abuse Screening, Documenting, and Reporting Policy for Grantees/Providers and train all staff on reporting requirements. c. use the System Agency Child Abuse Reporting Form located at xxxxx://xxx.xxxx.xxxxx.xx.xx/Contact Us/report abuse.asp as required by the System Agency. d. retain reporting documentation on site and make it available for inspection by the System Agency.

  • Additional Reporting Requirements Contractor agrees to submit written quarterly reports to H-GAC detailing all transactions during the previous three (3) month period. Reports must include, but are not limited, to the following information: a. Customer Name b. Product/Service purchased, including Product Code if applicable c. Customer Purchase Order Number

  • DATA REPORTING a) CONTRACTOR shall agree to provide all data related to student information and billing information with XXX. CONTRACTOR shall agree to provide all data related to any and all sections of this contract and requested by and in the format require by the LEA. CONTRACTOR shall provide the LEA with invoices, attendance reports and progress reports for LEA students enrolled in CONTRACTOR’s NPS/A. b) Using forms developed by the CDE or as otherwise mutually agreed upon by CONTRACTOR and XXX, CONTRACTOR shall provide LEA, on a monthly basis, a written report of all incidents in which a statutory offense is committed by any LEA student, regardless if it results in a disciplinary action of suspension or expulsion. This includes all statutory offenses as described in Education Code sections 48900 and 48915. CONTRACTOR shall also include, in this monthly report, incidents resulting in the use of a behavioral restraint and/or seclusion even if they were not a result of a violation of Education Code sections 48900 and 48915. c) The LEA shall provide the CONTRACTORS with approved forms and/or format for such data including but not limited to invoicing, attendance reports and progress reports. The LEA may approve use of CONTRACTORS-provided forms at their discretion.

  • Reporting Requirement (1) In the event the Contractor identifies covered telecommunications equipment or services used as a substantial or essential component of any system, or as critical technology as part of any system, during contract performance, or the Contractor is notified of such by a subcontractor at any tier or by any other source, the Contractor shall report the information in paragraph (d)(2) of this clause to the Contracting Officer, unless elsewhere in this contract are established procedures for reporting the information; in the case of the Department of Defense, the Contractor shall report to the website at xxxxx://xxxxxx.xxx.xxx. For indefinite delivery contracts, the Contractor shall report to the Contracting Officer for the indefinite delivery contract and the Contracting Officer(s) for any affected order or, in the case of the Department of Defense, identify both the indefinite delivery contract and any affected orders in the report provided at xxxxx://xxxxxx.xxx.xxx. (2) The Contractor shall report the following information pursuant to paragraph (d)(1) of this clause (i) Within one business day from the date of such identification or notification: the contract number; the order number(s), if applicable; supplier name; supplier unique entity identifier (if known); supplier Commercial and Government Entity (CAGE) code (if known); brand; model number (original equipment manufacturer number, manufacturer part number, or wholesaler number); item description; and any readily available information about mitigation actions undertaken or recommended. (ii) Within 10 business days of submitting the information in paragraph (d)(2)(i) of this clause: any further available information about mitigation actions undertaken or recommended. In addition, the Contractor shall describe the efforts it undertook to prevent use or submission of covered telecommunications equipment or services, and any additional efforts that will be incorporated to prevent future use or submission of covered telecommunications equipment or services.

  • General Reporting Requirements The MA-PD Sponsor agrees to submit to information to CMS according to 42 CFR §§423.505(f), 423.514, and the “Final Medicare Part D Reporting Requirements,” a document issued by CMS and subject to modification each program year.

  • Financial Reporting Requirements The Charter School shall follow the financial requirements of the Charter Schools Section of the Department’s Financial Management for Georgia Local Units of Administration Manual. The Charter School shall submit all information required by the State Accounting Office for inclusion in the State of Georgia Comprehensive Annual Financial Report.

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