From 1a21d5fae988711033f99d6b8f7228c8569f5b8e Mon Sep 17 00:00:00 2001 From: Mark Wardle Date: Sun, 18 Feb 2024 09:45:07 +0000 Subject: [PATCH] Fix #62 --- README.md | 10 +++++++++- 1 file changed, 9 insertions(+), 1 deletion(-) diff --git a/README.md b/README.md index fa73f45b..ab512a71 100644 --- a/README.md +++ b/README.md @@ -1286,12 +1286,20 @@ Search parameters: * `inactiveDescriptions` - whether to search inactive descriptions (default, `true`) * `fuzzy` - whether to use fuzziness for search (default, `false`) * `fallbackFuzzy` - whether to retry using a fuzziness factor if initial search returns no results (default, `false`) -* `removeDuplicates` - whether to remove results with the same conceptId and text (default, `false`) +* `removeDuplicates` - whether to remove consecutive results with the same conceptId and text (default, `false`) For autocompletion, in a typical type-ahead user interface control, you might use `fallbackFuzzy=1` (or `fallbackFuzzy=true`) and `removeDuplicates=1` (or `removeDuplicates=true`). That will mean that if a user mistypes one or two characters, they should still get some sensible results. +`removeDuplicates` is designed to create a better user experience when searching SNOMED CT. In general, during search, +you will want to show to the user the multiple synonyms for a given concept. Recently however, and particularly if you +are using multiple SNOMED CT distributions (e.g. both the UK clinical and drug extensions), then a single concept may +have multiple synonyms with the same textual content. This can be disconcerting for end-users as it looks as if there +are duplicates in the autocompletion list. Each, of course, has a different description id, but we do not show identifiers +to end-users. To improve the user experience, I advise using `removeDuplicates` to remove consecutive results with the +same conceptId and text. + Here I search for all UK medicinal products with the name amlodipine and populate my autocompletion control using the results: