K'aute data model

Background

This provides an overview of the K'aute data model, including systems of record and other incoming data sources.

Logical model

Most importantly, the bigger picture around strategy and outcomes should be understood first.

Integrated wellbeing

K'aute are developing and implementing a Wellbeing model. This encompasses:

1. A multidisciplinary holistic model of care
2. Integrated operating model
3. Enabling digital and data.

This article is concerned mostly with 'Enabling digital and data'.

A logical model drawing together PPDF deliverables is shown below:

graph TD id1[KPT Objectives]:::business -- Inform -->id2(((Wellbeing Model))):::wellbeing id3[Pop Health data]-- Informs -->id2 id5[Monitoring framework]-- Supports -->id4[Evaluation]:::business id3 -->id5 id2-- Defines -->id6[Enterprise Architecture] id6-- Defines -->id7[Technical requirements] id2-- Defines -->id8[Data flows] id8-- Determine -->id9[Integrations] id4 <-->id2 id2-- Informs -->id10[Digital strategy]:::business id6-- Informs -->id10 id8-- Review -->id11[Consent/governance]:::business id12[People Framework]:::business -- Enables -->id2 id10 <-->id13[Operating model]:::business id8-- Inform --> id5 classDef business fill:#99cc99 classDef technical fill:#663d66 classDef wellbeing fill:#ffffcc

This identifies the following dependencies:

• Wellbeing Model defined to deliver KPT objectives
• Population Health Data informs Wellbeing Model and contributes to Evaluation
• Strategic People Framework enables the Wellbeing Model

In turn, the Wellbeing Model itself determines most of the other activity under these Workstreams:

• It defines the Enterprise Architecture, which:
  • defines technical requirements
  • informs revised digital strategy
• It defines required Data flows, which:
  • determine required integrations
  • require updated consent/governance process
• It defines an updated Digital strategy, which:
  • informs the future operating model.

Systems view

This is a different view of above, showing systems and data sources - at a high level.

graph BT subgraph Systems id1[Indici] id5[Kotahi] id6[HRMS] id9[Discover] end id3[Staff] id2[K'aute data store] id3<-.->id1 id3<-.->id5 id3<-.->id6 id3<-.->id9 id1<-.->id2 id5<-.->id2 id6<-.->id2 id9<-.->id2 id2<-->id10[Aiga/Family]

Data store

Currently data is being centralised into a Postgresql 15.7 RDS instance at kaute1.cwrpufuni4fh.ap-southeast-2.rds.amazonaws.com. Access is controlled via security group rules.

Schema

See also: Indici data and Kotahi data supply

There is more or less a schema per data source, as well as staging/rpt variant where incoming data is a bit more complex and needs to be transformed or deduplicated.