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 82 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 with the clinician’s signature and date the note was completed.
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 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 (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 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

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

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

  • Compliance with Reporting Requirements The Company is subject to and in full compliance with the reporting requirements of Section 13 or Section 15(d) of the Exchange Act.

  • Filing Requirements Escrow securities will not be released under this Part until the Issuer does the following:

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