Tool preparing missing pharmaceutical content, both national and generic, for import into SNOMED CT (a.k.a. SCT).
- download ex. ihtsdo-sct-drugmatch-1.0-distributable.zip
- Java 7 (or compatible) runtime.
- HealthTerm™ v9.0 (or newer) access, with SCT preloaded.
Example:
example/drugmatch_input_example.csv
Example data is intended to cover the most common use cases, and may be subject to change.
The behavior of the tool is controlled via:
setting.properties
| Setting | Value | Description |
|---|---|---|
| input.file | path | Input file |
| input.file.include_first_line | boolean | Set to true if first line contains data and should be included for processing (default: false) |
| file.content.separator_character | character | Column separator character (default: ;) |
| file.content.quote_character | character | Column value quote character (optional) |
| sct.extension.language_code | Ex. 'en' | National language code (ISO 639-1) |
| sct.extension.namespace_id | Namespace ID | National SCT extension namespace ID |
| sct.id.service | URL | SCT ID service URL |
| sct.module_id | Source Module ID | |
| sct.extension.language_reference_set_id | Language Reference Set ID | |
| sct.extension.quantity_reference_set_id | Quantity Reference Set ID | |
| sct.release_id | Ex. '201401031' | SCT release ID |
| verification.login | username | Verification service username |
| verification.password | password | Verification service password |
| verification.service | URL | Verification service URL |
| output.dir | path | Output folder (ex. './result' is equal to execution directory/result) |
| generic_report | boolean | If set to true, reports will contain generic rule messages (default: false) |
| strict_mode | boolean | If set to true, "Check" warnings will be treated as errors (default: false) |
| sct.attribute_id.has_active_ingredient | Concept ID | "Match" attribute, Has active ingredient |
| sct.attribute_id.has_dose_form | Concept ID | "Match" attribute, Has dose form |
| sct.constraint_id.dose_form | Concept ID | "Check" dose form top point limitation |
| sct.constraint_id.substance | Concept ID | "Check" substance top point limitation |
| sct.constraint_id.unit | Concept ID | "Check" unit top point limitation |
Each phase in the DrugMatch flow, can be triggered independently using the matching executable (ex. check.bat).
Verify that all pharmaceutical components, ie. substance, dose form and unit of measurement, can be matched with only one exact SCT equivalent representation.
Generates a status report for each of the above mentioned pharmaceutical component attributes.
Based on successful completion of the previous step, the following approach should be able to match a national pharmaceutical product with only one exact SCT generic pharmaceutical product, if present, based on the product characteristics provided in the input file.
Retrieve SCT concept matches where the attributes contains the product components, from the product hierarchy.
Optionally generates a status report for this step, by providing runtime argument "--matchAttributeReport", in order to support debugging.
Based on successful completion of the previous step, the "Match" term attempts to determine if a pharmaceutical is present in either national or generic SCT concept representation.
Generates a status report for each of the above mentioned pharmaceutical component attributes.
Generates SCT Release Format 2 for unmatched SCT generic and national product concepts with fully dressed attributes and terms, based on the pharmaceutical products characteristics in the input file.
Also generates a simple 1 <-> 1 mapping file between the input Drug ID and corresponding SCT Concept ID.
This tool was developed with Java 7 and Apache Maven v3.2.1.
Build, unit test and generate reports for project, command:
mvn install site