| Table of Contents |
|---|
| Warning |
|---|
NOTE: Medical dictionaries can be LARGE files and frequently take several minutes to upload and process. Please be sure to allow the operation to fully complete, and do not cancel the operation or leave the page during processing. If you receive an error, please open a support ticket and include a full screenshot of the error message and provide details on the dictionary type and version. |
Summary
ClinSpark supports uploading use of WHODrug and MedDRA dictionaries for use in medical coding. These dictionaries must be are often licensed and must obtained by the customer from WHODrug and MedDRA respectivelycustomers from providers (vendors) UMC and ICH respectively. IQVIA will not provide copies of these dictionaries to customers.
Upon licensing, you will have available from the respective organizations zip files containing the dictionaries. These original zip downloads dictionary files in their original format from the vendor are what can be loaded uploaded for use into ClinSpark.
In ClinSpark the dictionaries can be loaded by an administrative user here:
...
NOTE: Medical dictionaries are LARGE files and frequently take several minutes to load. Please be sure to allow the operation to fully complete, and do not cancel the operation or leave the page during processing. If it takes longer than 6 minutes, or you receive an error, please open a support ticket.
WHODrug Uploads
...
| Info |
|---|
At this time, IQVIA does not support customers creating and uploading ‘custom’ versions of medical dictionaries. Limited support for this use case is only available based on the information contained in this article. This need is still under evaluation from the ClinSpark product team to improve support for custom dictionaries at a later time. |
Loading Dictionaries
The dictionaries can be uploaded to ClinSpark by a customer user with the ‘Administration Medical Dictionary’ role action here:
...
WHODrug Uploads
Acceptable formats
Customers are provided by the vendor a compressed zip archive file that contains both TXT or CSV variants of the dictionaries and other supplemental assets.
...
Supplementary files may also be in present within their own archive/zip directories.
...
The actual dictionary files will likely be those identified by file name not containing text accepted by ClinSpark will not contain names such as additional features.
The following example highlights the dictionary files that should be uploaded to ClinSpark.
...
ClinSpark will ignore the presence of any non .txt files during upload. It is not necessary to extract the .txt files from the licensed WHODrug zip, to create a new zip file, for the purpose of upload.
...
screenshot demonstrates this concept. The WHODrug Global txt_mar_1_2023.zip contains many archived directories; the correct ones are outlined.
...
The following screenshot highlights another example of dictionary files that are accepted by ClinSpark.
...
Expected Files for B3
For WHODrug dictionaries, the upload process expects the following files for B3:
BNA.txt
CCODE.txt
DD.txt
DDA.txt
DDSOURCE.txt
INA.txt
ING.txt
MAN.txt
VERSION.txt
| Info |
|---|
The above files are expected to be present in the root of the zip archive uploaded to ClinSpark. This is how the files come from vendor source. If customers chose to extract or modify dictionary files from the vendor source, prior to upload to ClinSpark, they must be repacked into a zip archive at the root. Placing files first into a folder, then compressing the folder into the zip archive, will not produce a valid zip. Error messages like this may present upon upload:  E.G. the expected file path for the ‘Version.txt’ file would be |
Files that are ignored
ClinSpark will ignore the presence of any non .txt files during upload. The upload feature expects this, and is designed to ignore the extra files. It is therefore not necessary to extract dictionary files from the licensed archive and create a new zip file, for the purpose of upload.
...