Utilization of Directory Entries Sample Clauses

Utilization of Directory Entries. The RCE Directory Service and Directory Entries contained therein shall be used by QHINs solely as necessary to create and maintain operational connectivity to enable TEFCA Exchange. Upstream QPS is providing You with access to, and the right to use, Directory Entries on the express condition that You only use and disclose Directory Entry information as necessary to advance the intended use of the Directory Entries or as required by Applicable Law. For example, You are permitted to disclose Directory Entry information to Your Workforce Members, Your Subparticipant’s Workforce Members, and/or to the Workforce Members of health information technology vendors who are engaged in assisting You or Your Subparticipant with establishing and maintaining connectivity via the Framework Agreements. Further, You shall not use another QPS’s Directory Entries or information derived therefrom for marketing or any form of promotion of Your own products and services, unless otherwise permitted pursuant to an SOP. In no event shall You use or disclose the information contained in the Directory Entries in a manner that should be reasonably expected to have a detrimental effect on ONC, the RCE, Upstream QPS, Your Subparticipants, other QHINs, other Participants, other Subparticipants, or any other individual or organization. For the avoidance of doubt, Directory Entries are Confidential Information of the CI Discloser except to the extent such information meets one of the exceptions to the definition of Confidential Information. Nothing herein shall be interpreted to prohibit a QHIN or Upstream QPS from publicly disclosing the identity of its own Participants or Subparticipants.
AutoNDA by SimpleDocs

Related to Utilization of Directory Entries

  • DATA USED FOR CALCULATIONS The calculations for payments under this Agreement shall be initially based upon the valuations that are placed upon all taxable property in the District, including the Applicant’s Qualified Property, by the Appraisal District in its annual certified tax roll submitted to the District for each Tax Year pursuant to TEXAS TAX CODE § 26.01 on or about July 25 of each year of this Agreement. Immediately upon receipt of the valuation information by the District, the District shall submit the valuation information to the Third Party selected and appointed under Section 4.3. The certified tax roll data shall form the basis of the calculation of any and all amounts due under this Agreement. All other data utilized by the Third Party to make the calculations contemplated by this Agreement shall be based upon the best available current estimates. The data utilized by the Third Party shall be adjusted from time to time by the Third Party to reflect actual amounts, subsequent adjustments by the Appraisal District to the District’s certified tax roll or any other changes in student counts, tax collections, or other data.

  • Office of Inspector General Investigative Findings Expert Review In accordance with Senate Bill 799, Acts 2021, 87th Leg., R.S., if Texas Government Code, Section 531.102(m-1)(2) is applicable to this Contract, Contractor affirms that it possesses the necessary occupational licenses and experience.

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

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