Walkie-talkie device information Sample Clauses

Walkie-talkie device information. We may collect your walkie-talkie device attribute, activation status and board ID, firmware version number to activate the walkie-talkie, implement firmware upgrades, and enable you to operate your walkie- talkie through the app. If you need to delete the stored information, you can do the following:
AutoNDA by SimpleDocs

Related to Walkie-talkie device information

  • 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

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

  • Notice Information Notice identifier/version: 4b0dc758­f0da­45e7­b7bb­8b9faca6d8be ­ 01 Form type: Competition Notice type: Contract or concession notice – standard regime Notice dispatch date: 2024­02­01Z 23:32:31Z Languages in which this notice is officially available: English

  • Service Information Pages Verizon shall include all VarTec NXX codes associated with the geographic areas to which each directory pertains, to the extent it does so for Verizon’s own NXX codes, in any lists of such codes that are contained in the general reference portion of each directory. VarTec’s NXX codes shall appear in such lists in the same manner as Verizon’s NXX information. In addition, when VarTec is authorized to, and is offering, local service to Customers located within the geographic area covered by a specific directory, at VarTec’s request, Verizon shall include, at no charge, in the “Customer Guide” or comparable section of the applicable alphabetical directories, VarTec’s critical contact information for VarTec’s installation, repair and Customer service, as provided by VarTec. Such critical contact information shall appear alphabetically by local exchange carrier and in accordance with Verizon’s generally applicable policies. VarTec shall be responsible for providing the necessary information to Verizon by the applicable close date for each affected directory.

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

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

  • - CLEC INFORMATION CLEC agrees to work with Qwest in good faith to promptly complete or update, as applicable, Qwest’s “New Customer Questionnaire” to the extent that CLEC has not already done so, and CLEC shall hold Qwest harmless for any damages to or claims from CLEC caused by CLEC’s failure to promptly complete or update the questionnaire.

  • Confidential System Information HHSC prohibits the unauthorized disclosure of Other Confidential Information. Grantee and all Grantee Agents will not disclose or use any Other Confidential Information in any manner except as is necessary for the Project or the proper discharge of obligations and securing of rights under the Contract. Grantee will have a system in effect to protect Other Confidential Information. Any disclosure or transfer of Other Confidential Information by Xxxxxxx, including information requested to do so by HHSC, will be in accordance with the Contract. If Grantee receives a request for Other Confidential Information, Xxxxxxx will immediately notify HHSC of the request, and will make reasonable efforts to protect the Other Confidential Information from disclosure until further instructed by the HHSC. Grantee will notify HHSC promptly of any unauthorized possession, use, knowledge, or attempt thereof, of any Other Confidential Information by any person or entity that may become known to Grantee. Grantee will furnish to HHSC all known details of the unauthorized possession, use, or knowledge, or attempt thereof, and use reasonable efforts to assist HHSC in investigating or preventing the reoccurrence of any unauthorized possession, use, or knowledge, or attempt thereof, of Other Confidential Information. HHSC will have the right to recover from Grantee all damages and liabilities caused by or arising from Grantee or Grantee Agents’ failure to protect HHSC’s Confidential Information as required by this section. IN COORDINATION WITH THE INDEMNITY PROVISIONS CONTAINED IN THE UTC, Xxxxxxx WILL INDEMNIFY AND HOLD HARMLESS HHSC FROM ALL DAMAGES, COSTS, LIABILITIES, AND EXPENSES (INCLUDING WITHOUT LIMITATION REASONABLE ATTORNEYS’ FEES AND COSTS) CAUSED BY OR ARISING FROM Grantee OR Grantee AGENTS FAILURE TO PROTECT OTHER CONFIDENTIAL INFORMATION. Grantee WILL FULFILL THIS PROVISION WITH COUNSEL APPROVED BY HHSC.

  • Contractor Sensitive Information 17.1 The Authority must:

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