DESCRIPTION AND SCOPE Sample Clauses

DESCRIPTION AND SCOPE. Several factors or their combination may encourage or discourage labour market participation  Contextual factors (linked to the economic and labour market environment)
AutoNDA by SimpleDocs
DESCRIPTION AND SCOPE.  This Framework Agreement covers those persons who encounter difficulties in entering, returning to or integrating into the labour market (OUT) and those who, although in employment, are at risk (IN) of losing their job due to the factors referred to below.  This Framework Agreement does not focus on specific groups.
DESCRIPTION AND SCOPE. 2 4. TERM .............................................. 2 5. TERMINATION ....................................... 2
DESCRIPTION AND SCOPE. Developer is responsible for the preparation, development and submission of a schematic, environmental document, covering the proposed alignment ofan approximate 400 ft. wide strip of land crossing the N.D. Xxxxxx tract from Mines Road (FM 1472) and traversing the property to approximately 0.1 mile east of Beltway Parkway, (as shown on the attached Exhibit A.), which complies with all applicable federal and state environmental laws and regulations, including but not limited to the National Environmental Policy Act, the National Historic Preservation Act of 1966 and the Endangered Species Act of 1973, which require environmental clearance of federal-aid projects for the environmental clearance ofthis Project, to include, written documentation from the appropriate regulatory agency or agencies that all environmental clearances have been obtained. Developer shall coordinate its efforts with Xxxx County's efforts to prepare and submit a single, unified schematic and environmental assessment, pursuant to NEPA, for the remaining alignment ofthe 400 ft. wide strip ofland which crosses the Reuthinger property and as shown on the Localion Map showing the Project Limits in the attached Exhibit "A". City grants a license to Developer to use all documents, including butnot limited to reports, drawings, and schematics that have been developed by City or its consultants for the preparation ofa schematic document and environmental assessment.
DESCRIPTION AND SCOPE. Inclusive labour markets allow and encourage all people of working age to participate in paid work and provide a framework for their development. This Framework Agreement covers those persons who encounter difficulties in entering, returning to or integrating into the labour market and those who, although in employment, are at risk of losing their job due to the factors referred to below. The social partners recognise that these people face different challenges which require adapted measures. This Framework Agreement does not focus on specific groups. Instead it provides a general framework focusing on what can be done to enhance labour market inclusion. Several factors or their combination may encourage or discourage labour market participation. These factors can be contextual, work-related or individual and they may evolve over time. There is no hierarchy between the different factors. 🗸 Contextual factors are linked to the economic and labour market environment. These may be of structural or geographical nature such as employment opportunities, the existence and quality of care facilities and employment services, transport networks or housing, as well as the interplay between fiscal and social policies. 🗸 Work-related factors include amongst others work organisation and work environment, recruitment processes, technological evolution and training policies. 🗸 Individual factors are linked to aspects such as skills, qualification and education levels, motivation, language knowledge, health status and frequent or long unemployment periods.
DESCRIPTION AND SCOPE. Kainos Evolve is a robust electronic document management system that has been optimised to act as an electronic casenote management system. Within UHBristol it is being used to replace the legacy (‘buff’) casenote across all hospitals in the group, removing historical paper from all locations and provide immediate, shared access of patient notes across the Trust and other BNSSG locations. As well as replacing the historical casenote, Evolve is used to collect ‘new’ paper being produced in those areas that have not yet been able to adopt paper-free operation, another aspect of the project that involves Xxxxxx’s clinical noting module and the GDE ‘clinical workstation components described elsewhere. Current position:  Partially funded by Tech Fund 1, the first phases of the roll-out have taken longer than expected because we have encountered an ‘underground’ economy of local notes as we have progressed through the various phases of the Evolve roll-out.  Learning from observation of other Trusts adopting EDMS systems, we have approached this project in an ‘industrial’ manner. This has included the creation of our own in-house scanning bureau, which has scanned over 16m documents since the project commenced in October 2014.  We have rolled out Evolve across St Michael’s Hospital and the Bristol Royal Hospital for Children.  The use of Evolve has helped colleagues to understand the potential impact and increased the appetite for well-designed digital solutions.
DESCRIPTION AND SCOPE. Medway Electronic Prescribing and Medicines Administration is a core module that will contribute to UHBristol’s HIMSS 7≡ and provide an integrated electronic prescribing capability for all general wards and outpatients across the Trust. Developed in partnership between System C and UHBristol, Medway EPMA is a completely new module, fully integrated into Medway and designed with detailed participation between clinical, pharmacy and technical users. The module will replace the paper drug chart and all prescribing and drug admin functions through to automated transfer of TTOs into the Medway-based discharge summary. Current position:  Partially funded by Tech Fund 1, the development process for this product has taken longer than expected but is now in advanced testing stage. Delivery plan:  The System C and UHBristol deployment team have completed a detailed implementation plan for the roll-out of EPMA.  Phase 1 of the roll-out will commence with the pilot of the adult functionality in the Bristol Heart Institute in Q3 17/18, followed by staged roll-out across all adult general wards by the end of Q4 17/18.  Phase 2 includes the delivery of additional technical functions and paediatric prescribing. We are currently agreeing the timescales and detailed scope for this phase, which will be completed by the end of the GDE programme term.
AutoNDA by SimpleDocs
DESCRIPTION AND SCOPE. The development and use of specialist apps associated with the PHR to support patient involvement and self-care for long-term and complex conditions. The initial phase will use an existing project, currently expected to be Cardiac Heart Failure. This will lead the way and inform the future rollout of other condition focused solutions, taking into consideration: • Development of new NMC solutions associated with BNSSG’s STP priorities (e.g. COPD, frail and elderly, MSK). • Additional NMCs already developed elsewhere to be integrated into the core solution (e.g. Southampton’s prostate cancer and IBS apps). Note that additional pathways to be defined STC in collaboration with the Connecting Care Partnership. This programme component will use the CareCentric IDCR and Careflow alerts along with the Microsoft Healthvault platform to deliver the ‘myCareCentric’ solution for patients to use as part of the supported self-care agenda. Along with the patient app the corresponding clinician views will be accessible from within Associated Delivery Milestones: DM1 Initial candidate Long Term Condition agreed DM2 Pathway scope agreed build / configuration in progress and est. 20 – 50 pilot patients recruited DM3 Pilot Commenced DM4 Pilot evaluation completed; plan for roll-out DM5 Roll-out (extended cohort of patients for initial LTC) DM6 Adopted for full LTC patient cohort Exclusions: Provision of devices and networks used by enrolled patients to access the PHR and NMC apps (possible inclusion of essential wearables associated with the apps depending on requirements). Integration of other organisation-based PHR products used in BNSSG (e.g. PKB) not specifically identified as included in the pilot. Key Outputs: Initial cohort of LTC related patients and clinical teams active use of NMoC for condition management Pilot report including recommendations for further LTC solutions produced Pilot extended to the wider cohort as appropriate Key Outcomes: Measured benefits associated with direct patient collaboration and self-care. Reduced unnecessary face-to-face contacts, interventions and admissions; improved patient communication and triggered interventions; immediate availability of patient status to improve safety and quality of outcomes. Dependencies: A.18/19, B.01, C.04, D.01/02
DESCRIPTION AND SCOPE. The on-going development and delivery of dashboards and whiteboards based on our extensive business intelligence capability is seen as a ‘generic’ business-as-usual project that will progressively encourage our users to make more and better use of ‘right here, right now’ information. One spin-off from this project is the development of our WardView product, which will deliver an interactive whiteboard tailored to the needs of each xxxx across the Trust. Fed with data from Medway, eHandover and other relevant sources, WardView also allows users to interact directly with the ‘board to mimic the use of magnets on ‘proper’ whiteboards so that patient status can be maintained and accurately in real time. Current position: • The development of the WardView product has been completed and the first pilot wards have reported back on their experiences. • Configuration of WardView for the remaining wards has commenced, with all wards being encouraged to adopt a ‘standard’ view to reduce additional development, but able to define additional content if required. • Engagement and implementation plans have been prepared and the first crop of wards engaged to refine their requirements. Delivery plan: • All wards will be engaged and requirements captured by August 17. • Wards not requiring additional content and development will be prioritized for delivery. It is hoped that most wards will be equipped by September/October 17. • Delivery will involve mounting large touch screens in each xxxx location, requiring collaboration between IM&T, estates and the wards. • Business continuity plans for each xxxx will be agreed and supported with a roll-up stand-by whiteboard. Just in case. Exclusions: • None relevant. Key Outcomes: • Real-time view of patient status allowing improvement in patient flow, discharge planning, bed availability and planning. • Immediate, visible feedback driving ‘in-the-moment’ update and use of core information systems including Medway. • Key safety and quality improvements.
DESCRIPTION AND SCOPE. 1. The Xxxxxx Site consists of approximately 0.75 acres and is depicted on attached Exhibit B. 2. The Mitigation Project consists of removing non-native plants and replacing them with native vegetation, grading, and installing stormwater pipe to improve habitat diversity and water quality on the Xxxxxx Site. The Mitigation Project includes:
Draft better contracts in just 5 minutes Get the weekly Law Insider newsletter packed with expert videos, webinars, ebooks, and more!