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.
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. 3.1.2 The exchange of depersonalised quantitative or aggregate qualitative information is applicable where such information can be used to facilitate strategic planning and performance review between the partner agencies in Lincolnshire MAPPA. 3.1.3 The partners to this agreement may share the following depersonalised information:  Statistics on offenders managed under the arrangements, by MAPPA category and management level  Statistical performance data (key performance indicators) as prescribed from time to time by the Secretary of State for Justice  Statistical data prescribed by the Secretary of State for publication as public statistics, including serious further offences  ViSOR Management Information Reports  Aggregate audit data  Diversity data in relation to the above  Statistics on registered sexual offenders within the Area, including offenders wanted/missing or in breach of requirements  Statistics on actions taken in respect of those offenders in breach of requirements  Statistics on the number of civil preventative orders (Sexual Offences Prevention Orders; Violent Offender Orders; Risk of Sexual Harm Orders; Anti Social Behaviour Orders) etc in relation to relevant offenders  Statistics on ‘other’ offenders included under the arrangements  Statistics on the review of MAPPA eligible offenders managed at XXXX Level 1  Statistics on Serious Further Offences charged against offenders subject to the arrangements, by MAPPA Category and management level  Outcomes from Serious Further Offences charged  Local crime statistics relevant to the purposes of the arrangements  Diversity data in relation to the above  Statistics on registered sexual offenders jointly managed with the Police  Statistics on violent offenders and other sexual offenders identified and managed  Statistics on ‘other’ MAPPA offenders managed  Statistics on the review of MAPPA eligible offenders managed at XXXX Level 1  Statistics on the number of eligible offenders recalled to prison for breach of Licence or notice of supervision requirements, by MAPPA category and management level  Statistics on Serious Further Offences charged against offenders subject to the arrangements, by MAPPA Category and management level  Outcomes from Serious Further Offences...

Related to Routine Information Sharing- Depersonalised Data

  • Line Information Database LIDB is a transaction-oriented database accessible through Common Channel Signaling (CCS) networks. For access to LIDB, ONS 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/.

  • 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 C. 9.2 BellSouth will provide LIDB Storage upon written request to <<customer_name>>’s Account Manager stating a requested activation date.

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

  • 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. 5.2 If a ECI Customer is served by resold Verizon dial tone line Telecommunications Service or a Verizon Local Switching UNE, to the extent reasonably feasible, Verizon will route Voice Information Service Traffic originating from such Service or UNE to the appropriate Voice Information Service connected to Verizon’s network unless a feature blocking such Voice Information Service Traffic has been installed. For such Voice Information Service Traffic, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its Customer. 5.3 ECI shall have the option to route Voice Information Service Traffic that originates on its own network to the appropriate Voice Information Service connected to Verizon’s network. In the event ECI exercises such option, ECI will establish, at its own expense, a dedicated trunk group to the Verizon Voice Information Service serving switch. This trunk group will be utilized to allow ECI to route Voice Information Service Traffic originated on its network to Verizon. For such Voice Information Service Traffic, unless ECI has entered into a written agreement with Verizon under which ECI will collect from ECI’s Customer and remit to Verizon the Voice Information Service provider’s charges, ECI shall pay to Verizon without discount any Voice Information Service provider charges billed by Verizon to ECI. ECI shall pay Verizon such charges in full regardless of whether or not ECI collects such charges from its own Customer.

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

  • Substance Abuse Treatment Information Substance abuse treatment information shall be maintained in compliance with 42 C.F.R. Part 2 if the Party or subcontractor(s) are Part 2 covered programs, or if substance abuse treatment information is received from a Part 2 covered program by the Party or subcontractor(s).

  • User Information Any user or usage data or information collected via Station’s digital properties or related to Station’s digital properties, or any information collected from websites operated by Station’s affiliates under this Agreement, shall be the property of Station and/or such affiliates. Advertiser shall have no rights in such information by virtue of this Agreement.

  • Handling Sensitive Personal Information and Breach Notification A. As part of its contract with HHSC Contractor may receive or create sensitive personal information, as section 521.002 of the Business and Commerce Code defines that phrase. Contractor must use appropriate safeguards to protect this sensitive personal information. These safeguards must include maintaining the sensitive personal information in a form that is unusable, unreadable, or indecipherable to unauthorized persons. Contractor may consult the “Guidance to Render Unsecured Protected Health Information Unusable, Unreadable, or Indecipherable to Unauthorized Individuals” issued by the U.S. Department of Health and Human Services to determine ways to meet this standard. B. Contractor must notify HHSC of any confirmed or suspected unauthorized acquisition, access, use or disclosure of sensitive personal information related to this Contract, including any breach of system security, as section 521.053 of the Business and Commerce Code defines that phrase. Contractor must submit a written report to HHSC as soon as possible but no later than 10 business days after discovering the unauthorized acquisition, access, use or disclosure. The written report must identify everyone whose sensitive personal information has been or is reasonably believed to have been compromised. C. Contractor must either disclose the unauthorized acquisition, access, use or disclosure to everyone whose sensitive personal information has been or is reasonably believed to have been compromised or pay the expenses associated with HHSC doing the disclosure if: 1. Contractor experiences a breach of system security involving information owned by HHSC for which disclosure or notification is required under section 521.053 of the Business and Commerce Code; or 2. Contractor experiences a breach of unsecured protected health information, as 45 C.F.R. §164.402 defines that phrase, and HHSC becomes responsible for doing the notification required by 45 C.F.R. §164.404. HHSC may, at its discretion, waive Contractor's payment of expenses associated with HHSC doing the disclosure.

Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!