Let me give a simple comparison. I leave it to others to provide a more in-detailed explanation of DQD, because there is much to say about the principles behind that framework.
Achilles is around for a while. It does characterisation of your OMOP dataset (i.e. counting occurrences of events) AND executes a small set of data validation checks (the Achilles Heel component). The characterisation component is the input for the ‘Data Sources’ component in Atlas.
The DataQualityDashboard was released during last years symposium. It only does data validation and does so very rigorously with a big set of checks. This framework is easily extensible with your own checks and the threshold for each check can be customised for your dataset.
At The Hyve, we are switching from using Achilles Heel to using DQD for data validation. We will still use Achilles for data characterisation.
OHDSI has no “investigative” checks. We seem to be afraid of writing those. Our grade of notification had “mixed reaction”. (and mostly not moved to DQD).