Valid Provider Numbers Sample Clauses

Valid Provider Numbers. ‌ a) A Worker must receive and maintain a DHS/OHA provider number, as defined in Article 8, in order to be paid. b) Expectations for the State and the Worker are defined in Article 8. c) For HCWs/PSWs paid through state systems, notices will begin ninety (90) days after ratification of this Agreement. For PSWs paid through fiscal intermediaries, notices will begin no later than three-hundred sixty-five (365) days after ratification of this Agreement. Until the notices specified above are sent for PSWs paid through fiscal intermediaries, the OHCC shall send out a quarterly notice to Providers who have any credentials expiring in the next three (3) months.
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Valid Provider Numbers. ‌ a) A Worker must receive and maintain a DHS/OHA provider number, as defined in Article 8, in order to be paid. b) Expectations for the State and the Worker are defined in Article 8.
Sample 1Sample 2Sample 3See All (5)
Valid Provider Numbers. ‌ a) A Worker must receive and maintain a DHS/OHA provider number in order to be paid. b) HCWs/PSWs shall be provided a one-hundred and twenty (120) and sixty (60) day reminder prior to the expiration of any of their credentials. c) For HCWs/PSWs paid through state systems, notices will begin ninety (90) days after ratification of this Agreement. For PSWs paid through fiscal intermediaries, notices will begin no later than three-hundred sixty-five (365) days after ratification of this Agreement. Until the notices specified above are sent for PSWs paid through fiscal intermediaries, the OHCC shall send out a quarterly notice to Providers who have any credentials expiring in the next three (3) months. d) HCWs/PSWs are responsible to keep their mailing address, phone number and email address (if available) up-to-date with DHS/OHA Provider Relations Units and the OHCC Registry. e) Homecare and Personal Support Workers must take action to renew their credentials at least fifty-five (55) days prior to the credential end date. f) Failure to submit all credential renewal paperwork at least fifty-five (55) days prior to the credential end date may result in the inactivation of the worker’s provider number if the paperwork is not processed by the credential end date. g) A HCW/PSW with an inactivated/terminated provider number is not eligible to receive Medicaid service payments.
Sample 1Sample 2Sample 3See All (4)

Related to Valid Provider Numbers

  • Exceptional Access to Thick Registration Data In case of a registrar failure, deaccreditation, court order, etc. that prompts the temporary or definitive transfer of its domain names to another registrar, at the request of ICANN, Registry Operator will provide ICANN with up-­‐to-­‐date data for the domain names of the losing registrar. The data will be provided in the format specified in Specification 2 for Data Escrow. The file will only contain data related to the domain names of the losing registrar. Registry Operator will provide the data as soon as commercially practicable, but in no event later than five (5) calendar days following ICANN’s request. Unless otherwise agreed by Registry Operator and ICANN, the file will be made available for download by ICANN in the same manner as the data specified in Section 3.1 of this Specification.

  • The Web Services E-Verify Employer Agent agrees to, consistent with applicable laws, regulations, and policies, commit sufficient personnel and resources to meet the requirements of this MOU.

  • Bulk Registration Data Access to Icann Periodic Access to Thin Registration Data. In order to verify and ensure the operational stability of Registry Services as well as to facilitate compliance checks on accredited registrars, Registry Operator will provide ICANN on a weekly basis (the day to be designated by ICANN) with up-to-date Registration Data as specified below. Data will include data committed as of 00:00:00 UTC on the day previous to the one designated for retrieval by ICANN.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes. 11.2 We may (i) compile statistical and other information related to the performance, operation and use of the Services, and (ii) use data from the Services in aggregated form for security and operations management, to create statistical analyses, and for research and development purposes (clauses i and ii are collectively referred to as “Service Analyses”). We may make Service Analyses publicly available; however, Service Analyses will not incorporate Your Content, Personal Data or Confidential Information in a form that could serve to identify You or any individual. We retain all intellectual property rights in Service Analyses. 11.3 We may provide You with the ability to obtain certain Oracle Software (as defined below) for use with the Services. If we provide Oracle Software to You and do not specify separate terms for such software, then such Oracle Software is provided as part of the Services and You have the non-exclusive, worldwide, limited right to use such Oracle Software, subject to the terms of this Agreement and Your order (except for separately licensed elements of the Oracle Software, which separately licensed elements are governed by the applicable separate terms), solely to facilitate Your use of the Services. You may allow Your Users to use the Oracle Software for this purpose, and You are responsible for their compliance with the license terms. Your right to use any Oracle Software will terminate upon the earlier of our notice (by web posting or otherwise) or the end of the Services associated with the Oracle Software. Notwithstanding the foregoing, if Oracle Software is licensed to You under separate terms, then Your use of such software is governed by the separate terms. Your right to use any part of the Oracle Software that is licensed under the separate terms is not restricted in any way by this Agreement.

  • Data Encryption Contractor must encrypt all State data at rest and in transit, in compliance with FIPS Publication 140-2 or applicable law, regulation or rule, whichever is a higher standard. All encryption keys must be unique to State data. Contractor will secure and protect all encryption keys to State data. Encryption keys to State data will only be accessed by Contractor as necessary for performance of this Contract.

  • Business Associate “Business Associate” shall have the same meaning as the term “business associate” at 45 C.F.R. 160.103, and shall refer to Contractor.

  • Minimum Data Necessary Shared The Provider attests that the Student Data request by the Provider from the LEA in order for the LEA to access the Provider’s products and/or services is limited to the Student Data that is adequate, relevant, and limited to what is necessary in relation to the K-12 school purposes for which it is processed.

  • Benchmarks for Measuring Accessibility For the purposes of this Agreement, the accessibility of online content and functionality will be measured according to the W3C’s Web Content Accessibility Guidelines (WCAG) 2.0 Level AA and the Web Accessibility Initiative Accessible Rich Internet Applications Suite (WAI-ARIA) 1.0 for web content, which are incorporated by reference.

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