1 / 27

Data Linkage Strategies

Data Linkage Strategies. Shihfen Tu, Ph.D. University of Maine shihfen.tu@umit.maine.edu. Faculty Disclosure Information.

randy
Download Presentation

Data Linkage Strategies

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. Data Linkage Strategies Shihfen Tu, Ph.D. University of Maine shihfen.tu@umit.maine.edu

  2. Faculty Disclosure Information In the past 12 months, I have not had a significant financial interest or other relationship with the manufacturer(s) of the product(s) or provider(s) of the service(s) that will be discussed in my presentation. This presentation will not include discussion of pharmaceuticals or devices that have not been approved by the FDA.

  3. Acknowledgements • University of Maine • Quansheng Song • Cecilia Cobo-Lewis • Maine Bureau of Health • Kim Church • Pat Day • Ellie Mulcahy • Toni Wall

  4. Data Linkage

  5. Data Linkage

  6. Data Linkage

  7. Data Linkage - Probabilistic

  8. Data Linkage - Probabilistic

  9. Data Linkage - Probabilistic

  10. Data Linkage - Probabilistic

  11. Data Linkage - Inconsistency

  12. Message Inconsistency Detected Correcting…. Data Linkage - Inconsistency

  13. Inconsistencies ID=4484 Brad A. Graham • Record in EHDI links to two records in other database • The other source indicates the records belong to different people • How to address depends on processing of other database EHDI_ID=394 Brad A. Graham ID=7354 Brad Graham

  14. Inconsistencies ID=4484 Brad A. Graham • Other source not de-duplicated ? • Other source de-duplicated, but insufficient evidence to conclude ID=4484 and ID=7354 are the same person ? • BD may provide additional information so that these probabilities have changed EHDI_ID=394 Brad A. Graham ID=7354 Brad Graham

  15. ID=4048 John A. Graham EHDI_ID=394 John A. Graham EHDI_ID=948 Jon A. Graham ID=4048 Jon A. Graham EHDI_ID=948 Jon Graham ID=9324 Jon Graham Inconsistencies

  16. Inconsistencies • How this "cross-over" is resolved depends on whether one or neither file is given precedence • Influenced by probabilistic de-duplication process performed after a linkage

  17. Linkage Creep • EHDI Database contributes an individual,Catherine A. Sampson

  18. Linkage Creep • Link the Electronic Birth Certificate • Name is Catherine A. Simpson • Are these the same person? • Perform probabilistic match • Require .85 probability of a match to conclude two similar records are the same (Critical p = .85) • Probability is .90, we conclude they’re the same person

  19. Linkage Creep • Link Birth Defects Registry Data • Name is Kathy A. Simpson • Are these the same person? • Perform probabilistic match (require .85) • PMatch is .90, we conclude they’re the same person

  20. Linkage Creep • If we compare to Catherine A. Sampson • PMatch=.81 • Conclude they are NOT the same individual • Would not assign same ID • Which is correct?

  21. Linkage Creep • When is this a problem? • Over time, two distinct individuals may project “tendrils” composed of combinations of identifiers that statistically overlap in probabilistic space

  22. Linkage Creep • When is this a problem? • Linkage creep will result in the two distinct individuals being erroneously combined under a single ID

  23. Linkage Creep • When is this not problem? • Over time, certain key identifiers for an individual are expected to change • This phenomenon will increase as a historical database grows, and as additional sources are input into a centralized system

  24. Linkage Creep • Complexity of “creep” in longitudinal datasets • Black records are related to all records • Yellow and Blue records are NOT related to White record • Yellow record is also not related to Red record at

  25. Linkage Creep • Forbidding “creep” will result in a single individual being divided into two IDs over time • Further challenge—where to divide records into additional IDs?

  26. Tools for Evaluating Linkage • Inconsistencies can occur in deterministic linkage, but are more common in probabilistic linkages • Probabilities that create potential for problems provide a valuable tool for evaluating linkages • Instead of a “are two records the same person ?” Yes/No • Estimates or indices of how likely it is that two records are the same person • Should be able to estimate the number of erroneous linkages • Possible to conduct a detailed examination of quality by ignoring very strong and very weak pairings, and only focusing on pairings that are ambiguous

More Related