SUGGESTED METHODS FOR COMPLIANCE Sample Clauses

SUGGESTED METHODS FOR COMPLIANCE. Activities held in physically accessible location, or staff at activities available to meet with person in an accessible location as necessary
View SourceView Similar (13)
SUGGESTED METHODS FOR COMPLIANCE. Procedures for requesting specialist physicians to function as PCP
View SourceView Similar (3)
SUGGESTED METHODS FOR COMPLIANCE. Process for the Contractor to evaluate provider network to ascertain the degree of provider accessibility to persons with disabilities, to identify barriers to access and required modifications to policies/procedures
View SourceView Similar (2)
SUGGESTED METHODS FOR COMPLIANCE. Procedures for requesting standing referrals to specialists and/or specialty centers, specialist physicians to function as PCP, out-of-network referrals, and continuation of existing relationships with out-of-network providers for course of treatment
View SourceView Similar (2)
SUGGESTED METHODS FOR COMPLIANCE. Appropriate post Enrollment health screening for each Enrollee, using an appropriate health screening tool
View Source
SUGGESTED METHODS FOR COMPLIANCE. 1 Appropriate post enrollment health screening for each enrollee, using an appropriate health screening tool 2 Patient profiles by condition/disease for comparative analysis to national norms, with appropriate outreach and education
View Source

Related to SUGGESTED METHODS FOR COMPLIANCE

  • Time for Compliance Consultant shall not commence work under this Agreement until it has provided evidence satisfactory to the City that it has secured all insurance required under this section. In addition, Consultant shall not allow any subconsultant to commence work on any subcontract until it has provided evidence satisfactory to the City that the subconsultant has secured all insurance required under this section. Failure to provide and maintain all required insurance shall be grounds for the City to terminate this Agreement for cause.

  • Standards Compliance 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”).

  • Subcontractor Compliance The Recipient is responsible for Subrecipient compliance with the requirements of this clause and may be held liable for unpaid wages due Subrecipient workers.

  • Contractor Compliance Contractor represents and warrants to pay, at its sole expense, for all applicable permits, licenses, tariffs, tolls and fees to give all notices and comply with all laws, ordinances, rules and regulations of any governmental entity in conjunction with the performance of obligations under the Contract. Prior to award and during the Contract term and any renewals thereof, Contractor must establish to the satisfaction of the Commissioner that it meets or exceeds all requirements of the Bid/Contract and any applicable laws, including but not limited to, permits, insurance coverage, licensing, proof of coverage for worker’s compensation, and shall provide such proof as required by the Commissioner. Failure to do so may constitute grounds for the Commissioner to cancel or suspend this Contract, in whole or in part, or to take any other action deemed necessary by the Commissioner.

  • Program Compliance The School Board shall be responsible for monitoring the program to provide technical assistance and to ensure program compliance.