Line Information Database 9.1 LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, e-Tel must purchase appropriate signaling links pursuant to Section 10 of this Attachment. LIDB contains records associated with End User Line Numbers and Special Billing Numbers. LIDB accepts queries from other Network Elements and provides appropriate responses. The query originator need not be the owner of LIDB data. LIDB queries include functions such as screening billed numbers that provides the ability to accept Collect or Third Number Billing calls and validation of Telephone Line Number based non-proprietary calling cards. The interface for the LIDB functionality is the interface between BellSouth’s CCS network and other CCS networks. LIDB also interfaces to administrative systems.
Line Information Database (LIDB 9.1 BellSouth will store in its Line Information Database (LIDB) records relating to service only in the BellSouth region. The LIDB Storage Agreement is included in this Attachment as Exhibit B.
Originating Switched Access Detail Usage Data A category 1101XX record as defined in the EMI Telcordia Practice BR-010-200- 010.
Service Information Service Visit Date Mode of service Face-to face, telephone, etc. Responsibility for payment Used to exclude federal govt., WCB, etc. Main and secondary diagnoses ICD10-CA codes Main and other interventions and attributes CCI procedure codes and attributes Type of Anesthetic Identifies the type used for interventions (general, spinal, local, etc.) Provider types NACRS code assigned to provider type (MD, Dentist, RN, etc.) Doctor name and identifier Physician specific information Admit via Ambulance Used if a Client is brought to the service delivery site by ambulance Institution from and institution to Used when a Client is transferred from or to another acute care facility Visit disposition Discharged, admitted, left without being seen, etc. Schedule “D” Appendix 2 Additional Elements Required for Data Management (XXX) Client Identifying Information Province Client‟s Home Province AB, BC, SK, MB, NL, PE, NS, NB, QC, ON, NT, YT, NU, US, OC (Other Country), NR (Unsp. Non-resident) Service Information Facility Code AHS provided code that indicates service being provided. Facility Fee Dollar value of service being provided Alberta Health Physician Fee Billing Code Alberta Health Physician Service Fee code that further defines facility code Regional standard format and submission method remains as is via excel file and email. NOTE: Submission method may be adjusted in accordance with security standards of AHS. Schedule “D” Appendix 3
Product Information EPIZYME recognizes that by reason of, inter alia, EISAI’s status as an exclusive licensee in the EISAI Territory under this Agreement, EISAI has an interest in EPIZYME’s retention in confidence of certain information of EPIZYME. Accordingly, until the end of all Royalty Term(s) in the EISAI Territory, EPIZYME shall keep confidential, and not publish or otherwise disclose, and not use for any purpose other than to fulfill EPIZYME’s obligations, or exercise EPIZYME’s rights, hereunder any EPIZYME Know-How Controlled by EPIZYME or EPIZYME Collaboration Know-How, in each case that are primarily applicable to EZH2 or EZH2 Compounds (the “Product Information”), except to the extent (a) the Product Information is in the public domain through no fault of EPIZYME, (b) such disclosure or use is expressly permitted under Section 9.3, or (c) such disclosure or use is otherwise expressly permitted by the terms and conditions of this Agreement. For purposes of Section 9.3, each Party shall be deemed to be both the Disclosing Party and the Receiving Party with respect to Product Information. For clarification, the disclosure by EPIZYME to EISAI of Product Information shall not cause such Product Information to cease to be subject to the provisions of this Section 9.2 with respect to the use and disclosure of such Confidential Information by EPIZYME. In the event this Agreement is terminated pursuant to Article 12, this Section 9.2 shall have no continuing force or effect, but the Product Information, to the extent disclosed by EPIZYME to EISAI hereunder, shall continue to be Confidential Information of EPIZYME, subject to the terms of Sections 9.1 and 9.3 for purposes of the surviving provisions of this Agreement. Each Party shall be responsible for compliance by its Affiliates, and its and its Affiliates’ respective officers, directors, employees and agents, with the provisions of Section 9.1 and this Section 9.2.
Contractor Sensitive Information 17.1 The Authority must:
Root-‐zone Information Publication ICANN’s publication of root-‐zone contact information for the TLD will include Registry Operator and its administrative and technical contacts. Any request to modify the contact information for the Registry Operator must be made in the format specified from time to time by ICANN at xxxx://xxx.xxxx.xxx/domains/root/.
Voice Information Service Traffic 5.1 For purposes of this Section 5, (a) Voice Information Service means a service that provides [i] recorded voice announcement information or [ii] a vocal discussion program open to the public, and (b) Voice Information Service Traffic means intraLATA switched voice traffic, delivered to a Voice Information Service. Voice Information Service Traffic does not include any form of Internet Traffic. Voice Information Service Traffic also does not include 555 traffic or similar traffic with AIN service interfaces, which traffic shall be subject to separate arrangements between the Parties. Voice Information Service Traffic is not subject to Reciprocal Compensation charges under Section 7 of the Interconnection Attachment.
COMMERCIALLY SENSITIVE INFORMATION 1. The Authority acknowledges that the Contractor has requested that the following information be treated as Commercially Sensitive Information; Document Page Number Section Condition or Paragraph Number Explanation of harm which may result from disclosure and time period applicable to sensitivity.
Operator Materials Operator retains all right, title and interest in and to any and all of Operator’s software, materials, tools, forms, documentation, training and implementation materials and intellectual property (“Operator Materials”). Operator grants to the LEA a personal, nonexclusive license to use the Operator Materials for its own non-commercial, incidental use as set forth in the Service Agreement. Operator represents that it has all intellectual property rights necessary to enter into and perform its obligations in this DPA and the Service Agreement, warrants to the District that the District will have use of any intellectual property contemplated by the Service Agreement free and clear of claims of any nature by any third Party including, without limitation, copyright or patent infringement claims, and agrees to indemnify the District for any related claims.
