1 / 6

Citizen360 Citizen Record Concepts

Citizen360 Citizen Record Concepts. An Introduction to the citizen record pattern. You should see the system overview before you run this presentation. Click here to launch the overview presentation. Version 1.0. Citizen360 – Data Record Concepts.

mostyn
Download Presentation

Citizen360 Citizen Record Concepts

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Citizen360 Citizen Record Concepts An Introduction to the citizen record pattern You should see the system overview before you run this presentation. Click here to launch the overview presentation. Version 1.0

  2. Citizen360 – Data Record Concepts • The same person may be in the system several times because they are from several source systems, e.g., DHS, DOR or DSS • There is no conflict in this situation – but it is not what is desired • We identify Citizens using any one of three mechanisms: • The key used by the source system that provided the Citizen • A Master Index (optional) • An internal identifier • Identity Resolution processes exist to find possible people matches • When People are linked/merged: • The detailed data elements are moved under a common citizen “header record” • Source systems are not forced to have the same values – they are still decoupled

  3. Data is kept uniquely by Source-System The following Citizen Search screen illustrates the concepts 3 of the 5 records are linked across the source-systems – they have the same Master Index value The search found 5 different records from 5 different systems

  4. Data is kept uniquely by Source-System Citizen Id: 222222 Master Index:10001340065 Citizen Id: 333333 Master Index:1000130073 Citizen Id: 111111 Master Index: 10001340057 Date of Birth Date: 07/14/1965 Source DSS Date of Birth Date: 07/13/1965 Source DOH Date of Birth Date: 07/14/1965 Source DOL Date of Birth Date: 12/28/2009 Source DOR Date of Birth Date: 07/14/1965 Source DHS There are 3 citizen “header records” in our example… The first “header record” has data from three different systems. Note that the systems are decoupled and can have different values for the same data element.

  5. Merging does not change the data – it is still held by Source System Citizen Id: 222222 Master Index:10001340065 Citizen Id: 333333 Master Index:1000130073 Citizen Id: 111111 Master Index: 10001340057 Identity Resolution Process Match: 82% Identity Resolution Process Match: 83% Date of Birth Date: 12/28/2009 Source DOR Date of Birth Date: 07/14/1965 Source DSS Date of Birth Date: 07/14/1965 Source DSS Date of Birth Date: 07/13/1965 Source DOH Date of Birth Date: 07/14/1965 Source DOL Date of Birth Date: 07/14/1965 Source DHS Date of Birth Date: 07/13/1965 Source DOH Master Index History Value: 10001340057 Master Index History Value: 10001340065 Master Index History Value: 1000130073 Based on Identity Resolution processes we may decide to merge other records… We can continue to use any of the original/historic “master index” values to reference the citizen The data is still unique by source system - but we now know that it is for a common citizen

  6. THANK YOU info@bSolv.com www.bsolv.com 3330 Cumberland Boulevard Suite 500 Atlanta, GA 30339 Office: +1 678.638.6692 Confidential and Proprietary

More Related