Information Sharing Process Sample Clauses

Information Sharing Process. This agreement has been formulated to facilitate the exchange of information between the partners identified in this agreement at point 8 (D.A.N.S SPoC’s). It is however incumbent on all partners to recognise that any information shared must be justified on the merits of each case. Bedfordshire Police in line with The General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Luton will send via the secure e-mail system to Bedford Borough Integrated front door the domestic incident referral report and DASH (Domestic Abuse, Stalking and Honour Based Violence) risk assessment form, for all domestic abuse incidents with children recorded. Bedford Borough Children’s Services, in line with The General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Luton, will share where appropriate to do so the following information (which has been extracted from the referral report and DASH) with Bedford Borough Schools/Post 16 Providers who have signed up to the information sharing agreement: • Childs/young persons name • Date of incident • Type of Incident • Rating of incident (risk) Bedford Borough Schools/Post 16 Providers, in line with The General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Luton, will only share information with relevant staff in the School/Post 16 Provider staff on a need to know basis. Relevant staff may include but are not limited to: a School Safeguarding Lead or nominated Officer, a School Nurse or Pastoral Worker or a Counsellor, a Head Teacher or Form Tutor, a College Tutor or Welfare Officer and on a need to know basis, with the aim to observe or support the individual affected. Once information has been received by the nominated D.A.N.S officers at the educational setting, they will become the responsible parties for holding and disseminating the information to specific and relevant member/s of staff who need to know and may be identified in the list above.
AutoNDA by SimpleDocs
Information Sharing Process. 8.1 Information will be shared using the following methods: Secure email: Relevant project information will be disclosed via secure electronic means on a monthly basis. 8.2 Information sharing may be shared on an ad hoc basis when necessary. Ad hoc information should be shared using the following procedure: Handling Requests for ad hoc Information - requests for information from the project will be handled and logged on the project plan master document held by the partners. Decisions regarding responses will also be recorded.
Information Sharing Process. 9.1 Relevant photographs will be supplied by Lincolnshire Police to members of the Cycle Watch Scheme on a regular basis, providing that they are supported with a Form B (P698B) - Response to Request for Information, which must be retained by the Police SPoC within the file created for such purpose.
Information Sharing Process. 9.1 Relevant photographs will be supplied by Lincolnshire Police to members of the Caravan Park Watch Scheme on a regular basis, providing that they are supported with a Form B (P698B) - Response to Request for Information, which must be retained by the Police SPoC within the file created for such purpose.
Information Sharing Process. This agreement has been formulated to facilitate the exchange of information between the Parties identified in this agreement. It is however, incumbent on all Parties to recognise that any information shared must be justified on the merits of each case. The Police in line with the General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Bedford Borough will send, via the secure e-mail system (PNN), to the relevant education establishment the Domestic Incident or Missing Episode Referral Report; for all domestic abuse incidents and Missing Episodes with children recorded, for the previous 24 hours on a daily basis in a timely manner. The Council, in line with the General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Bedford Borough, will provide read only access to Bedfordshire Police to Children’s Services systems to enable research to identify: - • School associated with relevant child • Identification of CP Plan, CIN, Children’s Services or Early Help involvement • Siblings relevant to the child and the incident to be referred. The School, in line with the General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Bedford Borough, will only share information with relevant staff in the School on a need to know basis. Relevant staff may include but are not limited to: a School Safeguarding Lead, Nominated Op Encompass Single Point Of Contact (SPOC), School Nurse, Pastoral Worker, Counsellor, Head Teacher, Form Tutor, College Tutor, or Welfare Officer and with the aim to observe or support the individual affected. Once information has been received by the Nominated Op Encompass SPOC at the School, they will become the responsible party for holding and disseminating the information to specific and relevant member(s) of staff who need to know and may be identified in the list above. There is no requirement for schools to further refer this Op Encompass information to the MASH as this will be completed by the Police based on their agreed thresholds. The team responsible for Elective Home Schooled (EHE) Children, in line with the General Protocol for Sharing Information between Partner Organisations in Bedfordshire and Bedford Borough, will receive information from the Police in line with process. EHE parents will be provided information regarding their engagement in this process via guidance provided to new parents engaging in EHE and via the EHE website info...
Information Sharing Process. 9.1 On a daily basis members from the Lincolnshire Fire & Rescue Service control room, complete a Form ARSON 01 when Arson is suspected. This form will then be e-mailed via secure methods to a member of the Arson Task Force.
Information Sharing Process. 8.1 Information will be shared using the following methods: ➢ Secure email: Relevant project information will be disclosed via secure electronic means on a monthly basis.
AutoNDA by SimpleDocs
Information Sharing Process. The primary points of contact (POCs) for the implementation of this Agreement are the DOE Director, Office of Nuclear Safety within the Office of Environment, Health, Safety and Security and the NRC Director, Division of Fuel Cycle Safety and Safeguards, within the Office of Nuclear Material Safety and Safeguards. These primary POCs will determine and mutually agree on the specific form and content of information exchanges that would be beneficial to the agencies. The information exchanges can occur through meetings, sharing of documents, or reviewing of documents. The information exchanged can include operating experience, nuclear safety research and development results, or analysis of such information. The primary POCs may each designate individuals within their respective organizations to facilitate specific exchanges. The agencies shall prepare joint summaries which document each mutually agreed information exchange.
Information Sharing Process 

Related to Information Sharing Process

  • Third Party Proprietary Data The Disclosing Party's Third Party Proprietary Data, if any, will be identified in a separate technical document.

  • Access Toll Connecting Trunk Group Architecture 9.2.1 If CBB chooses to subtend a Verizon access Tandem, CBB’s NPA/NXX must be assigned by CBB to subtend the same Verizon access Tandem that a Verizon NPA/NXX serving the same Rate Center Area subtends as identified in the LERG.

  • Joint Network Implementation and Grooming Process Upon request of either Party, the Parties shall jointly develop an implementation and grooming process (the “Joint Grooming Process” or “Joint Process”) which may define and detail, inter alia:

  • Hiring Process i. School District and Teach For America will collaborate in good faith to facilitate the efficient hiring of individual Teachers, in accordance with the School District’s established District hiring practices.

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

  • SERVICE MONITORING, ANALYSES AND ORACLE SOFTWARE 11.1 We continuously monitor the Services to facilitate Oracle’s operation of the Services; to help resolve Your service requests; to detect and address threats to the functionality, security, integrity, and availability of the Services as well as any content, data, or applications in the Services; and to detect and address illegal acts or violations of the Acceptable Use Policy. Oracle monitoring tools do not collect or store any of Your Content residing in the Services, except as needed for such purposes. Oracle does not monitor, and does not address issues with, non-Oracle software provided by You or any of Your Users that is stored in, or run on or through, the Services. Information collected by Oracle monitoring tools (excluding Your Content) may also be used to assist in managing Oracle’s product and service portfolio, to help Oracle address deficiencies in its product and service offerings, and for license management purposes.

  • Personal Data, Confidentiality, Recording of Telephone Calls and Records 22.1. The Company may collect client information directly from the Client (in his completed Account Opening Application Form or otherwise) or from other persons including, for example, the credit reference agencies, fraud prevention agencies, banks, other financial institutions, third authentication service providers and the providers of public registers.

  • Information Access Each Party (“Disclosing Party”) shall make available to another Party (“Requesting Party”) information that is in the possession of the Disclosing Party and is necessary in order for the Requesting Party to: (i) verify the costs incurred by the Disclosing Party for which the Requesting Party is responsible under this Agreement; and (ii) carry out its obligations and responsibilities under this Agreement. The Parties shall not use such information for purposes other than those set forth in this Article 25.1 of this Agreement and to enforce their rights under this Agreement.

  • Sensitive data Where the transfer involves personal data revealing racial or ethnic origin, political opinions, religious or philosophical beliefs, or trade union membership, genetic data, or biometric data for the purpose of uniquely identifying a natural person, data concerning health or a person’s sex life or sexual orientation, or data relating to criminal convictions and offences (hereinafter ‘sensitive data’), the data importer shall apply the specific restrictions and/or additional safeguards described in Annex I.B.

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

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