Discussion
Open question
- Posts
Names and email addresses change, and duplicate people or organizations can look similar. What should an integration design include?
Accepted answerChoose stable source identifiers and define which system owns each identity. Document crosswalk creation, confidence rules, duplicate handling, manual review, merge and unmerge processes, history, and error reporting. Never silently overwrite a source key with a heuristic match. Test ambiguous and changed records before launch. FAR Part 11 supports defining essential functional and performance requirements before selecting the technical solution.
Community replyHow should the system handle a confident match that a human later proves is wrong?
- You must be logged in to reply to this topic.