Metadata Management and Data Governance - Data Governance: Creating Value from Information Assets - page 47

Encounter ID Clinical Discharge Date Billing Discharge Date

101 12/1/2011 12/2/2011

FIGURE 3.3
Additional columns for Fit for Purpose model.

In addition, we can add additional columns to the main table to support
a Fit for Purpose model (Figure 3.3).

GOVERNANCE BOARD

The Governance Board should be a group of key BI senior sponsors, project
sponsors, and IT (information technology) personnel from each of the
business units. IT should serve the Governance Board as trusted advisors,
not the primary drivers of the board. The leadership of the board should
come from the business side. The board is not expected to be involved in
day-to-day management of the governance program, but is there to set
policies and standards.
The Governance Board should meet regularly, e.g., every month or quar-
terly depending upon number of issues. When the governance program is
first initiated, more frequent meeting will be required.

PROGRAM VERSUS PROJECT GOVERNANCE

The governance program should be program-managed as opposed to
project-managed. A program-managed governance program forces the
governance program to be enterprise-based. Figure 3.4 points out the
differences between the two approaches.

METADATA FRAMEWORK DEFINED

Metadata provides context for data by describing data about data. It
answers “who, what, when, where, how, and why” about every facet of