Provider Network and Affiliation Files Sample Clauses

Provider Network and Affiliation Files. The HMO will supply network provider data to the Enrollment Broker and Claims Administrator. This data will consist of a Provider Network File and a Provider Affiliation File. The HMO will submit the Provider Network File to the Enrollment Broker and the Provider Affiliation File to the Claims Administrator. Both files shall accomplish the following objectives: 1. Provide identifying information for all managed care providers (e.g. name, address, etc.). 2. Maintain history on provider enrollment/disenrollment. 3. Identify PCP capacity. 4. Identify any restrictions (e.g., age, sex, etc.). 5. Identify number and types of specialty providers available to Members. 6. Provide other information identified by HHSC.”
Sample 1Sample 2Sample 3See All (5)
AutoNDA by SimpleDocs
Provider Network and Affiliation Files. The HMO will supply network provider data to the Enrollment Broker and Claims Administrator. This data will consist of a Provider Network File and a Provider Affiliation File. The HMO will submit the Provider Network File to the Enrollment Broker and the Provider Affiliation File to the Claims Administrator. Both files shall accomplish the following objectives: 1. Provide identifying information for all managed care providers (e.g. name, address, etc.). 2. Maintain history on provider enrollment/disenrollment.
Sample 1

Related to Provider Network and Affiliation Files

  • Provider Network The Panel of health service Providers with which the Contractor contracts for the provision of covered services to Members and Out-of-network Providers administering services to Members.

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

  • Provider If the Provider is a State Agency, the Provider acknowledges that it is responsible for its own acts and deeds and the acts and deeds of its agents and employees. If the Provider is not a State agency, then the Provider agrees to indemnify and save harmless the State and its officers and employees from all claims and liability due to activities of itself, its agents, or employees, performed under this contract and which are caused by or result from error, omission, or negligent act of the Provider or of any person employed by the Provider. The Provider shall also indemnify and save harmless the State from any and all expense, including, but not limited to, attorney fees which may be incurred by the State in litigation or otherwise resisting said claim or liabilities which may be imposed on the State as a result of such activities by the Provider or its employees. The Provider further agrees to indemnify and save harmless the State from and against all claims, demands, and causes of action of every kind and character brought by any employee of the Provider against the State due to personal injuries and/or death to such employee resulting from any alleged negligent act by either commission or omission on the part of the Provider.

  • Provider Services Charges for the following Services when ordered by a Physician for the treatment of an Injury or Illness.

  • THIRD-PARTY CONTENT, SERVICES AND WEBSITES 10.1 The Services may enable You to link to, transfer Your Content or Third Party Content to, or otherwise access, third parties’ websites, platforms, content, products, services, and information (“Third Party Services”). Oracle does not control and is not responsible for Third Party Services. You are solely responsible for complying with the terms of access and use of Third Party Services, and if Oracle accesses or uses any Third Party Services on Your behalf to facilitate performance of the Services, You are solely responsible for ensuring that such access and use, including through passwords, credentials or tokens issued or otherwise made available to You, is authorized by the terms of access and use for such services. If You transfer or cause the transfer of Your Content or Third Party Content from the Services to a Third Party Service or other location, that transfer constitutes a distribution by You and not by Oracle. 10.2 Any Third Party Content we make accessible is provided on an “as-is” and “as available” basis without any warranty of any kind. You acknowledge and agree that we are not responsible for, and have no obligation to control, monitor, or correct, Third Party Content. We disclaim all liabilities arising from or related to Third Party Content. 10.3 You acknowledge that: (i) the nature, type, quality and availability of Third Party Content may change at any time during the Services Period, and (ii) features of the Services that interoperate with Third Party Services such as Facebook™, YouTube™ and Twitter™, etc., depend on the continuing availability of such third parties’ respective application programming interfaces (APIs). We may need to update, change or modify the Services under this Agreement as a result of a change in, or unavailability of, such Third Party Content, Third Party Services or APIs. If any third party ceases to make its Third Party Content or APIs available on reasonable terms for the Services, as determined by us in our sole discretion, we may cease providing access to the affected Third Party Content or Third Party Services without any liability to You. Any changes to Third Party Content, Third Party Services or APIs, including their unavailability, during the Services Period does not affect Your obligations under this Agreement or the applicable order, and You will not be entitled to any refund, credit or other compensation due to any such changes.

  • Registration Data Directory Services Until ICANN requires a different protocol, Registry Operator will operate a WHOIS service available via port 43 in accordance with XXX 0000, and a web-­‐based Directory Service at <whois.nic.TLD> providing free public query-­‐based access to at least the following elements in the following format. ICANN reserves the right to specify alternative formats and protocols, and upon such specification, the Registry Operator will implement such alternative specification as soon as reasonably practicable. Registry Operator shall implement a new standard supporting access to domain name registration data (SAC 051) no later than one hundred thirty-­‐five (135) days after it is requested by ICANN if: 1) the IETF produces a standard (i.e., it is published, at least, as a Proposed Standard RFC as specified in RFC 2026); and 2) its implementation is commercially reasonable in the context of the overall operation of the registry. 1.1. The format of responses shall follow a semi-­‐free text format outline below, followed by a blank line and a legal disclaimer specifying the rights of Registry Operator, and of the user querying the database. 1.2. Each data object shall be represented as a set of key/value pairs, with lines beginning with keys, followed by a colon and a space as delimiters, followed by the value. 1.3. For fields where more than one value exists, multiple key/value pairs with the same key shall be allowed (for example to list multiple name servers). The first key/value pair after a blank line should be considered the start of a new record, and should be considered as identifying that record, and is used to group data, such as hostnames and IP addresses, or a domain name and registrant information, together. 1.4. The fields specified below set forth the minimum output requirements. Registry Operator may output data fields in addition to those specified below, subject to approval by ICANN, which approval shall not be unreasonably withheld.

  • Information and Services Required of the Owner The Owner shall provide information with reasonable promptness, regarding requirements for and limitations on the Project, including a written program which shall set forth the Owner’s objectives, constraints, and criteria, including schedule, space requirements and relationships, flexibility and expandability, special equipment, systems, sustainability and site requirements.

  • Web Services Our Web Services are designed to enable you to easily establish a presence on the Internet. Our Web Hosting and Design is composed of our Web Hosting and Design Publishing Component and other miscellaneous components. These components may be used independently or in conjunction with each other.

  • Verizon OSS Services 8.2.1 Upon request by ECI, Verizon shall provide to ECI Verizon OSS Services. Such Verizon OSS Services will be provided in accordance with, but only to the extent required by, Applicable Law. 8.2.2 Subject to the requirements of Applicable Law, Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services that will be offered by Verizon, shall be as determined by Verizon. Subject to the requirements of Applicable Law, Verizon shall have the right to change Verizon Operations Support Systems, Verizon Operations Support Systems functions, Verizon OSS Facilities, Verizon OSS Information, and the Verizon OSS Services, from time-to-time, without the consent of ECI. 8.2.3 To the extent required by Applicable Law, in providing Verizon OSS Services to ECI, Verizon will comply with Verizon’s applicable OSS Change Management Guidelines, as such Guidelines are modified from time-to-time, including, but not limited to, the provisions of the Guidelines related to furnishing notice of changes in Verizon OSS Services. Verizon’s OSS Change Management Guidelines will be set out on a Verizon website.

  • Information Services Traffic 5.1 For purposes of this Section 5, Voice Information Services and Voice Information Services Traffic refer to switched voice traffic, delivered to information service providers who offer recorded voice announcement information or open vocal discussion programs to the general public. Voice Information Services Traffic does not include any form of Internet Traffic. Voice Information Services Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information services Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment. 5.2 If a D&E Customer is served by resold Verizon Telecommunications Service or a Verizon Local Switching UNE, subject to any call blocking feature used by D&E, to the extent reasonably feasible, Verizon will route Voice Information Services Traffic originating from such Service or UNE to the Voice Information Service platform. For such Voice Information Services Traffic, unless D&E has entered into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from D&E’s Customers, D&E shall pay to Verizon without discount the Voice Information Services provider charges. D&E shall pay Verizon such charges in full regardless of whether or not it collects such charges from its own Customers. 5.3 D&E shall have the option to route Voice Information Services Traffic that originates on its own network to the appropriate Voice Information Services platform(s) connected to Verizon’s network. In the event D&E exercises such option, D&E will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow D&E to route Voice Information Services Traffic originated on its network to Verizon. For such Voice Information Services Traffic, unless D&E has entered into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from D&E’s Customers, D&E shall pay to Verizon without discount the Voice Information Services provider charges. 5.4 D&E shall pay Verizon such charges in full regardless of whether or not it collects charges for such calls from its own Customers. 5.5 For variable rated Voice Information Services Traffic (e.g., NXX 550, 540, 976, 970, 940, as applicable) from D&E Customers served by resold Verizon Telecommunications Services or a Verizon Local Switching Network Element, D&E shall either (a) pay to Verizon without discount the Voice Information Services provider charges, or (b) enter into an arrangement with Verizon to xxxx and collect Voice Information Services provider charges from D&E’s Customers. 5.6 Either Party may request the other Party provide the requesting Party with non discriminatory access to the other party’s information services platform, where such platform exists. If either Party makes such a request, the Parties shall enter into a mutually acceptable written agreement for such access. 5.7 In the event D&E exercises such option, D&E will establish, at its own expense, a dedicated trunk group to the Verizon Information Service serving switch. This trunk group will be utilized to allow D&E to route information services traffic originated on its network to Verizon.

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