Page Comparison

General NotesMVP Discussion

• Ensure we include provide the context of the MVP : we want to make sure that there was we share this with for the HAs (whether it’s it is verbal/written). There Emphasize that there is flexibility throughout the agile process . This and that this is not the end-all and be-all. Emphasize that the agile approach will allow us to be flexible, etc. One of the problem’s with the last web tool, it was on an old platform. Emphasize that this is

Project Status

• Reviewed Budget, quality, scope, schedule, milestones and risks.

• Milestone identified as having sign-off on MVP by Jul 29.

Communication/Engagement Strategy

• Emphasize that this new tool will be a modern, user-friendly tool, based on a modern user-friendly platform.

• quarterly submission will start off as a budget (their FY plan as of April 1). When at the end of Q1, you enter your YTD for your actuals and your forecast.

• We want to have the RHAs' input (they didn’t have a say at all last time with the RKL tool)

  • July 27th - Kerri would like to have this as an agenda item for the HA working group mtg on July 27 and for HAs to sign off.

Key Discussions

• Kerri’s thoughts: we have to be careful/sensitive with the contracted operators (200+ sites). Kerri needs to see an engagement plan/overall engagement strategy for this sector. This will be a highly contentious /sensitive communication piece - Show the benefits that the new tool will offer as far as improvements go.

• Crucial to have the HAs' input and feedback.

• Need to produce an engagement plan for this sector which may have to go to the Minister . We need to allow significant time for this (i.e., briefing note with deputy).

• Make it clear the benefits that CHEFS offer.

  • Take the RKL and show the issues that have been identified and what the CHEFS tool is going to do as far as improvements go.

• Batch upload → CHEFS doesn’t offer any capabilities for this currently. We need to allow significant time for this.

General

• Killian confirmed that once a submission is completed in CHEFS, no changes to the submission can be made.

• Kerri wants to meet weekly until we get this project well-underway.

• Agenda for tomorrowAgenda for tomorrow’s LTC working group meeting: HAMIS folks will be there; Killian will do a run-through of CHEFS tool; 5 min for the end (pivot)

Agenda for LTC WG - Jul 27

• Review the final MVP as an agenda item so the HAs can share their input and provide sign-off on as well.

• HAMIS demo session

• CGI CHEFS demo

• Allow 5 min for pivoted approach to HA data collection standardization.

ID

Description

Owner

Creation Date

2022

Due Date

2022

Status (New, In Progress, Completed, Closed)

Notes

1

•  Killian Faussart (Unlicensed)/ Samuel

• Ramos (Unlicensed)Engagement Plan/Strategy

• Produce an engagement strategy for the operators. This will include what we need to engage on, who we need to engage with and when.

CGI

Jul 19

TBC in following meeting

New

Provide a clear estimation on how much work this will require with the contractors. We will need support from SS/

Finance/

IMIT.

Next Steps: Samuel will update the project plan (schedule/milestones) to incorporate this item.

2

•  Kerri to

• review the revised MVP and provide sign-off

LTC

Jul 19

Jul 29

In Progress

Jul 22 – Kerri reviewed and sent back to CGI.

Kerri to provide sign-off.

3

•  Samuel Ramos (Unlicensed)Communication Strategy CGI to make it clear to the HAs the benefits that CHEFS offer. Take the RKL and show the issues that have been identified and what the CHEFS tool is going to do as far as improvements go.

CGI

Jul 19

TBC

In Progress

Samuel, Eddy & Linda are working on getting a resource for the OCM component of the project, which will include this deliverable.

4

•  Samuel Ramos (Unlicensed) Schedule a weekly meeting with the project team, Kerri, Heather, Bonnie, Jay

 Samuel/Linda

Jul 19

Jul 22

Completed

5

•  Cut-off/Roll-out Plan

Figure out roughly when the health authorities can be expected to start inputting their quarterlies.

Jul 19

October

New

LTC’s preference is for FY22/23. Ideally, it would be good to have

the budget first inputted, and then

input the quarterly submission

.