IBM Initiate Master Data Service. Glossary. Version9Release7 SC

Transcription

1 IBM Initiate Master Data Service Glossary Version9Release7 SC

2

3 IBM Initiate Master Data Service Glossary Version9Release7 SC

4 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, US Government Users Restricted Rights Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.

5 Contents IBM Initiate glossary Active Attribute Aggregation Algorithm Algorithm Editor 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 Enterprise Customer Identity Management Enterprise ID IBM Initiate Enterprise Service Oriented Architecture (ESOA) Toolkit Entity Entity Manager Entity Type EntRecno Environment ER Error Types ETL Event Event Date Event Initiator False Negative False Positive False Positive Filter Fixed Segments Get Glue Member Golden Record Group Entities Groups Hardlink HasShadow Hierarchy Hierarchy Tree Hints Historical Attributes HL7 Query Adapter (Query Broker) Hook Point Household / Household Entity Hub Attributes Hub-controlled Attributes Hybrid Hub Identification Task Identifier Identity Domain Identity Entity Identity Rules IMM Implementation-Defined Segments Inactive Attribute Inbound Broker Informational Source Interaction Interceptor Invalid Reference Linkage Linkage Modification Date Linkage Set Linkage Status Linkage Type Log Files Logical Deletion Copyright IBM Corp. 1995, 2011 iii

6 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/Member Registry Hub Relationship Creation Relationship Creation Rule Relationship Task Relationship Type Re-parenting Review Identifier Routing Message Manager (Routing Broker) 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 Legal Statement Notices and trademarks Index Contacting IBM iv Glossary

7 IBM Initiate glossary Active Attribute Aggregation Algorithm Algorithm Editor Anonymous Values 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. 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) In IT, aggregation is the process of amassing or gathering individual parts of information (data) from disparate systems to create one complete customer view. 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. A component of IBM Initiate Workbench that allows for quick and easy configuration of algorithms. 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 or 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. Copyright IBM Corp. 1995,

8 Attribute Information or demographics describing particular data for a member person (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 Auto-link Threshold Auto-timeout Auto-Unlink Bootweights (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. 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) 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. 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 are pre-determined, hardcoded weights that are used to start the weight generation process. 2 Glossary

9 Bridge Member Broker Bucket / Bucketing Bucket Data Bulk Cross Match Callback Handler Candidate 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.) See: Inbound Broker and Outbound Broker. 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 + 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 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_ 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) 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. 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. 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. IBM Initiate glossary 3

10 Candidate Selection CDI Centralized Hub Clerical Review Threshold Cloud 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) 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. 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) 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) (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. 4 Glossary

11 cltdicd A file containing database metadata defined for an IBM Initiate Master Data Service software configuration at the time of system configuration. Comparison Comparison Data Comparison Score Composite View Consuming System Context Pool Size The application of one or more algorithms to determine similarities and differences between two or more records. This process compares the individual attributes attribute by attribute of each record selected during the candidate selection process. (See: Bucket Data, Bucket / Bucketing, Candidate Selection, Comparison Score.) 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) 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. 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) 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. (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 IBM Initiate glossary 5

12 Controlled View Core Member Data Cross Bucketing Customer Profiling Data Extract File Data Files Data Manager 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. 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. 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. 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 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. 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. 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) 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. 6 Glossary

13 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 Definitional Source Delete Deleted Attribute Demographic Data Derivation Process Derived Data 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. A definitional source is one in which members (records) are created and usually updated. (See: Source, Informational Source) (Linkage type). Indicates that an IBM Initiate Inspector user logically deleted the record the record is no longer used in algorithmic comparisons. (See: Logical Deletion) An attribute status of D indicates that the attribute has been logically deleted. (See: Logical Deletion, Active Attribute, Inactive Attribute) Information describing a person or object (for example, name, address, part number, organization). (See: Attribute) 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) 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) IBM Initiate glossary 7

14 Deterministic Matching Duplicate Record Dynamic Task Creation EID EID Synchronization EMCA EMPI Encounter Data 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. Two or more records representing the same person or object that are stored in the same original source system. 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) Enterprise ID. (See: Enterprise ID, Non-Simple EID, Simple EID) 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. 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) Enterprise Master Patient Index. Used in the healthcare industry, an EMPI contains unique identifiers for each person or patient. (See: CDI, MPI) Dates and information regarding a member's visit to a facility within your organization. 8 Glossary

15 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 Enterprise ID 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. 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 Entity Entity Manager 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. 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) 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. IBM Initiate glossary 9

16 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 v v v Identity an individual. Records in an identity entity (multiple records representing the same person) are linked based on attribute similarity. Household multiple 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. Group 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. Organization multiple 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 data Test or Production and 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

17 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 False Positive Filter Fixed Segments Get Glue Member Two linked members that are not the same person. 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. The set of standard, packaged segments shipped with the IBM Initiate Master Data Service software. (See: Implementation-Defined Segments, Segment) 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. 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 = , Ph = John Quentin Public, , John Quentin, , IBM Initiate glossary 11

18 Golden Record Group Entities Groups Hardlink HasShadow Hierarchy 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. A golden record refers to a transactions hub where the most relevant/appropriate representation of the customer/entity is persisted instead of dynamically created. 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 (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. When working with organizational hierarchies, a hardlink occurs when members compare above the auto-link threshold. (See: Softlink) 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) 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

19 Hierarchy Tree Hints Historical Attributes A tree represents a visual image of a hierarchy. A tree can be one or multiple levels deep. See: Task Hints. 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) Hook Point 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. The location that callback invocation occurs during Master Data Engine processing. (See: Callback Handler) Household / Household Entity Hub Attributes Hub-controlled Attributes 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 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) 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, IBM Initiate glossary 13

20 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 Identification Task Identifier Identity Domain Identity Entity Identity Rules IMM 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) Unit of work, created by the Master Data Engine, which facilitates user review, and possibly resolution. Also sometimes called Identity Task. A number or code referring to a specific individual. (See: Enterprise ID, Source ID) 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. An entity type; a single individual whose records are grouped by demographic attributes. (See: Entity Type) An identity rule is applied when two members have been given the same Enterprise ID. (See: Non-Identity Rules) 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

21 Implementation-Defined Segments Inactive Attribute Inbound Broker Informational Source Interaction Interceptor Invalid Reference Linkage 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) 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) 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 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. 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. 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. (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. Two or more records that are associated by a common Enterprise ID. IBM Initiate glossary 15

22 Linkage Modification Date Linkage Set Linkage Status Linkage Type Log Files Logical Deletion Madlogs ManuLink-MS ManuLink-SS The date a linkage was modified any change made to a member or record in a linkage set (for example, Enterprise ID change or status update) in the Hub database. 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. 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). 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. 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.) Reference to a record that remains in the database, but is not included in comparisons or retrieved in searches. 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) (Linkage type.) Indicates an IBM Initiate Inspector user manually linked records from multiple sources. (Linkage type.) Indicates an IBM Initiate Inspector user manually linked records from the same source. 16 Glossary

23 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) Master Data Engine Master Data Engine server Master Data Extract Match Matched Pairs 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. 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) The actual computer on which Master Data Engine is installed. (See: MPINET) 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. 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 Manager using the thresholds and only returning those members that are above the CR threshold, or that take part in a Review Identifier task. Two members identified as the same person by the Master Data Engine. IBM Initiate glossary 17

24 MCA Most Current Attribute. The most current attribute value. (See: EMCA) MDM Member Get Interaction Member Logical Model Member Match Interaction Member Put Interaction Member Search Interaction Member Status 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. 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) 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. 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) 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) 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. The current status of a member; status can be Active, Inactive, or Deleted. 18 Glossary

25 Member Type Member/Record MemRecno Merge Message Broker Message Processor 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. 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. 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. 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. See: Inbound Broker and Outbound Broker. 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 message was processed successfully, or to a reject queue (for example, reject-yyyymmdd-tttt.dat) if the message was not processed successfully. IBM Initiate glossary 19

26 Message Reader Missing Relationship MPI MPINET mpxdata Configuration File Multiplicity Relationship NoChange Non-Event 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. (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. 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 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) 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. (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. (Linkage type.) An IBM Initiate Inspector user updates the workflow status, but does not make a change to the Enterprise ID. 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

27 Non-Identity Rules Non-Obvious Relationships Non-Simple EID Non-transitive entity Organization Outbound Broker Overlay Owner 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) 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.) A non-simple EID is an Enterprise ID shared by more than one record (records that have been linked). (See: EID, Simple EID) 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) One of the defined member types. Organization is used in the business or corporate environment to accommodate the management of organization data. 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. An overlay occurs when one member's information overrides the information of another, different, member record. (See: Potential Overlay) 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. IBM Initiate glossary 21