When marking possible duplicates as "Not a Duplicate" from DB View Duplicate Constituent Management Tool, this should also reflect in the NXT Data Health view. Without this, duplicate management is a doubled-up task as have to do it in both views. The Duplicate Constituent Management Tool is easiest to view/use as it shows multiple possible duplicates per master whereas the NXT view only shows 1. With the duplicate matching criteria being so broad, the majority of possible duplicates found are Not a Duplicate. As the duplicate matching criteria is hard coded and is different in DB View to what it is in NXT view, as is so broad it returns lots of possible duplicates, I find the tool at the moment (either view) to be unusable, and therefore, duplicate management is not maintained.