Entity Resolution is the algorithmic process of identifying, linking, and merging disparate data records that refer to the same real-world entity—such as a patient, provider, or organization—across heterogeneous data sources. It resolves semantic ambiguity by determining whether John A. Smith, DOB 05/12/1980 in an EHR system and J. Smith, MRN 88921 in a lab feed represent the same individual, using a combination of deterministic matching on unique identifiers and probabilistic matching on fuzzy attributes.
Glossary
Entity Resolution

What is Entity Resolution?
The computational task of disambiguating and linking disparate records that refer to the same real-world object across different data sources, a core function of master data management.
The core mechanisms involve blocking to reduce the computational search space, pairwise comparison using similarity algorithms like Levenshtein distance or Jaccard index, and clustering to group matched records. The output is a golden record—a single, authoritative, de-duplicated view of the entity. This process is foundational to clinical data integrity, enabling accurate patient longitudinal records, reliable cohort identification, and the elimination of duplicate medication orders that could lead to adverse safety events.
Core Characteristics of Entity Resolution
The foundational computational techniques and logical processes that enable systems to determine whether disparate data records refer to the same real-world object, a critical function for creating a unified golden record in master data management.
Deterministic Matching
A rule-based approach that establishes record linkage through exact or partial agreement on predefined identifier fields. This method applies strict logical conditions—such as exact Social Security Number or composite key matches—to generate binary match/no-match outcomes.
- Exact Matching: Requires character-for-character equality on a unique identifier.
- Deterministic Rule Sets: Uses cascading logic, such as matching on first name, last name, and date of birth simultaneously.
- Guarantees: 100% precision for the defined rule but suffers from low recall due to typos or missing data.
- Use Case: Ideal for high-certainty linking in financial compliance where false positives are unacceptable.
Probabilistic Record Linkage
A statistical framework, formalized by Fellegi and Sunter, that calculates the likelihood that two records belong to the same entity by comparing multiple fields and assigning agreement and disagreement weights. This method models the probability of chance agreement versus true match agreement.
- M-Probability: The probability that a field agrees given the pair is a true match.
- U-Probability: The probability that a field agrees by random chance.
- Composite Weight: Sum of log-likelihood ratios across all compared attributes.
- Threshold Tuning: A cutoff score is set to classify pairs as matches, non-matches, or potential matches requiring clerical review.
Blocking and Indexing
A performance optimization technique that reduces the quadratic computational complexity of comparing every record against every other record. Blocking keys partition the dataset into mutually exclusive buckets, ensuring only records within the same block are compared.
- Sorted Neighborhood Method: Slides a window over a sorted list of records to compare only nearby entries.
- Canopy Clustering: Uses a cheap, approximate distance metric to create overlapping subsets for candidate generation.
- Phonetic Blocking: Groups records by sound-based encodings like Soundex or Metaphone to catch phonetic spelling variations.
- Goal: Drastically reduce the number of pairwise comparisons from billions to millions.
Fuzzy String Similarity
Algorithms that quantify the lexical distance between two text strings to account for typographical errors, abbreviations, and formatting inconsistencies that defeat exact matching. These metrics are the core distance functions in probabilistic models.
- Levenshtein Distance: The minimum number of single-character edits (insertions, deletions, substitutions) required to change one string into another.
- Jaro-Winkler Similarity: A metric optimized for short strings like names, giving higher weight to matching prefixes.
- Cosine Similarity with TF-IDF: Treats strings as vectors of n-grams or tokens to measure angular similarity, robust to word transpositions.
- Phonetic Algorithms: Double Metaphone reduces names to a primary and secondary phonetic hash to handle diverse linguistic origins.
Graph-Based Resolution
An approach that models entities and their relationships as a connected graph, where nodes represent records and edges represent match links. This enables transitive resolution, where if record A matches B, and B matches C, then A and C are inferred to be the same entity.
- Connected Components: Identifies clusters of records that are transitively linked, merging them into a single resolved entity.
- Community Detection: Algorithms like Louvain can identify dense clusters of identity in massive graphs.
- Edge Weighting: Match confidence scores are stored as edge weights, allowing for weighted graph traversal and pruning of weak links.
- Advantage: Resolves complex many-to-many relationships that pairwise matching misses.
Survivorship and Merging
The post-resolution process of constructing a single, authoritative golden record from a cluster of matched duplicate records. Survivorship rules are deterministic policies that select the best value for each attribute from the competing source records.
- Source Trustworthiness: A hierarchical ranking of data sources, where a value from a trusted source (e.g., passport) overrides a less trusted one (e.g., utility bill).
- Data Currency: Rules that prioritize the most recent timestamp or the most frequently occurring value.
- Attribute-Level Rules: Different survivorship strategies can apply to different fields; a name might take the longest value, while an address takes the most recent.
- Lineage Tracking: The golden record must retain pointers back to the source records that contributed to its values for auditability.
Frequently Asked Questions
Clear, technical answers to the most common questions about disambiguating and linking records across disparate healthcare data sources.
Entity resolution is the computational task of identifying and linking disparate records that refer to the same real-world object—such as a patient, provider, or medication—across different data sources. It works by applying a combination of deterministic matching rules (exact comparisons on unique identifiers) and probabilistic matching algorithms (statistical models that weigh the likelihood of a match based on multiple attributes). The process typically involves blocking to reduce the search space, pairwise comparison of record attributes using similarity metrics like Levenshtein distance or Jaccard index, and clustering to group matched records. A final canonicalization step merges linked records into a single, authoritative golden record. In healthcare, this is critical for creating a unified patient view from fragmented EHR systems, ensuring clinical data integrity and patient safety.
Enabling Efficiency, Speed & Accuracy
Intelligent Analysis, Decision & Execution
We build AI systems for teams that need search across company data, workflow automation across tools, or AI features inside products and internal software.
Talk to Us
Search across company data
Give teams answers from docs, tickets, runbooks, and product data with sources and permissions.
Useful when people spend too long searching or get different answers from different systems.

Automate internal workflows
Use AI to route work, draft outputs, trigger actions, and keep approvals and logs in place.
Useful when repetitive work moves across multiple tools and teams.

Add AI to products and internal tools
Build assistants, guided actions, or decision support into the software your team or customers already use.
Useful when AI needs to be part of the product, not a separate tool.
Related Terms
Entity resolution relies on a constellation of complementary techniques to transform fragmented data into unified, actionable records. Explore the core concepts that power master data management.

About the author
Prasad Kumkar
CEO & MD, Inference Systems
Prasad Kumkar is the CEO & MD of Inference Systems and writes about AI systems architecture, LLM infrastructure, model serving, evaluation, and production deployment. Over 5+ years, he has worked across computer vision models, L5 autonomous vehicle systems, and LLM research, with a focus on taking complex AI ideas into real-world engineering systems.
His work and writing cover AI systems, large language models, AI agents, multimodal systems, autonomous systems, inference optimization, RAG, evaluation, and production AI engineering.
Partnered with leading AI, data, and software stack.
How We Work
Custom AI workflows for your Business
One-fit-all AI don't work for modern businesses. At Inferensys, we aim to understand your business & custom requirements; which we use to define most efficient agentic workflows, the data, and the tools for your business.
01
Review the use case
We understand the task, the users, and where AI can actually help.
Read more02
Pick the right approach
We define what needs search, automation, or product integration.
Read more03
Build the first useful version
We implement the part that proves the value first.
Read more04
Improve from there
We add the checks and visibility needed to keep it useful.
Read moreThe first call is a practical review of your use case and the right next step.
Talk to Us