Encounter Data File Submission Procedures Sample Clauses

Encounter Data File Submission Procedures. A certification letter shall accompany the submission of an encounter data file in the ODM-specified medium. The certification letter shall be signed by the MCP’s Chief Executive Officer (CEO), Chief Financial Officer (CFO), or an individual who has delegated authority to sign for, and who reports directly to, the MCP’s CEO or CFO. Pursuant to 42 CFR 438.606, the CEO or CFO remains responsible for certification regardless of delegated signee.
AutoNDA by SimpleDocs
Encounter Data File Submission Procedures. A certification letter must accompany the submission of an encounter data file in the ODJFS-specified medium. The certification letter must be signed by the MCP’s Chief Executive Officer (CEO), Chief Financial Officer (CFO), or an individual who has delegated authority to sign for, and who reports directly to, the MCP’s CEO or CFO. Timing of Encounter Data Submissions ODJFS recommends that MCPs submit encounters no more than thirty-five (35) days after the end of the month in which they were paid. For example, claims paid in January are due March 5. ODJFS recommends that MCPs submit files in the ODJFS-specified medium by the 5th of each month. This will help to ensure that the encounters are included in the ODJFS master file in the same month in which they were submitted.
Encounter Data File Submission Procedures. A certification letter must accompany the submission of an encounter data file in the ODJFS-specified medium. The certification letter must be signed by the MCP's Chief Executive Officer (CEO), Chief Financial Officer (CFO), or an individual who has delegated authority to sign for, and who reports directly to, the MCP's CEO or CFO. No more than two production files in the ODJFS-specified medium per format (e.g., NSF) should be submitted each month. If it is necessary for an MCP to submit more than two production files in the ODJFS-specified medium for a particular format in a month, they must request and receive permission to do so from their designated Contract Administrator. Timing of Encounter Data Submissions ODJFS recommends that MCPs submit encounters no more than thirty-five (35) days after the end of the month in which they were paid. (For example, claims paid in January are due March 5.) ODJFS recommends that MCPs submit files in the ODJFS-specified medium by the 5th of each month. This will help to ensure that the encounters are included in the ODJFS master file in the same month in which they were submitted.
Encounter Data File Submission Procedures. A certification letter must accompany the submission of an encounter data file in the ODJFS-specified medium. The certification letter must be signed by the MCP's Chief Executive Officer (CEO), Chief Financial Officer (CFO). or an individual who has delegated authority to sign for. and who reports directly to, the MCP's CEO or CFO. No more than two production files in the ODJFS-specified medium per format (e.g., NSF) should be submitted each month. If it is necessary for an MCP to submit more than two production files in the ODJFS-specified medium for a particular format in a month, they must request permission to do so through their Contract Administrator. Timing of Encounter Data Submissions ODJFS recommends that MCPs submit encounters no more than thirty-five days after the end of the month in which they were paid. For example, claims paid in January are due March 5. ODJFS recommends that MCPs submit files in the ODJFS-specified medium by the 5th of each month. This will help to ensure that the encounters are included in the ODJFS master file in the same month in which they were submitted.
Encounter Data File Submission Procedures. A certification letter must accompany the submission of an encounter data file in the ODJFS-specified medium. The certification letter must be signed by the MCP’s Chief Executive Officer (CEO), Chief Financial Officer (CFO), or an individual who has delegated authority to sign for, and who reports directly to, the MCP’s CEO or CFO. Appendix C Aged, Blind or Disabled (ABD) population Page 21 Timing of Encounter Data Submissions ODJFS recommends that MCPs submit encounters no more than thirty-five (35) days after the end of the month in which they were paid. (For example, claims paid in January are due March 5.) ODJFS recommends that MCPs submit files in the ODJFS-specified medium by the 5th of each month. This will help to ensure that the encounters are included in the ODJFS master file in the same month in which they were submitted.

Related to Encounter Data File Submission Procedures

  • Notification Procedures To address non-compliance, the receiving Competent Authority would notify the providing Competent Authority pursuant to Article 5 of the IGA. The notification procedures would differ depending upon whether the receiving Competent Authority seeks to address administrative or other minor errors or significant non-compliance.

  • Review Procedures The Parties agree to jointly conduct a review, sampling transactions of the incidents managed under this Agreement. Findings that are inconsistent with the normal or accepted way of doing business will be reconciled on a case by case basis. Any decision to further examine records will be considered on a case by case basis and appropriate follow up action agreed upon by all agencies involved. Payment for Protection Services (use if appropriate) Geographic, Statewide or Sub-Geographic (local) operating plans and procurement documents or agreement will establish billing procedures for Fee Basis Protection Services.

  • Selection Procedures In selecting the Loan Assets to be Pledged pursuant to this Agreement, no selection procedures were employed which are intended to be adverse to the interests of the Lenders.

  • Election Procedures Each holder of record of shares of Company Common Stock (“Holder”) shall have the right, subject to the limitations set forth in this Article II, to submit an election in accordance with the following procedures:

Time is Money Join Law Insider Premium to draft better contracts faster.