Implementation Barriers Sample Clauses

Implementation Barriers. Participants identified numerous issues that are likely to affect successful implementation of passive remote monitoring technology. The physical safety concerns raised, relating to ligature risk and use as a weapon, appeared to be linked to a specific design characteristic (elastic armband) of a device presented during the focus groups. This highlights the importance of considering the physical design of passive remote monitoring technology intended for use in inpatient services, where physical safety and risk of self-harm are management priorities. Concerns were raised that continuous monitoring may exacerbate symptoms of paranoia, consistent with concerns raised in Bourla et al. (2018) regarding exacerbating symptoms of anxiety. While previous studies in the community indicate the acceptability of passive remote monitoring for individuals with psychosis (Xxxxx et al., 2018, 2019; Xxxxx et al., 2018), it may be a pertinent issue for those involuntarily admitted to inpatient services and experiencing loss of control and restrictive practices (XxXxxxxxxx et al., 2018). Establishing trust with users beforehand and evaluating whether adverse effects do arise as a consequence of monitoring, is therefore likely to be integral to successful implementation. Consistent with previous research among staff (Xxxxxxxxx et al., 2019; Huckvale et al., 2019) and service users (Xxxxxxxx et al., 2018), participants expressed data privacy concerns. The specific concerns related to three areas where they would require adequate assurance to be comfortable using passive remote monitoring: data storage, security, and accessibility by third parties. Addressing these concerns in the long term will require transparency from digital health companies about the procedures in place for handling user data, and to ensure that users have access to this information. In the shorter term, participants reported that staff could play an important role in providing reassurance to users. The suggestion that staff could lead by example by trialling the devices themselves reflects the role of staff as positive role models in inpatient services (Xxxxxxxx & Xxxxx, 2018) and is a practical approach to alleviating user concerns. Participants expressed concern that incorporating passive remote monitoring technology into their working practice might negatively affect their existing workload. Like Xxxxx et al. (2019), participants were concerned with the potential burden of handling and analysing large ...
AutoNDA by SimpleDocs

Related to Implementation Barriers

  • Implementation Services Vendor shall provide the Implementation Services, if any, described in Exhibit A. The Services Fees for any Implementation Services shall be described in Exhibit A.

  • Project Implementation Manual The Recipient, through the PCU, shall: (i) take all action required to carry out Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4 (ii) of the Project in accordance with the provisions and requirements set forth or referred to in the Project Implementation Manual; (ii) submit recommendations to the Association for its consideration for changes and updates of the Project Implementation Manual as they may become necessary or advisable during Project implementation in order to achieve the objective of Parts 1.1, 1.3, 1.4, 2, 3.1(b), 3.2, 3.3 and 4(ii) of the Project; and (iii) not assign, amend, abrogate or waive the Project Implementation Manual or any of its provisions without the Association’s prior agreement. Notwithstanding the foregoing, if any of the provisions of the Project Implementation Manual is inconsistent with the provisions of this Agreement, the provisions of this Agreement shall prevail and govern.

  • Project Implementation The Borrower shall:

  • Implementation and Review The Parties shall consult annually, or as otherwise agreed, to review the implementation of this Chapter and consider other matters of mutual interest affecting trade in services. (10) 10 Such consultations will be addressed under Article 170 (Free Trade Commission) of Chapter 14 (Administration of the Agreement).

  • Implementation Arrangements Institutional Arrangements

  • COOPERATION IN IMPLEMENTATION On demand of the other Spouse and without undue delay or expense, each Spouse shall execute, acknowledge, or deliver any instrument, furnish any information, or perform any other acts reasonably necessary to carry out the provisions of this Agreement. If a Spouse fails to execute any document as required by this provision, the court may appoint the court clerk or his or her authorized designee to execute the document on that Xxxxxx’s behalf.

  • Implementation Plan The Authority shall cause to be prepared an Implementation Plan meeting the requirements of Public Utilities Code Section 366.2 and any applicable Public Utilities Commission regulations as soon after the Effective Date as reasonably practicable. The Implementation Plan shall not be filed with the Public Utilities Commission until it is approved by the Board in the manner provided by Section 4.9.

  • Procedures for Providing NP Through Full NXX Code Migration Where a Party has activated an entire NXX for a single Customer, or activated at least eighty percent (80%) of an NXX for a single Customer, with the remaining numbers in that NXX either reserved for future use by that Customer or otherwise unused, if such Customer chooses to receive Telephone Exchange Service from the other Party, the first Party shall cooperate with the second Party to have the entire NXX reassigned in the LERG (and associated industry databases, routing tables, etc.) to an End Office operated by the second Party. Such transfer will be accomplished with appropriate coordination between the Parties and subject to appropriate industry lead times for movements of NXXs from one switch to another. Neither Party shall charge the other in connection with this coordinated transfer.

  • Implementation Report Within 150 days after the Effective Date, Ensign Group shall submit a written report to OIG summarizing the status of its implementation of the requirements of this CIA (Implementation Report). The Implementation Report shall, at a minimum, include: 1. the name, address, phone number, and position description of the Compliance Officer required by Section III.A, and a summary of other noncompliance job responsibilities the Compliance Officer may have; 2. the names and positions of the members of the Compliance Committee required by Section III.A; 3. the names and positions of the members of the Board of Directors who are responsible for satisfying the Board of Directors compliance obligations described in Section III.A.3; 4. a copy of Ensign Group’s Code of Conduct required by Section III.B.1; 5. the number of individuals required to complete the Code of Conduct certification required by Section III.B.1, the percentage of individuals who have completed such certification, and an explanation of any exceptions (the documentation supporting this information shall be available to OIG upon request); 6. a summary of all Policies and Procedures required by Section III.B (copies of the Policies and Procedures shall be made available to OIG upon request); 7. the following information regarding each type of training required by Section III.C: a. a description of such training, including a summary of the topics covered, the length of sessions, and a schedule of training sessions; b. the number of individuals required to be trained, percentage of individuals actually trained, and an explanation of any exceptions. A copy of all training materials and the documentation supporting this information shall be made available to OIG upon request. 8. a description of the Disclosure Program required by Section III.E; 9. the following information regarding the IRO(s): (a) identity, address, and phone number; (b) a copy of the engagement letter; (c) information to demonstrate that the IRO has the qualifications outlined in Appendix A to this CIA; (d) a summary and description of any and all current and prior engagements and agreements between Ensign Group and the IRO; and (e) a certification from the IRO regarding its professional independence and objectivity with respect to Ensign Group; 10. a description of the process by which Ensign Group fulfills the requirements of Section III.F regarding Ineligible Persons; 11. a list of all of Ensign Group’s locations (including locations and mailing addresses); the corresponding name under which each location is doing business; the corresponding phone numbers and fax numbers; each location’s Medicare and state Medicaid program provider number and/or supplier number(s); and the name and address of each Medicare and state Medicaid program contractor to which Ensign Group currently submits claims; 12. a description of Ensign Group’s corporate structure, including identification of any parent and sister companies, subsidiaries, and their respective lines of business; and

  • Trunk Group Architecture and Traffic Routing 5.2.1 The Parties shall jointly establish Access Toll Connecting Trunks between CLEC and CBT by which they will jointly provide Tandem-transported Switched Exchange Access Services to Interexchange Carriers to enable such Interexchange Carriers to originate and terminate traffic from and to CLEC's Customers. 5.2.2 Access Toll Connecting Trunks shall be used solely for the transmission and routing of Exchange Access and non-translated Toll Free traffic (e.g., 800/888) to allow CLEC’s Customers to connect to or be connected to the interexchange trunks of any Interexchange Carrier that is connected to the CBT access Tandem. 5.2.3 The Access Toll Connecting Trunks shall be one-way or two-way trunks, as mutually agreed, connecting an End Office Switch that CLEC utilizes to provide Telephone Exchange Service and Switched Exchange Access Service in the given LATA to an access Tandem Switch CBT utilizes to provide Exchange Access in the LATA.

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