Skip Headers

 
Go to Documentation Home
Home
Go to Book List
Book List
Go to Table of Contents
Contents
Go to Feedback page
Contact Us

Oracle Healthcare Analytics Data Integration Release Content Document

Release 1.0

Part Number: E26521-01

November 2011


1. Introduction

Welcome to the Oracle® Healthcare Analytics Data Integration 1.0 Release Content Document.

1.1 Purpose of Document

This Release Content Document (RCD) communicates information about Oracle® Healthcare Analytics Data Integration (OHADI). It is a new product, which provides a solution that addresses the multiple challenges involved in the integration of data from disparate sources. It facilitates the loading of heterogeneous data into a set of standard, source system-agnostic data structures and then manage that data proactively. It's major components include:

  1. System of Record Proxy (Interface Tables)

  2. Rules Framework and Engine

  3. Exception Management Framework

  4. Master Data Management

  5. Meta Data Management

  6. Business rules framework using ODI

  7. Out of the box business rules

2. Oracle Healthcare Analytics Data Integration

2.1 Release Overview

OHADI is a means by which clinical, financial, administrative, and research data from the Providers' source systems can be validated, consolidated, integrated, cleansed, and loaded into the EHA HDWF-based enterprise data warehouse. In combination with the HDWF data warehouse, OHADI provides a productized solution that addresses the multiple challenges involved in the integration of data from disparate sources. The goal of data integration is to facilitate the loading of heterogeneous data into a set of standard, source system-agnostic data structures and then manage that data proactively:

2.2 Features

2.2.1 System of Record Proxy

The System provides a system of record proxy (SORP) for all systems that populate EHA. That is, it retains all data as received from the source system in the form in which is was received.

  1. Data is persisted in the SORP before data quality validation rules and data quality transformation rules have processed the data.
  2. From the perspective of EHA – this persistence represents the proxy for system of record (source system).

2.2.2 Rules Framework and Engine

Business rules in data integration and warehousing cover the entire gamut of data and metadata that is stored and used in these systems and data management processes. At a high level, these rules can be categorized into the following categories:

2.2.3 Master Data Management

OHADI provides a flexible, extensible and unified data model to hold the master data and all needed attributes. It accounts for the varied uses of master and reference data from the interface tables to HDWF to data marts/cubes/analytical applications. This model supports a full and robust set of data management features and a user experience for collaboration that maximizes adoption. It includes a data quality function that can find and eliminate duplicate data while insuring correct data attribute survivorship (via business rules) to create a “single source of truth”.

2.2.5 Meta Data Management

OHADI supports the following categories of metadata:

OHADI also provides the appropriate system columns that allow for end-to-end metadata management even if the customer does not have a dedicated and stand-alone metadata management system.

2.2.6 Business Rules Framework using ODI

OHADI provides data lineage via ODI funcitonality, system columns, and via out of the box mappings across all Oracle EHA products in addition to more advanced features that may be available from ODI 11g, ODI Metadata Navigator, Informatica Metadata Manager, and the like.

2.2.7 Out of the Box Business Rules

OHADI includes out of the box rules which are configurable and ready to use by the customer. It includes rules that leverage master seed values, seeded terminologies, and pre-defined mappings (from a terminology vendor like Apelon or HLI) or a Terminology Management System (such as ETS Lite or similar). OHADI preserves the customer's modifications to the out of the box rules and will not overwrite them during product upgrades.

Documentation Accessibility

For information about Oracle's commitment to accessibility, visit the Oracle Accessibility Program website at http://www.oracle.com/pls/topic/lookup?ctx=acc&id=docacc.

Access to Oracle Support

Oracle customers have access to electronic support through My Oracle Support. For information, visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=info or visit http://www.oracle.com/pls/topic/lookup?ctx=acc&id=trs if you are hearing impaired.

Related Documents

The Oracle Healthcare Analytics Data Integration 1.0 Integrated Documentation Package:

Conventions

The following text conventions are used in this document:

Convention Meaning
boldface Boldface type indicates graphical user interface elements associated with an action, or terms defined in text or the glossary.
italic Italic type indicates book titles, emphasis, or placeholder variables for which you supply particular values.
monospace Monospace type indicates commands within a paragraph, URLs, code in examples, text that appears on the screen, or text that you enter.

Top