TEFCA Exchange Activities Sample Clauses

TEFCA Exchange Activities. In addition to the requirements below, a QHIN, Participant, or Subparticipant may only Request information under the applicable Framework Agreement for a specific Exchange Purpose if the QHIN, Participant, or Subparticipant is the type of person or entity that is described in the definition of the applicable Exchange Purpose. Such a QHIN, Participant, or Subparticipant may use a Business Associate, agent, or contractor to make such a Request, Use, or Disclosure for the applicable Exchange Purpose. For example, only a Health Care Provider as described in the definition of Treatment (or a Business Associate, agent, or contractor acting on that Health Care Provider’s behalf) may Request information for the Exchange Purpose of Treatment. This Common Agreement specifies, among other things, the reasons for which information may be Requested and transmitted from one QHIN to another QHIN. Participants and Subparticipants should understand that, despite their participation under a Framework Agreement, QHINs are prohibited from engaging in QHIN-to-QHIN exchange for any purpose other than an Exchange Purpose under this Common Agreement. The RCE recognizes that Signatory may participate in other health information exchange networks and Signatory’s Participants and their Subparticipants also likely participate in other networks, as well as non-network information exchange. This Common Agreement does not affect these other activities or the reasons for which Participants and Subparticipants may request and exchange information within their networks and/or subject to other agreements. Such activities are not in any way limited by the Framework Agreements.
Sample 1Sample 2See All (5)
AutoNDA by SimpleDocs
TEFCA Exchange Activities 
Sample 1Sample 2Sample 3See All (4)

Related to TEFCA Exchange Activities

  • Outside Activities Subject to the Articles of Incorporation and any agreements entered into by the General Partner or its Affiliates with the Partnership or a Subsidiary, any officer, director, employee, agent, trustee, Affiliate or stockholder of the General Partner shall be entitled to and may have business interests and engage in business activities in addition to those relating to the Partnership, including business interests and activities substantially similar or identical to those of the Partnership. Neither the Partnership nor any of the Limited Partners shall have any rights by virtue of this Agreement in any such business ventures, interest or activities. None of the Limited Partners nor any other Person shall have any rights by virtue of this Agreement or the partnership relationship established hereby in any such business ventures, interests or activities, and the General Partner shall have no obligation pursuant to this Agreement to offer any interest in any such business ventures, interests and activities to the Partnership or any Limited Partner, even if such opportunity is of a character which, if presented to the Partnership or any Limited Partner, could be taken by such Person.

  • Registry Functions Activity Report This report shall be compiled in a comma separated-value formatted file as specified in RFC 4180. The file shall be named “gTLD-activity-yyyymm.csv”, where “gTLD” is the gTLD name; in case of an IDN-TLD, the A-label shall be used; “yyyymm” is the year and month being reported. The file shall contain the following fields: Field # Field Name Description 01 operational-registrars number of operational registrars at the end of the reporting period 02 ramp-up-registrars number of registrars that have received a password for access to OT&E at the end of the reporting period 03 pre-ramp-up-registrars number of registrars that have requested access, but have not yet entered the ramp-up period at the end of the reporting period 06 web-whois-queries number of Web-based Whois queries responded during the reporting period, not including searchable Whois 09 dns-udp-queries-responded number of DNS queries received over UDP transport that were responded during the reporting period 10 dns-tcp-queries-received number of DNS queries received over TCP transport during the reporting period 11 dns-tcp-queries-responded number of DNS queries received over TCP transport that were responded during the reporting period 12 srs-dom-check number of SRS (EPP and any other interface) domain name “check” requests responded during the reporting period 13 srs-dom-create number of SRS (EPP and any other interface) domain name “create” requests responded during the reporting period 14 srs-dom-delete number of SRS (EPP and any other interface) domain name “delete” requests responded during the reporting period 15 srs-dom-info number of SRS (EPP and any other interface) domain name “info” requests responded during the reporting period 16 srs-dom-renew number of SRS (EPP and any other interface) domain name “renew” requests responded during the reporting period 17 srs-dom-rgp-restore-report number of SRS (EPP and any other interface) domain name RGP “restore” requests delivering a restore report responded during the reporting period 18 srs-dom-rgp-restore-request number of SRS (EPP and any other interface) domain name RGP “restore” requests responded during the reporting period 19 srs-dom-transfer-approve number of SRS (EPP and any other interface) domain name “transfer” requests to approve transfers responded during the reporting period 20 srs-dom-transfer-cancel number of SRS (EPP and any other interface) domain name “transfer” requests to cancel transfers responded during the reporting period 21 srs-dom-transfer-query number of SRS (EPP and any other interface) domain name “transfer” requests to query about a transfer responded during the reporting period 22 srs-dom-transfer-reject number of SRS (EPP and any other interface) domain name “transfer” requests to reject transfers responded during the reporting period 23 srs-dom-transfer-request number of SRS (EPP and any other interface) domain name “transfer” requests to request transfers responded during the reporting period 24 srs-dom-update number of SRS (EPP and any other interface) domain name “update” requests (not including RGP restore requests) responded during the reporting period 25 srs-host-check number of SRS (EPP and any other interface) host “check” requests responded during the reporting period 26 srs-host-create number of SRS (EPP and any other interface) host “create” requests responded during the reporting period 27 srs-host-delete number of SRS (EPP and any other interface) host “delete” requests responded during the reporting period 28 srs-host-info number of SRS (EPP and any other interface) host “info” requests responded during the reporting period 29 srs-host-update number of SRS (EPP and any other interface) host “update” requests responded during the reporting period 30 srs-cont-check number of SRS (EPP and any other interface) contact “check” requests responded during the reporting period 32 srs-cont-delete number of SRS (EPP and any other interface) contact “delete” requests responded during the reporting period 33 srs-cont-info number of SRS (EPP and any other interface) contact “info” requests responded during the reporting period 34 srs-cont-transfer-approve number of SRS (EPP and any other interface) contact “transfer” requests to approve transfers responded during the reporting period 35 srs-cont-transfer-cancel number of SRS (EPP and any other interface) contact “transfer” requests to cancel transfers responded during the reporting period 36 srs-cont-transfer-query number of SRS (EPP and any other interface) contact “transfer” requests to query about a transfer responded during the reporting period 37 srs-cont-transfer-reject number of SRS (EPP and any other interface) contact “transfer” requests to reject transfers responded during the reporting period 38 srs-cont-transfer-request number of SRS (EPP and any other interface) contact “transfer” requests to request transfers responded during the reporting period 39 srs-cont-update number of SRS (EPP and any other interface) contact “update” requests responded during the reporting period The first line shall include the field names exactly as described in the table above as a “header line” as described in section 2 of RFC 4180. No other lines besides the ones described above shall be included. Line breaks shall be <U+000D, U+000A> as described in RFC 4180. For gTLDs that are part of a single-instance Shared Registry System, the Registry Functions Activity Report may include the total contact or host transactions for all the gTLDs in the system. REGISTRATION DATA PUBLICATION SERVICES

  • Eligible Activities 7.1 Subject to the provisions of this Article, the PERFORMING PARTY agrees to complete all Grant Activities as described in the Scope of Work and in accordance with the Contract Documents.

  • Personally Owned Professional Material The employer shall reimburse an employee to a maximum of $150 for loss, damage or personal insurance deductible to personally owned professional material brought to the employee’s workplace to assist in the execution of the employee’s duties, provided that:

  • Cease Activities Upon receiving a notice of termination of this Grant, Grantee must immediately cease all activities under this Grant, unless Agency expressly directs otherwise in such notice. Upon termination, Grantee must deliver to Agency all materials or other property that are or would be required to be provided to Agency under this Grant or that are needed to complete the Project activities that would have been performed by Grantee.

  • Marketing Activities The Borrower will not, and will not permit any of its Subsidiaries to, engage in marketing activities for any Hydrocarbons or enter into any contracts related thereto other than (i) contracts for the sale of Hydrocarbons scheduled or reasonably estimated to be produced from their proved Oil and Gas Properties during the period of such contract, (ii) contracts for the sale of Hydrocarbons scheduled or reasonably estimated to be produced from proved Oil and Gas Properties of third parties during the period of such contract associated with the Oil and Gas Properties of the Borrower and its Subsidiaries that the Borrower or one of its Subsidiaries has the right to market pursuant to joint operating agreements, unitization agreements or other similar contracts that are usual and customary in the oil and gas business and (iii) other contracts for the purchase and/or sale of Hydrocarbons of third parties (A) which have generally offsetting provisions (i.e. corresponding pricing mechanics, delivery dates and points and volumes) such that no “position” is taken and (B) for which appropriate credit support has been taken to alleviate the material credit risks of the counterparty thereto.

  • EXTRA-CURRICULAR ACTIVITIES 1. In this agreement, extra-curricular programs and activities include all those that are beyond the provincially prescribed and locally determined curricula of the school.

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