COVID-19 Employees of Contractor and/or persons working on its behalf, including, but not limited to, subcontractors (collectively, “Contractor Personnel”), while performing services under this Agreement and prior to interacting in person with City employees, contractors, volunteers, or members of the public (collectively, “In-Person Services”) must be fully vaccinated against the novel coronavirus 2019 (“COVID-19”). “Fully vaccinated” means that 14 or more days have passed since Contractor Personnel have received the final dose of a two-dose COVID-19 vaccine series (Moderna or Pfizer-BioNTech) or a single dose of a one-dose COVID-19 vaccine (Xxxxxxx & Xxxxxxx/Xxxxxxx) and all booster doses recommended by the Centers for Disease Control and Prevention. Prior to assigning Contractor Personnel to perform In-Person Services, Contractor shall obtain proof that such Contractor Personnel have been fully vaccinated. Contractor shall retain such proof for the document retention period set forth in this Agreement. Contractor shall grant medical or religious exemptions (“Exemptions”) to Contractor Personnel as required by law. If Contractor wishes to assign Contractor Personnel with Exemptions to perform In- Person Services, Contractor shall require such Contractor Personnel to undergo weekly COVID-19 testing, with the full cost of testing to be borne by Contractor. If Contractor Personnel test positive, they shall not be assigned to perform In-Person Services or, to the extent they have already been performing In-Person Services, shall be immediately removed from those assignments. Furthermore, Contractor shall immediately notify City if Contractor Personnel performing In-Person Services (1) have tested positive for or have been diagnosed with COVID-19, (2) have been informed by a medical professional that they are likely to have COVID-19, or (3) meet the criteria for isolation under applicable government orders.
Digital Health The HSP agrees to:
(a) assist the LHIN to implement provincial Digital Health priorities for 2017-18 and thereafter in accordance with the Accountability Agreement, as may be amended or replaced from time to time;
(b) comply with any technical and information management standards, including those related to data, architecture, technology, privacy and security set for health service providers by MOHLTC or the LHIN within the timeframes set by MOHLTC or the LHIN as the case may be;
(c) implement and use the approved provincial Digital Health solutions identified in the LHIN Digital Health plan;
(d) implement technology solutions that are compatible or interoperable with the provincial blueprint and with the LHIN Cluster Digital Health plan; and
(e) include in its annual Planning Submissions, plans for achieving Digital Health priority initiatives.
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.
WASHINGTON’S ELECTRONIC BUSINESS SOLUTION (WEBS). Contractor represents and warrants that Contractor is registered in Washington’s Electronic Business Solution (WEBS), Washington’s contract registration system and that, all of Contractor’s information therein is current and accurate and that throughout the term of this Contract, Contractor shall maintain an accurate profile in WEBS.
AT&T-21STATE made an offer (the “Offer”) to all Telecommunications carriers to exchange Section 251(b)(5) Traffic, Non-toll VoIP-PSTN Traffic and ISP-Bound Traffic pursuant to the terms and conditions of the FCC’s interim ISP terminating compensation plan of the FCC’s Order on Remand and Report and Order, In the Matter of Implementation of the Local Competition Provisions in the Telecommunications Act of 1996, Intercarrier Compensation for ISP-Bound Traffic, FCC 01-131, CC Docket Nos. 96-98, 99-68 (rel. April 27, 2001)) (“FCC ISP Compensation Order”) which was remanded but not vacated in WorldCom, Inc. v. FCC, No. 01-1218 (D.C. Cir. 2002).
Telemedicine Services This plan covers clinically appropriate telemedicine services when the service is provided via remote access through an on-line service or other interactive audio and video telecommunications system in accordance with R.I. General Law § 27-81-1. Clinically appropriate telemedicine services may be obtained from a network or non- network provider, and from our designated telemedicine service provider. When you seek telemedicine services from our designated telemedicine service provider, the amount you pay is listed in the Summary of Medical Benefits. When you receive a covered healthcare service from a network or non-network provider via remote access, the amount you pay depends on the covered healthcare service you receive, as indicated in the Summary of Medical Benefits. For information about telemedicine services, our designated telemedicine service provider, and how to access telemedicine services, please visit our website or contact our Customer Service Department.
AT&T-12STATE acknowledges that CLEC may have an embedded base of one-way trunks ordered and installed prior to the Effective Date of this Agreement that were used for termination of CLEC’s Section 251(b)(5)/IntraLATA Toll Traffic to AT&T-12STATE (Embedded Base). To the extent that CLEC has such an Embedded Base, CLEC shall only augment trunk groups in the Embedded Base with the mutual agreement of the Parties. CLEC shall not order any new one-way trunk groups following the Effective Date of this Agreement. Moreover, the Parties agree that the Embedded Base will be converted to two-way trunk groups under the following circumstances:
4.2.1.1 With reasonable notification from AT&T-12STATE and upon AT&T-12STATE’s request, CLEC shall convert all of its Embedded Base to two-way trunks.
4.2.1.2 At any time an Embedded Base trunk group (either originating or terminating) requires augmentation, AT&T-12STATE can require the associated originating and terminating trunks to be converted to a single two-way trunk group prior to the augmentation.
4.2.1.3 When any network changes are to be performed on a project basis (i.e., central office conversions, tandem re-homes, etc.), upon request and reasonable notice by AT&T-12STATE, CLEC will convert all of its Embedded Base affected by the project within the intervals and due dates required by the project parameters.
4.2.1.4 In addition to the foregoing, CLEC may choose, at any time, to convert its Embedded Base to two-way trunk groups.
4.2.1.5 The Parties will coordinate any trunk group migration, trunk group prioritization and implementation schedule. AT&T-12STATE agrees to develop a cutover plan within thirty (30) days of notification to CLEC of the need to convert pursuant to Section 4.2.1.1 above and Section 4.2.1.3 above.
