implementation_international_drug_vocabulary
Differences
This shows you the differences between two versions of the page.
| Both sides previous revision Previous revision Next revision | Previous revision Last revision Both sides next revision | ||
|
implementation_international_drug_vocabulary [2020/06/26 19:54] aostropolets |
implementation_international_drug_vocabulary [2021/06/09 10:15] adavydov |
||
|---|---|---|---|
| Line 1: | Line 1: | ||
| - | ===== International drugs vocabulary implementation process ===== | + | ===== International drug vocabulary implementation process ===== |
| The most straightforward way to standardize a local drug [[documentation:vocabulary|Vocabulary]] is to utilize [[documentation:international_drugs|RxNorm Extension]] logic to extend standard Drug concept pool and map source drug products to concepts in RxNorm and RxNorm Exterension. | The most straightforward way to standardize a local drug [[documentation:vocabulary|Vocabulary]] is to utilize [[documentation:international_drugs|RxNorm Extension]] logic to extend standard Drug concept pool and map source drug products to concepts in RxNorm and RxNorm Exterension. | ||
| Line 56: | Line 56: | ||
| Brand Names that are simple combinations of generic international name of active substance and manufacturer name (e.g. "Aspirin Bayer") should not appear as attributes for Drug Products. Manufacturer information should be stored as a concept with Supplier class. | Brand Names that are simple combinations of generic international name of active substance and manufacturer name (e.g. "Aspirin Bayer") should not appear as attributes for Drug Products. Manufacturer information should be stored as a concept with Supplier class. | ||
| - | Concepts that belong to the source vocabulary, but do not belong to Drug domain by OMOP CDM conventions, should be classified as 'Device'. Typically, these belong to different substance groups: | + | Concepts that belong to the source vocabulary, but do not belong to Drug domain by OMOP CDM conventions, should be classified as 'Device'. Typically, these belong to different groups - check them [[documentation:vocabulary:drug|here]]. |
| - | * Radiographic contrasts and dyes (barium sulfate, radiolabeled iodides) | + | |
| - | * Formulas for infant feeding | + | |
| - | * Parenteral nutrition (aminoacids and/or lipid mixes) | + | |
| - | * Solution for dialysis, catheter maintenance etc. | + | |
| - | * Blood products for transfusion, blood plasma, autologous and non-autologous transplants of any kind | + | |
| - | * Cosmetics, sunscreens, non-medicated shampoos and soaps, etc. | + | |
| - | * Surgical materials like bone cements | + | |
| - | * Topical/external disinfectants | + | |
| Animal drugs can be handled as Drugs or Devices, depending on what their role in patient data can be expected to be. | Animal drugs can be handled as Drugs or Devices, depending on what their role in patient data can be expected to be. | ||
| Line 72: | Line 64: | ||
| This table should contain the mapping between source codes and Standard Concepts for Ingredients, Brand Names, Dose Forms, Suppliers and Units. All other relationships will be ignored. | This table should contain the mapping between source codes and Standard Concepts for Ingredients, Brand Names, Dose Forms, Suppliers and Units. All other relationships will be ignored. | ||
| - | ^Field^Required^Type^Description^ | + | ^ Field ^ Required ^ Type ^ Description ^ |
| - | |concept_code_1|Yes|VARCHAR(50)|The source code| | + | | concept_code_1 | Yes | VARCHAR(50) | The source code | |
| - | |concept_id_2|Yes|INTEGER|The existing target Concept| | + | | vocabulary_id_1 | Yes | VARCHAR(20) | The source vocabulary | |
| - | |precedence|No|SMALLINT|For multiple concept_code_1/concept_id_2 combination the order of precedence in which they should be considered for equivalence testing. The mapping with the highest prevalence among the drugs will be used for writing a record to the CONCEPT_RELATIONSHIP table. A missing precedence will be interpreted as precedence 1. Every precedence value should be unique per concept_code_1| | + | | concept_id_2 | Yes | INTEGER | The existing target Concept | |
| - | |conversion_factor|No|NUMERIC|The factor used to convert the source code to the target Concept. This is usually defined for units| | + | | precedence | No | SMALLINT | For multiple concept_code_1/concept_id_2 combination the order of precedence in which they should be considered for equivalence testing. The mapping with the highest prevalence among the drugs will be used for writing a record to the CONCEPT_RELATIONSHIP table. A missing precedence will be interpreted as precedence 1. Every precedence value should be unique per concept_code_1 | |
| + | | conversion_factor | No | NUMERIC | The factor used to convert the source code to the target Concept. This is usually defined for units | | ||
| This table should contain all mappings from the new to existing Concepts and their precedence. | This table should contain all mappings from the new to existing Concepts and their precedence. | ||
implementation_international_drug_vocabulary.txt · Last modified: 2021/06/09 10:15 by adavydov
Page Tools
