1. Community Mental Health Common Assessment Project (CMH CAP) Vendor Update Mary Lou Bozin Delivery Manager, CMH CAP

2. 2 SECURITY NOTICE This material and the information contained herein are proprietary to Continuing Care e-Health and may not be used, reproduced, stored in electronic retrieval systems, or disclosed to others, in any form or by any means, except as specifically permitted in writing by creator of the document. The recipient of this information, by its retention and use, agrees to protect it from any loss, theft or compromise. Please contact the creator of this document if you wish to share this document with organizations outside of Continuing Care e-Health. This document has a MEDIUM Classification.

3. 3 Agenda Purpose of this session Project background Initial pilot recap NE LHIN pilot overview Next steps Q&A

4. 4 Purpose of this session Share information on the North East LHIN pilot Inform vendors of software approach to support OCAN in the NE LHIN pilot Provide opportunity for vendors to ask questions

5. 5 Architecture & Integration Standards Security, Privacy & Risk Management Common Assessments Community Care Information Management Business Systems Program StreamsLTCHCMH & ACSSCCAC CMH CAP (OCAN) LTCH CAP (RAI MDS) Local Health Integration Networks CMH&A MIS LTCH MIS FSMS CSS MIS CSS HRIS CMH&A HRIS Project Legend CAP = Common Assessment Project CCM = Common Case Management CIAT = Common Intake Assessment Tool CMH&A = Community Mental Health & Addictions CSS = Community Support Services HC = Home Care FSMS = Financial & Statistical Mgmt Systems HRIS = Human Resources Information System LSAS = Long Stay Assessment Software LTCH = Long-Term Care Home MIS = Management Information Systems RAI MDS = Resident Assessment Tool Min. Data Set Project Rolling Out Project in pilot Completed project HC CAP (CIAT) HC CAP (LSAS)

6. 6 Early origins and project development Phase 1 – Initiation (with stakeholder representation) Analysis of many assessments tools Selection of a core tool – Camberwell Assessment of Need –Internationally used; recognized in numerous academic research papers Province-wide consultations to introduce the tool Formation of working groups Phase 2 - Pilot Piloting of the automated OCAN in 16 CMH organizations, including two hospitals Early learnings gatherings NE LHIN pilot in 38 CMH organizations Phase 3 - Implementation Provincial roll-out Integration with a changing CMH landscape Powerful reporting to drive enhanced consumer-centred service and system planning

7. 7 What is OCAN? Ontario Common Assessment of Need (OCAN) is a standardized, client-led decision making tool that allows key information to be electronically gathered in a secure and efficient manner. Assists client-led decision-making at an individual level Identifies individual needs and helps match these to existing services and identifies service gaps Provides aggregate data to inform organizational, regional and provincial level planning and decision making that is consistent with a recovery approach Further facilitates inter-agency communication through common data standards

8. 8 Initial pilot – technology approach CMH CAP Central Repository Pilot Organizations Pilot Vendors 16 pilot organizations across Ontario 13 pilot sites (2 partnerships) Technical lead position CMH CAP team located in Toronto Support of pilot site-vendor relationship Delivery Manager, technical BA positions 6 software vendors Regular dialogue with pilot sites and CMH CAP team

9. 9 CMH CAP Central Repository Pilot Organizations Pilot Vendors Identification of defined criteria 1 Provision of technical application 2 Data submission to single source 3 4 Report generation Report delivery 5 LHINS, MOH Report delivery 6 Future focus Initial pilot – technology approach

10. 10 Consumer portal DIRECT ENTRY Computer Assessment DIRECT ENTRY IN THE AGENCY IN THE FIELD Paper Assessment INDIRECT ENTRY Paper Assessment INDIRECT ENTRY Data submission to single source CMH CAP Central Repository Initial pilot – technology approach

11. 11 Initial pilot - experiences Use of existing technology was well received and minimized technology training requirements Consumer portals can be used as a way to collect self assessments Field assessments pose a challenge to direct entry Key clinician level reports are critical to sustained technology adoption Case Management systems provided an appropriate context for assessments Solution offerings and cost structures vary by vendors Pilot organizations were largely self sufficient in dealing with vendors Common information can be collected across a variety of vendors

12. 12 NE LHIN pilot - purpose To pilot the implementation approach To pilot the use of OCAN LHIN-wide Further testing of: –Use of OCAN in diverse populations (French and Native) –Use of OCAN in specific programs (building on initial pilot learnings)

13. 13 NE LHIN pilot – technology approach An automated solution –Pilots must automate OCAN Multi-vendor approach Pilot organizations choose their pilot vendors A common set of vendor specifications will be provided to all interested vendors Central reporting repository –Data is submitted from Pilot organizations (i.e. via vendor application) to a central reporting repository Support for vendors –CMH CAP online portal –Vendor teleconferences –Process for testing vendor submission files

14. 14 NE LHIN pilot – technology approach

15. 15 NE LHIN pilot – technology timelines Requirements are expected to be released in the next two weeks Pilot organizations have attended kick-off meetings and will begin contacting vendors (as required) Targeting early go-lives for May Software training (provided by vendors) has been recommended to take place 1 week prior to go-live

16. 16 NE LHIN pilot – roles and deliverables CMH CAP team –Provide vendor requirements –Provide test capabilities and test submission files –Conduct ongoing vendor touch-points –Support Pilot organizations –Secure CAN-C copyrights for participating pilot sites Pilot organizations –Vendor selection, contract negotiations and vendor relationship management –Implementation Vendors –Deliver solution to meet requirements –Submit test files for data submission –Provide software training

17. 17 NE LHIN pilot – next steps Pilot organizations will be contacting vendors Communication will be sent to provide vendors access to requirements Vendor teleconference sessions will be scheduled

18. 18 Questions??