Editing Handover (section)

==Overview of next steps==
Piecing all the above together, the below table summarises key information. Here '''complexity''' indicates something that has a lot of interacting or overlapping parts and/or something with requirements or properties that have not been defined. '''Workload''' indicates amount of effort required in total to deliver what is currently known. Many of these are nascent or evolving, so these categorisations are subject to change!

Key:<br>
<span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> - High<br>
<span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> - Medium<br>
<span style="color:#33d17a; font-weight:bold;">{{#fas:circle-down fa-xl}}</span> - Low

{| class="wikitable sortable"
! Item || Complexity || Workload || Competency || Timeline
|-
| Kotahi implementation || style="text-align:center;" | <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> || style="text-align:center;" | <span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> ||  <ul><li>Product expertise</li><li>Business analysis</li><li>Process mapping</li></ul>|| July 2025
|-
| Population health data || style="text-align:center;" | <span style="color:#33d17a; font-weight:bold;">{{#fas:circle-down fa-xl}}</span> || style="text-align:center;" | <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> || <ul><li>Managing flat files</li><li>Database administration</li><li>Visualisation/Power BI</li></ul> || TBC
|-
| Internal reporting || style="text-align:center;" | <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> || style="text-align:center;" | <span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> ||  <ul><li>Change management</li><li>Professional development</li><li>Requirements gathering</li><li>Power BI development</li></ul> ||
|-
| External reporting || style="text-align:center;" | <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> || style="text-align:center;" | <span style="color:#ff8533; font-weight:bold;">{{#fas:circle-right fa-xl}}</span> || <ul><li>Data modelling</li><li>Database administration</li><li>Operational/business workflow</li></ul> ||
|-
| Digital strategy || style="text-align:center;" | <span style="color:#33d17a; font-weight:bold;">{{#fas:circle-down fa-xl}}</span> || style="text-align:center;" | <span style="color:#33d17a; font-weight:bold;">{{#fas:circle-down fa-xl}}</span> || <ul><li>Digital/data thought leadership</li><li>Thorough understanding of KPT current state</li><li>Understanding of Wellbeing model/future state</li></ul> || ASAP
|-
| Data integration || style="text-align:center;" | <span style="font-weight:bold;">{{#fas:circle-question fa-xl}}</span> || style="text-align:center;" | <span style="font-weight:bold;">{{#fas:circle-question fa-xl}}</span> || <ul><li>Data engineering</li><li>Process mapping</li><li>User requirements</li></ul> || TBC
|-
| Insights || style="text-align:center;" | <span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> || style="text-align:center;" | <span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> || <ul><li>Familiarity with National Collections data</li><li>Understanding of health system workflow/data flow</li><li>Modelling data</li><li>Generating insights</li></ul> || TBC
|-
| Data sovereignty pilot || style="text-align:center;" | <span style="color:#dc1111; font-weight:bold;">{{#fas:circle-up fa-xl}}</span> || style="text-align:center;" | <span style="color:#33d17a; font-weight:bold;">{{#fas:circle-down fa-xl}}</span> || <ul><li>Pacific cultural competence</li><li>Managing community/stakeholders</li><li>Organising/hosting workshops</li><li>Issues pertinent to Pacific data sovereignty</li></ul> || December 2025
|}

===Suggested resourcing===

Some suggestions about resourcing are provided below.

====Kotahi implementation====
* Development and configuration in Kotahi can be handled by Solomon.
* We should also think about developing other 'champions' who can handle configuration tasks.
* Will need help with process mapping and planning. We can use our Kotahi agreement to fill this gap, but also directly involve Team Leads.

====Population health data====
* This is a simple pickup and load of data.
* However, putting it together usefully requires careful consideration.
* Suggest involving someone familiar with National Collections data and/or a stakeholder who can contribute to understanding of this data (Te Ngira/Polly).

====Internal reporting====
* Business side could be led by Mel/Dianne or Team Leads.
* Will need outside expertise if we want to go ahead with organisational upskilling.
* Data/app development can be handled by Solomon.

====External reporting====
* Particularly for PIC, business side again led by Mel/Dianne.
* Data/app work can be handled by Solomon.

====Digital strategy====
* To be carried out by Spark Health.
* KPT requires informed contributions to manage scope and potential for provider capture.

====Data integration====
* Work to be determined via Wellbeing model/user story development.
* Likely to need some external resourcing/capability if new products, particularly client-facing products are needed.
* Otherwise BAU integrations can be handled by Solomon.

====Insights====
* Needs additional resource; quite a niche field to do really well (again, possibly Te Ngira or similar).

====Data sovereignty====
* Bulk of work to be led by Matou.
* We need to support with access to our client base/community reps.
* We should also ensure Solomon is directly engaged in as much as possible, because this project speaks to key issue for Pasifika.