Transcript Mayo Clinic's Information Architecture: A Meta

Mayo Clinic's Information
Architecture: A Meta-data
Repository Implementation
April 19, 2000
Minnesota DAMA Chapter
Sonja Ziegler - Data Administrator
Mayo Foundation, Rochester, Minnesota USA
Copyright, 2000 © Mayo Foundation
Agenda
•
•
•
•
•
Background Overview
The Vision
The Scope
The Project
The Future
Background
• Began the search for a comprehensive data
model repository in 1995
• Purchased Rochade in 1996
• Training and familiarization throughout
1996
• Established steering committee in late 1996
• Throughout 1996-1998 a variety of projects
were undertaken to address varying needs
Lessons Learned
• Identification of a specific business need
that requires attention is crucial
• The scope of the implementation efforts
must be tightly controlled
• An appropriately staffed repository team is
needed for implementation and coordination
• A committed user/proponent must be
engaged in the project
The Vision
Information Architecture
• Data Architecture
Documentation of all pertinent information about an organization’s
data and its interactions
• System Architecture
The documentation of applications areas and their relations to
business areas, information systems, vendors and IT personnel
• Business Rules
The documentation of business related knowledge that defines the
rules of behavior to support the business’ operating procedures
using business vernacular
• Impact Analysis
The ability of developers to gauge the impact that a change to some
architectural element will have upon its surrounding elements
The Scope
• The Mayo Data Architecture - our first step to a
complete Information Architecture and we had a
committed user base!
• A top-down approach was not feasible because of
current company culture
• With a diverse multi-platform environment, just
documenting what’s there is a vast improvement
• Recognizing the difference between the efforts
that can be automated by the repository and those
that can’t
The Data Architecture Project
•
•
•
•
•
The Team
The RIMs (Repository Information Models)
The User Interface
The Infrastructure Components
Mayo’s Problem Space
–
–
–
–
Summarization
The Data
Population
Our Goal
The Team
• One FTE for Project Coordination/Management
• One FTE for Database and System
Administration
• One FTE (at least) for Application
Development
Plus a group of individuals to act as users.
- FTE (full time employee)
Mayo Data Conceptual Level RIM
DA/Abbreviation
DA/SubjectArea
DA/Synonym
DA/AttributeCategory
DA/Relationship
DA/Entity
DA/Attribute
DA/PreferRepresentation
DA/RelationshipMAP-Rule
DA/EntityMAP Rule
DA/AttributeMAP-Rule
Mayo Data Logical Level RIM
DA/SubjectArea
DA/Relationship
DA/Entity
DA/Attribute
DA/RelationshipMAP-Rule
DA/EntityMAP Rule
DA/Attribute-
XREF/DataModel
XREF/Relationship
XREF/Entity
XREF/Attribute
XREF/DataSchema
XREF/Reference
XREF/DataStructure
XREF/Field
PWRDES/
CDM-Model
PWRDES /
Relationship
PWRDES /Entity
MAP-Rule
PWRDES /Attribute
Mayo Data Physical Level RIM
PWRDES/
CDM-Model
PWRDES /
Relationship
XREF/DataModel
XREF/Relationship
XREF/DataSchema
XREF/Reference
SYB/Database
SYB/Table
PWRDES /Entity
PWRDES /Attribute
XREF/Entity
XREF/Attribute
XREF/DataStructure
SYB/Column
NSSQL/Table
XREF/Field
NSSQL/Column
Mayo Application RIM
DA/SubjectArea
DA/Relationship
DA/RelationshipMAP-Rule
XREF/Relationship
DA/Entity
DA/EntityMAP Rule
XREF/Entity
XREF/Reference
XREF/DataStructure
XREF/DataModel
XREF/DataSchema
DA/Attribute
Appl/AttributeMAP-Rule
DA/AttributeMAP-Rule
DA/InterfaceAttribute
Appl/Message
XREF/Attribute
Appl/Interface
XREF/Field
Appl/CRUDMAP-Rule
Appl/Application
The User Interface &
Infrastructure Components
Rochade™
BUSES AND SCANNERS
FROM VIASOFT™
• Sybase™ Catalogs
• PowerDesigner™ Models
• DB2® Catalogs
• COOL:Gen™
• MVS JCL
• COBOL Programs
• COBOL Data Libraries
• Assembler Programs
DEVELOPED SCANNERS
• Enscribe
• FOCUS®
• NonStop™ SQL
CSV IMPORT UTILITY
• Microsoft® Access Data
USER INTERFACE
• VIASOFT™ AutoPilot
• MDX-Manager
MAINTENANCE
• Application
• Data Architecture
• Cross Reference
METAQUEST™ QUERY/
REPORTING MODULES
• Easy (EZ)
• Dual Display (DD)
• Extended (EX)
• Power (PW)
• Administration Tool
MetaQuest™ Cross Reference Update
MetaQuest™ Query/ EZ-Query
MetaQuest™ Report Display
MetaQuest™ Query/ DD-Query
Problem Summarization
• Mayo has chosen to follow a philosophy of selecting many
best-of-breed applications and then interfacing between
them.
• Their relative data models were not designed from an
overriding Enterprise Architecture (a bottom-up approach).
• As a result, we have data concepts represented differently
and named in many different ways throughout our
information architecture.
ISSUES:
• the need to understand our diverse data concepts
• the need to integrate our applications
The Data
• MICS (Mayo Integrated Clinical Systems)
Data Architecture Project undertaken by
Data Administration in cooperation with the
application development teams
• The Data Architecture Model (DAM), the
Application Logical Models (ALMs), and
the database catalog information
Population of the Repository
•
•
•
•
Data entry by summer student personnel
Real work here, no silver bullets
Commitment from management for project
Identified personnel from Data
Administration and development projects
• Ongoing processes established to maintain
integrity of repository contents
Mayo’s Goal
To have information at hand that will facilitate the
understanding needed for:
• creating efficient application interfaces
• effectively designing new databases
• redesigning existing databases.
Now & Our Future
• Continued commitment from Data
Administration to populate the Data Architecture
• Benefits are already being seen, which turns into
good advertising for further IS involvement
• Prioritize and keep the scope under control of
the varying requests for implementations of the
repository (Mayo Rochade Steering Committee)
Questions
Contact Information
Sonja Ziegler - [email protected]
Mayo Foundation
200 1st Street SW – Massey Studio
Rochester, MN 55905