Table Detail Report
AP_FOLDER_PROXY
Column Section | Top of Page |
Table-level Detail
Description: | ap_folder_proxy |
Definition: | This table contains all of the user and their given permissions pertaining to anatomic pathology folders. |
Table Type: | ACTIVITY |
Column Detail - AP_FOLDER_PROXY
Column Name | Type | Null? | Definition |
---|---|---|---|
CONTACT_IND | DOUBLE | Y | This field identifies whether or not the given user should be used as a point of reference for the given folder. For example, if a user has a question about the purpose of the folder they would contact the person labeled a "contact". |
FOLDER_ID | DOUBLE | N | This field contains the foreign key value used to join to the ap_folder table. |
PARENT_ENTITY_ID | DOUBLE | N | The value of the primary identifier of the table to which the 'ap_folder_proxy' row is related. |
PARENT_ENTITY_NAME | VARCHAR(32) | N | The upper case name of the table to which this 'ap_folder_proxy' row is related. At this point valid values are PRSNL_GROUP and PRSNL. |
PERMISSION_BITMAP | DOUBLE | Y | This field contains the permission values for a given user or group of users. |
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. |
AP_FOLDER_ROLE
Column Section | Top of Page |
Table-level Detail
Description: | ap_folder_role |
Definition: | This table contains a listing of folder roles. Specific permissions can be attributed to given roles. In addition, users can be assigned a role, thus dictating the permissions they will have on given folders. |
Table Type: | ACTIVITY |
Column Detail - AP_FOLDER_ROLE
Column Name | Type | Null? | Definition |
---|---|---|---|
PERMISSION_BITMAP | DOUBLE | Y | This field contains the "Default" permission values used when adding new 'proxy privileges'. |
ROLE_ID | DOUBLE | N | This field contains the unique identifier for this table. |
ROLE_NAME | VARCHAR(40) | Y | This field contains the display name for a folder role. |
ROLE_NAME_KEY | VARCHAR(40) | N | This field contains the role_name value with all special characters removed and all alpha characters converted to upper case. |
ROLE_NAME_KEY_A_NLS | VARCHAR(160) | Y | ROLE_NAME_KEY_A_NLS column |
ROLE_NAME_KEY_NLS | VARCHAR(82) | Y | This field was added for internationalization purposes. |
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. |
AP_FT_EVENT
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | AP Followup Tracking Event |
Definition: | This activity table contains parameters associated with a follow-up tracking event. Follow-up activities are triggered by the verification of a cytology report. The event created is determined by the alpha response diagnosis value assigned to the report. |
Table Type: | ACTIVITY |
Column Detail - AP_FT_EVENT
Column Name | Type | Null? | Definition |
---|---|---|---|
CASE_ID | DOUBLE | N | This field contains the foreign key value used to join to case information stored on the PATHOLOGY_CASE activity table. |
EXPECTED_TERM_DT | DATETIME | Y | This field contains the expected termination date for the follow-up tracking event. This date is calculated based on the report diagnosis alpha response value, and indicates the date the event is scheduled to be deleted from the table. |
FINAL_OVERDUE_DT_TM | DATETIME | Y | This field contains the scheduled final overdue notification date for the follow-up event. This date is calculated based on the report diagnosis alpha value, and indicates the date the event is scheduled to print on the final overdue report. |
FINAL_OVERDUE_PRINT_FLAG | DOUBLE | Y | This field contains a numeric flag value indicating whether or not the follow-up tracking event has been included (printed) on a final overdue report. |
FIRST_OVERDUE_DT_TM | DATETIME | Y | This field contains the scheduled initial overdue notification date for the follow-up event. This date is calculated based on the report diagnosis alpha value, and indicates the date the event is scheduled to print on the initial overdue report. |
FIRST_OVERDUE_PRINT_FLAG | DOUBLE | Y | This field contains a numeric flag value indicating whether or not the follow-up tracking event has been included (printed) on an initial overdue report. |
FOLLOWUP_EVENT_ID | DOUBLE | N | This field uniquely defines a row included on the AP_FT_EVENT table. This field would be used to join to other tables (as a foreign key) such as the FT_TERM_CANDIDATE_LIST activity table. |
FOLLOWUP_TYPE_CD | DOUBLE | N | This field contains the foreign key value used to join to the follow-up tracking type codeset (codeset 1317). |
INITIAL_NOTIF_DT_TM | DATETIME | Y | This field contains the scheduled initial notification date for the follow-up event. This date is calculated based on the report diagnosis alpha response value, and indicates the date the event is scheduled to print on the follow-up notification report. |
INITIAL_NOTIF_PRINT_FLAG | DOUBLE | Y | This field contains a numeric flag value indicating whether or not the follow-up tracking event has been included (printed) on an initial notification report. |
ORIGIN_DT_TM | DATETIME | Y | This field contains the date and time the follow-up tracking event record was added to this table. |
ORIGIN_FLAG | DOUBLE | Y | This field contains a numeric flag value indicating how the follow-up tracking event record was added to this table. Fields can be added by the system (automatically based the verification of a cytology report) or manually (entered by a user). |
ORIGIN_PRSNL_ID | DOUBLE | N | If the event record was manually added to the table, this field contains the user's internal ID value. This value could be used to join to personnel information on the PRSNL or PERSON tables. If the record was system-added, the field includes a zero. |
PERSON_ID | DOUBLE | N | This is the value of the unique primary identifier of the person table. It is an internal system assigned number. |
TERM_ACCESSION_NBR | CHAR(21) | Y | This field contains the terminating case number entered by the user or system when the follow-up tracking event was updated to a terminated status. |
TERM_COMMENT | VARCHAR(100) | Y | This field is no longer used. Refer to the term_long_text_id for comment information. |
TERM_DT_TM | DATETIME | Y | If the follow-up tracking event was terminated, this field contains the date and time the follow-up tracking event was updated to a terminated status. |
TERM_ID | DOUBLE | N | If the event record was manually terminated, this field contains the user's internal ID value. This value could be used to join to personnel information on the PRSNL or PERSON tables. If the record was system-terminated, the field includes a zero. |
TERM_LONG_TEXT_ID | DOUBLE | N | This field contains the value representing the entry on the LONG_TEXT table that contains the termination comment. |
TERM_REASON_CD | DOUBLE | N | If the follow-up tracking event was terminated, this field contains the termination reason code ID value. Termination reason codes are stored on codeset 1313. |
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 - AP_FT_EVENT
Child Column in AP_FT_EVENT(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | FOLLOWUP_TYPE_CD | AP_FT_TYPE | FOLLOWUP_TRACKING_TYPE_CD |
TERM_LONG_TEXT_ID | LONG_TEXT | LONG_TEXT_ID | |
CASE_ID | PATHOLOGY_CASE | CASE_ID | |
PERSON_ID | PERSON | PERSON_ID | |
ORIGIN_PRSNL_ID | PRSNL | PERSON_ID | |
TERM_ID | PRSNL | PERSON_ID |
Parent Column in AP_FT_EVENT (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | FOLLOWUP_EVENT_ID | FT_TERM_CANDIDATE_LIST | FOLLOWUP_EVENT_ID |
AP_FT_REPORT_PROC
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | AP Followup Tracking Report Procedure |
Definition: | This reference table contains the report component procedures (discrete tasks) that are associated with a follow-up tracking type. The results of these procedures appear with the patient-specific data on follow-up tracking reports. |
Table Type: | REFERENCE |
Column Detail - AP_FT_REPORT_PROC
Column Name | Type | Null? | Definition |
---|---|---|---|
FOLLOWUP_TRACKING_TYPE_CD | DOUBLE | N | This field contains the reference to the follow-up tracking type for which report component procedures are assigned. This field contains the foreign key value used to join to follow-up tracking type information stored on the AP_FT_TYPE reference table. |
TASK_ASSAY_CD | DOUBLE | N | This field contains the reference to the report component procedures (discrete tasks) which are assigned to the follow-up tracking type identified in the FOLLOW-UP TRACKING_TYPE_CD field. |
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 - AP_FT_REPORT_PROC
Child Column in AP_FT_REPORT_PROC(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | FOLLOWUP_TRACKING_TYPE_CD | AP_FT_TYPE | FOLLOWUP_TRACKING_TYPE_CD |
TASK_ASSAY_CD | DISCRETE_TASK_ASSAY | TASK_ASSAY_CD |
AP_FT_TERM_PROC
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | AP Followup Tracking Termination Procedure |
Definition: | This reference table contains the report order catalog items that will cause a previously-initiated follow-up tracking event for a patient to be terminated. The termination action is triggered based on the verification of one of these reports. |
Table Type: | REFERENCE |
Column Detail - AP_FT_TERM_PROC
Column Name | Type | Null? | Definition |
---|---|---|---|
AUTO_TERMINATION_IND | DOUBLE | Y | This field contains a flag value indicating whether or not the associated report order catalog item will cause an existing follow-up tracking event for a patient to be terminated when the report order catalog item is verified. |
AUTO_TERMINATION_REASON_CD | DOUBLE | N | If the termination report order catalog item is flagged to cause automatic (versus manual) termination, this field identifies the termination reason code value (from codeset 1313) to be assigned as the termination reason for the follow-up tracking event. |
CATALOG_CD | DOUBLE | N | This field contains the reference to the order catalog report procedures associated with the follow-up tracking type. The verification of one of these reports causes any active follow-up tracking event for the patient to be evaluated for termination. |
FOLLOWUP_TRACKING_TYPE_CD | DOUBLE | N | This field contains the reference to the follow-up tracking type for which termination report order catalog items are assigned. This field contains the foreign key value used to join to follow-up type information stored on the AP_FT_TYPE reference table. |
LOOK_BACK_DAYS | DOUBLE | Y | This field contains the number of days that the system will look back to determine the presence of a termination report order catalog item. The report causing a follow-up event to be terminated may be verified before the follow-up event is initiated. |
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 - AP_FT_TERM_PROC
Child Column in AP_FT_TERM_PROC(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | FOLLOWUP_TRACKING_TYPE_CD | AP_FT_TYPE | FOLLOWUP_TRACKING_TYPE_CD |
CATALOG_CD | ORDER_CATALOG | CATALOG_CD |