Solved

Can we get the MasterID (Unique, deduplicate) for a NEW person in real time/ online?

  • 21 January 2022
  • 3 replies
  • 212 views

Userlevel 1
Badge

Hi there,

Imagine Ataccama is the primary source of truth (transactional) for PII information inside a Financial Service company. Now, we would have different ONBOARDING systems (one for each Financial Line of Business that we offer). When a new person tries to create a profile, the Onboard system would (while the user is still looking into the APP) SYNCHRONOUSLY call an Ataccama API with meaningful data that we collected from this person, say: (Full Name, DoB, Insurance Number / Any other ID document, Email(s), Phone(s))m then Ataccama would quickly do the “Match” and return if this person (according to the information we provided) is likely to ALREADY exist. If the probability is higher than some threshold (Ie. 95%), it would also return the MASTER UUID for this person in Ataccama (Lookup key). Then the onboarding would ask this person to log in, as this person ALREADY exists in our Ataccama Database.

Can Ataccama do the MATCH and return the % probability in near real-time? 

Instead of allowing duplicate records (and IDs) to be created and only much later trying to match them, we would like to use Ataccama to minimize drastically (avoid??) data duplication in the first place. Is that something Ataccama can do?
Our database is small, with less than 1 million customers so far. So even if we become a complete success, we would still have less than 10 MM customers.

Any help would be appreciated.

icon

Best answer by oliver 21 February 2022, 09:01

View original

3 replies

Userlevel 1
Badge

@hoo Please, can you help? Regards 

Badge +1

Hi jfbaro,


Ataccama MDM provides Identify online service and it is possible to achieve what you described using this service. 

The Identify service answers the question, "is this record similar to any record stored in the hub?". Input is in the form of the instance entity, while similarity is defined by the matching rules of this entity. Output is either nothing or matching information and master record (including Master ID).


The service cleanses input data and tries to match the record to records in the MDM hub using matching rules (under the hood, it runs cleansing and matching plans). If an input record is matched to a master group, a master record is returned.

Userlevel 1
Badge

That's really helpful! Thanks! :pray:

Reply