Data Requirements
dm+d
The dm+d data fields used for this process are;
| VTM | VMP | VMP-VPI | VMP-FORM | VMP-ROUTE |
|---|---|---|---|---|
| VTMID | VTMID | |||
| VPID | VPID | VPID | VPID | |
| NM | NM | |||
| INVALID | INVALID | |||
| NON_AVAILCD | ||||
| UDFS | ||||
| UDFS_UOMCD | ||||
| UNIT_DOSE_UOMCD | ||||
| STRNT_NMRTR_VAL | ||||
| STRNT_NMRTR_UOMCD | ||||
| STRNT_DNMTR_VAL | ||||
| STRNT_DNMTR_UOMCD | ||||
| FORMCD | ROUTECD |
Together with the FORM, ROUTE and UNIT_OF_MEASURE vocabularies from the dm+d LOOKUP data.
When dm+d data is imported into a relational database, concepts marked as INVALID or VMP concepts flagged as "not actual products available" may be excluded from the import.
Mapping between UCUM and SNOMED/dm+d
The following mapping table needs to be available to the implementing system. It is required to identify the units of measure within the UCUM standard that use different different codes to the dm+d.
For example g is a UCUM code for "gram" and the equivalent within dm+d is gram|258682000 so a mapping is required to associate g with the SNOMED code 258682000. This mapping table may need to be extended within a local implementation depending on which UCUM units are to be expected.
| SNOMED/dm+d code | UCUM unit |
|---|---|
| 258683005 | kilogram |
| 258682000 | g |
| 258684004 | milligram |
| 258686002 | ng |
| 258685003 | ug |
| 258773002 | milliliter |
| 258770004 | liter |
| 258770004 | l |