Table Detail Report
CV_LESION
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CVNet Summary table for storing CVNet OMF Clinical and Management Report data |
| Definition: | Lesion -Stores data that are lesion related. |
| Table Type: | ACTIVITY |
Column Detail - CV_LESION
| 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. |
| ACTIVE_STATUS_CD | DOUBLE | N | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
| ACTIVE_STATUS_DT_TM | DATETIME | Y | The date and time that the active_status_cd was set. |
| ACTIVE_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the active_status_cd to be set or change. |
| 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. |
| DATA_STATUS_CD | DOUBLE | N | Data status indicates a level of authenticity of the row data. Typically this will either be AUTHENTICATED or UNAUTHENTICATED. |
| DATA_STATUS_DT_TM | DATETIME | Y | The date and time that the data_status_cd was set. |
| DATA_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the data_status_cd to be set or change. |
| 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. |
| LESION_ID | DOUBLE | N | This is the unique identifier for a row in the table. |
| NUM_LES_COMPL | DOUBLE | Y | Number of lesion complicationsColumn |
| PARENT_EVENT_ID | DOUBLE | N | The parent Event ID to identify the Devices as belonging to a single deviceColumn |
| PROCEDURE_ID | DOUBLE | N | This is the foreign key . |
| UPDT_APP | DOUBLE | Y | The application number of the process that does the updating |
| 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_REQ | DOUBLE | Y | The request number of the application that update the process . |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - CV_LESION
| Parent Column in CV_LESION (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | LESION_ID | CV_DEVICE | LESION_ID |
| CV_LES_ABSTR_DATA | LESION_ID |
CV_LES_ABSTR_DATA
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CVNet Summary table that stores clinical events for "Omf clinical reports" |
| Definition: | CVNet Summary table that stores clinical events for "Omf clinical reports" |
| Table Type: | ACTIVITY |
Column Detail - CV_LES_ABSTR_DATA
| 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. |
| ACTIVE_STATUS_CD | DOUBLE | N | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
| ACTIVE_STATUS_DT_TM | DATETIME | Y | The date and time that the active_status_cd was set. |
| ACTIVE_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the active_status_cd to be set or change. |
| 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. |
| DATA_STATUS_CD | DOUBLE | N | Data status indicates a level of authenticity of the row data. Typically this will either be AUTHENTICATED or UNAUTHENTICATED. |
| DATA_STATUS_DT_TM | DATETIME | Y | The date and time that the data_status_cd was set. |
| DATA_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the data_status_cd to be set or change. |
| 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. |
| EVENT_CD | DOUBLE | N | Event codes represent clinical events. Used in "CVNet Omf " Clinical reports |
| EVENT_ID | DOUBLE | N | The Event Id Associated with the Clinical EventColumn |
| EVENT_TYPE_CD | DOUBLE | N | Event type code: Describes the type of event e.g. lesionColumn |
| GROUP_TYPE_CD | DOUBLE | N | Group Type Code. Related events are grouped based on their nature or location e.g. Inlab,out of lab |
| LESION_ID | DOUBLE | N | Lesion Id : It is a foreign key to this table. |
| LES_ABSTR_DATA_ID | DOUBLE | N | This is the primary key or unique identifier of a row in the table |
| NOMENCLATURE_ID | DOUBLE | N | This is a foreign key to this table and is the unique identifier to the nomenclature table |
| RESULT_CD | DOUBLE | N | Result Code: This is the coded resultColumn |
| RESULT_DT_TM | DATETIME | Y | The date and time of the result value. The value is in "DATE" format. |
| RESULT_ID | DOUBLE | N | The Result Id for the Lesion Abstract DataColumn |
| RESULT_SOURCE | VARCHAR(32) | Y | The Source table name for the result_idColumn |
| RESULT_VAL | VARCHAR(255) | Y | Result value: This is the value of the clinical eventsColumn |
| UPDT_APP | DOUBLE | Y | The application number that updates a row |
| 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_REQ | DOUBLE | Y | The request number of the application that updates the row |
| UPDT_TASK | DOUBLE | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - CV_LES_ABSTR_DATA
| Child Column in CV_LES_ABSTR_DATA(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | LESION_ID | CV_LESION | LESION_ID |
CV_MED_R
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CV Medication Order relationship |
| Definition: | Relates CV_PROC to ORDER (Pharmacy - Medication Orders) |
| Table Type: | ACTIVITY |
Column Detail - CV_MED_R
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CV_MED_R_ID | DOUBLE | N | PRIMARY KEY |
| CV_PROC_ID | DOUBLE | N | Procedure_ID of the Cardiovascular procedure from CV_PROC table for which a medication order has been placed |
| EVENT_ID | DOUBLE | N | Event_ID for the action performed on the Pharmacy order from CLINICAL_EVENT table. |
| MED_REF_LOG_EVENT_VALUE | DOUBLE | N | Medication Reference Event Value |
| PHARM_ORDER_ID | DOUBLE | N | Order_ID of the pharmacy order from ORDERS table |
| STATUS_TXT | VARCHAR(30) | N | The state indicates the point at which a failure occurred or a successful completion. The possible states: 0 - NOT STARTED 1 - IN PROCESS 2 - ORDER 3 - CLINICAL EVENT 4 - CHARGE 5 - COMPLETED |
| UPDT_APPLCTX | DOUBLE | N | 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 | 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. 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 | N | 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 | 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. 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 | N | 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. |
Relationship Detail - CV_MED_R
| Child Column in CV_MED_R(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | CV_PROC_ID | CV_PROC | CV_PROC_ID |
| PHARM_ORDER_ID | ORDERS | ORDER_ID |
CV_NORMALCY_CLASSIFICATION
| Column Section | Top of Page |
Table-level Detail
| Description: | Normalcy Classification |
| Definition: | Stores the mapping between the ECG Classification Statements and Normalcy Indicator |
| Table Type: | REFERENCE |
Column Detail - CV_NORMALCY_CLASSIFICATION
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | DOUBLE | N | 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. |
| ACTIVITY_SUBTYPE_CD | DOUBLE | N | Used to determine for what modality (Activity sub type) the corresponding interpretation would be used to calculate the normalcy |
| BEG_EFFECTIVE_DT_TM | DATETIME | N | 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. |
| CLASSIFICATION_STATEMENT | VARCHAR(400) | N | System generated/Cardiologist provided interpretation of the study |
| CV_NORMALCY_CLASSIFICATION_ID | DOUBLE | N | Primary Key |
| END_EFFECTIVE_DT_TM | DATETIME | N | 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. |
| NORMALCY_INDICATOR_CD | DOUBLE | N | States whether the result is normal, critical or abnormal. |
| UPDT_APPLCTX | DOUBLE | N | 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 | 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. 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 | N | 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 | 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. 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 | N | 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. |
CV_OMF_INDICATOR
| Column Section | Top of Page |
Table-level Detail
| Description: | Stores CDF_Meaning and Indicator_cd It is a reference table. |
| Definition: | Stores CDF_Meaning and Indicator_cd. |
| Table Type: | REFERENCE |
Column Detail - CV_OMF_INDICATOR
| 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. |
| ACTIVE_STATUS_CD | DOUBLE | N | Indicates the status of the row itself (not the data in the row) such as active, inactive, combined away, pending purge, etc. |
| ACTIVE_STATUS_DT_TM | DATETIME | Y | The date and time that the active_status_cd was set. |
| ACTIVE_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the active_status_cd to be set or change. |
| 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. |
| CDF_MEANING | CHAR(12) | Y | The actual string value for the cdf meaning.Column |
| DATA_STATUS_CD | DOUBLE | N | Data status indicates a level of authenticity of the row data. Typically this will either be AUTHENTICATED or UNAUTHENTICATED. |
| DATA_STATUS_DT_TM | DATETIME | Y | The date and time that the data_status_cd was set. |
| DATA_STATUS_PRSNL_ID | DOUBLE | N | The person who caused the data_status_cd to be set or change. |
| 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. |
| INDICATOR_CD | DOUBLE | N | Indicator's code value. cdf_meaning=INDICATOR, display = "indicator"Column |
| TASK_ASSAY_CD | DOUBLE | N | The task Assay code of the clinical event. There is a cdf_meaning associated with the "task_assay_cd" . This allows the value of an event to be retrieved from the code_value table. |
| 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. |