Data and analytics strategy PUBLIC - ADHB 2021

Data & Analytics Strategy
Executive Summary
June 2021
Ali Khan
Data & Analytics Director
Auckland District Health Board
© Ali Khan on behalf of ADHB 2021

Welcome Haere Mai | Respect Manaaki | Together Tūhono | Aim High Angamua
INTRODUCTION
01
What are the problems
we want to solve whilst
considering a holistic
view of the wider
challenge in front of us.
UNLEASHING OUR
DATA
02
Our design thinking –
how do we change our
delivery eco-system to
embed cost effectiveness
and sustainability at its
core.
SELF-SERVICE AND
DATA INNOVATION
03
Enabling data innovation
at the front-line safely
and with speed through
“true” self-service.
ENABLING THE
DIGITAL ECOSYSTEM
04
Build once, use many
times. How can we
leverage our data to
meet a diverse set of
business data needs.
2
2
© Ali Khan, Shayne Tong on behalf of ADHB 2021

Introduction
01
What are the problems we want to solve whilst considering a
holistic view of the wider challenge in front of us.

We have adopted the approach of proving value first using existing or trial technologies, and then after
qualifying business demand implementing new solutions
1.0 Introduction – ADHB have a comprehensive data & analytics strategy in response to our
business needs with good progress across a number of areas
Real-time IOC Dashboards
Clinical Audit / Registries
PowerBI, Azure Analysis
Services, SQL Server,
HealthCare Logic (POV)
Clinical Research
Management
Clinical Trial Management Departmental Databases
Enterprise Data
Warehouse
Self-Service Analytics
SQP Business Objects, SQL
2005
PowerBI, SQL Server
Data Science
R, Python on Data
Science Server
Dendrite Clinical Systems Edge Clinical Trial
Management &
Research
Redcap Database
Solution
Microsoft Access, SQL
Server, Oracle APEX
Existing (Legacy) Existing New Capability !!! Initial Implementation
MVP#1 Solution
Interim Production
Solution
Hosted in Azure Trial Capability (APEX)
4

This document describes how ADHB is leveraging data & analytics to deliver to our strategic priorities
and in particular digital transformation
1.1 Introduction – We have used our strategic priorities to provide focus 5
ADHB’s priorities are aligned to recently announced Health system
outcomes:
• Equity for all New Zealanders – so everyone can achieve the same
outcomes, and have the same access to services and support,
regardless of who they are or where they live.
• Partnership – through embedding the voice of Māori and other
consumers of care into how the system plans and makes decisions,
ensuring that Te Tiriti o Waitangi principles are meaningfully upheld.
• Excellence – ensuring consistent, high-quality care is available when
people need it, and harnessing leadership, innovation and new
technologies to the benefit of the whole population.
• Sustainability – focusing the health system on prevention and not just
treating people when they are unwell – ‘wellness not illness’ – and
ensuring that we use resources to achieve the best value for money.
• Person and whānau-centred care – by aiming to empower people to
manage their own health and wellbeing and put them in control of the
support they receive.

Creating a connected patient centric view of data is critical to shifting to improving throughput,
reducing wait times and more importantly moving to proactive models of care.
1.2 Introduction – We also know that we have to design for a connected health system
• The public health system is shifting, from a sometimes
fragmented health and disability system with a siloed
service models, to a more connected and whānau-centric
approach (Health and Disablity System Review March
2020).
• Data and analytics are essential to making the community,
patient and whānau experience transparent and to
informing system redesign and that will also improve
performance.
6

With an IT centric model, we simply cannot ever build the delivery capacity needed to meet total demand,
or have the embedded knowledge needed to translate “intelligence into action”
1.3 Introduction – We are not able to meet business demand with a traditional “Report Centric”
delivery model
There are many reasons why an IT centric model cannot meet business
needs. The key reasons include:-
1) Most demand is urgent, requirements change continuously ,
decisions need to be made urgently – it is impossible to organise
and join data to cover every single scenario.
2) Business context is required – This is even harder in the clinical
setting where it is impossible for a data team to understand all the
nuances of very specific business and clinical processes.
3) Need to deliver at low to zero cost – The business never has the
budget to scale to their intelligence needs.
4) Trust – Self-delivered insights always have a higher level of trust
than those delivered by central teams
And most importantly ….
5) Impossible to organise and join data to cover every single
scenario – we just cannot predict all the combinations and
permutations of data need to be joined to meet business demand
Total
Demand
Qualified
Demand
( HIT Requests )
Capacity
cannot
meet
7
How do we address the gap ?

Cloud Data Staging Layer
As we transition more capabilities to the cloud, how do we increase the range and reach to deliver
more value to our business ?
1.4 Introduction – Finally, Cloud provides a range of new capabilities we can easily utilise to
meet our needs without the need for significant upfront investment
8
Older/delicate
DHB Source
Systems
Raw Data Staging Layer
Newer DHB
Source Systems
Cloud Raw Data (Structured)
Reporting &
Analytics
Operational
Data Stores
DevOps
CI/CD
GitHub
Management Console
Fast Data
Cache
API Gateway & Catalog
Batch Load,
Micro Batch
Streaming
Batch,
Micro batch
Cloud Raw Data (Unstructured)
Playpen
(for self-
service)
Reconciliation
CDS
Single view
of data
Container
Management
for Analytics &
Micro services
EDW
Analytical
Datasets
Micro Batch
Streaming
Medical Devices,
Data Lake
Batch, Micro Batch, Streaming
Data
Catalog
Data
Profiling
Security
/
Authentication
&
Role
Based
Access
&
Controls

• Changing our operating model
• Focusing on value
• Changing our information architecture
Unleashing our data
Our design thinking – how do we change our delivery eco-system
to embed cost effectiveness and sustainability at its core.
02

2.0 Unleashing our data – “DataOps” is at the center of our new delivery model, with true self-
service and automation being key enablers of business value
10
Modern Approach – DataOps at the core
Developing data products
Analytics as a strategic business function
Focus on capabilities and support using a repeatable framework of tools
Questions are not pre-defined
Timeline is based on solving business needs
Full range of self-service capabilities including pro-typing, ad-hoc querying across
multiple data sets
Real-time or near real-time data for all data
Integrated data delivery for BI, data & digital
Traditional IT Centric BI Delivery Approach
Managing business intelligence projects
Analytics as a demand-driven support function
Proliferation of dashboards and reports
Hypothesis (questions) are pre-defined
Timeline is project-driven
Limited or BI tool driven self-service
Most processes are overnight batch
Digital & analytics are separate
This approach focuses on building data products, prototyped by (or in collaboration with) the business in safe
modern self-service environments, powered by automation and data discovery
Strategic shift from “Building Reports”
To
Delivering “Business Led Intelligence” through
data products
vs

Our data strategy hinges on delivering to the 4 key pillars below through fit for purpose capabilities
and accelerated delivery via people, process and technology changes
2.1 Unleashing our data – We are unlocking the value in data by enabling our citizen workforce 11
• Search for data and reports
existing across ALL ADHB systems
• Understand what the data means
and how it is used
• Interact with regular users of this
data to improve understanding
• Understand the quality of the data
and its suitability for usage
Data Discovery
• Use modern tools like PowerBI or
their preferred tool to build
insights
• Data is available in a language
easily understood by the
business and already linked for
simple usage
• Data remains safe and secure at
all times and availability
controlled by access rights and
data classification
Self-Service Automation Innovation
• All manual processes engineered
out through automation where
possible
• Creation of data products and
reusable data assets to
accelerate delivery
• Automated workflows to
accelerate data access approvals
• Automated data provisioning
capabilities
• Enabling citizen data analysts,
geeks, scientists and engineers to
use data in innovative ways to
create value
• Intelligence teams co-designing
and delivering side by side with
business teams
• Testing production insights as
you go and changing on the fly
Discover data “within”
and “outside” our data
platforms
“Experiment and
create new value”
at low to zero cost
Reduce the
friction and cost
of delivering data
(new and existing)
Enable our “untapped
workforce of thousands” to
build sharable, repeatable
insights

We have started at the bottom of the pillar by enabling slices of base data and analytics to deliver
immediate value, whilst tactically delivering higher value products as we build our data foundation
2.2 Unleashing our data – We have adopted a sustainable product centric approach
Level 4 - Performance
Products
Level 2 – Business
Intelligence, Self-Service
Analytics, Data API’s
L5 - Predictive
Products
L6 -
Strategic
Products
Level 3 - Single View Products
Level 1 -
Base Data
Increasing
complexity and
“System Value”
Data consolidated source
data e.g. Patient, clinician,
facility, event, financials
Information value added products e.g.
• Integrated Patient journey
(pathways)
• Staff journey
• Patient record
• Integrated patient dashboard
• Operations Dashboards
• Key Performance Indicators
Knowledge understanding what might happen e.g.
• Predictive Interventions
• Recommendation Engines
Wisdom driving outcomes through the application of knowledge, information and data e.g.
• Data driven clinical care
• Patient flow optimisation
DIKW pyramid
Increasing
velocity of delivery
and “Operational
Value”
12

Our customers are not just patients, but also include clinicians, healthcare providers, government as
well as the general public
2.3 Unleashing our data – Our data & analytics strategy is built around understanding our
customers and how to create a sustainable eco-system to deliver to their needs
Patients & Whanau – A secure, single
view of my health data
Clinicians – a current view of my patients,
my activities, where are my patients in
their care journey, understating my
patients needs
Hospital Operations – how are we
performing, what is due, where do we
need to improve
Related Healthcare Providers – enabling
a seamless patient care journey,
frictionless handoffs as people move
across care boundaries
Ministry – meeting our obligations,
ensuring equity
General Public – trust in our healthcare
system, maximising value from our
investment
13
D&A
Capabilities
Data Content
(Structured &
Unstructured
Data)
D&A Products
& Services
Business Capabilities
Products & Services
Patients &
Whanau
Clinicians
Hospital
Operations
Related
Healthcare
Providers
Ministry
General
Public

Through clarity about what the business need, we are able to link back to the data, identify missing
data, and build a holistic and strategic views of hospital performance
2.4 Unleashing our data – We have used a value mapping framework to define hospital value 14
Hospital Value
Finance People Patient Experience Productivity
Assets /
Liabilities Revenue Cost Equity Quality
Patient
Safety
Engagement /
Wellness
Education Staff Safety Effectiveness Efficiency
 Acute
Volume
 DNA
 DOSA
 Elective
Discharges
 IDF
 Long term
illness
measure
 LOS
 PAR
 Readmissio
n
 Capacity
 Health
Targets -
ADHB
 Health
Targets -
Regional
 Occupancy
 Utilisation
 Waiting List
 Accidents
 Incidents
 Mandatory
Training
 OHS
Measures
 Annual
Practising
Certification
 Training/confere
nces
 Annual
Leave
 No meal
breaks
 Overtime
 Sick Leave
 Turnover
 CBU
Outliers
 Mixed
Gender
Occupancy
 Single Room
Occupancy
 Smoking
Advice
 Accidents
 Incidents
 Mortality
 Patient
experience
 Readmissions
 Falls
 Hand Hygiene
 Infections
 Medication Errors
 Patient Safety
Audit Compliance
 Pressure Injuries
 Building values
 Car parks
 Equipment
 Fleet
 Stock on hand
(Pharmacy, other
supplies)
 Short Term
Liabilities
 Accounts
receivable (non
resident)
 Long Term
Liabilities
 Non-Resident
Revenue
 Cash
generating
outsourcing
 Clinical Training
& Education
Income (CTA)
 Contract
 Donations
 IDF
 MOH top ups
 Parking
 Programme
Funding
 Rental
 Tertiary
Revenue
 WIES
 Ambulance
 Cleaning
 Clinical supplies
 Contract vs Actual
Volumes
 Equipment cost
 Excess Annual
Leave in $
 Infrastructure
maintenance
(buildings)
 Laundry/Staff
Uniform
 LOS
 Meals
 Non Clinical
supplies
 Non Clinical
support
 Offsite Rentals
 Outsourcing
 Overheads (Power ,
Phone , Gas, Fleet
maintenance)
 Penalties
 Personnel
allowance &cost
 PHO Cost
 Security
 Training /
conferences
 Write offs - non
funded patients
Improvement
Levers
Value Drivers
Asking the right questions
1.1 Are we on target to achieve our safety targets e.g. hand hygiene, falls, mortality, infections, goals of care
2.1 How are we tracking against MoH targets
2.2 Increasing the number of additional patients booked e.g. lists, ITC (using our spaces right)
3.1 Benchmarking ourselves against others= hospitals e.g. via HRT, Telehealth, LOS, DOSA
3.2 Measuring the effectiveness of care navigation capability e.g. equity
3.3 Meeting or exceeding our planned care objectives to receive MoH allocated funding
3.4 Measuring the financial spend progress of programmes against planned capital expenditure
3.5 Effectively managing our cashflow to reduce borrowing costs
3.6 Improving Inpatients/Outpatients experiences.
4.1 Delivering against our price volume schedule e.g. Discharge targets, IDFs (Contract Volume)
4.2 Maximising our OR/OP usage & utilisation to improve throughput e.g. DNAs
4.3 Reducing our annual leave balances to agreed targets
4.4 Optimising the mix of staff between agency and DHB staff overtime to effectively and efficiently deliver services
4.5 Monitoring how we are tracking against our budgeted FTE
4.6 Measuring the intended planned savings to be delivered by improvement initiatives
4.7 Minimising the use of high cost or off catalogue items

We have been running governance for over 24 months and have successfully completed a number of
initiatives under its mandate
2.5 Unleashing our data – Governance provides the foundation for sound decisions
Digital Steering
Committee
Data Governance Support
Office
Data Stewardship
Council
Working
Group(s)
(as required)
Role:
• Approve DG
Strategy
• Final point of
escalation
Membership:
ELT
Cadence:
• Weekly
Role:
• Provide a data governance mandate across
business
• Provide strategic direction
• Point of escalation
• Approve data governance strategy & priorities
• Provide funding where deemed a priority or
escalate to ELT for support
• Strategic guidance as required
Membership:
• Clinical Directors, GM’s, HIT Leadership team
members
Cadence:
• Monthly
Role:
• Frontline view of our data challenges
• Set operational & strategic data priorities
• Key group of people to guide governance for
operational outcomes (real value !!!)
• Propose data stewards who can make decisions
on the form of data
Membership:
• Business operational leaders, domain data
stewards, operational data stewards
Cadence:
• Monthly
Role:
• Provide topic specific leadership where extra
facilitation is required
• Formed around key initiatives or domains
• Example groups could include: RCP data
remediation, HARP data management, Domain
specific – Patient, Appointment etc.
Role:
• Operational
management and
delivery of data
governance across
ADHB
• Running data
governance committees
and working groups
• Facilitating workshops
• Writing governance
papers and
presentations
Membership:
• DG Lead
• DG Business Analyst
• Data Architect / Modeller
• Data Analyst
15

Data & Analytics
Develop products to
enhance clinical and
operational insights
Working on innovation
and capital projects
Enable and support
business teams using self-
service analytics
Insights & Enablement
Engineering centre of
excellence for data
movement and
visualisation
Increasing automation
and adding resilience
Enabling new data
sources
Engineering & Integration
A function dedicated to
the develop of advanced
analytics
Working with directorate
teams to leverage new
AI/ML capabilities
Data Science
Establishing and maturing
data architecture, data
governance and data
stewardship across ADHB
Developing enterprise data
models and data artefacts such as
data catalogs, business glossaries
Driving data quality
improvement through
data standards, data
quality KPI’s and cleansing
activities
Enterprise Data
Management
Developing and extending
our BI and data
architecture
Delivering cloud data
environments
Engineering L2, L3 support Running data governance
This has meant creating a new focus on engineering and bringing in new skills to deliver change at
speed and within our financial boundaries
2.6 Unleashing our data – to enable our new operating mode, we are transitioning our
internal team structures and capabilities
16
Delivery Management
Specialist data delivery
management capability
consolidated across
Projects and BAU delviery
Agile delivery
management using a mix
of DataOps related
processes
Management of squads
and work distribution
Co-ordination across
multiple squads

17
Business
Analysis
Data
Analysis
Business
Writing
BI
/
Report
Development
Data
Modelling
ETL
Dev
Business Intelligence
Analyst
Business
Analyst
Data
Analyst
Business
Intelligence
Developer
+ +
1 Transition to T-shaped roles to bring a
multi-dimensional approach to problem
solving
In the example above, it is normal
practice for business intelligence
analysts to be cross-functional.
Complex delivery can be supported
or delivered by a specialist
capabilities where needed.
2 Addition of advanced capabilities to lift
overall D&A capability , tackle complex
delivery, evolve our frameworks and tools,
increase automation and enable self-service.
Data Story
Teller
Engineering
& Integration
Manager
Senior Data
Engineer /
Senior Data
Operation
Engineer
Senior
Visualisation
Developer
Senior
Enterprise
Data Analyst
Data
Architect &
Modeler
• Design & implement the evolution of
ADHB’s data warehouse capabilities
• Support hybrid cloud implementation
• Drive self-service architecture, data
security
• Implement ADHB’s target state technical architecture
• Increase automation & real-time capabilities
• Deliver self-service including data security
• On-board new capabilities e.g. cloud adoption, API’s
• Owner for our visualisation toolsets and BI architecture
• Lift existing technical BI capabilities
• Implement embedded analytics
• Trial and implement new capabilities
• Own all aspects of data architecture across
projects and BAU.
• Define, design and implement data assets
such as data models, data catalogue etc.
• Lead data governance activities.
• Lead data analysis and modelling activities on
complex projects.
• Own and deliver data assets as agreed with
the data architect and data leadership.
• Lead the multi-functional capability within D&A.
• Implement processes to drive quality and
consistency of delivery.
• Mentor and grow analyst capabilities.
3 Focus on defining and implementing
BI products to meet business needs.
The insights team also lead project
delivery and bring in resources from
other D&A teams.
Insights &
Enablement
Manager
Senior Business
Intelligence
Analyst
Business
Intelligence
Analyst
Data Story Teller
4 The creation of enduring assets, tools
and frameworks to increase reuse,
accelerate delivery and enable self-
service.
Information Architecture Models
Reusable Data Models
Data assets including data catalogue,
data dictionary, business glossary
Frameworks and tools to monitor
data quality, data sharing etc.
Automation of
capabilities such as data
provisioning, data
sharing, approvals
2.7 Unleashing our data – With the focus on improving capabilities and the use of repeatable
frameworks, changes are being introduced into the Data & Analytics function to lift productivity.
These changes are designed to lift capabilities within the team, reduce inefficiencies and support a
modern approach to delivery of outcomes.

18
Data & Analytics
Insights & Enablement
Roles
Engineering & Integration
Roles
Data Science
Roles
Revenue & Cost
Management
Roles
Enterprise Data
Management
Roles
Delivery Management
Roles
Business Intelligence
Analyst (technical &
business)
Process mining specialist
Cloud Engineer
Visualisation Engineer
Data Operations
Engineer
Principal Data Scientist Revenue & Contract
Reproting Analyst
Costing Analyst
Data Architect &
Modeller
Data governance analyst
Enterprise data analyst Financial Modeller
Delivery Lead
Delivery Co-ordinator
Delivery Analyst
The new roles allow us to have a new focus on engineering as an enabler, and new skills/focus in
others areas to deliver new value at speed within our financial boundaries
2.8 Unleashing our data – we are progressively becoming a true centre of excellence
Data Warehouse
Developer
Data story teller

Capability verticals enables our team develop high levels of competence in their area of expertise. The
focus on outcomes is provided through delivery squads which we recalibrate on a regular basis. Bringing
this together is an agile operating and governance model.
2.9 Unleashing our data – We have also split our operating model into multiple layers 19
Focus on lifting core capabilities to increase capability and
productivity
Organised into outcome focussed squads with a focus a
clear set of objectives and outcomes (Porter’s model)
Self-Service
Delivery
Squads Platform
Management
EDW
Automation
Clinical
Databases
Data
Management
Agile delivery model powered by tools
such as Jira & Confluence

20
By taking a lightly modelled approach, we are able to surface real-time data to the presentation layer
whilst enabling an enterprise perspective
2.10 Unleashing our data – We are also continuing to invest in a real-time information architecture
Key design features include:-
1) A conformed layer in the middle enabling
enterprise insights
2) A lightly curated RDS layer allowing
citizen analysts to innovate with new
data
3) A data presentation layer, prior to
entering the BI tool, to allow portability
4) Ability to bridge enterprise metrics to any
data in our platform at the right grain
5) Independent resilient data layers that
allow for systems to be added or
replaced but still maintain an enterprise
view

Info Consumer Info Explorer Analysts Citizen Developer
Citizen Data Scientist
Visualisation
PowerBI Web N Y Y Y Y
PowerBI Desktop (Pro) N N Y Y Y
Custom Visualisation Tool (HIT managed) N N N Y Y
Data Management
Query Data (light & advanced) Synapse,
Snowflake Studio, DataBricks
Y Y Y Y y
Data Transformation Light
PowerBI Flow,
N N Y N N
Data Transformation Advanced ( Synapse,
Snowflake Studio, DataBricks, Snowflake DBT)
N N Y Y Y
Data Import / Export (light) – PowerBI Data Flow N Y Y N N
Data Import / Export (advanced) – PowerBI Data
Flow
N N Y Y Y
Data Storage
Fast Read Access (analytical) Synapse, Databricks, PowerBI (cached reports), Snowflake
Fast Read Access (OLTP) Cosmos, Azure Gen2 Data Lake
Bulk Load Azure Gen2 Data Lake
Fast UPSERT Azure Gen2 Data Lake, Azure SQL
Archive Azure Gen2 Data Lake
Replacing monolithic on-premise capabilities with monolithic cloud capabilities is not the answer and will result in
unsustainable cost profiles and mismatched capabilities. We are continually assessing cloud technologies to deliver cost-
effective outcomes
2.11 Unleashing our data – We are continually assessing and adopting fit for purpose capabilities

• Why does intelligence fail ?
• Enabling data innovation
• True self-service analytics
Self-service and data innovation
Clinical &
Operational
Intelligence
Self-Service &
Innovation
Integrated Real-
time Analytics
Enabling data innovation at the front-line safely and with speed
through “true” self-service.
03

No one has made the traditional
business intelligence model work ”
- Big Mountain Analytics
“
Common issues include:-
• Cannot traditional BI scale to the level required
to meet business needs
• The Business typically finds BI slow and
ineffective
• By the time IT delivers a solution, the problem
that generated the request is no longer a
problem
• The traditional model only addresses known
data and questions. It doesn’t address unknown
or future question

We are enabling a new set of users in the business we can extend our intelligence capabilities through virtual teams.
3.1 Self-service and data innovation - Where do we focus to deliver the required shift ? 24
Traditional Business Intelligence
Information
Consumers
Occasional
Analysts
BI Analysts
Modern Analytics Paradigm
Citizen
Analysts
Citizen
Data Engineers
Citizen Data
Scientists
Geeks /
Unicorns
Information
Explorers
Business Data
Stewards
Growth
Opportunity
Traditional
Users
Traditional Business Intelligence
Management /
Performance
Reporting
Strategic /
Compliance
Reporting
Operational
Data Science
Ad-hoc Data Analysis, Experimentation, Research
Operational
Reporting
Operational
Analysis
True Self-serve Analytics & Data Innovation
IN CONFIDENCE – Please do not distribute outside ADHB

We have designed this capability with security, governance and privacy at the centre, whilst enabling
our business teams to use their data when they need it
3.2 Self-service and data innovation - Our self-service analytics framework
Detailed Access Controls &
Usage Auditing
Self-Service
Personas
Self-Service
Framework
A realigned D&A capability model ‘DataOps’ Delivery Model Information Architecture
Outcome focused squads incl
Self-Service Enablement
Community of practice (chat, teams channel),
Wiki, Web Portal, Data Catalog (excel)
25

26
Decision Maker
/ Information
Consumer
Information
Explorer
Citizen
Analyst
Citizen Data
Developer
Citizen Data
Scientist
Key Activities
Technical Skills
Required
Tools Used
• View prebuilt reports • View prebuilt reports
• Slice and dice
intelligence reports
• Create and run excel
pivot tables to explore
data
• Build new SQL queries
to interrogate data
• Build PowerBI Reports
from datasets
• Publish new reports
• Write complex code to
transform data
• Develop deterministic
models
• Prototype new
intelligence outputs
• Build analytical models
using statistical and
programmatic
approaches
• None • Excel pivot tables and
pivot charts
• PowerBI Development
• SQL Code
• PowerBI development
• SQL Scripting &
procedures
• Lightweight
programming (e.g.
HTML, JavaScript)
• R / Python
• Advanced SQL coding
• Lightweight
programming (e.g.
HTML, JavaScript)
• Web browser • Excel
• PowerBI Web (optional)
• PowerBI Desktop
• PowerBI Web
• SQL Management
Studio (or similar)
• PowerBI Desktop
• SQL Management
Studio (or similar)
• R Studio
• PowerBI Desktop or
similar
• SQL Management
Studio (or similar)
We are working with business teams to enable key roles with the required skills to align to the
requirements of each of these personas
3.3 Self-service and data innovation - Our self-service product design revolves around 5 key
business user personas

27
How does it work?
1) HIT uses our new Self-Service data
generation engine to create
business and analyst data views
(simple excel like views). These
views remove all complexities of
joining data from different systems
2) The business data views are
published as PowerBI data sets
3) PowerBI reports and dashboards
are generated using 1 or more
PowerBI data sets
4) Business Intelligence analysts (or
similar) in the business can
generate new insights by :-
a) Creating new reports using
PowerBI Datasets
b) Adding data to existing business
data views and publish new
PowerBI datasets (manual)
c) Create brand new business data
views using analyst data views,
business data views and/or raw
source system data views
Analyst
Playpen
• Business data views
• Analyst data Views
• Raw source system data
Source Systems
e.g. CMS,
Safer sleep
Data
Warehouse
(Titan)
new
Import
PowerBI
Data Sets
Self-
Service
Engine
Enterprise Datasets –
Generated by
HIT SS Engine
Prototype +
Ad0hoc insights
Convert Prototype
insights into Enterprise
Directorate Staff
Use playpen to build new insights using :-
• Additional data from Titan
and source systems
• Import custom data from
spreadsheets & external sources
• Write SQL to build new views
HIT Data & Analytics team-
• Creates new libraries of simplified
views joining data from systems as
directed by customers
• Implements processes to publish
data to PowerBI data sets on a
regular basis (daily, hourly etc.)
• Implement security and
monitoring to ensure data usage is
governed
PowerBI
Visualisations
Microsoft Excel
Pivot tables and
charts
new
new
Analysts in directorate teams can prototype new datasets to build deeper insights. If required, these
can be optimised by HIT and released into production.
3.4 Self-service and data innovation - Business led data innovation is allowing us to deliver value

3.5 Self-service and data innovation - Our army of Citizen Analysts have led the delivery of new value 28
All of insights below have been prototyped and delivered by analysts in the business, building
prototypes and continuously iterating until they can land on insights that deliver value
Deliberately fuzzy

• Establishing a reliable data core
• Connected via data API’s
• Delivered to multiple data consumers
Enabling the digital ecosystem
Clinical Decision
Support Systems
Electronic
Health Record
Digital
Applications
Build once, use many times. How can we leverage our data to
meet a diverse set of business data needs
04

Integrated data & analytical insights delivered into our eco-system creates the opportunity to supply
data and rich content for delivery via modern digital platforms and multiple channels
4.0 Enabling the digital ecosystem – Integrated data & analytics is also key to driving digital
transformation
• Successful AI and analytics transformations require elements similar to
those found in successful digital transformations
• Need to focus on business outcomes and specific business use cases
• Data silos need to be broken down with integrated quality data
available for consumption and integration
• The right platforms needs to be selected to make data available for
consumption to operational and analytical use cases
SOURCE: The age of analytics: Competing in a data-driven world, McKinsey Global Institute, December 2016;
McKinsey Global Institute analysis
30

31
 Dendrite - Audit / Registry solutions requiring
patient context data (operational, clinical etc.) to
enrich clinical outcomes data and build rich data
registries
 Edge - Clinical trial management solution
requiring operational and clinical data to provide
contextual information
 REDCap – Clinical research database solution to
provide relevant clinical data to support clinical
research activities
 Other approved internal and external ancillary
systems needing data supply
 Clinical pathway applications to incorporate
patient, operational and clinical data from ADHB
and regional systems e.g. Orion care pathways,
SMT
 ADHB workflow and automationn solutions
required integrated data from ADHB systems e.g.
single view of employee, single view of patient
etc. Examples of these solutions include care
navigation, OIA automation, telehealth etc.
 AI/ML driven patient flow optimisation solutions
such as Signals for Noise, System View
 Using the CDS Master Data model, an integrated
view of patient and hospital data can be surfaced
via data API’s to populate a regional Health
Information Platform.
 This can include a variety of information
including patient history, clinical information
Clinical Decision
Support Systems
Electronic
Health Record
Data Supply
Digital
Workflow
Applications
Integrated EMR and PAS systems take many years, sometimes decades to implement fully, EHR’s
require costly data integration, which is even costlier in a changing application eco-system
4.1 Enabling our digital ecosystem – Our digital applications need data from our disparate legacy
systems

Cloud Data Staging Layer
These data API’s can be wrapped into integration and business orchestration layers as needed, or
used by our digital eco-system directly through a private gateway
4.2 Enabling our digital ecosystem – Our data foundation will be extended to meet our digital
needs through light weight cloud data API’s
32
Older/delicate
Source Systems
Raw Data Staging Layer
On-Premise
Cloud
Newer Source
Systems
Cloud Raw Data
(Structured)
Fast Data Cache
API
Gateway
Batch Load,
Micro Batch
Streaming
Batch,
Micro batch
Cloud Raw Data
(Unstructured)
CDS
Single View of
Data
Container
Management
for Micro-
services
Micro Batch
Streaming
Medical Devices
Batch, Micro Batch, Streaming
A secure data foundation
- real-time data where possible
(fast micro-batch data supply for
legacy systems)
- Treated as an operational
system 99.99% uptime
- Data encrypted at rest and in
motion
- Secure gateway connecting
Azure cloud to ADHB systems
- Avoids the cost of building
multiple data foundations and
integrated data sets

An integrated view of data is needed now to
4.3 Enabling our digital ecosystem – The business opportunity for the use of integrated data &
analytics is vast but challenged by large disparate application blueprint
Through our new modern delivery model and new capabilities, we
are shifting our capability models to support a wide variety of
business scenarios, operating across a hybrid eco-system of new
and legacy capabilities.
The opportunities are massive, and cloud enables delivery at very
low cost: -
1) True Self-serve analytics & data innovation
2) Integrated / prescriptive data science
3) Data driven clinical decisioning
4) Connected patient support through IOT and distributed
networks
All delivered through digital systems of engagement in context of
the care setting.
33
Hospital Systems
e.g. CMS, PHS,
pIMS
External
Systems
Cloud
Data
Warehouse,
ODS, Data
Marts
NoSQL +
Fast Data
Caches
API Gateway
Content
Stores e.g.
RIS, PACS
Connector Connector Connector Connector Connector
Connector
Raw Data External data
Analytical
Playpens
Data
Exchange
Security
&
Auditing
Master
Data
Management
Clinical &
Operational
Intelligence
Self-Service &
Innovation
Integrated Real-
time Analytics
Clinical Decision
Support Systems
Electronic
Health Record
Internet of things
e.g. bedside
monitoring,
devices
Internal &
External API
based data
sources
National and
3rd Party
Systems
Traditional DHB
Systems e.g. CMS,
HCC
Cloud Hosted
Systems (SaaS &
PaaS)
Digital
Applications
Data
Governance
Container
Management
Master &
Shared Data
(CDS)
Analytical
Models
Curated Raw
Data

Data and analytics strategy PUBLIC - ADHB 2021

More Related Content

What's hot (20)

Similar to Data and analytics strategy PUBLIC - ADHB 2021 (20)

Recently uploaded (20)

Data and analytics strategy PUBLIC - ADHB 2021