Customize DIT Client Matching
Currently, Clarity has 2 client-matching options when using the DIT - full and regular. It would be helpful if users could select custom conditions for client matching in addition to full and regular.
In several communities, the data quality of SSNs are poor (often not collected/NULL), as an example. This results in the auto duplication of client records when other client-matching conditions could have been met. Many communities are very clear they do not want to match clients based on SSNs.
As such, more flexibility in client matching would be beneficial for many communities and make the DIT more useful overall.
Melissa Sutton-Dement
shared this idea
-
Swati Pande
commented
it would help us clean our data
-
Gary Culshaw
commented
This would be very useful to add more flexibility to the matching conditions.
-
Veena Sandra
commented
This would be super helpful to have custom conditions for client matching.
-
Tucker Morgan commented
It would also be useful to be able to define different client id#s coming from different databases that we are getting exports from. Like we are done with the client id#s from the HMIS we migrated out of entirely but if there's a VA HOMES ID that matches one of those old IDs it sometimes incorrectly updates that record id.
-
Anonymous
commented
We need to periodically delete clients in bulk from our Training Site and want to be able to match by the unique client identifier contained in HUDX-111's CSV output. That way we can feed some of these client rows back into the DIT (with an added DateDeleted) and it will match these clients and delete them.
Currently, HUDX-111's Client.csv file contains a PersonalID column, which looks to actually contain the client's Client ID. So we'd like to be able to match on this Client ID. And if this Client ID will be changed to a different client identifier in the future in HUDX-111, then we'd like that new identifier to work for matching.
We basically want a unique 1-to-1 identifier for each of the clients in HUDX-111 that can be used to match clients when importing a list of clients into the DIT for deletion.Our process would be to run the HUDX-111 report (CSV export), then open up the Client.csv file and filter to a subset of the Client list by DateCreated or DateUpdated. Then we'd enter a date to the DateDeleted column for all clients in this subset. Then we'd save, and upload this Client.csv file (as part of a .zip file containing the other requisite DIT import files) to the Data Import Tool, and expect the DIT to correctly match these clients by the entry in the PersonalID column and delete them all.
-
Arthur Warmoth commented
This would solve a whole host of problems and make the DIT more useful, especially with functions like deleting client data, not just importing.