Table Detail Report
CV_DEVICE_LOCATION_REF
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CV DEVICE LOCATION REF |
| Definition: | Stores the Device name which will be mapped to a location for which DBA has access to. |
| Table Type: | REFERENCE |
Column Detail - CV_DEVICE_LOCATION_REF
| 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. |
| CV_DEVICE_LOCATION_REF_ID | DOUBLE | N | PRIMARY KEY |
| DEVICE_NAME | VARCHAR(1000) | N | Name of the Cardiovascular device |
| 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 - CV_DEVICE_LOCATION_REF
| Parent Column in CV_DEVICE_LOCATION_REF (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | CV_DEVICE_LOCATION_REF_ID | CV_DEVICE_LOCATION_R | CV_DEVICE_LOCATION_REF_ID |
CV_DEV_ABSTR_DATA
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CVNet Device Abstract Data |
| Definition: | OMF Summary Table for the CVNet Device Abstract Data |
| Table Type: | ACTIVITY |
Column Detail - CV_DEV_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. |
| DEVICE_ID | DOUBLE | N | This is the primary key identifier to the CV_DEVICE table and serves as a foreign key to the CV_DEV_ABSTR_DATA table. |
| DEV_ABSTR_DATA_ID | DOUBLE | N | This is the primary key identifier to the CV_DEV_ABSTR_DATA table. |
| 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 code that represents the clinical event for the OMF Clinical Report |
| EVENT_ID | DOUBLE | N | Uniquely identifies a logical clinical event row. There may be more than one row with the same event_id, but only one of those rows will be current as indicated by the valid_until_dt_tm field. This is an EVENT_ID value from the CLINICAL_EVENT table. |
| EVENT_TYPE_CD | DOUBLE | N | Event type code defines the group of data this particular event belongs for example Lesion, PTCA, Case, etc. |
| GROUP_TYPE_CD | DOUBLE | N | Related events are grouped based on their nature or location |
| NOMENCLATURE_ID | DOUBLE | N | Stores the identifier (from the nomenclature table) that stores the text for the result. |
| RESULT_CD | DOUBLE | N | This is the coded result. It is used to identify a particular patient response to a clinical event (instead of nomenclature id). |
| RESULT_DT_TM | DATETIME | Y | The date and time that the result_value was set. |
| RESULT_ID | DOUBLE | N | This is the identifier for the result. It depends on the field type, but at the moment we only use it for PERSON_ID when the result_val is a person name. (The usage in the other CV_*_ABSTR_DATA tables). |
| RESULT_SOURCE | VARCHAR(32) | Y | This is the source table for the result. |
| RESULT_VAL | VARCHAR(255) | Y | The value associated with the abstract event |
| 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 - CV_DEV_ABSTR_DATA
| Child Column in CV_DEV_ABSTR_DATA(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | DEVICE_ID | CV_DEVICE | DEVICE_ID |
| NOMENCLATURE_ID | NOMENCLATURE | NOMENCLATURE_ID |
CV_ED_REVIEW
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CV_ED_REVIEW |
| Definition: | Stores information about an ED physician's review of a cardiology order and the cardiologist's subsequent review |
| Table Type: | ACTIVITY |
Column Detail - CV_ED_REVIEW
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CV_ED_REVIEW_ID | DOUBLE | N | Primary key |
| ORDER_ID | DOUBLE | N | Order ID to which the record is associated |
| REQUESTOR_PRSNL_ID | DOUBLE | N | The Provider who requested the review. |
| REQUEST_DT_TM | DATETIME | Y | The date and time when the request was placed. |
| REVIEWER_PRSNL_ID | DOUBLE | N | The Provider who reviewed the request. |
| REVIEW_DT_TM | DATETIME | Y | The date and time when the request was reviewed. |
| REVIEW_STATUS_CD | DOUBLE | N | A code representing the status of tghe review request |
| 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. |
| VALID_UNTIL_DT_TM | DATETIME | Y | Date/Time used for versioning the states of a review request for an order. |
Relationship Detail - CV_ED_REVIEW
| Child Column in CV_ED_REVIEW(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | ORDER_ID | ORDERS | ORDER_ID |
| REQUESTOR_PRSNL_ID | PRSNL | PERSON_ID | |
| REVIEWER_PRSNL_ID | PRSNL | PERSON_ID |
CV_FAILED_TRANSACTION
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | CV FAILED TRANSACTIONS |
| Definition: | Stores the CVNet services Transaction failure information |
| Table Type: | ACTIVITY |
Column Detail - CV_FAILED_TRANSACTION
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| CV_FAILED_TRANSACTION_ID | DOUBLE | N | PRIMARY KEY |
| ORDER_ID | DOUBLE | Y | An Unique ID which identifies the procedure (ORDER) for which the transaction is failed(can be duplicate) |
| TRANSACTION_ACTION | VARCHAR(255) | Y | It signifies the transaction Action or workflow which is invoked when the transaction failed eg:save/sign/match/unlink |
| TRANSACTION_CORRELATION_IDENT | VARCHAR(2000) | Y | It store the correlation id of the transaction which has failed. It is basically a unique id generated for every transaction(optional) requestid |
| TRANSACTION_FAILURE_REASON | VARCHAR(4000) | Y | It stores the failure reason when a transaction fails. Usually the response status message(if any) when transaction fails. |
| TRANSACTION_NAME | VARCHAR(255) | Y | It stores the information about the source where the transaction has failed. Eg. ExamStatusAPI v2reportstatusAPI CCL_script_name |
| TRANSACTION_RETRY_CNT | DOUBLE | Y | Number of retry attempts |
| TRANSACTION_SEQUENCE | DOUBLE | Y | The sequence of the transaction |
| TRANSACTION_SOURCE | VARCHAR(255) | Y | It signifies the transaction source/module from where the transaction has failed Eg- report-inbound CCL |
| TRANSACTION_SUCCESS_IND | DOUBLE | Y | This will capture the status of the transaction. By default it will be 0 indicating failed. Once replay action is success then it will be updated to True/1 |
| 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. |
Relationship Detail - CV_FAILED_TRANSACTION
| Child Column in CV_FAILED_TRANSACTION(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | ORDER_ID | ORDERS | ORDER_ID |
| Parent Column in CV_FAILED_TRANSACTION (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | CV_FAILED_TRANSACTION_ID | CV_FAILED_TRAN_BLOB | CV_FAILED_TRANSACTION_ID |
CV_FAILED_TRAN_BLOB
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Transaction BLOB table |
| Definition: | To store the XML or PDF data saved as Media Object during the Transaction failure. |
| Table Type: | ACTIVITY |
Column Detail - CV_FAILED_TRAN_BLOB
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| BLOB_TYPE_TFLG | VARCHAR(20) | Y | This is a Text Flag field which indicates if the BLOB field contains PDF or XML data stored as a Media Object. during the transaction failure. AKA "Stream_Handle." Valid values are PDF or XML |
| CV_FAILED_TRANSACTION_ID | DOUBLE | N | A Foreign Key value which identifies the Failed Transaction in the CV_FAILED_TRANSACTION table. |
| CV_FAILED_TRAN_BLOB_ID | DOUBLE | N | PRIMARY KEY |
| FAILED_TRAN_BLOB | LONGBLOB | Y | A BLOB field which contains the PDF or XML data Media Object related to the fail |
| 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. |
Relationship Detail - CV_FAILED_TRAN_BLOB
| Child Column in CV_FAILED_TRAN_BLOB(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | CV_FAILED_TRANSACTION_ID | CV_FAILED_TRANSACTION | CV_FAILED_TRANSACTION_ID |