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

  • DEVELOPMENT OR ASSISTANCE IN DEVELOPMENT OF SPECIFICATIONS REQUIREMENTS/ STATEMENTS OF WORK Firms and/or individuals that assisted in the development or drafting of the specifications, requirements, statements of work, or solicitation documents contained herein are excluded from competing for this solicitation. This shall not be applicable to firms and/or individuals providing responses to a publicly posted Request for Information (RFI) associated with a solicitation.

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

  • OFFICE OF MANAGEMENT AND BUDGET (OMB) AUDIT REQUIREMENTS The parties shall comply with the requirements of the Single Audit Act of 1984, P.L. 98-502, ensuring that the single audit report includes the coverage stipulated in 2 CFR 200.

  • Technical and Organizational Measures The following sections define SAP’s current technical and organizational measures. SAP may change these at any time without notice so long as it maintains a comparable or better level of security. Individual measures may be replaced by new measures that serve the same purpose without diminishing the security level protecting Personal Data.

Time is Money Join Law Insider Premium to draft better contracts faster.