Suppose an existing codelist has the following code:
ICD-10 | I21.9 | Acute myocardial infarction
And now I want to upload a CSV file to this codelist, and my file contains hundreds of codes, including the code below:
ICD-10 | I21.9 | Acute myocardial infarction, unspecified
Here the code and coding system are identical, but the code name is slightly different from what I already had in my codemapper codelist, maybe because of the dictionary updates.
In the current behaviour of Codemapper, the system treats this as a conflict and stops the entire import because the duplicate code has a different code name and gives the following error:
However, reviewers do not have the time to manually go through the entire CSV file and compare it with the existing codelist to identify discrepancies. Therefore, we would prefer that CodeMapper not block the import process in such cases. Instead, the system should allow the file to be imported normally while flagging situations where a code already exists in the codelist but with a different code name . This could be presented either as an import warning message or as a flag within the codelist, enabling the reviewer to easily identify and review these discrepancies.
Suppose an existing codelist has the following code:
ICD-10 | I21.9 | Acute myocardial infarction
And now I want to upload a CSV file to this codelist, and my file contains hundreds of codes, including the code below:
ICD-10 | I21.9 | Acute myocardial infarction, unspecified
Here the code and coding system are identical, but the code name is slightly different from what I already had in my codemapper codelist, maybe because of the dictionary updates.
In the current behaviour of Codemapper, the system treats this as a conflict and stops the entire import because the duplicate code has a different code name and gives the following error:
However, reviewers do not have the time to manually go through the entire CSV file and compare it with the existing codelist to identify discrepancies. Therefore, we would prefer that CodeMapper not block the import process in such cases. Instead, the system should allow the file to be imported normally while flagging situations where a code already exists in the codelist but with a different code name . This could be presented either as an import warning message or as a flag within the codelist, enabling the reviewer to easily identify and review these discrepancies.