CLINICAL_EVENT_SEC_LBL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Clinical Event Security Label |
| Definition: | Storage for security attributes associated to millennium data entities. |
| Table Type: | ACTIVITY |
Column Detail - CLINICAL_EVENT_SEC_LBL
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_PRSNL_ID | DOUBLE | Y | The ID of the personnel who has taken an action (modified, deleted, etc.) this label. |
| 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. |
| 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. |
| CLINICAL_EVENT_SEC_LBL_ID | DOUBLE | N | System generated number used to uniquely identify a row on the CLINICAL_EVENT_SEC_LBL table. |
| CREATED_BY_PRSNL_ID | DOUBLE | Y | The ID of the personnel who associated this label with the data entity. |
| 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_ID | DOUBLE | Y | Identifies a unique event on the CLINICAL_EVENT table. |
| SENSITIVITY_REASON_CD | DOUBLE | Y | The code value indicating why the tagged data is considered sesitive. |
| 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 - CLINICAL_EVENT_SEC_LBL
| Child Column in CLINICAL_EVENT_SEC_LBL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | CREATED_BY_PRSNL_ID | PRSNL | PERSON_ID |
DIAGNOSIS_SEC_LBL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Diagnosis Security Label |
| Definition: | Storage for security attributes associated to millennium data entities. |
| Table Type: | ACTIVITY |
Column Detail - DIAGNOSIS_SEC_LBL
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_PRSNL_ID | DOUBLE | Y | The ID of the personnel who has taken an action (modified, deleted, etc.) this label. |
| 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. |
| 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. |
| CREATED_BY_PRSNL_ID | DOUBLE | Y | The ID of the personnel who associated this label with the data entity. |
| DIAGNOSIS_GROUP_ID | DOUBLE | Y | The ID of the data entity that this security attribute is associated with. |
| DIAGNOSIS_SEC_LBL_ID | DOUBLE | N | A system generated number to uniquely identify a row on the Diagnosis Security Label Identifier 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. |
| SENSITIVITY_REASON_CD | DOUBLE | Y | The code value indicating why the tagged data is considered sensitive. |
| 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 - DIAGNOSIS_SEC_LBL
| Child Column in DIAGNOSIS_SEC_LBL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | DIAGNOSIS_GROUP_ID | DIAGNOSIS | DIAGNOSIS_ID |
| CREATED_BY_PRSNL_ID | PRSNL | PERSON_ID |
ORDER_CONFID_LBL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Order Confidentiality Label |
| Definition: | Stores confidentiality information for each order. |
| Table Type: | ACTIVITY |
Column Detail - ORDER_CONFID_LBL
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_PRSNL_ID | DOUBLE | Y | The ID of the person who took the last action on this confidentiality label. |
| 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. |
| 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. |
| CONFID_LBL_CD | DOUBLE | Y | The code value indicating why the tagged data is considered confidential. Values should be taken from the SENSITIVITY_REASON Code Set (4702082) and ORDERS_SENSITIVITY_REASON (4740922). This column will support other code sets in the future. |
| CREATED_BY_PRSNL_ID | DOUBLE | Y | The ID of the person who created this confidentiality label. |
| 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. |
| ORDER_CONFID_LBL_ID | DOUBLE | N | Unique generated number that identifies a single row on the ORDER_CONFID_LBL table. |
| ORDER_ID | DOUBLE | Y | The ID of the order the confidentiality labels are applied to. |
| 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 | 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 | 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 - ORDER_CONFID_LBL
| Child Column in ORDER_CONFID_LBL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | ORDER_ID | ORDERS | ORDER_ID |
| ACTION_PRSNL_ID | PRSNL | PERSON_ID | |
| CREATED_BY_PRSNL_ID | PRSNL | PERSON_ID |
ORDER_PROPOSAL_CONFID_LBL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Order Proposal Confidentiality Label |
| Definition: | Stores confidentiality information for each order proposal. |
| Table Type: | ACTIVITY |
Column Detail - ORDER_PROPOSAL_CONFID_LBL
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_PRSNL_ID | DOUBLE | Y | The ID of the person who took the last action on this confidentiality label. |
| 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. |
| 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. |
| CONFID_LBL_CD | DOUBLE | Y | The code value indicating why the tagged data is considered confidential. Values should be taken from the SENSITIVITY_REASON Code Set (4702082) and ORDERS_SENSITIVITY_REASON (4740922). This column will support other code sets in the future. |
| CREATED_BY_PRSNL_ID | DOUBLE | Y | The ID of the person who created this confidentiality label. |
| 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. |
| ORDER_PROPOSAL_CONFID_LBL_ID | DOUBLE | N | System generated number to uniquely identify a row on the ORDER_PROPOSAL_CONFID_LBL table. |
| ORDER_PROPOSAL_ID | DOUBLE | Y | Uniquely identifies the related order proposal. |
| 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 - ORDER_PROPOSAL_CONFID_LBL
| Child Column in ORDER_PROPOSAL_CONFID_LBL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | ORDER_PROPOSAL_ID | ORDER_PROPOSAL | ORDER_PROPOSAL_ID |
| ACTION_PRSNL_ID | PRSNL | PERSON_ID | |
| CREATED_BY_PRSNL_ID | PRSNL | PERSON_ID |
PREGNANCY_SEC_LBL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | PREGANCY SECURITY LABEL |
| Definition: | Storage for security attributes associated to millennium data entities related to Womens Health |
| Table Type: | ACTIVITY |
Column Detail - PREGNANCY_SEC_LBL
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_PRSNL_ID | DOUBLE | Y | The ID of the personnel who has taken an action (modified, deleted, etc) this label. |
| 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. |
| 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. |
| CREATED_BY_PRSNL_ID | DOUBLE | Y | The ID of the personnel who associated this label with the data entity. |
| 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. |
| PREGNANCY_ID | DOUBLE | Y | The ID of the data entity that this security attribute (PREGNANCY INSTANCE) is associated with. |
| PREGNANCY_SEC_LBL_ID | DOUBLE | N | PRIMARY KEY |
| SENSITIVITY_REASON_CD | DOUBLE | Y | The code value indicating why the tagged data is considered sensitive. |
| 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 - PREGNANCY_SEC_LBL
| Child Column in PREGNANCY_SEC_LBL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PREGNANCY_ID | PREGNANCY_INSTANCE | PREGNANCY_INSTANCE_ID |
| ACTION_PRSNL_ID | PRSNL | PERSON_ID | |
| CREATED_BY_PRSNL_ID | PRSNL | PERSON_ID |