LEVERAGING THE ENTERPRISE INFORMATION
ENVIRONMENT
Louise Edmonds
Senior Manager Information Management
ACT Health
Information as an Asset
• Data is a corporate asset and must be accessible
• Distribution of data & information to the right people at the right time in the right format
• Create once, use many• One version of truth• Credible, coherent data using best practice
data principles
Data Governance Principles
• Data/Information management must be unified
• Authoritative sources must be identified• Data warehouse domain architecture
facilitates information availability• Data needs to be restructured for easy
access and management• Information security policy addresses
authorisation and authentication
ACT Health Business Requirements
• Enterprise wide approach to Information Management
• Enabling warehouse and report platform• Processes to support data governance and
standards • Consolidation of information systems• Development of online reporting for internal
and external stakeholders
Information Evolution Model
Level 1: Operate – Chaotic Information Environment– Individual silos – have authority over information usage
– Information infrastructure is limited, highly variable or subjective
– Individual methods of finding & analysing information are used. Little is documented and process repeatability is limited to individual knowledge.
– Individual results are adopted as ‘corporate truth’ - Many versions of truth
Information Evolution Model
Level 2: Consolidate – Departmental or Functional Level Information Environment
– Independent department islands of information are created
– Data are consolidated and accessed at department level.
– Departmental business measures are inconsistent across the enterprise
– Multiple interfaces and data extracts from operational databases reflect different versions of the truth
Information Evolution Model
Level 3: Integrate – Integrated Information Environment– Cross enterprise information access is in place
– Decision making is in an enterprise wide context
– An enterprise information governance process is in place
– Enterprise data frameworks are in place
– Information management concepts are applied
– Data Quality is valued and feedback is established
Information Evolution Model
Level 4: Optimise – Extension of the Integrated Information Environment– Enterprise Information Environment– Knowledge sharing leveraged
Level 5: Innovate – Organisational Culture of Innovation based on Integrated Information Environment– Agile innovation of organisation’s information assets
Information Evolution Model
Inf
orm
atio
n C
apab
ilitie
s
Strategic Value
Operate
Consolidate
Integrate
Optimize
Innovate
ACT Health Enterprise Information Management environment (ACTHEIM)
• The ACTHEIM environment is about how the information flow is managed from start to finish
• Provision of end to end dynamic data • Set of structured compliance elements that are
centralised to support shared corporate information knowledge.
• Central service point for the organisation’s information management and data requirements.
Business Metadata Management System (BMMS)
• Data Dictionary linked to AIHW METeORDescribes the data elements used in reporting
• Performance Indicator RegisterDescribes the Indicators derived and reported
• Information Output Register (IOR)Describes the reporting from systems
• Central Data Systems Register (CDSR)Describes data collection systems
ACT Health Data Dictionary
• Established set of National and Local definitions
• Ensures consistent collection, improved comparability, use and interpretation of data
• National definitions support and provide guidelines for development and use of local definitions
• Business Rules developed to provide detailed guide for use, additional information and direction for use in data collection
Performance Indicator Register
• Performance Indicators help define and measure progress toward organisational goals
• Performance Indicator Register is a set of comprehensive indicators defined for use in ACT Health including government and agency indicators
• The specification describes how each field in the register should be filled out. It clearly defines what constitutes valid data for each field
• Data Dictionary elements are the platform for development
Documentsthat define the need for the
indicatorNO FURTHER
ACTIONNO
Indicator Specification
Strategic Plan
Mandatoryreporting
Benchmarking
PolicyCompliance
Funding Agreements
Expected benefits and outcomes
Impacts on policies and procedures
Are restrictions on access needed?
Who is the sponsor?
Who sets targets?
Who has to achieve the targets?
Who receives the reports?
WHYWhy develop this indicator?
HOWHow will it be used?
WHO
Who is involved?
WHENWhat are the timelines?
WHATContext and details
Implementation deadline
Report frequency
Review dates
RESEARCH
Contract dates
Software application or care discipline
ACT Performance Domain (Divisions)
National Performance Domains
Threshold values used to assess results
Other essential criteria for development
DATA ENTRY INTO KEY PERFORMANCE INDICATOR SYSTEM
IS IT NECESSARY?
YES
Impacts on software applications
Privacy issues eg small cell values
Who are the stakeholders?
End dates - retirement of indicator
Indicator Concept Model
DataElement
Condition+ = INDICATOR
INDICATOR
Data element 1Condition 1
Data Element 2
Condition 2
Condition 3
Data Element n Condition nn
Modified by
Modified by
Modified by
PLUS
PLUS
Relational attributesRepresentational
attributes
Data DictionarySource systems
(CDSR)External definitions
Administrative attributes
FormatsData typesField size
Ownership, Responsibilities,frequency, strategies
Registration, tracking andversion control
Modified by
Information Output Register (IOR)
• Contains the list of outputs such as reports, including instructions on how these reports are generated and maintained.
• Provides operational and business areas a tool to document their outputs.
• Is critical in describing the output to be published in the enterprise environment.
• Supports identification of opportunities to develop efficiency gains and automation
Central Data Systems Register (CDSR)
• The Central data Systems Register (CDSR) is a repository of metadata about the various sources of data (primary, secondary and/or derived).
– ACTPAS = primary data source
– Admitted Patient Care dataset = Secondary + derived elements
Data Management Governance Framework
• Policy, Data Standards and Business Rules
• Accountabilities and processes
• Change management
• Data validation and cleansing protocols
• Extraction, Transformation and Loading processes
• Technical Metadata capability to support impact assessments and change management
• Defined operational requirements supporting integrated aligned data
Benefits
• Dynamic reports interfaced with underlying business metadata – consistent terminologies/standards
• Opportunity leveraging of organisation knowledge capital ie work undertaken in one area shared
• Reduction of duplication - elimination of redundancies• Availability to organisation of libraries of definitional
work, specifications and standards• Credible robust data – One source of Truth
Thank you