Operational Protocol Clause Samples

Operational Protocol. Before the State may claim FFP for Populations 8 and 9, it must submit an operational protocol documenting the eligibility processes and procedures used to transition the adults without children population from the State-only funded MinnesotaCare program into the Demonstration. Through this protocol, the State will assure it complies with all Federal law, including but not limited to, citizenship verification and identification of MinnesotaCare enrollees who become incarcerated between eligibility determinations.
View SourceView Similar (2)
Operational Protocol. The Operational Protocol will be reviewed and modified as deemed necessary at a meeting of the Data Security Coordinator, the GRCC, the corresponding BU Representative(s) and any other personnel responsible for the security of Education Records, Teacher or Principal Data, and End User Confidential Information. The review meeting will take place at least annually. Any modifications to the Operational Protocol will be published in an updated version of the WISPP. At the time of publication, a copy of the WISPP will be distributed to all current HSS employees and to new hires on their date of employment.
View SourceView Similar (2)
Operational Protocol. INTRODUCTION This protocol describes the agreement for data sharing between the Scottish Prison Service (SPS) and NHS Scotland, hereafter referred to as ‘partners’. Effective data sharing is the key to multi-agency working in any sphere. The partners are committed to the partnership approach and recognise the invaluable contribution of collaborative working. This protocol has been drafted to assist in identifying the key procedures and safeguards that will be used to allow the legal sharing of information between the partner agencies in providing joint services to their users. DATA SHARING PROCEDURES Only the minimum necessary personal information will be shared on a need-to-know basis and only when it supports the delivery of the purposes and functions set out in this agreement. Personal information will only be collected using the approved collection methods, ensuring the required information is complete and up-to-date. All reasonable steps must be taken to ensure that anyone who has received information is notified of any relevant changes and if any inaccuracies are found the necessary amendments will be made. Decisions about prisoners should never be made by referring to known inaccurate, incomplete or out-of-date information. Staff must also follow their own organisation’s procedures relating to the handling of personal information. Please note: Staff should not hesitate to share personal information in order to prevent abuse or serious harm, in an emergency or in life-or-death situations. If there are concerns relating to capacity, support or protection or issues relating to age or gender, the relevant organisational procedures must be followed. Information will be shared between SPS and NHS through a number of different processes: Data Transferred from SPS to PSD – to allow PSD to identify prisoners currently serving prison sentences of 6 years or more to prevent their medical records from being destroyed. SPS hosting the GPASS system – SPS will continue to host the NHS GPASS system for a transition period until GPASS is no longer required. Data transferred electronically from PR2 to NHS eLinks Ensemble - Prisoners’ personal demographic data will be extracted from PR2 (the SPS prisoner records database) every 15 minutes and sent via secure FTP on a Restricted network to the NHS eLinks Ensemble, to enable patient registration and recovery of records. It is intended that the NHS will automatically electronically acknowledge receipt of the data, althou...
View Source
Operational Protocol. (a) Not later than ninety (90) days prior to the Planned Completion Date, Project Co shall submit to HMQ and the Independent Certifier a draft Operational Protocol which shall be reviewed by HMQ in accordance with the Review Procedure. (b) Project Co shall comply with all of its obligations with respect to the Operational Protocol.
View Source
Operational Protocol. An Operational Protocol will be developed by DADS and the BON in consultation with the Advisory Committee to detail the:  Specifics of implementing the pilot program referenced in Article II;  Requirements for conducting the LVN on call pilot program;  Requirements for data collection and evaluation for the pilot program; and  Actions to be taken when data indicate that adverse consequences are occurring because of the implementation of the pilot program.
View Source

Related to Operational Protocol

  • CONTRACT WORK HOURS AND SAFETY STANDARDS As per the Contract Work Hours and Safety Standards Act (40 U.S.C. 3701-3708), where applicable, all Customer Purchase Orders in excess of ,000 that involve the employment of mechanics or laborers must include a provision for compliance with 40 U.S.C. 3702 and 3704, as supplemented by Department of Labor regulations (29 CFR Part 5). Under 40 U.S.C. 3702 of the Act, each contractor must be required to compute the wages of every mechanic and laborer on the basis of a standard work week of 40 hours. Work in excess of the standard work week is permissible provided that the worker is compensated at a rate of not less than one and a half times the basic rate of pay for all hours worked in excess of 40 hours in the work week. The requirements of 40 U.S.C. 3704 are applicable to construction work and provide that no laborer or mechanic must be required to work in surroundings or under working conditions which are unsanitary, hazardous or dangerous. These requirements do not apply to the purchases of supplies or materials or articles ordinarily available on the open market, or contracts for transportation or transmission of intelligence.

  • Technical Standards The technical standards used as a requirement for this Call- Off Contract are set out in the Supplier’s G-Cloud 12 Service Description document. Service level agreement: The service level and availability criteria required for this Call- Off Contract are set out in the Supplier’s Service Definition. Onboarding The onboarding plan for this Call-Off Contract is set out in the “Discovery” activity within the Supplier’s proposal for these services. Offboarding The offboarding plan for this Call-Off Contract is set out in the “Production Environment Enabled” activity within the Supplier’s proposal for these services. Collaboration agreement Not applicable. Limit on Parties’ liability The annual total liability of either Party for all Property Defaults will not exceed £1million. The annual total liability for Buyer Data Defaults will not exceed 125% of the Charges payable by the Buyer to the Supplier during the Call-Off Contract Term (whichever is the greater). The annual total liability for all other Defaults will not exceed the greater of 125% of the Charges payable by the Buyer to the Supplier during the Call-Off Contract Term (whichever is the greater). Insurance The insurance(s) required will be: ● a minimum insurance period of 6 years following the expiration or Ending of this Call-Off Contract; ● professional indemnity insurance cover to be held by the Supplier and by any agent, Subcontractor or consultant involved in the supply of the G-Cloud Services. This professional indemnity insurance cover will have a minimum limit of indemnity of £1,000,000 for each individual claim or any higher limit the Buyer requires (and as required by Law); ● employers' liability insurance with a minimum limit of £5,000,000 or any higher minimum limit required by Law. Force majeure A Party may End this Call-Off Contract if the Other Party is affected by a Force Majeure Event that lasts for more than 5 consecutive days. Audit The following Framework Agreement audit provisions will be incorporated under clause 2.1 of this Call-Off Contract to enable the Buyer to carry out audits: - Clauses 7.4 to 7.13 of the Framework Agreement. ▇▇▇▇▇’s responsibilities The Buyer is responsible for providing the supplier with access to the MHCLG O365 tenant and a laptop if required. Buyer’s equipment The Buyer’s equipment to be used with this Call-Off Contract includes a laptop if required. (A laptop may be required for access to the MHCLG O365 tenant).

  • Safety Standards Performance of the Contract for all commodities or contractual services must comply with requirements of the Occupational Safety and Health Act and other applicable State of Florida and federal requirements.

  • Quality Management System Supplier hereby undertakes, warrants and confirms, and will ensue same for its subcontractors, to remain certified in accordance with ISO 9001 standard or equivalent. At any time during the term of this Agreement, the Supplier shall, if so instructed by ISR, provide evidence of such certifications. In any event, Supplier must notify ISR, in writing, in the event said certification is suspended and/or canceled and/or not continued.