Table Detail Report
MLTM_COMBINATION_DRUG
| Column Section | Top of Page |
Table-level Detail
| Description: | Multum Combination Drug |
| Definition: | This table contains a listing of all clinically active ingredients for multi-ingredient (combination) drugs using the Multum drug_identifier. |
| Table Type: | REFERENCE |
Column Detail - MLTM_COMBINATION_DRUG
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| DRUG_IDENTIFIER | VARCHAR(6) | N | Contains the drug_identifier of the combination drug |
| MEMBER_DRUG_IDENTIFIER | VARCHAR(6) | N | Contains the drug_identifier of the clinically active ingredients |
| UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
| UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
| UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
MLTM_CONCEPT_NAME_MAP
| Column Section | Top of Page |
Table-level Detail
| Description: | MLTM_CONCEPT_NAME_MAP |
| Definition: | This is a new table for MULTUM allergy mappings. The CONCEPT_DRUG_NAMEs from this table will be used in building MULTUM allergies. |
| Table Type: | REFERENCE |
Column Detail - MLTM_CONCEPT_NAME_MAP
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CONCEPT_CKI | VARCHAR(50) | N | MULTUM CONCEPT_CKI |
| CONCEPT_DRUG_NAME | VARCHAR(255) | N | MULTUM CONCEPT_DRUG_NAME |
| DRUG_IDENTIFIER | VARCHAR(6) | N | MULTUM DRUG_IDENTIFIER |
| DRUG_SYNONYM_ID | DOUBLE | N | MULTUM DRUG_SYNONYM_ID |
| FUNCTION_IDENT | DOUBLE | N | MULTUM FUNCTION_ID |
| SOURCE_DISP | VARCHAR(25) | N | MULTUM SOURCE_DISP |
| UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
| UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
| UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
MLTM_CONDITION
| Column Section | Top of Page |
Table-level Detail
| Description: | Multum Condition |
| Definition: | This table assigns a common name to a medical condition. |
| Table Type: | REFERENCE |
Column Detail - MLTM_CONDITION
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CONDITION_DESCRIPTION | VARCHAR(255) | Y | This field contains a textual description for each condition term. |
| CONDITION_ID | DOUBLE | N | The PK for this table. This field contains a unique identifier for each condition term. |
| UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
| UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
| UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
MLTM_COUNTRY
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | MLTM_COUNTRY |
| Definition: | Table for identifying countries within Multum |
| Table Type: | REFERENCE |
Column Detail - MLTM_COUNTRY
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| COUNTRY_ID | DOUBLE | N | This field contains the Multum ID for the given country |
| COUNTRY_NAME | VARCHAR(100) | N | This field contains the name of the county supported by Multum |
| UPDT_APPLCTX | DOUBLE | N | The application context number from the record info block. |
| UPDT_CNT | DOUBLE | N | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. |
| UPDT_DT_TM | DATETIME | N | The date and time the row was last inserted or updated. |
| UPDT_ID | DOUBLE | N | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - MLTM_COUNTRY
| Parent Column in MLTM_COUNTRY (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | COUNTRY_ID | MLTM_GLOBAL_TYPE | COUNTRY_ID |
MLTM_CUSTOM_CSA_SCHEDULE
| Column Section | Top of Page |
Table-level Detail
| Description: | Multum Contolled Substance State Overrides |
| Definition: | This table contains customizations of the CSA schedules of drugs at the Generic Drug, and Generic Fomulation levels. |
| Table Type: | ACTIVITY |
Column Detail - MLTM_CUSTOM_CSA_SCHEDULE
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | DOUBLE | Y | The table row is active or inactive. A row is generally active unless it is in an inactive state such as logically deleted, combined away, pending purge, etc. |
| BEG_EFFECTIVE_DT_TM | DATETIME | Y | The date and time for which this table row becomes effective. Normally, this will be the date and time the row is added, but could be a past or future date and time. |
| CSA_SCHEDULE | VARCHAR(2) | Y | CSA Schedule value to be used for this drug/formuation |
| DRUG_IDENTIFIER | VARCHAR(6) | Y | Multum provided drug identifier which is having CSA customized. Format is d##### |
| END_EFFECTIVE_DT_TM | DATETIME | Y | The date/time after which the row is no longer valid as active current data. This may be valued with the date that the row became inactive. |
| MAIN_MULTUM_DRUG_CODE | DOUBLE | Y | Multum provided indicator that represents a generic trade product.Multum provided indicator that represents a generic trade product. |
| MLTM_CUSTOM_CSA_SCHEDULE_ID | DOUBLE | N | PRIMARY KEY |
| STATE_CD | DOUBLE | Y | Code value from code set 62 which identifies the state the customization is valid for. |
| UPDT_APPLCTX | DOUBLE | Y | The application context number from the record info block. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_CNT | DOUBLE | Y | Set to 0 on insert. Incremented by 1 on update. Used to recognize update conflict where data in a row updated by one application is at risk of being lost by a second application attempting to update the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_DT_TM | DATETIME | Y | The date and time the row was last inserted or updated. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_ID | DOUBLE | Y | The person_id of the person from the personnel table (prsnl) that caused the last insert or update of the row in the table. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |
| UPDT_TASK | DOUBLE | Y | The registered (assigned) task number for the process that inserted or updated the row. The UPDT family of columns are typically used for housekeeping and external system process and should never be depended on for solution specific logic. |