data modeling, meta data and data lineage demo - highlights from 2016 data modeling zone...

18
Metadata Management and Data Lineage at a Large Healthcare Organization How Data Flows are Documented and Managed (Excepts from Presentation Prepared for Data Modeling Zone) October 2013 Written by Angela Boyd–Center for Clinical Excellence 1

Upload: angela-boyd

Post on 22-Jan-2018

132 views

Category:

Documents


5 download

TRANSCRIPT

Metadata Management and Data Lineageat a Large Healthcare Organization

How Data Flows are Documented and Managed(Excepts from Presentation Prepared for Data Modeling Zone)

October 2013

Written by Angela Boyd–Center for Clinical Excellence

1

Metadata Management & Data LineageHow Data Flows are Documented and Managed

Presentation Agenda:

• Introduction

• Framework for beginning metadata documentation

• Tasks and Timeframes

• Demo of Metadata Management in PowerDesigner• Modeling Data Flows

• Data Lineage of Data Elements

• Managing the model

• Summary

• Questions and Answers

2

Current Clinical Data Architecture

3

Documentation of Data Flows in Current Systems – Metadata Management Needed

Framework for Beginning Metadata Documentation –Leadership Objectives to Support Metadata

1. Information Stewardship – Processes and policies are needed to manage data as an asset • Standardized metadata format to be used for entire enterprise

2. Data Quality Program – Collaborate across enterprise with database teams to begin formal data quality processes• Metadata needed to compare data across enterprise

3. Information Documentation – Begin Enterprise Metadata Management• Document enterprise data flows (data shared between two or more systems/databases)

• Start with crucial enterprise data (data used in algorithms for Governmental Measures)

• Expand into other data areas

4

Beginning Metadata Documentation – First Year

5

Tasks, Progress and the Time Required to Complete:

Tasks: Status/Progress:

• Establish documentation requirements of data flows across enterprise (in Excel)

• Create templates for documenting data flow/interfaces

• Create how-to documentation for documenting data flows

• Train enterprise database teams to use tool to document data flows/interfaces

• Each database/system enters data flows into PowerDesigner tool

Completed – Database teams established minimum set of fields needed (1-2 months)

Completed – Templates/Objects diagrammed in PowerDesigner tool (6 months)

Completed - Tutorials created for installing tool and how to document data lineage (3 months)

In progress – Two teams trained, and three teams require training (3-6 months)

In progress – Two teams have begun, and three need to begin to complete project by end of year (3-6 months)

Metadata of Data FlowsBeginning Diagram for each Database/System to Launch Home Page

6

Metadata of Data Flows

Database/System Interface Summary Diagram

7

Metadata of Data Flows

Interface Details: Icons for each step of the data flow

8

Interface Details - Administrative: CDR to PES Enterprise HL7 ADT

PES DatabaseCDR Database Data Flow Details - CDR -

CDR to PES Enterprise HL7

ADT

Data Flow Details - PES -

CDR to PES Enterprise HL7

ADT

Data Flow Details - IIG -

CDR to PES Enterprise

HL7 ADT

Administrative

Interface - IIG (from

CDR) - CDR to PES

Enterprise HL7 ADT

Administrative

Interface - CDR - CDR

to PES Enterprise

HL7 ADT

Metadata of Data FlowsFlat File Icons: Field names and description

9

Metadata of Data Flows

Flat File Icon: template created and used for HL7 messages

10

Metadata of Data Flows

Transformation Diagram: Details of data flow between message and database

11

Data Flow Details – CDR to PES Enterprise HL7 ADT

Metadata of Data Flows

12

Property Sheets of Tables: DMM tied to PDM tables

Metadata of Data Flows

13

Property Sheets of Tables: Additional Description

Data Lineage of Data Elements

14

Target Tables: Using the Data Structure Mapping Editor

Right-click,

and select

Data

Structure

Mapping

Editor

Data Lineage of Database Outputs

15

Target Table: ‘Registration’ - Impact and Lineage Analysis

Data Lineage of Data Columns

16

Data Structure Column: ‘Facility Concept ID’ - Impact and Lineage Analysis

Beginning Metadata Documentation of Data Lineage – Summarization

• Framework to begin metadata approved by management

• Support across enterprise

• Metadata requirements developed collaboratively

• All enterprise databases developed and vetted the content

• Standardized templates populated in PowerDesigner

• Metadata allows for complete data lineage

• Provides additional understanding of data across enterprise

• Supports our new Data Quality Program

• We are one year into process, and there are many data flows still to be documented

• Start small, stay focused and demonstrate/celebrate “wins”

17

Metadata Management and Data Lineageat a Large Healthcare Organization

Questions?

18

How Data Flows are Documented and Managed