Back to topics

How a database match can confuse two people

Combining two lists sounds simple until two people share the same name and birthday, or one person's name is spelled two different ways. In database record linkage, an overly strict rule misses real matches, while a loose rule merges two strangers into one file. When those merged records are used for credit checks, watchlists, or medical histories, a data-matching rule becomes a high-stakes human problem.

4–6 min

Questions you could explore

  • Why can a shared name and date of birth be insufficient to establish a unique identity?
  • What safeguards are needed before an automated database match triggers a real-world penalty?

Start reading

Ready to try your ideas aloud?

Your topic carries over. Record up to 2½ minutes, depending on your plan.

Computers and AI

Why can a damaged QR code still work?

A scratch or stain does not always stop a QR code from being read. Its stored information includes redundancy, but that does not mean any part of the image can be covered without consequence.

3–5 min
Computers and AI

How does a website name become an internet address?

You remember a website by its name, while the network needs an address for the connection. DNS supplies that translation, sometimes from a saved answer and sometimes by asking other servers.

4–5 min
Computers and AI

Same emoji, different picture

The same emoji can arrive with a different expression or style from the one you saw when sending it. Unicode identifies characters and sequences, while software platforms choose artwork and decide what their versions support.

2–3 min
How a database match can confuse two people | Speech Topic | speaking.app