Glossary: IBM Initiate Master Data Service

IBM Initiate Master Data Service
Version 10 Release 0
Glossary
GI13-2614-00
IBM Initiate Master Data Service

Version 10 Release 0
Glossary
GI13-2614-00
Note
Before using this information and the product that it supports, read the information in Notices and trademarks on page
35.
Copyright IBM Corporation 1995, 2011.

US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract
with IBM Corp.
Contents
IBM Initiate glossary . . . . . . . . . 1
Active Attribute . . . .
Aggregation . . . . .
Algorithm . . . . . .
Algorithms tab . . . .
Anonymous Values . . .
Attribute. . . . . . .
AutoLink MS . . . . .
AutoLink SS . . . . .
Auto-link Threshold . . .
Auto-timeout . . . . .
Auto-Unlink . . . . .
Bootweights . . . . .
Bridge Member . . . .
Broker . . . . . . .
Bucket / Bucketing . . .
Bucket Data . . . . .
Bulk Cross Match. . . .
Callback Handler . . . .
Candidate . . . . . .
Candidate Selection . . .
CDI . . . . . . . .
Centralized Hub . . . .
Clerical Review Threshold .
Cloud . . . . . . .
cltdicd . . . . . . .
Comparison . . . . .
Comparison Data . . . .
Comparison Score . . .
Composite View . . . .
Consuming System . . .
Context Pool Size . . . .
Controlled View . . . .
Core Member Data . . .
Cross Bucketing . . . .
Customer Profiling . . .
Data Extract File . . . .
Data Files . . . . . .
Data Manager . . . . .
Data Profiling . . . . .
Data Steward . . . . .
Definitional Source . . .
Delete . . . . . . .
Deleted Attribute . . . .
Demographic Data . . .
Derivation Process . . .
Derived Data . . . . .
Deterministic Matching . .
Duplicate Record . . . .
Dynamic Task Creation . .
EID . . . . . . . .
EID Synchronization . . .
EMCA . . . . . . .
EMPI . . . . . . . .
Encounter Data . . . .
Engine Callouts . . . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
Copyright IBM Corp. 1995, 2011
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
1
1
1
1
1
2
2
2
2
2
2
2
3
3
3
3
3
3
3
4
4
4
4
4
5
5
5
5
5
5
5
6
6
6
6
6
6
6
7
7
7
7
7
7
7
7
8
8
8
8
8
8
8
8
9
Enterprise Customer Identity Management . . . . 9

Enterprise ID . . . . . . . . . . . . . . 9
IBM Initiate Enterprise Service Oriented Architecture
(ESOA) Toolkit . . . . . . . . . . . . . 9
Entity. . . . . . . . . . . . . . . . . 9
Entity Manager . . . . . . . . . . . . . 9
Entity Type . . . . . . . . . . . . . . 10
EntRecno . . . . . . . . . . . . . . . 10
Environment . . . . . . . . . . . . . . 10
ER . . . . . . . . . . . . . . . . . 10
Error Types . . . . . . . . . . . . . . 10
ETL . . . . . . . . . . . . . . . . . 10
Event . . . . . . . . . . . . . . . . 10
Event Date . . . . . . . . . . . . . . 11
Event Initiator . . . . . . . . . . . . . 11
False Negative . . . . . . . . . . . . . 11
False Positive . . . . . . . . . . . . . . 11
False Positive Filter . . . . . . . . . . . . 11
Fixed Segments . . . . . . . . . . . . . 11
Get . . . . . . . . . . . . . . . . . 11
Glue Member . . . . . . . . . . . . . . 11
Golden Record . . . . . . . . . . . . . 12
Group Entities . . . . . . . . . . . . . 12
Groups . . . . . . . . . . . . . . . . 12
Hardlink . . . . . . . . . . . . . . . 12
HasShadow . . . . . . . . . . . . . . 12
Hierarchy . . . . . . . . . . . . . . . 12
Hierarchy Tree . . . . . . . . . . . . . 13
Hints . . . . . . . . . . . . . . . . 13
Historical Attributes . . . . . . . . . . . 13
HL7 Query Adapter (Query Broker) . . . . . . 13
Hook Point . . . . . . . . . . . . . . 13
Household / Household Entity . . . . . . . . 13
Hub Attributes . . . . . . . . . . . . . 13
Hub-controlled Attributes . . . . . . . . . 13
Hybrid Hub . . . . . . . . . . . . . . 14
Identification Task . . . . . . . . . . . . 14
Identifier . . . . . . . . . . . . . . . 14
Identity Domain . . . . . . . . . . . . . 14
Identity Entity . . . . . . . . . . . . . 14
Identity Rules . . . . . . . . . . . . . 14
IMM. . . . . . . . . . . . . . . . . 14
Implementation-Defined Segments. . . . . . . 15
Inactive Attribute . . . . . . . . . . . . 15
Inbound Broker . . . . . . . . . . . . . 15
Informational Source . . . . . . . . . . . 15
Interaction . . . . . . . . . . . . . . . 15
Interceptor. . . . . . . . . . . . . . . 15
Invalid Reference . . . . . . . . . . . . 15
Linkage. . . . . . . . . . . . . . . . 15
Linkage Modification Date . . . . . . . . . 16
Linkage Set . . . . . . . . . . . . . . 16
Linkage Status . . . . . . . . . . . . . 16
Linkage Type . . . . . . . . . . . . . . 16
Log Files . . . . . . . . . . . . . . . 16
Logical Deletion . . . . . . . . . . . . . 16
iii
Madlogs . . . . . . . . . . . .
ManuLink-MS . . . . . . . . . .
ManuLink-SS . . . . . . . . . . .
Many-to-Many Relationships . . . . .
Mapping Message Manager (Message Broker)
Master Data Engine . . . . . . . .
Master Data Engine server . . . . . .
Master Data Extract . . . . . . . .
Match . . . . . . . . . . . . .
Matched Pairs . . . . . . . . . .
MCA . . . . . . . . . . . . .
MDM . . . . . . . . . . . . .
Member Get Interaction . . . . . . .
Member Logical Model . . . . . . .
Member Match Interaction . . . . . .
Member Put Interaction . . . . . . .
Member Search Interaction . . . . . .
Member Status . . . . . . . . . .
Member Type. . . . . . . . . . .
Member/Record . . . . . . . . . .
MemRecno . . . . . . . . . . .
Merge . . . . . . . . . . . . .
Message Broker . . . . . . . . . .
Message Processor . . . . . . . . .
Message Reader . . . . . . . . . .
Missing Relationship . . . . . . . .
MPI . . . . . . . . . . . . . .
MPINET . . . . . . . . . . . .
mpxdata Configuration File . . . . . .
Multiplicity Relationship . . . . . . .
NoChange . . . . . . . . . . . .
Non-Event. . . . . . . . . . . .
Non-Identity Rules . . . . . . . . .
Non-Obvious Relationships . . . . . .
Non-Simple EID . . . . . . . . . .
Non-transitive entity . . . . . . . .
Organization . . . . . . . . . . .
Outbound Broker . . . . . . . . .
Overlay. . . . . . . . . . . . .
Owner . . . . . . . . . . . . .
Path to Root . . . . . . . . . . .
Person . . . . . . . . . . . . .
PIM . . . . . . . . . . . . . .
Pivot Record . . . . . . . . . . .
Potential Duplicate . . . . . . . . .
Potential Linkage . . . . . . . . .
Potential Overlay . . . . . . . . .
Premerge . . . . . . . . . . . .
Probabilistic Algorithms . . . . . . .
Probabilistic Matching . . . . . . . .
Proband . . . . . . . . . . . .
Promotion . . . . . . . . . . . .
Provider . . . . . . . . . . . .
Real Time . . . . . . . . . . . .
Record . . . . . . . . . . . . .
Registry Hub . . . . . . . . . . .
Relationship Creation . . . . . . . .
iv
Glossary
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
16
16
16
17
17
17
17
17
17
17
18
18
18
18
18
18
18
19
19
19
19
19
19
19
20
20
20
20
20
20
20
20
21
21
21
21
21
21
21
21
22
22
22
22
22
22
22
22
23
23
23
23
23
23
23
24
24
Relationship Creation Rule . . .

Relationship Task . . . . . .
Relationship Type . . . . . .
Re-parenting . . . . . . . .
Review Identifier . . . . . .
ROC Curve . . . . . . . .
Routing Message Manager (Routing
Score / Scoring . . . . . . .
Search . . . . . . . . . .
Segment . . . . . . . . .
Service Model . . . . . . .
Shadow Attribute . . . . . .
Simple EID . . . . . . . .
Singleton . . . . . . . . .
Softlink . . . . . . . . . .
Source . . . . . . . . . .
Source ID . . . . . . . . .
Source ID Status . . . . . . .
Source System . . . . . . .
SrcRecno . . . . . . . . .
Standardized Data . . . . . .
Surviving Enterprise ID . . . .
Surviving Source ID . . . . .
Tag . . . . . . . . . . .
Task Creation Date . . . . . .
Task Get Interaction . . . . .
Task Hints . . . . . . . . .
Task Life Cycle . . . . . . .
Task Model . . . . . . . .
Task Modification Date . . . .
Task Put Interaction . . . . .
Task Resolution . . . . . . .
Task Search Interaction . . . .
Task Set . . . . . . . . .
Task Types. . . . . . . . .
Templates . . . . . . . . .
Threshold . . . . . . . . .
Transitive entity . . . . . . .
Trigger Member or Trigger Record.
Trusted Source View . . . . .
Undelete . . . . . . . . .
Virtual Attributes . . . . . .
Virtual Member . . . . . . .
Virtual Source . . . . . . .
Web Services . . . . . . . .
Weight . . . . . . . . . .
Weight Generation . . . . . .
Workflow Status . . . . . . .
. . .
. . .
. . .
. . .
. . .
. . .
Broker)
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
. . .
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
24
24
24
24
24
25
25
25
25
25
25
25
26
26
26
26
26
26
26
26
27
27
27
27
27
27
28
28
28
28
28
28
28
29
29
29
29
29
29
30
30
30
30
30
30
30
30
31
Legal Statement. . . . . . . . . . . 33
Notices and trademarks . . . . . . . 35
Index . . . . . . . . . . . . . . . 39
Contacting IBM . . . . . . . . . . . 41
IBM Initiate glossary

The terms in this glossary are used throughout the IBM Initiate products. This
glossary is distributed as part of the base IBM Initiate Master Data Service software
and is also used as an attachment to other product documentation. As new terms
are identified, they will be added to this document.
Active Attribute
An attribute status of A indicates that the attribute displayed is the most current,
active value of the attribute. An attribute can have more than one active value
depending upon settings in the database. (See: Attribute, Inactive Attribute,
Deleted Attribute)
Aggregation
In IT, aggregation is the process of amassing or gathering individual parts of
information (data) from disparate systems to create one complete customer view.
Algorithm
IBM Initiate Master Data Service software applies proprietary algorithms to
compare and score member attribute similarities and differences. An algorithm is a
step-by-step procedure for solving a problem. The IBM Initiate Master Data Service
algorithm has three steps: Standardize, Bucket, and Compare. The final step,
Compare, is what yields the score. The algorithms are applied to data to create
tasks and support search functionality, and are tailored to use attributes specific to
your business.
Algorithms tab
A component of the IBM Initiate Workbench Configuration Editor that allows for
quick and easy configuration of algorithms.
Anonymous Values
To accommodate the occurrence of fictitiously entered member data without
adversely affecting a comparison score, a list of anonymous values are maintained
in the Hub database. For example, if a record is being entered into a source system
and the Social Security information is not available, users may enter a value of
000-00-0000 or 999-99-9999. In such a case, if these numbers are seen in the SSN
field, they are not considered by the algorithm in the comparison. The algorithms
are configured to not assign a score to attributes containing anonymous or missing
values.
Attribute
Information or demographics describing particular data for a memberperson (for
example, name, date of birth, address, Social Security number) or object (for
example, company name, part number). While there are some attributes that may
be considered pre-configured standards for a particular member type
implementation, all attributes are configurable based on the needs of your
organization. (See: Hub Attributes, Hub-controlled Attributes, Virtual Attributes)
AutoLink MS
(Linkage type.) Indicates records compared from multiple sources that scored
above the auto-link threshold. When this occurs, a common Enterprise ID is
assigned by the Master Data Engine.
AutoLink SS
(Linkage type.) Indicates records compared from the same source which scored
above the auto-link threshold, indicating that they are duplicates. A common
Enterprise ID is assigned by the Master Data Engine. Same source linking can be
disabled.
Auto-link Threshold
This threshold setting determines the score at which linkages are created. Records
with comparison scores above this value are deemed to have a high likelihood of
representing the same person, and are automatically linked and assigned a
common Enterprise ID. These records can be manually reviewed if your workflow
process deems it necessary. The auto-link threshold can be customized to meet the
needs of your organization. (See: Clerical Review Threshold, Threshold)
Auto-timeout
To assist in data security, many applications have been designed with an automatic
timeout feature. If a user is logged in to an application and does not interact with
the application (for example, performing a search or editing an attribute) for a
pre-defined time, the application automatically logs the user out of the system.
Auto-Unlink
A previously auto-linked record that, because of new information, no longer
compares above the auto-link threshold with another record and has been
automatically unlinked by the Master Data Engine.
Bootweights
Bootweights are pre-determined, hardcoded weights that are used to start the
weight generation process.
Glossary
Bridge Member
In the context of group entities, a bridge member is a member that is associated
with more than one bucket. (See: Group Entities, Many-to-Many Relationships,
Cross Bucketing, and Non-Obvious Relationships.)
Broker
See: Inbound Broker and Outbound Broker.
Bucket / Bucketing
Bucketing is a part of the derivation process in which the Master Data Engine
groups specify attributes for use by the candidate selection process. Examples of
possible buckets are: Last Name + Phone, or Last Name + Email Address, or Last
Name + First Name. Buckets are defined during your initial configuration of IBM
Initiate Master Data Service software by the project team and can have one or
more attributes per bucket. (See: Bucket Data)
Bucket Data
Bucket data is the output of the derivation attributes configured to participate in
the candidate selection. For example if you have a bucket configured for Address,
the bucket data for an address might be 1043_W_EASY_ST_85545. The
standardized string is converted to a format that makes for quick access during
candidate selection. Bucket data is created during the derivation process after
standardization. (See: Bucket / Bucketing, Comparison Data, Derivation Process,
Standardized Data)
Bulk Cross Match

The bulk cross match (BXM) is a process that allows you to compare and link
thousands of records per second. The BXM is most commonly performed in the
initial stage of the implementation and again just before the system goes live. The
BXM process is made up of two primary utilities: MPXCOMP (Compare Members
in Bulk) and MPXLINK (Link Entities). Details about these two utilities can be
found in the IBM Initiate Master Data Service Engine Installation Guide and IBM
Initiate Workbench User's Guide.
Callback Handler
Custom code that defines the callout logic. Used by the Master Data Engine to call
out to third-party systems or to implement conditional security, event notification,
or additional processing steps.
Candidate
When a search request is sent to the Master Data Engine, the engine returns a list
of individuals that meet the search parameters. These individuals are referred to as
candidates.
Candidate Selection
Candidate selection is a behind-the-scenes process whereby records stored within
the Hub database are selected, based on common buckets, for comparison against
another member record to determine a potential match. The selection process uses
the values of an incoming record to compare against existing member records with
similar buckets and the returned result is a list of candidates who share at least
one bucket in common. This list of candidates then proceeds to the comparison
stage. (See: Bucket Data, Bucket / Bucketing, Comparison)
CDI
Customer Data Integration. The sum of procedures, automation, and skills required
to standardize and integrate customer data that originates from different sources.
CDI attempts to address the situation when two or more sources that contain
records referring to an overlapping set of real-world customers lack unique
identifiers that show the correspondences between the records in the multiple
sources. Furthermore, the records representing the same entity might have differing
information. For example, one record might have the address misspelled, another
record might be missing some fields, and so on.
Centralized Hub
Also called Transactional Hub or Persistent Hub, Centralized Hub describes an
architectural style in which the Master Data Engine gathers and synchronizes data
from sources and persists a copy of an Entity-level composite view. With a
Centralized Hub, the engine maintains the official versions of records and
propagates any required changes out to source systems. In a Registry Hub
implementation, this view is only generated at runtime by the MEMSEARCH or
MEMGET APIs. (See: Registry Hub, Hybrid Hub)
Clerical Review Threshold

Threshold levels are scoring levels which determine how records are managed in
the Master Data Engine. This threshold setting is compared to the linkage score
generated by the comparison routines and algorithms. Records with comparison
scores above this value but below the Auto-link Threshold are added into a
review queue for manual determination of the linkage or potential data issue.
Records that compare below this threshold have such a small likelihood of being
the same customer that task creation has little value and therefore, a task is not
generated. Clerical Review threshold might be customized for your organization.
(See: Auto-link Threshold, Threshold)
Cloud
(IBM Initiate Inspector functionality) When the number of relationships of a
specific type exceeds the threshold set during configuration, a cloud displays in the
Relationship View.
Glossary
cltdicd
A file containing database metadata defined for an IBM Initiate Master Data
Service software configuration at the time of system configuration.
Comparison
The application of one or more algorithms to determine similarities and differences
between two or more records. This process compares the individual
attributesattribute by attributeof each record selected during the candidate
selection process. (See: Bucket Data, Bucket / Bucketing, Candidate Selection,
Comparison Score.)
Comparison Data
Each algorithm implemented is configured to compare certain attributes. Such
identified attributes are extracted from the core data, standardized, and stored as
comparison data in the derived data layer of the Hub database. Comparison data
is formatted and stored in a manner that allows for fast access and comparison.
Comparison data is stored in the Hub database. (See: Core Member Data, Bucket
Data, Bucket / Bucketing, Standardized Data, Derivation Process)
Comparison Score
The score returned for records after the comparison process is performed by the
Master Data Engine. Comparison scores might result in task or linkage creation
based on the thresholds set for your organization. The higher the score, the more
likely that the records represent the same person.
Composite View
A composite view is a defined way of displaying attribute information; for
example the views might be either enterprise most current attribute or
source-specific attribute values for a person. (See: Controlled View, EMCA, Trusted
Source View)
Consuming System
These systems (for example, a radiology system) consume, rely upon and/or use
identity information such as a medical record number, frequent customer number,
or other identifiers assigned by a source system to identify a given object or
member. Consuming systems are often referred to as transactional systems. It is
possible for a system to be both a source and a consuming system, such as
registration or reservation systems.
Context Pool Size

(ContextPoolSize) The context pool size is the number of Master Data Engine
'threads' that are started concurrently. Each context pool has its own connection to
the database and can operate independently of the others. If you have your context
pool set at 5, for example, you can send in five searches or gets or puts at the exact
same millisecond, and they are all processed concurrently. If six are sent, then the
first five process while the sixth waits for the next free context.
Controlled View
This type of composite view displays a selection of various attributes from
multiple specified sources. For example, you can specify to display name and
address from Source A, phone and birth date from Source B, and Social Security
number and address from Source C.
Core Member Data

The complete set of data (all attributes) about a member stored in the Hub
database. This set might include historical data for a member as well as the most
up-to-date version.
Cross Bucketing
In group entity functionality, cross bucketing occurs when a member acts as a
bridge between two or more non-related member sets. (See: Group Entities, Bridge
Member, Many-to-Many Relationships, and Non-Obvious Relationships)
Customer Profiling
Customer profiling is the practice of mining data to gain a complete picture of
each customer known in a data source. Successful customer profiling enables
businesses to identify information such as customer purchase habits, special
requests, brand loyalties, and transaction history.
Data Extract File

A file generated from a source system or database for inclusion in the Master Data
Engine. Data Extract Files can be created in many formats including pipe-delimited
text files, CSV files, and tab-delimited text files. The Member Model Transform
Graph wizard in CloverETL can prepare the data extract for import to the Master
Data Engine, or the Derive Data and Create UNLs (mpxdata) job can be used to
process the Data Extract File.
Data Files
Files written by Message Broker interfaces containing messages relevant to the
processing of HL7 or XML messages. Examples include: input.dat, success.dat, and
reject.dat. (See: Madlogs)
Data Manager
The data management role is responsible for the project management aspects of a
CDI (Customer Data Integration) or MDM (Master Data Management)
implementation at an enterprise. This role manages stakeholder expectations, the
team of data stewards and the successes of the project from a cost and time
perspective.
Glossary
Data Profiling
Data profiling enables users to view various aspects about the data (attributes)
stored in their sources systems to better understand and improve the quality of the
data. Specifically you can determine what sources have or are creating bad or
incomplete data, which ultimately affects your overall business operational and
financial success.
Data Steward
Data steward is a data management role tasked with maintaining and
implementing the data governance policies agreed upon by the company. Data
stewards are often the individuals using the IBM Initiate Inspector application to
resolve data issues.
Definitional Source
A definitional source is one in which members (records) are created and usually
updated. (See: Source, Informational Source)
Delete
(Linkage type). Indicates that an IBM Initiate Inspector user logically deleted the
recordthe record is no longer used in algorithmic comparisons. (See: Logical
Deletion)
Deleted Attribute
An attribute status of D indicates that the attribute has been logically deleted.
(See: Logical Deletion, Active Attribute, Inactive Attribute)
Demographic Data
Information describing a person or object (for example, name, address, part
number, organization). (See: Attribute)
Derivation Process
The derivation process comprises four steps: 1) standardization of the data, 2)
creation of bucket data, 3) creation of comparison data, and 4) creating binary files
that are used for the Bulk Cross Match and Weight Generation processes. Not all
core member data goes through the derivation process; only attributes used in
bucketing and comparison participate in this process. (See: Derived Data,
Standardized Data, Bucket Data, Core Member Data, Comparison Data)
Derived Data
Data resulting from the derivation process; this attribute data is configured to
participate in comparison and scoring. Derived data is stored in the Hub database.
(See: Derivation Process, Standardized Data, Bucket Data, Core Member Data,
Comparison Data)
Deterministic Matching
Deterministic Matching refers to a rules-based process to determine a match
between two records. The process works best for simple, easily-defined matches.
IBM Initiate uses deterministic matching for relationships and hierarchies.
Duplicate Record
Two or more records representing the same person or object that are stored in the
same original source system.
Dynamic Task Creation

Task creation in the Master Data Engine is dynamic, meaning that tasks are not
saved as sets in the Hub database. Rather tasks are generated each time the engine
runs a comparison (for example, during task searches, data loads, and data
updates). The exception to this dynamic task model occurs when records in a task
have their workflow status set to deferred. This setting then saves the records as
a task set until the task is resolved. (See: Task Model)
EID
Enterprise ID. (See: Enterprise ID, Non-Simple EID, Simple EID)
EID Synchronization
Also called Enterprise ID update. This process, configured in the Outbound Broker
configuration files, can be used to propagate Enterprise ID changes made in the
Master Data Engine to source systems.
EMCA
Entity Most Current Attribute. An EMCA composite view displays the most
current attributes for any member within a defined linkage (members that share a
common Enterprise ID) and combines the attributes so that the view of the entity
(for example, person) is a conglomeration of attributes from your various source
systems. (See: MCA)
EMPI
Enterprise Master Patient Index. Used in the healthcare industry, an EMPI contains
unique identifiers for each person or patient. (See: CDI, MPI)
Encounter Data
Dates and information regarding a member's visit to a facility within your
organization.
Glossary
Engine Callouts
The functionality that enables the Master Data Engine to increase its reach via
Callback Handlers. Callouts extend the capabilities of the Hub by interrupting the
normal process (whether beforehand or afterward) of querying a web service,
validating data values, and implementing logical statements around interactions in
order to make automated decisions regarding how best to handle the data.
Enterprise Customer Identity Management

The process of identifying all of the information for a customer (member data)
throughout the enterprise, linking it together for a 360-degree view of a member
and maintaining that view going forward.
Enterprise ID
The identifier number used to represent an entity (which is the same person or
object across multiple sources or within the same source). This identifier is
assigned by the Master Data Engine and can be shared by more than one member
record. (See: EID, Entity)
IBM Initiate Enterprise Service Oriented Architecture (ESOA) Toolkit

The IBM Initiate Enterprise Service Oriented Architecture (ESOA) Toolkit is a Java
application programming interface (API) and SOAP Web Service generator that
generates an API in both Java and Web Service forms. SOA stands for Services
Oriented Architecture.
Entity
An entity is defined as something that exists as a particular and discrete unit. In
terms of data management, an entity is the logical relationship between two or
more member records. Entities are represented in the IBM Initiate Master Data
Service software environment as records sharing an Enterprise ID. An entity is also
called a linkage set. There can be an unlimited number of records in an entity or
linkage set. (See: Linkage Set, Transitive entity, Non-transitive entity)
Entity Manager
The entity manager is a process within the Master Data Engine that facilitates
comparison and entity definition. As new members or updates reach the engine,
the associated MemRecnos are added to a work queue. The entity manager scans
the queue and when it finds an updated member, a cross-match is triggered.
Depending on the configuration of the system, the results of this cross-match might
be used to link new entities, change existing linkages, or create tasks to allow for
further review. The entity manager operates in synchronous or asynchronous
mode. If the entity manager is running in synchronous mode, comparison is done
between derived data creation and storage in the database. If set to asynchronous,
the data is stored in the database before comparison is performed. The entity
manager can also be set to on or off, with the default being on.
Entity Type
Entity types allow for distinction between the way members are viewed and linked
within IBM Initiate Master Data Service software. Examples of entity types include:
v Identityan individual. Records in an identity entity (multiple records
representing the same person) are linked based on attribute similarity.
v Householdmultiple individuals who are associated with the same physical
location and share common attributes of home address and phone number (for
example, family members, non-family members sharing a household). Members
of a household entity share a common Enterprise ID.
v Groupin normal processing, a record can only belong to a single entity within
an entity type. Group entity functionality enables records to have multiple entity
record numbers (entRecno) within a single entity type. A member of a group
entity must match all members of that entity set above the auto-link threshold.
v Organizationmultiple individuals who are associated with a single
organization (for example, employees of a company or students at a university).
Records of an organization entity also share a common Enterprise ID.
EntRecno
The internal database reference to the Enterprise ID assigned to a record. (See:
Enterprise ID)
Environment
Environment refers to the type of dataTest or Productionand specific system
(server) to which a user has access.
ER
Entity Resolution. (See: CDI)
Error Types
False negative and false positive. Algorithms improve the accuracy of linkages in
two ways. First, they reduce the overall number of inaccurate linkages by
simultaneously reducing the occurrence of false negatives. Second, the algorithms
reduce false positive results when matching records. (See: False Negative, False
Positive)
ETL
Extract, transform, load. A process of extracting data from a source database,
transforming, and formatting it to meet to the needs of the system that consumes
it, and loading it into a destination database.
Event
A transaction that triggers a change to a member in the Hub database.
10
Glossary
Event Date
The date associated with incoming transaction messages to the Hub database. Data
in these messages are added or updated to appropriate member records.
Event Initiator
The person (user) or process that creates an event. For example, the term
Registrar may display on the Event Summary report, which indicates that the
registration process created the associated event.
False Negative
Two members not linked that are the same person.
False Positive
Two linked members that are not the same person.
False Positive Filter

Functionality within the Master Data Engine that assists in correctly determining
whether linked records are the same person. This functionality is helpful when
working with family records, especially twins or Senior/Junior names.
Fixed Segments
The set of standard, packaged segments shipped with the IBM Initiate Master Data
Service software. (See: Implementation-Defined Segments, Segment)
Get
A process used in the Retrieve functionality of IBM Initiate Inspector and
Enterprise Viewer, or by applications developed using an IBM Initiate SDK.
Associated with the MEMGET interaction, this functionality retrieves a specific
record via Enterprise ID or Source ID. This function is not a search, and therefore a
comparison score is not returned.
Glue Member
The term glue member is used to describe the record in a linkage set to which
all other records in the set are linked. In other words, the record bringing the
linkage set together. For example, if you had the following records:
John Public, DOB = 10-24-1950, Ph = 602-555-6060
John Quentin Public, 10-24-1970, 602-555-6060
John Quentin, 10-24-1970, 602-554-3232
11
Record 1 would likely link with Record 2 and Record 3 would likely link with
Record 2; however Record 1 would not likely link with Record 3. Therefore, Record
2 is the glue member.
Golden Record
A golden record refers to a transactions hub where the most
relevant/appropriate representation of the customer/entity is persisted instead of
dynamically created.
Group Entities
In normal processing, a record can only belong to a single entity within an entity
type. Group entity functionality enables records to have multiple entity record
numbers (entRecno) within a single entity type. A member of a group entity must
match all members of that entity set above the auto-link threshold. (See: Bridge
Member, Many-to-Many Relationships, Cross Bucketing, and Non-Obvious
Relationships.)
Groups
Groups (user groups) and their associated system privileges are established within
IBM Initiate Workbench to assist in controlling system security. As users are added,
their access to sources and their ability to view and/or update attributes can be
controlled by assignment to an appropriate group.
Hardlink
When working with organizational hierarchies, a hardlink occurs when members
compare above the auto-link threshold. (See: Softlink)
HasShadow
System-trigger task type. When tasks are created, users have the ability to modify
data via IBM Initiate Inspector to resolve the issue. If resolution required that the
member attribute data be modified, that attribute is assigned a status of S for
shadow and a HasShadow trigger is sent to the Outbound Broker. The
Outbound Broker then creates a message reflecting the attribute change and sends
it to the appropriate source system. When the client system is updated with the
change, a confirmation message is returned to the Master Data Engine via the
Inbound Broker. When the confirmation is received, the attribute status changes
from Shadow to Active. (See: Shadow Attribute)
Hierarchy
In the context of the IBM Initiate Master Data Service software, a hierarchy is the
relationship between two or more entities by virtue of a parent-child identifier on
one or both of the records. A member record may have one and only one parent
for a given Hierarchy Type and that parent must be in the same source as the
child.
12
Glossary
Hierarchy Tree
A tree represents a visual image of a hierarchy. A tree can be one or multiple
levels deep.
Hints
See: Task Hints.
Historical Attributes
The Master Data Engine enables you to store and view attribute values that are no
longer active (or valid) for historical reference. These attributes might be used in
comparison or matching depending on your configuration. The number of values
you store is controlled via the nsExists field in the mpi_segattr table.
HL7 Query Adapter (Query Broker)

The Query Broker functionality enables message-based requests from customer
applications to be sent to the Master Data Engine for the retrieval of information
about a member (or member's entity). The information is returned to the
requesting client via a message-based response.
Hook Point
The location that callback invocation occurs during Master Data Engine processing.
(See: Callback Handler)
Household / Household Entity

An entity type; multiple individuals who are associated with the same physical
location, and share common attributes of home address and phone number (for
example, family members and non-family members sharing a household).
Members of a household entity share a common Enterprise ID. (See: Entity Type)
Hub Attributes
Hub attributes are those that originate from a source system and are stored in the
Hub database. These attributes can be configured for use in searches and
comparisons. (See: Attribute, Hub-controlled Attributes, Virtual Attributes)
Hub-controlled Attributes
Attributes stored in the Hub database are typically a copy of the attribute values
stored in a source system. Hub-controlled attributes are member attributes that are
stored and maintained only in the Hub database. In normal implementations, once
a member is merged or logically deleted, their attributes cannot be modified.
Additionally, attributes that are in a shadow state cannot be modified. However, if
an attribute is defined as controlled, and thus is independent of a source system,
the usual attribute validation does not apply and modification is allowed.
Hub-controlled attributes are used mainly in data remediation efforts. However,
13
customers outside the realm of remediation might also identify attributes specific
to the IBM Initiate Master Data Service software that are not stored in a source
system. (See: Attribute, Hub Attributes, Virtual Attributes)
Hybrid Hub
Hybrid Hub describes an architectural style that mixes the notion of Centralized
Hubs and Registry Hubs. With a Hybrid Hub, the Master Data Engine maintains
indexes of data from the source systems as well as a persisted master record. (See:
Centralized Hub, Registry Hub)
Identification Task
Unit of work, created by the Master Data Engine, which facilitates user review, and
possibly resolution. Also sometimes called Identity Task.
Identifier
A number or code referring to a specific individual. (See: Enterprise ID, Source ID)
Identity Domain
A set of systems that includes a source system and a collection of consuming
systems. Each system in a given identity domain uses the same unique identifier.
The Master Data Engine enables the integration of information across multiple
identity domains.
Identity Entity
An entity type; a single individual whose records are grouped by demographic
attributes. (See: Entity Type)
Identity Rules
An identity rule is applied when two members have been given the same
Enterprise ID. (See: Non-Identity Rules)
IMM
IBM Initiate Member Model. IMM refers specifically to the .imm file within an IBM
Initiate Workbench configuration that contains all IBM Initiate Master Data Service
dictionary settings (for example, settings for members, attributes, segments, and so
on). The .imm file is an XML file stored on your local system. Once the
configuration is deployed to the server, these settings reside in the database. The
.imm file does not store the algorithm.
14
Glossary
Implementation-Defined Segments
Custom member attribute segments defined by IBM Initiate or Partner
implementers. Segments are tables in the database for storing member data, and
implementation-defined segments are those that are not part of the fixed segments
that are shipped with the product. (See: Segment)
Inactive Attribute
An attribute status of inactive (I) indicates that an update has been made to the
specific attribute and the inactive value represents old information. These
attributes are used in record comparison. (See: Active Attribute, Deleted Attribute)
Inbound Broker
The Inbound Broker, part of the Message Broker Suite, is a generic interface
designed to manage client-specific extensible markup language (XML) or health
level 7 (HL7) messages. To process messages successfully, two services are
installed: a message reader and a message processor. (See: Outbound Broker,
Message Reader, Message Processor)
Informational Source
Informational sources typically provide valid values that can be used as attribute
values. For example, an informational source might provide valid credit card
numbers or frequent flyer numbers. Member records are not created in
informational sources.
Interaction
An interaction is best defined as a request from a client application, such as IBM
Initiate Inspector, to the Master Data Engine and the result of that request from the
engine back to the client. When creating users and groups in the IBM Initiate
Workbench, you can specify interaction permissions, which means that you are
specifying the actual functions a user can perform.
Interceptor
An administrative tool for recording and replaying interactions executed on a
Master Data Engine. Interceptor facilitates upgrade and routine maintenance by
allowing the engine to be taken offline without losing data updates.
Invalid Reference
(Relationship Task type) A type of task in which an entity (according to its data
and creation rules) wants to have a relationship with another entity, but the target
entity does not exist within the Master Data Engine.
Linkage
Two or more records that are associated by a common Enterprise ID.
15
Linkage Modification Date

The date a linkage was modifiedany change made to a member or record in a
linkage set (for example, Enterprise ID change or status update)in the Hub
database.
Linkage Set
A grouping of two or more records that have a high likelihood of representing the
same person. An unlimited number of records can be included in a linkage set,
which may contain records from a single source or multiple sources.
Linkage Status
The label assigned to a linkage set which tracks user review. The status types can
be customized, but usually include Examined OK (linkage has been reviewed and
confirmed) and Examined Error (linkage has been reviewed and an error in the
linkage is confirmed).
Linkage Type
Label assigned to a linkage set associated when an Enterprise ID assignment is
made by the IBM Initiate Master Data Service software or by a user. Examples of
linkage types include AutoLink-SS and ManuLink-MS.
Log Files
Files written by the message interfaces containing information relevant to the
operation of the specific process. Examples include: mpinet.mlg, msgread.mlg and
msgproc.mlg files. (See: Madlogs.)
Logical Deletion
Reference to a record that remains in the database, but is not included in
comparisons or retrieved in searches.
Madlogs
Term referring to log files created by the Master Data Engine processes. Includes
both log files and data files. (See: Log Files and Data Files)
ManuLink-MS
(Linkage type.) Indicates an IBM Initiate Inspector user manually linked records
from multiple sources.
ManuLink-SS
(Linkage type.) Indicates an IBM Initiate Inspector user manually linked records
from the same source.
16
Glossary
Many-to-Many Relationships
This is general term to describe grouped entities. (See: Group Entities, Bridge
Member, Cross Bucketing, and Non-Obvious Relationships.)
Mapping Message Manager (Message Broker)

The Mapping Message Manager (also called Mapping Broker) provides a way to
query the Master Data Engine by reading messages from an input queue,
requesting data from the Hub, and then writing to a message queue. A Mapping
Message Broker instance is used for two basic purposes: retrieving information and
searching for information.
Master Data Engine

The core Master Data Engine contains the logic which is at the heart of IBM
Initiate Master Data Service product. The logic, rules, and algorithms configured
for each Hub implementation enable the Engine to compare member records and
produce scores that indicate which records are likely to represent the same entity
or which individual members form relationships with other individual members,
and the relative strength of the comparison. The comparison and linkage logic
supports required functionality in all product modules and applications. For
example any functionality available in IBM Initiate Inspector or IBM Initiate
Enterprise Viewer utilizes the Master Data Engine. (See: IBM Initiate Master Data
Service)
Master Data Engine server

The actual computer on which Master Data Engine is installed. (See: MPINET)
Master Data Extract

Master Data Extract uses Clover.ETL, an open-source Extract Transfer Load utility,
to extract data from the Master Data Engine for use with reporting and analytical
systems. This functionality replaces the data extract scripts which were used in
support of custom reports and Data/Customer Profiling Reports.
Match
A selection of records that match some of the attributes of a specific record. When
the match interaction is performed, the Master Data Engine retrieves the record for
the Source ID and Source system specified and then compares all the attributes of
that member to similar attributes of other member records. The match interaction
operates in the same manner as the Entity Managerusing the thresholdsand
only returning those members that are above the CR threshold, or that take part in
a Review Identifier task.
Matched Pairs
Two members identified as the same person by the Master Data Engine.
17
MCA
Most Current Attribute. The most current attribute value. (See: EMCA)
MDM
Master Data Management. The process of accurately identifying and linking the
records of customers to drive an on-demand enterprise. Clean, complete personal
profiles drive better, more cost-effective and robust interactions with customers,
patients, partners and organizations.
Member Get Interaction

MemGet. This interaction is used to retrieve a specific member using a member
key value such as an Enterprise ID or a Source ID and Source Code. MemGet is
used by the Retrieve function in an application such as IBM Initiate Inspector. (See:
Interaction)
Member Logical Model

A member logical model (MLM) is a read-only view of the members, attributes,
and segments defined for a Hub implementation. When defining external attributes
and enhanced composite views, MLMs are imported in the IBM Initiate Workbench
tool.
Member Match Interaction

MemMatch. This interaction performs a cross-match of a single member specified
in the input, against the other members stored in the Hub database. (See:
Interaction, Member Get Interaction)
Member Put Interaction

MemPut. The MemPut interaction puts member data in the Hub database. The
interaction has several options that control exactly how the data is stored. When
you update a member's attributes, whether through an application like IBM Initiate
Inspector or updates from a source system, the MemPut interaction is used. (See:
Interaction)
Member Search Interaction

MemSearch. Uses selected criteria, such as name, date of birth, address, and
gender, to search and return a list of records matching the criteria. The interaction
creates a virtual member based on the attribute criteria submitted and compares
those attributes with other records in the database. MemSearch is used by Search
functionality in applications.
18
Glossary
Member Status
The current status of a member; status can be Active, Overlay, Merged, Deleted, or
Fictitious. A Merged member becomes obsolete. The Deleted status indicates the
member has been logically deleted.
Member Type
A member type defines the kind of member data stored and managed in IBM
Initiate Master Data Service software. Member type definition enables products for
use in multiple business environments.
Member/Record
A member/record is defined as a set of demographic information that represents
one individual (for example, a person or organization) or object (such as a car or
machine part). A member/record object is the representation of what a single
source system asserts to be true about an individual or thing. In the healthcare
environment, a member/record is a patient known in the Master Person Index
(MPI) of the Hub database.
The term member/record is also used in the documentation as another synonym
for an individual or object known in the Hub database. (See: MPI, Person)
In IBM Initiate Inspector, the term record is used instead of member.
MemRecno
Each record stored in the Hub database is assigned a unique member record
number. This number serves as the surrogate primary key for a member.
Merge
A.) When two or more records are merged and now share one common Enterprise
ID or Source ID.
B.) (Linkage type.) Indicates when the Master Data Engine has received a merge
message from a source system.
Message Broker
See: Inbound Broker and Outbound Broker.
Message Processor
A stand-alone process (or service) that processes HL7 or XML messages from an
input queue. The messages are sent via a TCP/IP connection to the Master Data
Engine. The Engine attempts to process the message and sends a notification of
success or failure to the Message Processor. Finally, the Message Processor writes
the message to a success queue (for example, success-yyyymmdd-tttt.dat) if the
19
message was processed successfully, or to a reject queue (for example,

reject-yyyymmdd-tttt.dat) if the message was not processed successfully.
Message Reader
A stand-alone process (or service) that receives HL7 or XML messages through a
TCP/IP connection. The process reads messages from the socket and writes them
to a queue so the Message Processor can consume them.
Missing Relationship
(Relationship Task type) A type of task in which an entity is supposed to have a
relationship, according to the relationship type constraints, but does not. For
example, a patient might be required to have at least one provider. If there is a
patient which does not have a provider, a task would be created.
MPI
Master Person Index. The MPI is a system that provides a complete picture of data
for a person gathered from other source systems. (See: CDI)
MPINET
MPINET is a process that runs on the Master Data Engine server. Client
applications, as well as the Inbound and Outbound Brokers communicate with
MPINET requesting the Master Data Engine to perform various interactions. (See:
Interaction)
mpxdata Configuration File

The Derive Data and Create UNLs (mpxdata) job uses the mpxdata configuration
file as a map for reading the customer's Data Extract File and as a legend for
converting the data to the Master Data Engine database table layout. The
configuration file tells mpxdata where each field is located in the extract and how
to migrate it into the proper IBM Initiate data format.
Multiplicity Relationship
(Relationship Task type) A type of task in which an entity has too many of a
particular kind of relationship, for example, a patient with more than one provider,
or an organization with more than one owning organization.
NoChange
(Linkage type.) An IBM Initiate Inspector user updates the workflow status, but
does not make a change to the Enterprise ID.
Non-Event
An action that is not defined as an event type in the event table. The terms None
or Non-Event are often seen on event summary reports.
20
Glossary
Non-Identity Rules
Non-identity rules indicate that the specified records are not the same person. A
non-identity rule is created when two records have been reviewed and a user has
manually determined that they are not the same person. This determination
prevents those records from being placed together in a task at a later date. (See:
Identity Rules)
Non-Obvious Relationships
In group entities, a non-obvious relationship is a relationship that exists between
members that have a common bridge member. (See: Group Entities, Bridge
Member, Many-to-Many Relationships and Cross Bucketing.)
Non-Simple EID
A non-simple EID is an Enterprise ID shared by more than one record (records that
have been linked). (See: EID, Simple EID)
Non-transitive entity
Records in a non-transitive or strong entity, must match above the auto-link
threshold with all records in the entity set. Members of a non-transitive or strong
entity can only belong to one entity type set at a time (one Enterprise ID). (See:
Transitive entity)
Organization
One of the defined member types. Organization is used in the business or
corporate environment to accommodate the management of organization data.
Outbound Broker
The Outbound Broker provides a mechanism that reduces manual effort by
automatically updating source systems with data changes and identifier updates
made in the Master Data Engine. If a legacy system does not allow updates
directly from the engine, an Outbound Screen Scrape option is available to process
updates.
Overlay
An overlay occurs when one member's information overrides the information of
another, different, member record. (See: Potential Overlay)
Owner
The Master Data Engine assigns owners to tasks based on modifications to task
data. Owners include authorized users of the software and applications. Typically,
System is the default owner until a user begins to work and modify a task.
21
Path to Root
When viewing a hierarchy tree, this tree starts from a selected member, and moves
up to the top level, or rooted member.
Person
Person is one of the defined member types. In the user documentation, the term
person may be used as an interchangeable term for person, patient, provider, or
customer. (See: Member/Record)
PIM
Product Information Management. The process of managing information about a
collection of products with one centralizing system, including all data required to
market and sell the products through multiple distribution channels.
Pivot Record
The pivot record is the entity or record that the search was initiated with.
Potential Duplicate
(Identification Task type.) More than one Source ID exists for a person within a
source system.
Potential Linkage
(Identification Task type.) Records exist in different source systems that have a
high likelihood of being the same person.
Potential Overlay
(Identification Task type.) Two or more persons share the same Source ID and their
respective data has been commingled.
Premerge
(Linkage type.) After an IBM Initiate Inspector user has resolved a record as a
duplicate and set the Surviving Source ID, the Master Data Engine sets the linkage
type to Premerge. The Outbound Broker generates a message to the source system
reflecting the ID change. When the source returns a merge confirmation message to
the engine, this linkage type is then set to merge.
22
Glossary
Probabilistic Algorithms
The comparison methodology used in IBM Initiate Master Data Service software to
identify multiple records that represent the same person. Probabilistic algorithms
calculate scores based upon weights associated with values for specific attributes.
This methodology is used across all searchable attributes making the approach
much more accurate in identifying the most likely match of attributes.
Probabilistic Matching
Probabilistic Matching refers to the process of using statistical analysis to
determine the overall likelihood that two records match. Probabilistic Matching is
the preferred method for matching large data sets or when a large number of
attributes are involved in the matching process. (See: Probabilistic Algorithms)
Proband
A proband record is the record to which another record is being compared (the
trigger member). In the Compare display, you may see a message such as
comparing proband 5 with candidate 3. The numbers in the message represent
the Member ID number.
Promotion
Promotion occurs when a record, which was previously assigned to a task by the
Master Data Engine, is updated or changed and that action triggers a new data
issue or resolves the current issue. When this occurs, the software may
automatically promote the record to a different task type. If the action resolves the
data issue, the record no longer displays in task search results.
Provider
One of the defined member types. Provider member types are typically
implemented in healthcare provider/payor environments to accommodate
management of network provider data such as medical centers, doctors, and
laboratories.
Real Time
Refers to data updates/changes that are stored and become effective as you make
them.
Record
A record (also known as a member) is defined as a set of demographic information
that represents one individual (for example, a person or organization) or object
(such as a car or machine part). A member/record object is the representation of
what a single source system asserts to be true about an individual or thing. In the
healthcare environment, a member/record is a person known in the Master Person
Index (MPI) of the Hub database.
23
The term member/record is also used in the documentation as another synonym

for an individual or object known in the Hub database. (See: MPI, Person)
In IBM Initiate Inspector, the term record is used instead of member.
Registry Hub
Registry Hub describes an architectural style in which the sources maintain official
versions of records and the Master Data Engine simply indexes the data as it exists
in the sources. Within that index, records are linked to entities, and one entity may
point to multiple records across the systems. Unlike a Centralized Hub, with a
Registry Hub, the engine does not persist a single composite or golden record.
(See: Centralized Hub, Hybrid Hub)
Relationship Creation
(Relationship Task type) A type of task in which an entity has a relationship that
the engine has detected should not be there (according to the creation rules). This
occurs in a situation where a user has marked a relationship as unmodifiable.
Relationship Creation Rule

These are associated with a relationship type. A relationship creation rule indicates
exactly how a particular relationship should be derived between entities.
Relationship Task
A recorded event within the Master Data Engine which indicates that the engine
has detected a possible data quality issue with regard to one or more relationships.
Relationship Type
The types of relationships between entities and members. For example, boss,
patient or customer. Relationships are viewed in IBM Initiate Inspector and
types are defined in IBM Initiate Workbench.
Re-parenting
When working with hierarchies, re-parenting occurs when an entity is dragged
from its current parent and dropped on a new parent, resulting in a new
parent-child relationship.
Review Identifier
(Identification Task type.) Multiple persons incorrectly sharing unique identifying
information, such as Social Security number.
24
Glossary
ROC Curve
A Receiver Operating Characteristic (ROC) curve is a plot of true positive rate
against false positive rate for different threshold values. The Threshold Calculator
generates one or more ROC curves to help administrators determine optimal
Clerical Review Thresholds and Auto-link Thresholds. (See: Clerical Review
Threshold, Auto-link Threshold)
Routing Message Manager (Routing Broker)

The Routing Message Manager (also called Routing Broker) enables messages to be
routed from a single queue into multiple queues based on the information
contained in the message. Routing Message Broker differentiates message types
such as adds, changes, merges, and so on. For inbound traffic, the Routing Broker
determines the message type and sends the message to the appropriate inbound
queue. The message can then be processed in a specified manner. For outbound,
the messages are routed to an outbound queue that sends the message to a specific
destination.
Score / Scoring
A number assigned by the Master Data Engine indicating the probability that the
various records in a linkage set represent the same person. Specifically, the score is
an aggregate of the individual comparisons for each attribute. Typically, the higher
the score, the greater the likelihood that the records represent the same person.
Search
A search uses specific criteria, based on your attribute configuration, to locate a
record or task in the Hub database.
Segment
Segments coincide with the Hub data schema to define Master Data Engine
behavior and member information. Each segment coincides with a database table.
A set of fixed or primitive segments are packaged with the IBM Initiate Master
Data Service software. For example MemName, MemAddr, MemIdent are all fixed
segments. (See: Implementation-Defined Segments)
Service Model
The customer-defined data model used for Identity Services. Also referred to as a
user-defined logical model.
Shadow Attribute
When an attribute is updated for a member in the Hub database, the attribute is
assigned a status of S. Shadow indicates that attribute values in the Hub and the
source system are out of sync. When this occurs, the Outbound Broker generates a
message to the source system reflecting the attribute change. Once the Master Data
Engine receives confirmation that the updated attribute value has been changed in
25
the source system (via an inbound message), the status changes to A. Shadow
attributes are used in comparisons. (See: Active Attribute, HasShadow)
Simple EID
A simple EID is an Enterprise ID that is associated with only one member record.
If a record has the same EntRecno (Enterprise ID) and MemRecno stored in the
Hub database, this may indicate that there is only one record in the entity and is
thus called a "simple EID." If the EntRecno is not the same as the MemRecno, this
indicates that the record has been or is part of a multi-member linkage. (See: EID,
Non-Simple EID)
Singleton
A single member with an Enterprise ID that is not shared with other member
records; one member record in the entity.
Softlink
When working with organizational hierarchies, a softlink occurs when members
compare above the clerical review threshold and below the auto-link threshold.
(See: Hardlink)
Source
A separate system/database with which the Master Data Engine interacts and
receives member information and updates. (See: Definitional Source, Informational
Source, Source System)
Source ID
Reflects the state of the Source ID resolution; set by the system.
Source ID Status
Reflects the state of the Source ID resolution; set by the system.
Source System
The system (application) from which a specific record in the Hub database
originated. For example, a registration system or an accounting system.
SrcRecno
A record ID which identifies a data source. The SrcRecno is assigned by the IBM
Initiate Master Data Service software and is used in individual records to identify
which source the record originated from.
26
Glossary
Standardized Data
Part of the derivation process, standardization is the process by which similar data
received in various formats is transformed to a common format that enhances the
comparison process. For example, street names commonly contain directions, like
North or West. The standardization routines in IBM Initiate software would format
these values to N or W in order to speed up the comparison process. The
standardized data does not overwrite the core member data in the database;
therefore, when you view a record it will show the original format (for example,
North rather than N). (See: Derivation Process)
Surviving Enterprise ID
When it is determined that two or more records from multiple sources are the
same person, you may elect to assign one Enterprise ID to all of the records. The
Enterprise ID that you ultimately assign to the records becomes the Surviving
Enterprise ID.
Surviving Source ID
When it is determined that two or more records, within a source, are the same
person, you may choose to assign one Source ID to all of the records. The Source
ID that you ultimately choose to assign to these records is the Surviving ID.
Tag
Tags offer a method for creating rules that direct the Master Data Engine in
categorizing tasks. As issues are identified by the engine, it considers the defined
tags and automatically groups those tasks. Once tags have been defined, you can
use the bulk assignment capability to search for tasks with a specific tag and then
assign those tasks to a user or group. For example, you may decide that all tasks
associated with a given source should be assigned to a Group A, while all Potential
Overlay tasks be assigned to Group B and further, all Potential Overlay tasks
within a score range be assigned to User1. Any tag with at least one rule is
required to have an entity type association.
Task Creation Date

The recorded date a task was created by the Master Data Engine.
Task Get Interaction

TskGet. The TskGet interaction performs a cross-match using a member or entity
task record as input to the cross match. A task get returns all members in the same
entity as the input member, as well as any members that match above the Clerical
Review threshold. Typically, this interaction is performed after you have done a
task search and selected a specific member record to review. Note that a related
interaction, TskGet2, populates the new MEMRECNOs array in all task types. (See:
Task Search Interaction).
27
Task Hints
When configuring custom tasks, hints let you tell the IBM Initiate Inspector
application to highlight certain fields in the task resolution screen in order to help
Inspector users find and resolve data issues involving custom tasks. Hints like the
description field are part of the data that is associated with a member at the time
the custom task information is "put" (with the IxnTskPut2 interaction or the Clover
TSKPUT component).
Task Life Cycle

The process or cycle in which a task proceeds from point of creation to resolution.
Task Model
The task model defines how tasks are defined and managed. The Master Data
Engine uses a dynamic task model, which creates tasks each time a comparison is
performed. (See: Dynamic Task Creation)
Task Modification Date

The recorded date of any changes to a task, including update information for a
record or a change to workflow status.
Task Put Interaction

TskPut. This interaction enables modification of task level details for a member.
TskPut is the mechanism used to create manual linkages or to dissolve linkages.
For example, when you work a task in IBM Initiate Inspector and save the task
changes, the TskPut interaction is performed. Note that a related interaction,
TskPut2, allows the use of the MEMRECNOs array to specify members associated
to an individual task. (See: Task Get Interaction, Task Search Interaction).
Task Resolution
The act (end-user review and action) or process (such as automatic link) of
correcting data in order to remove a task from the task queue. Resolution is
recorded as a history of work performed (for example, Enterprise ID assignment or
workflow status update).
Task Search Interaction

TskSearch. The Task Search interaction takes search criteria input (for example, task
type, task owner, or task status) and returns a list of members with task issues.
(See: Task Get Interaction)
28
Glossary
Task Set
Two or more records explicitly identified as being in a task. Task sets are stored in
the MPI_Memxtsk (member tasks; typically Review Identifier and Potential
Overlay) and MPI_Entxtsk (entity tasks; typically Potential Duplicate and Potential
Linkage) tables.
Task Types
Tasks are generated by the Master Data Engine and are categorized as one of the
following types: Potential Linkage, Potential Overlay, Potential Duplicate, or
Review Identifier. (See: Potential Linkage, Potential Overlay, Potential Duplicate,
Review Identifier)
Templates
Templates comprise the base system settings for specific member types or products
such as IBM Initiate Patient and IBM Initiate Provider. After a base template is
installed, project implementers can customize the settings for an organization. (See:
Member Type)
Threshold
Threshold levels are scoring levels set for an organization to determine how
records will be managed. Records scoring below a certain threshold may be
designated as having such a small likelihood of matching that no action is
required. Records scoring between the lowest threshold level and highest threshold
level may generate a task and require review/action. Records scoring above the
highest threshold level may be designated as having a high likelihood of matching
and are automatically linked. (See: Clerical Review Threshold, Auto-link Threshold)
Transitive entity
Transitive entities operate on the glue member concept in that a record only
needs to match one other record in the entity set. This match can be achieved by
comparing above the auto-link threshold or by manual linking. In transitive
entities, a member can only belong to one entity at a time and thus have only one
Enterprise ID assignment. (See: Non-transitive entity)
Trigger Member or Trigger Record

When a task search is requested, the results are generated in real time (at the
moment the search is initiated). The record, or criteria, that the Master Data Engine
uses to compare against other records (candidates) is called the trigger member or
trigger record (the record triggering the comparison). When a task search returns
results, the trigger member typically displays with a higher score than the other
records. The score is higher based on the trigger record being compared against
itself during the comparison process. The other records returned are issued
comparison scores based upon their comparison against the trigger record.
A record is also considered to be the trigger member if an update to that member
causes a cross-match which results in task creation.
29
Trusted Source View

A trusted source composite view displays the attributes from one specified source.
Typically this is a source that you know to have the most accurate information.
Undelete
(Linkage type.) Indicates an IBM Initiate Inspector user activated the record after it
had been deleted.
Virtual Attributes
Virtual attributes are attributes that are not stored in the Hub database, but are
used in derived data form. Defining virtual attributes is done through the
mpi_segattr table, while defining a virtual source is done through mpi_srchead.
(See: Virtual Source)
Virtual Member
When a member search is performed, the Master Data Engine uses the criteria
specified on the search screen to create a virtual member. Other records with
similar attributes are then compared against this virtual member to determine the
likelihood that they represent the same member.
Virtual Source
If a source is defined as virtual, member attributes from the source are not
written to the Hub database, but do participate in derived data. (See: Virtual
Attributes)
Web Services
Web Services enables interaction between the Master Data Engine and web-based
clients. Web Services uses the Simple Object Access Protocol (SOAP) and Web
Services Description Language (WSDL) standards enabling developers to program
in multiple environments such as: Java, Perl, Visual Studio .NET, or any other
language which supports these standards.
Weight
In the Master Data Engine, a weight is a measure of the evidence that a
comparison result provides for a match or non-match. Simply, a positive number
indicates the result is evidence for a match while a negative number indicates the
result is evidence for a non-match.
Weight Generation
A process within the Master Data Engine that enables the generation and
assignment of weight values to attributes. Weight assignments enable
determination of a match or non-match between members. The weight generation
process is executed from IBM Initiate Workbench.
30
Glossary
Workflow Status
Indicates where a task stands in the resolution process (for example, an
unexamined status indicates the task has not been reviewed, while a deferred
status indicates that the task has been reviewed but not yet resolved) or, for
resolved tasks, indicates the resolution (for example, same person, not the same
person). Workflow statuses can be customized for each client.
31
32
Glossary
Legal Statement
Licensed Materials Property of IBM
Copyright IBM Corporation, 1995, 2011. US Government Users Restricted Rights
- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with
IBM Corp. IBM, the IBM logo, InfoSphere, Initiate, and Initiate Master Data Service
are trademarks of IBM Corp., registered in many jurisdictions worldwide. Java and
all Java-based trademarks and logos are trademarks or registered trademarks of
Oracle and/or its affiliates. Other product and service names might be trademarks
of IBM, or other companies. This Program is licensed under the terms of the
license agreement accompanying the Program. This license agreement may be
either located in a Program directory folder or library identified as "License" or
"Non-IBM License", if applicable, or provided as a printed license agreement.
Please read this agreement carefully before using the Program. By using the
Program, you agree to these terms.
33
34
Glossary
Notices and trademarks

This information was developed for products and services offered in the U.S.A.
Notices
IBM may not offer the products, services, or features discussed in this document in
other countries. Consult your local IBM representative for information on the
products and services currently available in your area. Any reference to an IBM
product, program, or service is not intended to state or imply that only that IBM
product, program, or service may be used. Any functionally equivalent product,
program, or service that does not infringe any IBM intellectual property right may
be used instead. However, it is the user's responsibility to evaluate and verify the
operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter
described in this document. The furnishing of this document does not grant you
any license to these patents. You can send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785 U.S.A.
For license inquiries regarding double-byte character set (DBCS) information,
contact the IBM Intellectual Property Department in your country or send
inquiries, in writing, to:
Intellectual Property Licensing
Legal and Intellectual Property Law
IBM Japan Ltd.
1623-14, Shimotsuruma, Yamato-shi
Kanagawa 242-8502 Japan
The following paragraph does not apply to the United Kingdom or any other
country where such provisions are inconsistent with local law:
INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS
PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER
EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED
WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS
FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or
implied warranties in certain transactions, therefore, this statement may not apply
to you.
This information could include technical inaccuracies or typographical errors.
Changes are periodically made to the information herein; these changes will be
incorporated in new editions of the publication. IBM may make improvements
and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for
convenience only and do not in any manner serve as an endorsement of those Web
35
sites. The materials at those Web sites are not part of the materials for this IBM
product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it
believes appropriate without incurring any obligation to you.
Licensees of this program who wish to have information about it for the purpose
of enabling: (i) the exchange of information between independently created
programs and other programs (including this one) and (ii) the mutual use of the
information which has been exchanged, should contact:
IBM Corporation
J46A/G4
555 Bailey Avenue
San Jose, CA 95141-1003 U.S.A.
Such information may be available, subject to appropriate terms and conditions,
including in some cases, payment of a fee.
The licensed program described in this document and all licensed material
available for it are provided by IBM under terms of the IBM Customer Agreement,
IBM International Program License Agreement or any equivalent agreement
between us.
Any performance data contained herein was determined in a controlled
environment. Therefore, the results obtained in other operating environments may
vary significantly. Some measurements may have been made on development-level
systems and there is no guarantee that these measurements will be the same on
generally available systems. Furthermore, some measurements may have been
estimated through extrapolation. Actual results may vary. Users of this document
should verify the applicable data for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of
those products, their published announcements or other publicly available sources.
IBM has not tested those products and cannot confirm the accuracy of
performance, compatibility or any other claims related to non-IBM products.
Questions on the capabilities of non-IBM products should be addressed to the
suppliers of those products.
All statements regarding IBM's future direction or intent are subject to change or
withdrawal without notice, and represent goals and objectives only.
This information is for planning purposes only. The information herein is subject to
change before the products described become available.
This information contains examples of data and reports used in daily business
operations. To illustrate them as completely as possible, the examples include the
names of individuals, companies, brands, and products. All of these names are
fictitious and any similarity to the names and addresses used by an actual business
enterprise is entirely coincidental.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which
illustrate programming techniques on various operating platforms. You may copy,
modify, and distribute these sample programs in any form without payment to
36
Glossary
IBM, for the purposes of developing, using, marketing or distributing application

programs conforming to the application programming interface for the operating
platform for which the sample programs are written. These examples have not
been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or
imply reliability, serviceability, or function of these programs. The sample
programs are provided "AS IS", without warranty of any kind. IBM shall not be
liable for any damages arising out of your use of the sample programs.
Each copy or any portion of these sample programs or any derivative work, must
include a copyright notice as follows:
(your company name) (year). Portions of this code are derived from IBM Corp.
Sample Programs. Copyright IBM Corp. _enter the year or years_. All rights
reserved.
If you are viewing this information softcopy, the photographs and color
illustrations may not appear.
Trademarks
IBM, the IBM logo, and ibm.com are trademarks or registered trademarks of
International Business Machines Corp., registered in many jurisdictions worldwide.
Other product and service names might be trademarks of IBM or other companies.
A current list of IBM trademarks is available on the web at "Copyright and
trademark information" at www.ibm.com/legal/copytrade.shtml.
The following terms are trademarks or registered trademarks of other companies:
Adobe is a registered trademark of Adobe Systems Incorporated in the United
States, and/or other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other
countries, or both.
Microsoft, Windows, and Windows NT are trademarks of Microsoft Corporation in
the United States, other countries, or both.
UNIX is a registered trademark of The Open Group in the United States and other
countries.
Java and all Java-based trademarks and logos are trademarks or registered
trademarks of Oracle and/or its affiliates.
Notices and trademarks
37
38
Glossary
Index
C
customer support
contacting 41
L
legal notices
35
S
software services
contacting 41
support
customer 41
T
trademarks
list of 35
39
40
Glossary
Contacting IBM
You can contact IBM for customer support, software services, product information,
and general information. You also can provide feedback to IBM about products
and documentation.
The following table lists resources for customer support, software services, training,
and product and solutions information.
Table 1. IBM resources
Resource
Description and location
IBM Support Portal
You can customize support information by

choosing the products and the topics that
interest you at www.ibm.com/support/
entry/portal/Overview/Software/
Information_Management/IBM
Initiate_Master_Data_Service
Software services
You can find information about software, IT,

and business consulting services, on the
solutions site at www.ibm.com/
businesssolutions/
My IBM
You can manage links to IBM web sites and

information that meet your specific technical
support needs by creating an account on the
My IBM site at www.ibm.com/account/
Training and certification
You can learn about technical training and

education services designed for individuals,
companies, and public organizations to
acquire, maintain, and optimize their IT
skills at http://www.ibm.com/software/swtraining/
IBM representatives
You can contact an IBM representative to

learn about solutions at
www.ibm.com/connect/ibm/us/en/
Providing feedback
The following table describes how to provide feedback to IBM about products and
product documentation.
Table 2. Providing feedback to IBM
Type of feedback
Action
Product feedback
You can provide general product feedback

through the Consumability Survey at
www.ibm.com/software/data/info/
consumability-survey
41
Table 2. Providing feedback to IBM (continued)

Type of feedback
Action
Documentation feedback
To comment on the information center, click

the Feedback link on the top right side of
any topic in the information center. You can
also send comments about PDF file books,
the information center, or any other
documentation in the following ways:
v Online reader comment form:
www.ibm.com/software/data/rcf/
v E-mail: comments@us.ibm.com
42
Glossary

Printed in USA
GI13-2614-00

Glossary: IBM Initiate Master Data Service

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

Glossary: IBM Initiate Master Data Service

Uploaded by

Copyright:

Available Formats

IBM Initiate Master Data Service

IBM Initiate Master Data Service

Copyright IBM Corporation 1995, 2011.

Copyright IBM Corp. 1995, 2011

Enterprise Customer Identity Management . . . . 9

Relationship Creation Rule . . .

IBM Initiate glossary

Copyright IBM Corp. 1995, 2011

Bulk Cross Match

IBM Initiate glossary

Clerical Review Threshold

Context Pool Size

Core Member Data

Data Extract File

Dynamic Task Creation

Enterprise Customer Identity Management

IBM Initiate Enterprise Service Oriented Architecture (ESOA) Toolkit

IBM Initiate glossary

False Positive Filter

IBM Initiate glossary

HL7 Query Adapter (Query Broker)

Household / Household Entity

Linkage Modification Date

Mapping Message Manager (Message Broker)

Master Data Engine

Master Data Engine server

Master Data Extract

IBM Initiate glossary

Member Get Interaction

Member Logical Model

Member Match Interaction

Member Put Interaction

Member Search Interaction

IBM Initiate glossary

message was processed successfully, or to a reject queue (for example,

mpxdata Configuration File

IBM Initiate glossary

IBM Initiate glossary

The term member/record is also used in the documentation as another synonym

Relationship Creation Rule

Routing Message Manager (Routing Broker)

Task Creation Date

Task Get Interaction

IBM Initiate glossary

Task Life Cycle

Task Modification Date

Task Put Interaction

Task Search Interaction

Trigger Member or Trigger Record

Trusted Source View

IBM Initiate glossary

Copyright IBM Corp. 1995, 2011

Notices and trademarks

Copyright IBM Corp. 1995, 2011

IBM, for the purposes of developing, using, marketing or distributing application

Notices and trademarks

Copyright IBM Corp. 1995, 2011

Description and location

IBM Support Portal

You can customize support information by

You can find information about software, IT,

You can manage links to IBM web sites and

Training and certification