Sprint’s Preferred Provider Status Sample Clauses

Sprint’s Preferred Provider Status. For so long as Sprint PCS (or an Affiliate) owns in excess of 10% of all outstanding equity interests in VMU, Sprint PCS (and its Affiliates) will be VMU’s preferred provider of all Telecommunications Services (other than Mobile Voice and Data Services that are subject to the exclusivity provisions of Section 2.7.1 above) , and as such will provide such Telecommunications Services so long as (x) Sprint PCS or its Affiliates have the capability to provide the requested service and (y) the terms under which Sprint PCS or its Affiliate would provide such service are at least as favorable as the terms VMU could obtain from third parties for substantially the same service, for substantially the same duration and for substantially the same volume of services being requested by VMU.
AutoNDA by SimpleDocs

Related to Sprint’s Preferred Provider Status

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

  • Obligations of Business Associate Upon Termination Upon termination of this Agreement for any reason, business associate shall return to covered entity or, if agreed to by covered entity, destroy all protected health information received from covered entity, or created, maintained, or received by business associate on behalf of covered entity, that the business associate still maintains in any form. Business associate shall retain no copies of the protected health information.

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

  • Your Guide to Selecting a Primary Care Provider (PCP) and Other Providers Quality healthcare begins with a partnership between you and your primary care provider (PCP). When you need care, call your PCP, who will help coordinate your care. Your healthcare coverage under this plan is provided or arranged through our network of PCPs, specialists, and other providers. You’re encouraged to: • become involved in your healthcare by asking providers about all treatment plans available and their costs; • take advantage of the preventive health services offered under this plan to help you stay healthy and find problems before they become serious. Each member is required to select and provide the name of his or her network PCP who will provide and arrange for your health care. Your PCP provides your health care, orders lab tests and x-rays, prescribe medicines or therapies, and arranges hospitalization when necessary. You may choose one from the list of Access Blue New England network PCP providers on our website. Each enrolled member may select a different PCP. If a PCP is not chosen, we may assign one for each enrolled member. You may change your designated PCP by calling our Customer Service Department or visiting our website. Finding a PCP in our network is easy. To select a provider, or to check that a provider is in our network, please use the “Find a Doctor” tool on our website or call Customer Service. Please note: We are not obligated to provide you with a provider. We are not liable for anything your provider does or does not do. We are not a healthcare provider and do not practice medicine, dentistry, furnish health care, or make medical judgments.

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

  • Provider Directory a. The Contractor shall make available in electronic form and, upon request, in paper form, the following information about its network providers: i. The provider’s name as well as any group affiliation; ii. Street address(es); iii. Telephone number(s); iv. Website URL, as appropriate; v. Specialty, as appropriate; vi. Whether the provider will accept new beneficiaries; vii. The provider’s cultural and linguistic capabilities, including languages (including American Sign Language) offered by the provider or a skilled medical interpreter at the provider’s office, and whether the provider has completed cultural competence training; and viii. Whether the provider’s office/facility has accommodations for people with physical disabilities, including offices, exam room(s) and equipment. b. The Contractor shall include the following provider types covered under this Agreement in the provider directory: i. Physicians, including specialists ii. Hospitals

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

  • Performing Agency’s Pre-existing Works A. To the extent that Performing Agency incorporates into the Work Product any works of Performing Agency that were created by Performing Agency or that Performing Agency acquired rights in prior to the Effective Date of this Contract (“Incorporated Pre-existing Works”), Performing Agency retains ownership of such Incorporated Pre-existing Works. B. Performing Agency hereby grants to System Agency an irrevocable, perpetual, non- exclusive, royalty-free, transferable, worldwide right and license, with the right to sublicense, to use, reproduce, modify, copy, create derivative works of, publish, publicly perform and display, sell, offer to sell, make and have made, the Incorporated Pre-existing Works, in any medium, with or without the associated Work Product. C. Performing Agency represents, warrants, and covenants to System Agency that Performing Agency has all necessary right and authority to grant the foregoing license in the Incorporated Pre-existing Works to System Agency.

  • Unbundled Network Terminating Wire (UNTW) 2.8.3.1 UNTW is unshielded twisted copper wiring that is used to extend circuits from an intra-building network cable terminal or from a building entrance terminal to an individual End User’s point of demarcation. It is the final portion of the Loop that in multi-subscriber configurations represents the point at which the network branches out to serve individual subscribers. 2.8.3.2 This element will be provided in MDUs and/or Multi-Tenants Units (MTUs) where either Party owns wiring all the way to the End User’s premises. Neither Party will provide this element in locations where the property owner provides its own wiring to the End User’s premises, where a third party owns the wiring to the End User’s premises.

  • Consider Provider as School Official The Parties agree that Provider is a “school official” under FERPA and has a legitimate educational interest in personally identifiable information from education records received from the LEA pursuant to the DPA. For purposes of the Service Agreement and this DPA, Provider: (1) provides a service or function for which the LEA would otherwise use employees; (2) is under the direct control of the LEA with respect to the use and maintenance of education records; and (3) is subject to the requirements of FERPA governing the use and redisclosure of personally identifiable information from the education records received from the LEA.

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