LTC WG - CHEFS Project Intro

Owned by Miranda Stewart, created
Last updated: Jun 30, 2022
3 min read

 Date

Jun 22, 2022

 Participants

  • CHEFS project team (CGI/CoCo)

    • @Miranda Stewart

    • @Killian Faussart (Unlicensed)

    • Samuel Ramos

    • Keyvan Torkanpoory

  • MoH (LTC/FSC)

    • Heather Cook

    • Linda Shaw (BPAM)

    • Jay Evans

    • Bonnie Wong

    • Kerri Harrison

  • RHAs (5)

    • Nic Van Westen - VIHA

    • Dan Goughnour - IHA

    • Rizwan Damji - VCH

    • Francis Moon - FHA

    • James Kinakin - IHA

    • Paul Champness - IHA

  • Regrets from Ana Paterson at NHA.

 Goals

  • Introduce the project (LTC portion) to health authorities and kick-off the working group sessions. Answer any questions HA representatives might have. 

 Discussion topics

Item

Notes

Item

Notes

Takeaways

  • 4 key components Kerri would like the project team to focus on: 

    1. Define business requirements (within the weekly HA working group). We need to ensure we have all the data points we need.  

    2. Concurrent work to be done with IT (CGI) to get platform running - identify any other key users from each HA and get contact details for them to connect with later on. 

    3. **Adequate training/change management processes followed. As part of this, there must be a clear mapping from the current quarterlies to the new tool (detailed mapping where "this cell goes here"). This cannot just be a technical manual that the average user cannot read/easily consume. There must be some time and effort dedicated to the actual transition from the current web tool/process to the new tool. 

    4. REPORTING. All the quarterlies must be standardized across HA's, so they are comparing apples to apples. This is not JUST to gather the data - we need to get the data in a format that replaces the info that’s currently collected in a quarterly statement. 

General Notes

  • Key piece is the elimination of duplicate/manual processes (we know this further emphasized as a major theme).

  • Start designing the tool/solution in-house and with lessons learned. Ensure we have a solid understanding first before engaging with the operators. Make sure we have an engagement plan. 

  • Focus on a user-centric design which will likely solve many of the issues/concerns that this same group ran into last time. 

  • re-focus the group → CHEFS is really about data ingestion.

  • We will need to explore the link to HAMIS. Is there any capacity to link to HAMIS? We may need to speak to the HAMIS-experts within each of the HA's (IT folks). 

  • appropriate sign-off and accountabilities is very important. 

 

Questions/Comments from HAs:

  • There are some providers that work in many different HAs/jurisdictions - who exactly will we be engaging? Is it our intention to get the providers to enter the data?

    • We need to identify the users of the new tool - will providers be included in our engagement plan? 

  • Will there be a data upload solution? VIHA is hoping we can run a blank report and attach the template back into the tool itself. 

  • The biggest thing from the operators during the previous web tool implementation was the usability/ease-of-use piece. Recommendation to lower the burden for how to get the info in. 

  • Data validation piece will be key and may be fairly complex.

  • VCH → What will the data extraction piece look like?

Next Steps

  • The next working group will involve gathering and confirming the business and data requirements (Bonnie/Kerri to section it off). Our goal over the next few weeks is to get 80-85% of the requirements gathered and prioritized. 

 Action items

 Decisions