Table Detail Report
CONTRIBUTING_DEPT
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | CONTRIBUTING DEPT |
Definition: | Contains the departments contributing to a protocol |
Table Type: | REFERENCE |
Column Detail - CONTRIBUTING_DEPT
Column Name | Type | Null? | Definition |
---|---|---|---|
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. |
CONTRIBUTING_DEPT_ID | DOUBLE | N | This is the value of the unique primary identifier of the contributing_dept table. It is an internal system assigned number. |
DEPT_CD | DOUBLE | N | The department contributing to the protocol. Examples of departments are Solid Tumor, Hematology, Immunology etc. |
DEPT_DESC | VARCHAR(255) | Y | The description of the department |
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. |
ORGANIZATION_ID | DOUBLE | N | This is the value of the unique primary identifier of the organization table. It is an internal system assigned number. |
PROT_MASTER_ID | DOUBLE | N | The protocol to which this department contributes. This is the value of the unique primary identifier of the person table. It is an internal system assigned number. |
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 - CONTRIBUTING_DEPT
Child Column in CONTRIBUTING_DEPT(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | ORGANIZATION_ID | ORGANIZATION | ORGANIZATION_ID |
PROT_MASTER_ID | PROT_MASTER | PROT_MASTER_ID |
CT_CUSTOM_FIELD
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Custom Field |
Definition: | This table stores the custom fields created by the user to store additional information about a protocol/amendment. |
Table Type: | REFERENCE |
Column Detail - CT_CUSTOM_FIELD
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. |
CODE_SET | DOUBLE | N | This field contains the code set number that will be used for the field. |
CT_CUSTOM_FIELD_ID | DOUBLE | N | Primary key |
FIELD_KEY | VARCHAR(30) | N | Contains the Field Key data. Uniquely identifies an active row of data. |
FIELD_LABEL | VARCHAR(255) | Y | This field contains text that will be used for the label. |
FIELD_TYPE_CD | DOUBLE | N | This field contains the code that defines the field type. |
LOGICAL_DOMAIN_ID | DOUBLE | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
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 - CT_CUSTOM_FIELD
Child Column in CT_CUSTOM_FIELD(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | LOGICAL_DOMAIN_ID | LOGICAL_DOMAIN | LOGICAL_DOMAIN_ID |
Parent Column in CT_CUSTOM_FIELD (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | CT_CUSTOM_FIELD_ID | CT_PROT_AMD_CUSTOM_FLD_VAL | CT_CUSTOM_FIELD_ID |
CT_CUSTOM_FIELD_GROUP_RELTN
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Custom field group relation |
Definition: | This table stores the relationship between custom fields and groups. |
Table Type: | REFERENCE |
Column Detail - CT_CUSTOM_FIELD_GROUP_RELTN
Column Name | Type | Null? | Definition |
---|---|---|---|
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. |
CT_CUSTOM_FLD_GRP_REL_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. |
FIELD_KEY | VARCHAR(30) | N | Field Key value carried down from parent table. |
GROUP_CD | DOUBLE | N | This field contains a code identifying the group. |
LOGICAL_DOMAIN_ID | DOUBLE | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
PREV_CT_CUSTOM_FLD_GRP_REL_ID | DOUBLE | N | The original value of the ct_custom_field_group_reltn_id used for grouping the related versons. Required for type 2 versioning methodology. |
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 - CT_CUSTOM_FIELD_GROUP_RELTN
Child Column in CT_CUSTOM_FIELD_GROUP_RELTN(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | PREV_CT_CUSTOM_FLD_GRP_REL_ID | CT_CUSTOM_FIELD_GROUP_RELTN | CT_CUSTOM_FLD_GRP_REL_ID |
LOGICAL_DOMAIN_ID | LOGICAL_DOMAIN | LOGICAL_DOMAIN_ID |
Parent Column in CT_CUSTOM_FIELD_GROUP_RELTN (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | CT_CUSTOM_FLD_GRP_REL_ID | CT_CUSTOM_FIELD_GROUP_RELTN | PREV_CT_CUSTOM_FLD_GRP_REL_ID |
CT_DEFAULT_CUSTOM_FIELDS
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | Default custom fields |
Definition: | This table stores the default custom fields of a protocol type. |
Table Type: | REFERENCE |
Column Detail - CT_DEFAULT_CUSTOM_FIELDS
Column Name | Type | Null? | Definition |
---|---|---|---|
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. |
CT_DEFAULT_CUSTOM_FLD_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. |
FIELD_KEY | VARCHAR(30) | N | The unique field identifier for the current version of ct_custom_field row from the CT_CUSTOM_FIELD table. |
FIELD_POSITION | DOUBLE | N | This field contains the default position of the field. |
LOGICAL_DOMAIN_ID | DOUBLE | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
PREV_CT_DEFAULT_CUSTOM_FLD_ID | DOUBLE | N | the original value of the ct_default_custom_field_id used for grouping the related versons. Required for type 2 versioning methodology. |
PROTOCOL_TYPE_CD | DOUBLE | N | This field contains a code identifying the protocol type. |
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 - CT_DEFAULT_CUSTOM_FIELDS
Child Column in CT_DEFAULT_CUSTOM_FIELDS(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | PREV_CT_DEFAULT_CUSTOM_FLD_ID | CT_DEFAULT_CUSTOM_FIELDS | CT_DEFAULT_CUSTOM_FLD_ID |
LOGICAL_DOMAIN_ID | LOGICAL_DOMAIN | LOGICAL_DOMAIN_ID |
Parent Column in CT_DEFAULT_CUSTOM_FIELDS (PK) | Child Table Name | Child Column Name | |
---|---|---|---|
Children: | CT_DEFAULT_CUSTOM_FLD_ID | CT_DEFAULT_CUSTOM_FIELDS | PREV_CT_DEFAULT_CUSTOM_FLD_ID |
CT_DEFAULT_MILESTONES
Column Section | Relationship Section | Top of Page |
Table-level Detail
Description: | CT DEFAULT MILESTONES |
Definition: | This table contains default milestones for protocol, amendment, concept etc.. |
Table Type: | REFERENCE |
Column Detail - CT_DEFAULT_MILESTONES
Column Name | Type | Null? | Definition |
---|---|---|---|
ACTIVITY_CD | DOUBLE | N | The activity related to the milestone. Example: Activated By, Approved By etc. |
COMMITTEE_ID | DOUBLE | N | The committee performing the milestone activity |
CT_DEFAULT_MILESTONES_ID | DOUBLE | N | This is the value of the unique primary identifier of the ct_default_milestones table. It is an internal system assigned number. |
DEFAULT_LIST_TYPE_CD | DOUBLE | N | Indicates that type of milestone. Whether it is a milestone for a protocol, or amendment or concept and so on. |
ENTITY_TYPE_FLAG | DOUBLE | N | Used to identify whether an Organization or Committee or role performed the activity. |
LOGICAL_DOMAIN_ID | DOUBLE | N | The unique identifier for a logical domain. This identifier allows the data to be grouped by logical domain. For example, If you assign clients a logical_domain_id this would allow you to store data for multiple clients on this table. |
ORGANIZATION_ID | DOUBLE | N | The Organization that performed the activity. This is the value of the unique primary identifier of the organization table. It is an internal system assigned number. |
PROT_ROLE_CD | DOUBLE | N | Identifies the role performing the activity |
SEQUENCE_NBR | DOUBLE | N | The number of the milestone |
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 - CT_DEFAULT_MILESTONES
Child Column in CT_DEFAULT_MILESTONES(FK) | Parent Table Name | Parent Column Name | |
---|---|---|---|
Parents: | COMMITTEE_ID | COMMITTEE | COMMITTEE_ID |
LOGICAL_DOMAIN_ID | LOGICAL_DOMAIN | LOGICAL_DOMAIN_ID | |
ORGANIZATION_ID | ORGANIZATION | ORGANIZATION_ID |