Page Comparison

General Notes

• The Ensure we include the context of the MVP: We we want to make sure that there was we share this with the HAs (whether it’s verbal/written). There is flexibility throughout the process. This is not the end all and be-all (whether it’s verbal/written). 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 a modern, user-friendly tool, based on a modern user-friendly platform. All of these reports

• quarterly submission will start off as a budget (their FY plan as of April 1)

  when

  . When at the end of Q1, you

  put in

  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 a little careful . We need 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 - may have to go to the Minister. We need to allow significant time .

• communication with that sector is VERY important. We have to

for this (i.e., briefing note with

the

deputy).

• Make it clear the benefits that CHEFS offer.

  • take 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 now. Ideally, we want an operator for this currently.

• 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 tomorrow: HAMIS folks will be there; Killian will do a run-through of CHEFS tool; 5 min for the end (pivot)