Memorandum of Understanding between the Central LHIN and the Toronto Central LHIN to establish a Joint ehealth Program

Transcription

1 Memorandum of Understanding between the Central LHIN and the Toronto Central LHIN to establish a Joint ehealth Program Purpose This Memorandum of Understanding (MOU) defines the terms of a joint ehealth program of the Toronto Central Local Health Integration Network (LHIN) and the Central Local Health Integration Network. The MOU describes the parties common expectations and will support consistent messaging to the stakeholders of the two LHINs. Scope The MOU covers the establishment and operation of a Joint ehealth Program and a Joint Project Management Office (PMO), and the integration of their activity with the other work of the two LHINs. The Joint ehealth Council will provide strategic and operational advice on the development and implementation of an e-health Strategy for the Toronto Central and Central LHINs. The full Terms of Reference for the Council are attached as Appendix A. Specifically, the Joint ehealth Program will Conduct joint ehealth planning for the two LHINs Create a Joint ehealth Strategy and revise / update it as necessary Develop a common set of priorities and annual work plan Conduct joint procurement of ehealth products and services Prepare and submit joint funding applications for ehealth projects where appropriate Make recommendations to the Boards of the two LHINs on ehealth matters. The Joint PMO will manage the implementation of the annual ehealth work plan including specific ehealth projects assigned to it and provide day-to-day ehealth support and advice to the staff of the two LHINs. Structure and Roles ehealth Governance The Governance of e-health in the respective LHINs remains unchanged. Each LHIN e-health Lead is accountable to his/her own LHIN CEO and Board. ehealth Management The two ehealth Leads will work collaboratively to execute the joint strategy of the two LHINs consistently across the two LHINs. ehealth Operations The Joint Project Management Office will be responsible for implementation of the annual ehealth plan and for day-to-day ehealth support to the staff of the two LHINs. Revised November 19,

2 Coordination with LHIN Staff and Advisory Bodies To effectively implement the ehealth plan and ensure its alignment with the integration work of the two LHINs, regular communication and coordination will be required. A designated member of the PMO will be assigned as the day-to-day liaison with the staff of the two LHINs. S/he will attend meetings of LHIN staff and advisory bodies as determined to ensure communication and ehealth support to the LHIN initiatives. The management and staff of the two LHINs will keep the Joint ehealth PMO informed of LHIN initiatives and include the PMO representative in regular meetings. Project Management The Joint PMO will be responsible for maintaining a team of project management staff to manage and report on the implementation of ehealth projects assigned to it by the Joint ehealth Council. It will use consistent project management methodology including monitoring and evaluation functions. The PMO will designate a specific resource as the responsible contact for each project and communicate that to the Council and project participants. Each project will have its own Project Agreement signed by the participating organizations for which the PMO will be accountable. The Project Agreement will include a Project Charter with: project description, scope, deliverables, work plan, timelines, funding, roles and responsibilities, and alignment with provincial and/or national plans as appropriate. Where appropriate, the Joint ehealth Council will mandate the PMO to establish Project Advisory Committees and establish guidelines for them. The PMO will provide monthly updates on the joint projects to the two LHIN ehealth Leads and any others designated by them. Appendix B of this MOU contains the Project Charter for the Connectivity and Secure Projects. Timelines for project implementation may vary in each LHIN (e.g. begin in one LHIN and roll-out to the second LHIN in the subsequent year) Funding Funding for the PMO for 2007/08 will be $200,000. Future funding will be determined annually or as amendments are made to the work plans. An equal contribution of $100,000 from each LHIN will be used to support the work plan. Revised November 19,

3 Funding for ehealth projects will be determined on a project-by-project basis and may include a variety of sources over and above the two LHINs. The project funding structure will be incorporated into the specific project agreements among the participating organizations. Term The term of this MOU will continue until such time as the parties determine that it no longer serves their purposes and/or requires amendment. At least 60 days notice will be provided by either party if they wish to amend or terminate the agreement. Termination of any shared project will be subject to the terms set out in the project agreement. Dated, 2007 Toronto Central LHIN CEO Central LHIN CEO Toronto Central LHIN ehealth Lead Central LHIN ehealth Lead Revised November 19,

4 Purpose: To provide strategic and operational advice on the development and implementation of an e-health Strategy for the Toronto Central and Central LHINs. Objectives: Identify and prioritize e-health initiatives for the development of an electronic health record (EHR) and health service integration that take into consideration: o Alignment with ongoing provincial priority projects & the LHINs Integrated Health Services Plans, e-health Strategic Plans and Annual Service Plans o Opportunities to leverage existing infrastructure and take advantage of existing voluntary collaborations between organizations o The measurable impact on the quality of care and health outcomes Determine the value proposition and benefits of e-health initiatives Develop metrics for measuring the impact of initiatives Provide leadership for the implementation of initiatives and assist with communication and adoption strategies Advise on and champion strategies for funding and change management Define environmental risks and develop a risk mitigation strategy Develop principles for the implementation of local versus collaborative project approaches Meetings: The committee will meet bi-monthly at first and set a regular meeting schedule, as well as meeting as necessary at the call of the Committee Co-chairs Accountability: The committee is accountable to the Chief Executive Officers of the Toronto Central and Central LHINs via the e-health Lead of each LHIN. Guiding Principles: The Joint e-health Advisory Committee will develop a unified e-health Strategy and aim to set common priorities for the year Planning for all e-health projects will be done together Timelines for project implementation may vary in each LHIN (e.g. begin in one LHIN and roll-out to the second LHIN in the subsequent year) Projects will be implemented through a single Project Management Office which is jointly financed Revised November 19,

5 Membership Structure*: Co-Chairs Toronto Central and Central LHIN e-health Leads Community Sector (4) 1. Community Care Access Centres: (1) 2. Community Health Centre: (1) 3. Community Support Services: (2) Mental Health and Addictions (2) 4. Mental Health: (1) 5. Addictions: (1) Hospitals (3) 6. Acute Care teaching hospital: (1) 7. Acute Care non-teaching hospital: (1) 8. Specialty hospital: (1) Physicians (2) 9. Primary Care Physician: (1) 10. Specialist Physician (1) Other Stakeholders (2) 11. Patient Representative: (1) 12. Ontario Telehealth Network: (1) Ex Officio Support (2) 13. Shared Information Management Services (SIMS) 14. Project Management Office (PMO) * Members will be chosen as follows: Members will be chosen from the current membership of the e-health Committees of each LHIN. A balance of representation from both LHINs will be sought (recognizing that the two LHINs share many community service providers). Members will be selected for their knowledge and involvement in e-health in their sector and their connection to the ehealth plan. Members will be selected by the Co-chairs. Revised November 19,

6 Appendix B: Connectivity and Secure Project Charter To be developed. Revised November 19,