Provider Network Information Requirements Sample Clauses

Provider Network Information Requirements. The CONTRACTOR’s Provider network capabilities shall include the following, in order to fulfill the Provider credentialing, recredentialing, and enrollment functions described in Section 4.8.16 of this Agreement, as further described in the MCO Systems Manual: Accepting a provider master file from HCA that identifies all Medicaid enrolled Providers; Transmitting a Provider network file to New Mexico Medicaid’s fiscal agent that identifies by Medicaid Provider ID and NPI any Provider enrolled with New Mexico Medicaid who is a Contract Provider. Non-Contract Providers are not to be included on this file. The CONTRACTOR shall include the date on which the Provider's status as a Contract Provider is effective and when the Provider is no longer a Contract Provider, the CONTRACTOR shall include the date the Provider’s status as a Contract Provider ended. The CONTRACTOR shall send this file monthly, due no later than the tenth day of each month, reflecting the Contract Providers for the previous month. This requirement may be modified or deleted with the implementation of MMIS-R. The CONTRACTOR shall adhere to all federal requirements related to the enrollment, identification, and reporting of billing, rendering, furnishing, ordering, referring, prescribing, attending and other Providers, as applicable; Accepting a Provider confirmation update file from New Mexico Medicaid that contains any newly active Contract Providers or changes to Contract Providers that lists, at a minimum, the provider’s NPI or FEIN/SSN, the provider’s Medicaid ID, servicing location zip code, provider type, specialty, and dates of enrollment/termination; Recording each Provider listed on the New Mexico Medicaid provider update confirmation file and the full provider confirmation file in the CONTRACTOR’s system with the Medicaid provider ID, the assigned provider type, specialty (if applicable), and dates of enrollment/termination and using this data to edit Claims and ensure that the appropriate provider taxonomy and provider servicing location zip code is assigned to Encounter Claims; Maintain an accurate and provide timely updates to an online Provider directory for Members as specified in Section 4.15.5 of this Agreement; and Upon HCA direction, the CONTRACTOR agrees to accept a single provider master file from HCA that has all enrolled Providers. This file will be updated on a daily basis with any changes and published monthly as a full file.
AutoNDA by SimpleDocs
Provider Network Information Requirements. The CONTRACTOR’S provider network capabilities shall include, but not be limited to: A. maintaining complete provider information for all providers contracted with the CONTRACTOR and its subcontractors and any other non-contracted providers who have provided services to date; B. transmitting a Provider Network File to HSD/MAD on a monthly basis, no later than the 28th day of each month, which must be sent along with encounter files, to include all contracted providers, non-contracted providers who have provided service to date, and providers who have been terminated. The file is a general replacement file each month with no deletions from the file until three (3) years past the date of the provider’s termination or denied status. Once a provider is shown on the file, the provider should continue to be reported regardless of whether any encounters are reported; C. providing a complete and accurate designation of each provider according to the data elements and definitions included in the Medicaid Systems Manual, including assignment of unique provider numbers to each type of certification the provider organization has, according to HSD/MAD classification of provider type; and D. providing automated access to members and providers of a member’s PCP assignment.
Provider Network Information Requirements. The CONTRACTOR’s provider network capabilities shall include, but not be limited, to: (1) maintaining complete provider information for all Network Providers with the CONTRACTOR and its subcontractors and any other non-Network Providers who have provided services to date, including the provider’s Medicare number for processing Medicare crossover claims; (2) transmitting an initial Provider Network File, if the CONTRACTOR has not previously submitted a Provider Network File to HSD/MAD and on an ongoing basis, which must be sent along with encounter files, to include new Network Providers, new non-Network servicing providers, changes to existing providers and termination of provider status including provider type and specialties assigned according to HSD/MAD criteria and definitions; (3) providing a complete and accurate designation of each Network Provider according to data elements and definitions included in the MCO/CSP Systems Manual, including assignment of unique provider numbers to each type of certification the provider organization has, according to national standards (National Provider Identifier (NPI)); (4) providing automated access to Members and providers of a Member’s PCP assignment; (5) using the NPI to identify health care providers and send a separate provider network file record for each unique combination of NPI, provider type, and ZIP code; (6) sending the tax ID (FEIN or SSN) for all providers and, for atypical providers, send a separate network file record for each unique combination of FEIN/SSN, provider type, and ZIP code; (7) ensuring that the provider type file contains no duplicate combinations of NPI or FEIN/SSN, provider type, and ZIP code; and (8) determining and reporting both billing and servicing provider types and specialties according to Medicaid provider type and specialty codes which are based on the provider’s licensure/certification and not the service that the provider is rendering.
Provider Network Information Requirements. The CONTRACTOR’S provider network capabilities shall include, but not be limited to: A. Maintaining complete provider information for all providers contracted with the CONTRACTOR and its subcontractors and any other non-contracted providers who have provided services to date; B. Transmitting a Provider Network File to HSD on a monthly basis, no later than the 28th day of each month, to include all contracted providers, non-contracted providers who have provided service to date, providers who have applied for contract and are pending, providers whose application has been denied, and providers who have been terminated from contract. The file is a general replacement file each month with no deletions from the file until 3 years past the date of the provider’s termination or denied status. Once a provider is shown on the file, the provider should continue to be reported regardless of whether any encounters are reported for that provider or not; C. Providing a complete and accurate designation of each provider according to the data elements and definitions included in the SALUD! Systems Manual; and D. Providing automated access to members and providers of a member’s PCP assignment.
Provider Network Information Requirements. The CONTRACTOR’s provider network capabilities shall include, but not be limited, to:

Related to Provider Network Information Requirements

  • Information Requirements The Company covenants that, if at any time before the end of the Effectiveness Period the Company is not subject to the reporting requirements of the Exchange Act, it will cooperate with any Holder and take such further reasonable action as any Holder may reasonably request in writing (including, without limitation, making such reasonable representations as any such Holder may reasonably request), all to the extent required from time to time to enable such Holder to sell Registrable Securities without registration under the Securities Act within the limitation of the exemptions provided by Rule 144 and Rule 144A under the Securities Act and customarily taken in connection with sales pursuant to such exemptions. Upon the written request of any Holder, the Company shall deliver to such Holder a written statement as to whether it has complied with such filing requirements, unless such a statement has been included in the Company’s most recent report filed pursuant to Section 13 or Section 15(d) of Exchange Act. Notwithstanding the foregoing, nothing in this Section 7 shall be deemed to require the Company to register any of its securities (other than the Common Stock) under any section of the Exchange Act.

  • Contracting Information Requirements Contractor represents and warrants that it will comply with the requirements of Section 552.372(a) of the Texas Government Code. Except as provided by Section 552.374(c) of the Texas Government Code, the requirements of Subchapter J (Additional Provisions Related to Contracting Information), Chapter 552 of the Government Code, may apply to the Contract and the Contractor agrees that the Contract can be terminated if the Contractor knowingly or intentionally fails to comply with a requirement of that subchapter.

  • Compliance with Safeguarding Customer Information Requirements The Servicer has implemented and will maintain security measures designed to meet the objectives of the Interagency Guidelines Establishing Standards for Safeguarding Customer Information published in final form on February 1, 2001, 66 Fed. Reg. 8616, and the rules promulgated thereunder, as amended from time to time (the “Guidelines”). The Servicer shall promptly provide the Seller information regarding the implementation of such security measures upon the reasonable request of the Seller.

  • Information Requirement The successful bidder's shall be required to advise the Office of Management and Budget, Government Support Services of the gross amount of purchases made as a result of the contract.

  • Encryption Requirements DST will not locally store Fund Data on any laptops or mobile devices (e.g., Blackberries, PDAs) managed by DST.

  • Food Service Waste Reduction Requirements Contractor shall comply with the Food Service Waste Reduction Ordinance, as set forth in San Francisco Environment Code Chapter 16, including but not limited to the remedies for noncompliance provided therein.

  • 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. B. Grantee shall use the Texas Abuse Hotline Website located at xxxxx://xxx.xxxxxxxxxxxxxx.xxx/Login/Default.aspx as required by the System Agency. Grantee shall retain reporting documentation on site and make it available for inspection by the System Agency.

  • Training Requirements Grantee shall: A. Authorize and require staff (including volunteers) to attend training, conferences, and meetings as directed by DSHS; B. Appropriately budget funds in order to meet training requirements in a timely manner, and ensure that staff and volunteers are trained as specified in the training requirements listed at xxxxx://xxx.xxxx.xxxxx.xxx/hivstd/training/ and as otherwise specified by DSHS. Grantee shall document that these training requirements are met; and C. Ensure that staff hired for HIV and syphilis testing are trained to perform blood draws within three (3) months of employment.

  • Compliance with Information Requests Notwithstanding any other provision of the Deposit Agreement, the Articles of Association and applicable law, each Holder and Beneficial Owner agrees to (a) provide such information as the Company or the Depositary may request pursuant to law (including, without limitation, relevant Cayman Islands law, any applicable law of the United States, the Memorandum and Articles of Association, any resolutions of the Company’s Board of Directors adopted pursuant to the Memorandum and Articles of Association, the requirements of any markets or exchanges upon which the Shares, ADSs or Receipts are listed or traded, or to any requirements of any electronic book-entry system by which the ADSs or Receipts may be transferred), (b) be bound by and subject to applicable provisions of the laws of the Cayman Islands, the Memorandum and Articles of Association and the requirements of any markets or exchanges upon which the ADSs, Receipts or Shares are listed or traded, or pursuant to any requirements of any electronic book-entry system by which the ADSs, Receipts or Shares may be transferred, to the same extent as if such Holder and Beneficial Owner held Shares directly, in each case irrespective of whether or not they are Holders or Beneficial Owners at the time such request is made and, without limiting the generality of the foregoing, (c) comply with all applicable provisions of Cayman Islands law, the rules and requirements of any stock exchange on which the Shares are, or will be registered, traded or listed and the Articles of Association regarding any such Holder or Beneficial Owner’s interest in Shares (including the aggregate of ADSs and Shares held by each such Holder or Beneficial Owner) and/or the disclosure of interests therein, whether or not the same may be enforceable against such Holder or Beneficial Owner. The Depositary agrees to use its reasonable efforts to forward upon the request of the Company, and at the Company’s expense, any such request from the Company to the Holders and to forward to the Company any such responses to such requests received by the Depositary.

  • Publication Requirements Those seeking to include renderings of more than 10 images from the UND Biometrics Database in reports, papers, and other documents to be published or released must first obtain approval in writing from the UND Principal Investigator. In no case should the face images be used in a way that could cause the original subject embarrassment or mental anguish.

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