Table Detail Report
PATIENT_EVENT
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Patient Event |
| Definition: | Table to capture event details for a patient_event row |
| Table Type: | ACTIVITY |
Column Detail - PATIENT_EVENT
| 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. |
| 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 | N | 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. |
| ENCNTR_ID | DOUBLE | N | Uniquely identifies the related Encounter |
| EVENT_DT_TM | DATETIME | Y | The date and time the event took place. |
| EVENT_TYPE_CD | DOUBLE | N | Type of event being written. |
| PATIENT_EVENT_ID | DOUBLE | N | Uniquely identifies a captured event for a patient. |
| PERSON_ID | DOUBLE | N | Uniquely identifies a related person. |
| TRANSACTION_DT_TM | DATETIME | Y | The date and time the event was written to the database. |
| 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 - PATIENT_EVENT
| Child Column in PATIENT_EVENT(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | ENCNTR_ID | ENCOUNTER | ENCNTR_ID |
| PERSON_ID | PERSON | PERSON_ID |
| Parent Column in PATIENT_EVENT (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | PATIENT_EVENT_ID | PATIENT_EVENT_DETAIL | PATIENT_EVENT_ID |
| PATIENT_EVENT_DETAIL_HIST | PATIENT_EVENT_ID | ||
| PATIENT_EVENT_HIST | PATIENT_EVENT_ID |
PATIENT_EVENT_DETAIL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Patient Event Detail |
| Definition: | Captures event details for a given Patient_Event row. |
| Table Type: | ACTIVITY |
Column Detail - PATIENT_EVENT_DETAIL
| 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. |
| 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 | N | 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. |
| PATIENT_EVENT_DETAIL_ID | DOUBLE | N | Uniquely identifies details about a patient event. |
| PATIENT_EVENT_ID | DOUBLE | N | Uniquely identifies a related patient event. |
| PE_VALUE_CD | DOUBLE | N | Coded value for the given patient event detail. |
| PE_VALUE_DT_TM | DATETIME | Y | Date and time value for the given patient event detail. |
| PE_VALUE_ID | DOUBLE | N | Uniquely identifies the related row on the table identified in the PE_VALUE_NAME column. |
| PE_VALUE_MEANING | VARCHAR(25) | Y | This meaning will define what value is being saved. This value can be created by whomever is writing the row. When reading from the table, every meaning should only have 1 of the corresponding pe_value columns actually valued. |
| PE_VALUE_NAME | VARCHAR(30) | N | Identifies the table to which this event is related. |
| PE_VALUE_NUMERIC | DOUBLE | Y | Numeric value for the given patient event detail. |
| PE_VALUE_STRING | VARCHAR(4000) | Y | The string value for the given patient event detail. |
| 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 - PATIENT_EVENT_DETAIL
| Child Column in PATIENT_EVENT_DETAIL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PATIENT_EVENT_ID | PATIENT_EVENT | PATIENT_EVENT_ID |
| Parent Column in PATIENT_EVENT_DETAIL (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | PATIENT_EVENT_DETAIL_ID | PATIENT_EVENT_DETAIL_HIST | PATIENT_EVENT_DETAIL_ID |
PATIENT_EVENT_DETAIL_HIST
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Patient Event Detail History |
| Definition: | Used for tracking history of changes to patient event detail. |
| Table Type: | ACTIVITY |
Column Detail - PATIENT_EVENT_DETAIL_HIST
| 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. |
| 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 | N | 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. |
| CHANGE_BIT | DOUBLE | N | Identifies which columns have had a change. |
| PATIENT_EVENT_DETAIL_HIST_ID | DOUBLE | N | Uniquely identifies a history record of a change to the person event detail table. |
| PATIENT_EVENT_DETAIL_ID | DOUBLE | N | Uniquely identifies the related patient_event_detail row. |
| PATIENT_EVENT_ID | DOUBLE | N | Uniquely identifies the related patient event. |
| PE_VALUE_CD | DOUBLE | N | The code value for the given patient event detail. |
| PE_VALUE_DT_TM | DATETIME | Y | The date and time value for the given patient event detail. |
| PE_VALUE_ID | DOUBLE | N | Uniquley identifies the related row on the table identified in the PE_VALUE_NAME column. |
| PE_VALUE_MEANING | VARCHAR(25) | Y | This meaning will define what value is being saved. this value can be created by whomever is writing the row. When reading from the table, every meaning should only have 1 of the corresponding pe_value columns actually valued. |
| PE_VALUE_NAME | VARCHAR(30) | N | Identifies the table to which this event is related. |
| PE_VALUE_NUMERIC | DOUBLE | Y | The numeric value for the given patient event detail. |
| PE_VALUE_STRING | VARCHAR(4000) | Y | The string value for the given patient event detail. |
| PM_HIST_TRACKING_ID | DOUBLE | N | This is the value of the unique primary identifier of the pm_hist_tracking table. It is an internal system assigned number. |
| TRACKING_BIT | DOUBLE | N | Identifies which columns are being tracked for history. |
| TRANSACTION_DT_TM | DATETIME | Y | ** OBSOLETE **. Use column updt_dt_tm for any filtering/ordering query. If transaction date time is needed, it should be retrieved from pm_hist_tracking table. Note that its date may be in the past, as in before the update date time. |
| 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 - PATIENT_EVENT_DETAIL_HIST
| Child Column in PATIENT_EVENT_DETAIL_HIST(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PATIENT_EVENT_ID | PATIENT_EVENT | PATIENT_EVENT_ID |
| PATIENT_EVENT_DETAIL_ID | PATIENT_EVENT_DETAIL | PATIENT_EVENT_DETAIL_ID | |
| PM_HIST_TRACKING_ID | PM_HIST_TRACKING | PM_HIST_TRACKING_ID |
PATIENT_EVENT_HIST
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Patient Event History |
| Definition: | Used for tracking history of changes to patient event. |
| Table Type: | ACTIVITY |
Column Detail - PATIENT_EVENT_HIST
| 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. |
| 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 | N | 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. |
| CHANGE_BIT | DOUBLE | N | Identifies which columns have had a change. |
| EVENT_DT_TM | DATETIME | Y | The date and time the event took place. |
| EVENT_TYPE_CD | DOUBLE | N | Identifies the type of event being written. |
| PATIENT_EVENT_HIST_ID | DOUBLE | N | Uniquely identifies a historical record of a change to the person event table. |
| PATIENT_EVENT_ID | DOUBLE | N | Uniquely identifies the related patient event. |
| PM_HIST_TRACKING_ID | DOUBLE | N | This is the value of the unique primary identifier of the pm_hist_tracking table. It is an internal system assigned number. |
| TRACKING_BIT | DOUBLE | N | Identifies which columns are being tracked for history. |
| TRANSACTION_DT_TM | DATETIME | Y | ** OBSOLETE **. Use column updt_dt_tm for any filtering/ordering query. If transaction date time is needed, it should be retrieved from pm_hist_tracking table. Note that its date may be in the past, as in before the update date time. |
| 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 - PATIENT_EVENT_HIST
| Child Column in PATIENT_EVENT_HIST(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PATIENT_EVENT_ID | PATIENT_EVENT | PATIENT_EVENT_ID |
| PM_HIST_TRACKING_ID | PM_HIST_TRACKING | PM_HIST_TRACKING_ID |
PM_INFO_HIST
| Column Section | Top of Page |
Table-level Detail
| Description: | PM Infomormation History Table |
| Definition: | This is a generic history table that contains history for a few tables. Waitlist letter history and mental health history are included in this table. |
| Table Type: | ACTIVITY |
Column Detail - PM_INFO_HIST
| 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. |
| 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 | N | 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 | 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. |
| C01_CD | DOUBLE | N | Code 01 |
| C02_CD | DOUBLE | N | Code 02 |
| D01_DT_TM | DATETIME | Y | Date and Time 01 |
| D02_DT_TM | DATETIME | Y | Date and Time 02 |
| D03_DT_TM | DATETIME | Y | Date and Time 03 |
| D04_DT_TM | DATETIME | Y | Date and Time 04 |
| DESCRIPTION | VARCHAR(200) | N | textual description |
| 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. |
| HIST_TYPE_CD | DOUBLE | N | Type of History for a given Information Type. |
| INFO_TYPE_CD | DOUBLE | N | Type of History Information, such as Wait List Letter History, etc.. |
| PARENT_ENTITY_ID | DOUBLE | N | Primary key of table defined by the parent_entity_name. |
| PARENT_ENTITY_NAME | VARCHAR(32) | N | Name of the parent table. |
| PM_INFO_HIST_ID | DOUBLE | N | Unique identifier for each pm_info_hist row. Servers as the primary key. |
| T01_TXT | VARCHAR(200) | N | Text 01 |
| 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. |