Routine Information Sharing- Depersonalised Data Sample Clauses

Routine Information Sharing- Depersonalised Data. Depersonalised information is defined as any information, which is provided to another partner in a format in which it is no longer possible to identify an individual. Whenever possible the use and exchange of depersonalised or aggregated information should be considered. This may assist with strategic planning processes with the partners of this information sharing agreement and provide quantitative information to the IOM SIG and Safer Communities Board. The following examples of depersonalised information may be shared: Derbyshire Constabulary recorded crime statistics Derbyshire Constabulary calls for service Derbyshire Substance Misuse Commissioning Team statistics Derby City DAAT statistics HM Prison Service statistics National Probation Service Derbyshire, Leicestershire, Nottinghamshire, and Rutland Community Rehabilitation Company (CRC) The following criteria will apply: • No attempt must be made to identify an individual through the provision of depersonalised information. • Information must not be released to those with a commercial interest in their use. • Requests under the Freedom of Information act must be handled in accordance with the partner agencies documented processes and procedures. • Each partner agency is responsible for making sure there are arrangements in place for the secure storage of information. • Partner agencies should have documented policies for records retention, maintenance and secure waste destruction. • Verification will be made that the information does not conflict with corporate statistics generated by the relevant partner.
Sample 1
AutoNDA by SimpleDocs
Routine Information Sharing- Depersonalised Data. 3.1.1 Depersonalised information is defined as information from a database or other information system which is provided to another agency in a format in which it is no longer possible to identify an individual.
Sample 1

Related to Routine Information Sharing- Depersonalised Data

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

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

  • Exception Where Databases Contain Sufficient Information A Reporting Financial Institution is not required to perform the paper record search described in subparagraph D.2. of this section if the Reporting Financial Institution’s electronically searchable information includes the following:

  • Contractor Information The Contractor will provide up to date information for each of the following in the form and manner specified by OGS:

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

  • Patient Information Each Party agrees to abide by all laws, rules, regulations, and orders of all applicable supranational, national, federal, state, provincial, and local governmental entities concerning the confidentiality or protection of patient identifiable information and/or patients’ protected health information, as defined by any other applicable legislation in the course of their performance under this Agreement.

  • Correction of Personal Information 8. Within 5 business days of receiving a written direction from the Public Body to correct or annotate any personal information, the Contractor must annotate or correct the information in accordance with the direction.

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

  • Contractor Sensitive Information 17.1 The Authority must:

  • Privacy Statement 6.1. The Parties agree to keep all information related to the signing and fulfillment of this Agreement confidential, and not to disclose it to any third parties, except for subcontractors involved in this agreement, unless prior written consent is obtained from the other Party. Should subcontractors be engaged under this agreement, they are required to adhere to its terms and conditions.

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