Your SlideShare is downloading. ×
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

Metadata Repositories in Health Care - Master Data Management Approach to Metadata Repositories

3,478

Published on

Karolyn Kerr …

Karolyn Kerr
(P11, 16/10/08, Data Quality stream, 11.10am)

1 Comment
12 Likes
Statistics
Notes
  • Please can you share the slide to jairajak@in.com
       Reply 
    Are you sure you want to  Yes  No
    Your message goes here
No Downloads
Views
Total Views
3,478
On Slideshare
0
From Embeds
0
Number of Embeds
0
Actions
Shares
0
Downloads
0
Comments
1
Likes
12
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  • 1. Metadata Repositories in Health Care Master Data Management Approach to Metadata Repositories Karolyn Kerr
  • 2. Outline of Presentation
    • What is Metadata?
    • What is Master Data?
    • Master Data Management
    • Using Master Data approach to Metadata Repository Management
    • Process for the Development of a Metadata Repository
    • Requirements of the Metadata Repository
  • 3. What is Metadata?
    • Meta - "an underlying definition or description"
    • Metadata is a definition or description of data
    • Back room metadata is process related – such as ETL guides for DBAs
    • Front room metadata is more descriptive helps query tools and report writers function smoothly
    • Front room and back room metadata can overlap
    • Kimball 1998
  • 4. What is Master Data?
    • Master data - data that are critical sets of data in the organisation
    • Consists of people (patients and staff), things (financial management, assets), places, reference data (such as the NHI and HPI)
    • Does not include all of the organisations data.
    • Distinct, clearly defined by the business users, and managed as a core dataset.
    • Example - Data that are used organisation wide and supported by a HISO standard
  • 5. Relationship between Master Data, Metadata, and the Enterprise Data Warehouse
  • 6. Master Data Management
    • Master data management is defined as
    • A set of disciplines, applications and technologies for harmonising and managing the system of record and entry for the data and metadata associated with the key business entities of an organisation.
    • (Powell Media LLC, 2006)
  • 7. Master Data Management
    • A structured and prioritised approach to managing metadata
    • Definitions and coding used is ‘locked down’ and unable to be edited by business users
    • Business processes used to collect this data are the same and defined in the master data repository
    • Supports a Total Data Quality Management approach
  • 8. Benefits of Master Data Management
    • Allows for the management of core business data in a consistent way across the organisation, including business processes, governance, and change management -
      • Reduced data redundancy
      • More consistent data
      • Significantly more efficient business through a complete view
      • Improved efficiency in change management processes
      • Improved return on IT investment
  • 9. What is Required?
    • Multi-year evolving strategic initiative that includes the development of:
    • Master data store and master metadata store
      • repository for storing and maintaining master data and its corresponding metadata
    • Master data integration services
      • such as enterprise application integration (EAI), extract, transform, and load (ETL) and enterprise information integration (EII)
    • Master data management processes
  • 10. Developing Master Data Management
    • Developed as an organisation wide strategic initiative with strong executive leadership support.
    • Challenges similar to any other strategic data quality initiative, and include:
      • Acceptance of ongoing roles and responsibilities
      • Organisation-wide governance to ensure discipline
      • Significant investment is required over time
      • Significant human resources may be required
      • Difficult to measure return on investment
  • 11. Governance and Change Management
    • A common set of master data governance procedures and business models, and business rules to maximise master data quality
    • Clear policies and procedures around changes to master data are critical to ensure consistent data management
  • 12. Metadata Repositories Including Master Data Management
    • Data and metadata reside in a single repository for consistent management of changes and updates
    • Master data allows for prioritisation in setting up the metadata repository. Decisions include:
      • What is our most important data in the data warehouse?
      • How do we want to manage this differently from our other data given finite resources?
  • 13. Contents of the Metadata Repository
    • Reason Purpose for of the Collection
    • Coverage of the Collection
    • Stakeholders of the Collection
    • Composition and lineage of the Collection
    • Access, Privacy & Security Requirements
    • Key Process Flows
    • Business Rules & Data definitions
    • Quality & Audit Requirements & Quality Assessment
    • Governance
    • References to Standards
    • Future Requirements
    • Collection Awareness/Communication
  • 14. Contents of the Metadata Repository
    • Data specific to individual departments, or defined differently by departments, may also be included in the data store and metadata repository.
    • May initially make up the majority of the metadata held in the repository.
    • Over time, as data elements are defined organisation wide, it can be moved into the master data store and repository.
  • 15. Access to the Repository
    • A web-based interface:
    • Allows all appropriate users access to the information
    • Data requests
    • A search browser will also assist users to find information, particularly once the repository increased in size.
  • 16. Conclusion
    • Master data management approach to setting up a metadata repository allows for:
      • Total Data Quality Management approach
      • Whole of organisation perspective
      • Prioritisation of data most important to the organisation
      • Allowing for other data to be held in the repository
  • 17.  

×