MEDICAL BILLING, CODING, AND DOCUMENTATION COMPLIANCE STANDARDS Sample Clauses

MEDICAL BILLING, CODING, AND DOCUMENTATION COMPLIANCE STANDARDS. 29 1. CONTRACTOR shall take reasonable precaution to ensure that the coding of health care 30 claims, xxxxxxxx and/or invoices for same are prepared and submitted in an accurate and timely manner 31 and are consistent with federal, state and county laws and regulations.
AutoNDA by SimpleDocs

Related to MEDICAL BILLING, CODING, AND DOCUMENTATION COMPLIANCE STANDARDS

  • Monitoring and Compliance Every year during the term of this Agreement on the anniversary date of the effective date of the Agreement, the Restaurant shall provide to the United States a narrative report of the actions taken during the reporting period to remove any barriers to access and otherwise enhance accessibility for individuals with disabilities at the Restaurant and any plans for action concerning ADA compliance in the coming year. The report shall include as an exhibit copies of any complaint, whether formal or informal, received during the reporting period alleging that the Restaurant was not being operated in compliance with the ADA or otherwise discriminated against any person on account of disability. The Owner and Operator of the Restaurant shall cooperate in good faith with any and all reasonable requests by the United States for access to the Restaurant and for information and documents concerning the Restaurant's compliance with this Agreement and the ADA. The United States shall have the right to verify compliance with this Agreement and the ADA, both as set forth in this Agreement and through any means available to the general public, including visits to the public areas of the Restaurant and communications with Restaurant staff. The United States shall have the right to inspect the facility at any time, and counsel for the United States need not identify themselves in the course of visits to the public areas.

  • Software compliance Unless explicitly agreed, software being used and developed to provide the service should: ● Be licensed under an open source and permissive license (like MIT, BSD, Apache 2.0,...). ● The license should provide unlimited access rights to the EGI community. ● Have source code publicly available via a public source code repository (if needed a mirror can be put in place under the EGI organisation in GitHub13.) All releases should be appropriately tagged. ● Adopt best practices: ○ Defining and enforcing code style guidelines. ○ Using Semantic Versioning. ○ Using a Configuration Management frameworks such as Ansible. ○ Taking security aspects into consideration through at every point in time. ○ Having automated testing in place. ○ Using code reviewing. 9 xxxxx://xxx.xxx.xx/about/policy/policies_procedures.html 10 xxxxx://xxxx.xxx.xx/wiki/OMB 11 xxxx://xxx.xxx.xx/ 12 xxxxx://xxx.xxx.xx/portal/index.php?Page_Type=NGI&id=4 13 xxxxx://xxxxxx.xxx/EGI-Foundation ○ Treating documentation as code. ○ Documentation should be available for Developers, administrators, and end users.

  • Information Technology Accessibility Standards Any information technology related products or services purchased, used or maintained through this Grant must be compatible with the principles and goals contained in the Electronic and Information Technology Accessibility Standards adopted by the Architectural and Transportation Barriers Compliance Board under Section 508 of the federal Rehabilitation Act of 1973 (29 U.S.C. §794d), as amended. The federal Electronic and Information Technology Accessibility Standards can be found at: xxxx://xxx.xxxxxx-xxxxx.xxx/508.htm.

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

  • REGULATORY FILINGS AND CAISO TARIFF COMPLIANCE 3.1 Filing

  • Quality Assurance Requirements There are no special Quality Assurance requirements under this Agreement.

  • Standards Compliance DNS. Registry Operator shall comply with relevant existing RFCs and those published in the future by the Internet Engineering Task Force (IETF), including all successor standards, modifications or additions thereto relating to the DNS and name server operations including without limitation RFCs 1034, 1035, 1123, 1982, 2181, 2182, 2671, 3226, 3596, 3597, 4343, and 5966. DNS labels may only include hyphens in the third and fourth position if they represent valid IDNs (as specified above) in their ASCII encoding (e.g., “xn--ndk061n”).

  • Documentation and compliance (a) The data importer shall promptly and adequately deal with enquiries from the data exporter that relate to the processing under these Clauses.

  • Child Abuse Reporting Requirement Grantee will:

  • Compliance with Accessibility Standards All parties to this Agreement shall ensure that the plans for and the construction of all projects subject to this Agreement are in compliance with standards issued or approved by the Texas Department of Licensing and Regulation (TDLR) as meeting or consistent with minimum accessibility requirements of the Americans with Disabilities Act (P.L. 101-336) (ADA).

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