Table Detail Report
EKS_MODULE_AUDIT_TEMP
| Column Section | Top of Page |
Table-level Detail
| Description: | Contains cross-reference of templates used within modules. |
| Definition: | Used to allow reports to easily determine which templates are used within a module. |
| Table Type: | REFERENCE |
Column Detail - EKS_MODULE_AUDIT_TEMP
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| MODULE_NAME | CHAR(30) | N | Name of module template is associated with |
| TEMPLATE_NAME | CHAR(30) | Y | Template name |
| TEMPLATE_NUM | NUMBER | N | Ordinal number of template within module |
| TEMPLATE_TYPE | CHAR(1) | N | type of template (evoke, logic, action, etc.) |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | 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 | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | 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 | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
EKS_NOTIFICATIONS
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | EKS Notifications |
| Definition: | Contains notification messages. |
| Table Type: | ACTIVITY |
Column Detail - EKS_NOTIFICATIONS
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTIVE_IND | NUMBER | 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. |
| BEGIN_ACTIVE_DT_TM | DATE | Y | The date/time when this notification became/becomes active. |
| END_ACTIVE_DT_TM | DATE | Y | The date/time this notification became/becomes inactive |
| EVENT_CLASS_ID | NUMBER | N | Identifies the event class id that describes the notification. |
| NOTIFICATION_ID | NUMBER | N | The id assigned to this notification instance |
| SUBJECT_CD | NUMBER | N | The high level subject's code. If this notification applies to an entity like encounter, person, order, result, etc, the subject cd will be non-zero and the subject_id will be the key into the associated table. |
| SUBJECT_FORMATTED | VC2(100) | Y | The formatted subject text associated with this notification. |
| SUBJECT_ID | NUMBER | N | If used, this field identifies the basic relationship of this notification to a Cerner Database entity. If the notification applies to a person, the subject id will be the key into the person table for this person. If encounter then encounter id, etc. |
| SUBJECT_TABLE | CHAR(30) | Y | The name of the table the subject id relates to. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | 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 | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | 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 | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
| VERSION_MAJOR | NUMBER | Y | The major version of this notification. |
| VERSION_MINOR | NUMBER | Y | Minor version of this notification. |
Relationship Detail - EKS_NOTIFICATIONS
| Parent Column in EKS_NOTIFICATIONS (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | NOTIFICATION_ID | EKS_NOTIFICATION_BLOB_R | NOTIFICATION_ID |
| EKS_NOTIFY_LOC_R | NOTIFICATION_ID | ||
| EKS_NOTIFY_PERSN_R | NOTIFICATION_ID |
EKS_NOTIFICATION_BLOB_R
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Relates a notification to an entry in the LONG_BLOB table |
| Definition: | Relates a notification to an entry in the LONG_BLOB table that contains the raw notification information. |
| Table Type: | ACTIVITY |
Column Detail - EKS_NOTIFICATION_BLOB_R
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| DATA_SEQ | NUMBER | N | multiple records may written to the long blob table, this field denotes the sequence of each blob that comprises the entire notification. |
| LONG_BLOB_ID | NUMBER | N | Identifies the record in the long_blob table that this record relates to. |
| NOTIFICATION_ID | NUMBER | N | Defines which notification this record is related to |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | 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 | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | 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 | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - EKS_NOTIFICATION_BLOB_R
| Child Column in EKS_NOTIFICATION_BLOB_R(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | NOTIFICATION_ID | EKS_NOTIFICATIONS | NOTIFICATION_ID |
| LONG_BLOB_ID | LONG_BLOB | LONG_BLOB_ID |
EKS_NOTIFY_DEST
| Column Section | Top of Page |
Table-level Detail
| Description: | This table holds the tcp/ip:port addresses of discern notify clients |
| Definition: | Holds the tcp/ip:port addresses of discern notify clients interested in messages routed to their specifc locations. |
| Table Type: | ACTIVITY |
Column Detail - EKS_NOTIFY_DEST
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| APP_VERSION_NBR | NUMBER | N | The version of the packed DiscernNotify message structuree to use. |
| LOCATION | VC2(100) | N | The location defined in the registry of the PC interested in receiving notifications. |
| PERSON_ID | NUMBER | Y | This is the value of the unique primary identifier of the person table. It is an internal system assigned number. |
| TCP_IP_ADDR | VC2(100) | N | The TCP/IP address of the location interested in notifications. |
| TCP_IP_PORT | NUMBER | Y | TCP Port that the notification client is listening on. |
| UPDT_APPLCTX | NUMBER | 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 | NUMBER | 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 | DATE | 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 | NUMBER | 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 | NUMBER | 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. |
EKS_NOTIFY_LOC_R
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Relationship table relating notifications to locations. |
| Definition: | Notification to location relationship table |
| Table Type: | ACTIVITY |
Column Detail - EKS_NOTIFY_LOC_R
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| LOCATION | VC2(100) | N | Physical location to deliver the notification to. |
| NOTIFICATION_ID | NUMBER | N | Id of the notification message this location is to receive. |
| READ_IND | NUMBER | Y | Indication of whether the notification has been read. |
| READ_PERSON_ID | NUMBER | N | The person id of the last person to read the notification at this location. It looks like this column is not being used as the only script that updates it always puts a 0 in it. |
| UPDT_APPLCTX | NUMBER | N | The application context number from the record info block. |
| UPDT_CNT | NUMBER | 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 | DATE | N | The date and time the row was last inserted or updated. |
| UPDT_ID | NUMBER | 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 | NUMBER | N | The registered (assigned) task number for the process that inserted or updated the row. |
Relationship Detail - EKS_NOTIFY_LOC_R
| Child Column in EKS_NOTIFY_LOC_R(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | NOTIFICATION_ID | EKS_NOTIFICATIONS | NOTIFICATION_ID |