A shared name is not a shared identity
Names can be common, misspelled, changed, or recorded in different formats. Addresses and phone numbers can change or be shared. A matching process therefore needs more than one convenient field, along with rules for uncertainty and review.
Making matching more permissive may recover some genuine links while also increasing the risk of incorrect ones.
Two error types, different consequences
| Error | Possible consequence |
|---|---|
| One person remains split across records | Relevant history may be missed |
| Two people are merged | Another person's result may appear in the chart |
Neither problem is solved simply by making the database look less duplicated.
If a portal contains unfamiliar information
An unfamiliar result or visit deserves clarification through the provider's records process. Preserve the date and description that seem wrong without assuming the cause. It could involve a matching problem, an entry error, or another issue.
For teams evaluating a matching system, report both false links and missed links against a suitable reference process. Overall agreement can conceal a small but consequential group of wrong merges. The aim is correct identity resolution with traceable review, not merely the highest percentage of records automatically connected.
