Find out the priorities by which people search, and how they differentiate by subsequent queries when they run across duplicate records.
The UUID from the database can be useful, but only if the users have prior knowledge about a record: they've used this ID before, they've memorized other distinguishing information that they associate with the ID, etc...
Who is searching for this person, and what do they know?
If I know a persons name, age and marital status, that could be the beginning of my query.
After that, I might look for their location (if given).
Or, if the search has no additional data to surface, I will have to look at the detailed history of any activity or operations performed on this record.
A database ID is only useful to me once I've established that it represents exactly the person whose record I need to access / perform operations on.