across systems. Most systems today integrate using file passing techniques driven by extract programs that are set to run at specific times. The new strategy calls for data exchanges that are message based and are triggered by data change and business events rather than by a schedule. This will result in a reduction in latency of data flows reducing the time it takes to propagate changes across the enterprise from days to minutes. 7.4.2 Master Data Management MDM is the physical embodiment of DG. It includes tools to perform data quality analysis, probabilistic matching and sophisticated record merge and unmerge functions. It also includes the ability for automatic decision making by categorizing matches according to a weighted score so that thresholds can be applied for automatic versus guided actions. Systems can submit data and/or subscribe to data. Kentucky is using IBM’s MDM tool which houses the matching functions of an MDM program. The tool has the ability to match person or business demographics information based on complex algorithms and it even has the ability to match based on common misspellings and nicknames. For example, it knows that “Rob”, “Bob” and “Bobby” are all likely nicknames for “Robert”. The MDM tool also has the ability to support subscriptions from other systems via files or web services. Subscribing systems receive the golden record, but that record also contains all versions of any field that was different for the underlying records that were matched to produce the golden record. For example, suppose the following three records were matched: First Middle Last Address City State John Michael Smith 141 Dead Oak Ave Corbin KY John M Smith 141 Dead Oak Ave Corbin KY John Smith 141 Dead Oak Ave Corbin KY Table 129: Master Data Management The resulting record would be John (Michael or M or “”) Smith. The fields that were originally different contain multiple values. 7.4.3 Enterprise Data Flows The following diagrams depict the current and future state overall Kentucky Medicaid processing assets and data flows. Figure 53: Kentucky Medicaid Enterprise Architecture (Current State) Figure 54: Kentucky Medicaid Enterprise Architecture (Future State)
across systems. Most systems today integrate using file passing techniques driven by extract programs that are set to run at specific times. The new strategy calls for data exchanges that are message based and are triggered by data change and business events rather than by a schedule. This will result in a reduction in latency of data flows reducing the time it takes to propagate changes across the enterprise from days to minutes. 7.4.2 Master Data Management MDM is the physical embodiment of DG. It includes tools to perform data quality analysis, probabilistic matching and sophisticated record merge and unmerge functions. It also includes the ability for automatic decision making by categorizing matches according to a weighted score so that thresholds can be applied for automatic versus guided actions. Systems can submit data and/or subscribe to data. Kentucky is using IBM’s MDM tool which houses the matching functions of an MDM program. The tool has the ability to match person or business demographics information based on complex algorithms and it even has the ability to match based on common misspellings and nicknames. For example, it knows that “Rob”, “Bob” and “Bobby” are all likely nicknames for “Robert”. The MDM tool also has the ability to support subscriptions from other systems via files or web services. Subscribing systems receive the golden record, but that record also contains all versions of any field that was different for the underlying records that were matched to produce the golden record. For example, suppose the following three records were matched: First Middle Last Address City State John Michael Smith 141 Dead Oak Ave Corbin KY John M Smith 141 Dead Oak Ave Corbin KY John Smith 141 Dead Oak Ave Corbin KY Table 129: Master Data Management The resulting record would be John (Michael or M or “”) Smith. The fields that were originally different contain multiple values. 7.4.3 Enterprise Data Flows The following diagrams depict the current and future state overall Kentucky Medicaid processing assets and data flows. Figure 53: Kentucky Medicaid Enterprise Architecture (Current State) Figure 54: Kentucky Medicaid Enterprise Architecture (Future State)