Contractor Exchange Function Sample Clauses

Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, creates, discloses or transmits Protected Health Information and/ or Personally Identifiable Information gathered from the Exchange, applicants, qualified individuals or enrollee in the process of assisting individuals with the purchase of health insurance coverage in SADPs or other functions under the California exchange program. Contractor is not performing a Contractor Exchange Function where Contractor establishes an independent relationship with the applicant through the offering and/or furnishing of health insurance, and Contractor may utilize Protected Health Information and Personally Identifiable Information gathered from the Exchange that relates to applicants consistent with the terms, conditions, consents, and other permissions agreed to by the applicants in establishing the independent relationship with Contractor and as permitted by applicable laws, regulations and agency guidance.
AutoNDA by SimpleDocs
Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, maintains, creates, discloses or transmits PHI and/ or Personally Identifiable Information gathered from the Exchange, applicants, Qualified Individuals or Enrollees in the process of assisting individuals and entities with the purchase of health insurance coverage in QDPs or other functions under The California Exchange program.
Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, maintains, creates, discloses or transmits PHI and/ or Personally Identifiable Information gathered from the Exchange, applicants, qualified individuals or enrollees in the process of assisting individuals and entities with the purchase of health insurance coverage in QHPs or other functions under the California exchange program. Notwithstanding the foregoing, Contractor shall not be deemed to be performing a Contractor Exchange Function under this agreement where (1) Contractor is performing activities related to furnishing or arranging for health care coverage and/or services for individuals enrolled in Contractor’s QHP using PHI or Personally Identifiable Information gathered from the Exchange, and (2) such use and/or disclosure is consistent with the terms of this agreement and permitted by applicable laws, regulations and agency guidance, and (3) if necessary under applicable laws, regulations and agency guidance, consistent with the consents and other permissions agreed to by applicant as an Enrollee in Contractor's QHP. The exception to Contractor Exchange Functions described herein shall not apply to the extent that Contractor receives PHI or Personally Identifiable Information from the Exchange that Contractor would not ordinarily gather for determining eligibility or enrollment in a health insurance plan.
Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, maintains, creates, discloses or transmits PHI and/ or Personally Identifiable Information gathered from the Exchange, applicants, Qualified Individuals or Enrollees in the process of assisting individuals and entities with the purchase of health insurance coverage in QDPs or other functions under The California Exchange program. Covered California for Small Business (CCSB) – The Exchange program providing coverage to eligible small businesses, formerly referred to as the Small Business Health Options Program (SHOP) and described in Government Code § 100502(m).
Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, maintains, creates, discloses or transmits PHI and/ or Personally Identifiable Information gathered from the Exchange, applicants, qualified individuals or enrollees in the process of assisting individuals and entities with the purchase of health insurance coverage in QHPs or other functions under the California exchange program. Notwithstanding the foregoing, Contractor shall not be deemed to be performing a Contractor Exchange Function under this agreement where (1) Contractor is performing activities related to furnishing or arranging for health care coverage and/or services for individuals enrolled in Contractor’s QHP using PHI or Personally Identifiable Information gathered from the of this agreement and permitted by applicable laws, regulations and agency guidance, and (3) if necessary under applicable laws, regulations and agency guidance, consistent with the consents and other permissions agreed to by applicant as an Enrollee in Contractor's QHP. The exception to Contractor Exchange Functions described herein shall not apply to the extent that Contractor receives PHI or Personally Identifiable Information from the Exchange that Contractor would not ordinarily gather for determining eligibility or enrollment in a health insurance plan.
Contractor Exchange Function. Any function that Contractor performs pursuant to this Agreement during which Contractor receives, creates, discloses or transmits PHI and/ or Personally Identifiable Information gathered from the Exchange, applicants, qualified individuals or enrollee in the process of assisting individuals with the purchase of health insurance coverage in QHPs or other functions under the California exchange program. Contractor is not performing a Contractor Exchange Function where Contractor establishes an independent relationship with the applicant through the offering and/or furnishing of health insurance, and Contractor may utilize PHI and Personally Identifiable Information gathered from the Exchange that relates to applicants consistent with the terms, conditions, consents, and other permissions agreed to by the applicants in establishing the independent relationship with Contractor and as permitted by applicable laws, regulations and agency guidance.

Related to Contractor Exchange Function

  • MANAGEMENT FUNCTIONS B-1 The Association recognizes that the management of the Hospital and the direction of the working forces are fixed exclusively in the Hospital and shall remain solely with the Hospital except as specifically limited by the provisions of this Agreement, and without restricting the generality of the foregoing, the Association acknowledges that it is the exclusive function of the Hospital to:

  • CERTIFYING FUNCTION Department of Information Resources acting as the owner of the DIR Contracts hereby certifies the eligibility of the DIR Customer to use the DIR Contracts.

  • Operations Support Systems Functions CBT shall provide CLEC, upon CLEC's request, nondiscriminatory access to CBT's Operations Support Systems functions for pre-ordering, ordering, provisioning, maintenance and repair and billing, in accordance with the terms and schedules established in the Commission’s Arbitration Award in Case No. 97-152-TP-ARB, August 14, 1997 (“Arbitration Award”). CBT shall provide CLEC advance written notice of any material changes to CBT operating support systems functions.

  • 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

  • Mixed Functions An employee engaged for more than two hours during one day or shift on duties carrying a higher rate than his or her ordinary classification shall be paid the higher rate for such day or shift. If for two hours or less during one day or shift he or she shall be paid the higher rate for the time so worked.

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