Table Detail Report
PERSON_DATA_NOT_COLL_HIST
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Person Data Not Collected History |
| Definition: | Stores history of the rows from person_data_not_coll. |
| Table Type: | ACTIVITY |
Column Detail - PERSON_DATA_NOT_COLL_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. |
| BIOMETRIC_IDENT_CD | DOUBLE | N | Contains the information describing if the biometric identifier is not collected or why it is not collected for the person |
| CHANGE_BIT | DOUBLE | N | Identifies which columns have had a change. |
| DRIVERS_LICENSE_CD | DOUBLE | N | The information describing if the driver¿s license is not collected or why it is not collected for the person. |
| HOME_ADDRESS_CD | DOUBLE | N | Information describing if the home address has not been collected or why the home address has not been collected for the person. |
| HOME_EMAIL_CD | DOUBLE | N | Information describing if the home email address has not been collected or why the home email address has not been collected for the person |
| NATIONAL_HEALTH_NBR_CD | DOUBLE | N | The information describing if the national health identification number (NHIN) is not collected or why it is not collected for the person |
| PERSON_DATA_NOT_COLL_HIST_ID | DOUBLE | N | Uniquely identifies historical information about data that has not been collected for a person. |
| PERSON_DATA_NOT_COLL_ID | DOUBLE | N | Uniquely identifies information about why certain person data like SSN, Phone Number, Home Address, etc. has not been collected |
| PHONE_CD | DOUBLE | N | Information describing if the phone number has not been collected or why the phone number has not been collected for the person |
| 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. |
| PRIMARY_CARE_PHYSICIAN_CD | DOUBLE | N | The information describing if the primary care provider is not collected or why it is not collected for the person |
| SSN_CD | DOUBLE | N | Information describing if the SSN has not been collected or why the SSN has not been collected for the person |
| 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 - PERSON_DATA_NOT_COLL_HIST
| Child Column in PERSON_DATA_NOT_COLL_HIST(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PM_HIST_TRACKING_ID | PM_HIST_TRACKING | PM_HIST_TRACKING_ID |
PERSON_DESIGNATION
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Person Designation |
| Definition: | Stores Information specific to person designations |
| Table Type: | ACTIVITY |
Column Detail - PERSON_DESIGNATION
| 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_ISO | VARCHAR(10) | Y | The begin effective date "as entered" during registration. The date 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. It will be formatted as an ISO 8601 string. |
| END_EFFECTIVE_DT_ISO | VARCHAR(10) | Y | The end effective date "as entered" during registration. The date after which the row is no longer valid as active current data. This may be valued with the date that the row became inactive. It will be formatted as an ISO 8601 string. |
| PERSON_DESIGNATION_ID | DOUBLE | N | Unique generated number that identifies a single row on the PERSON_DESIGNATION table. |
| PERSON_ID | DOUBLE | N | This is the value of the unique primary identifier of the person table. It is an internal system assigned number. |
| TYPE_CD | DOUBLE | N | Indicates the type of person designation. |
| TYPE_CLASS_CD | DOUBLE | N | Designation type class is used to categorize person designations into more general groups than designation type. The values in this codeset all have Cerner defined meanings. |
| 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 - PERSON_DESIGNATION
| Child Column in PERSON_DESIGNATION(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PERSON_ID | PERSON | PERSON_ID |
| Parent Column in PERSON_DESIGNATION (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | PERSON_DESIGNATION_ID | PERSON_DESIGNATION_HIST | PERSON_DESIGNATION_ID |
PERSON_DESIGNATION_HIST
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Person Designation History |
| Definition: | Used for tracking changes to the person_designation table. |
| Table Type: | ACTIVITY |
Column Detail - PERSON_DESIGNATION_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_ISO | VARCHAR(10) | Y | The begin effective date "as entered" during registration. The date 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. It will be formatted as an ISO 8601 string. |
| CHANGE_BIT | DOUBLE | N | Identifies which columns have had a change. |
| END_EFFECTIVE_DT_ISO | VARCHAR(10) | Y | The end effective date "as entered" during registration. The date after which the row is no longer valid as active current data. This may be valued with the date that the row became inactive. It will be formatted as an ISO 8601 string. |
| PERSON_DESIGNATION_HIST_ID | DOUBLE | N | Unique generated number that identifies a single row on the PERSON_DESIGNATION_HIST table. |
| PERSON_DESIGNATION_ID | DOUBLE | N | Unique generated number that identifies a single row on the PERSON_DESIGNATION table. |
| 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. |
| TYPE_CD | DOUBLE | N | Indicates the type of person designation. |
| TYPE_CLASS_CD | DOUBLE | N | Designation type class is used to categorize person designations into more general groups than designation type. The values in this codeset all have Cerner defined meanings. |
| 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 - PERSON_DESIGNATION_HIST
| Child Column in PERSON_DESIGNATION_HIST(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PERSON_DESIGNATION_ID | PERSON_DESIGNATION | PERSON_DESIGNATION_ID |
| PM_HIST_TRACKING_ID | PM_HIST_TRACKING | PM_HIST_TRACKING_ID |
PERSON_DISMISSAL
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Person Dismissal |
| Definition: | The person dismissal table contains information about a person dismissal including the entity from which the person is being or has been dismissed and any reinstatement information. |
| Table Type: | ACTIVITY |
Column Detail - PERSON_DISMISSAL
| 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. |
| DISMISS_DT_TM | DATETIME | Y | The date that the patient was dismissed from the location or provider. |
| LOCATION_CD | DOUBLE | N | The location from which the patient is being or has been dismissed. This should be no lower in the location hierarchy than the ambulatory/nurse unit level. |
| PERSON_DISMISSAL_ID | DOUBLE | N | Uniquely identifies information about a person dismissal including the entity from which the person is being or has been dismissed and any reinstatement information. |
| PERSON_ID | DOUBLE | N | Uniquely identifies the person that is being or has been dismissed. |
| PRSNL_PERSON_ID | DOUBLE | N | Uniquely identifies the provider from which the patient is being or has been dismissed. |
| REINSTATE_DT_TM | DATETIME | Y | The date that the patient was reinstated from the dismissal. |
| 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 - PERSON_DISMISSAL
| Child Column in PERSON_DISMISSAL(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | LOCATION_CD | LOCATION | LOCATION_CD |
| PERSON_ID | PERSON | PERSON_ID | |
| PRSNL_PERSON_ID | PRSNL | PERSON_ID |
| Parent Column in PERSON_DISMISSAL (PK) | Child Table Name | Child Column Name | |
|---|---|---|---|
| Children: | PERSON_DISMISSAL_ID | PERSON_DISMISSAL_ACTN | PERSON_DISMISSAL_ID |
PERSON_DISMISSAL_ACTN
| Column Section | Relationship Section | Top of Page |
Table-level Detail
| Description: | Person Dismissal Action |
| Definition: | The person dismissal table contains information about each action taken as part of a patient dismissal. |
| Table Type: | ACTIVITY |
Column Detail - PERSON_DISMISSAL_ACTN
| Column Name | Type | Null? | Definition |
|---|---|---|---|
| ACTION_TYPE_CD | DOUBLE | N | The type of action taken on the dismissal. |
| 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. |
| NOTIFY_DT_TM | DATETIME | Y | The date and time the patient was notified of their impending dismissal via the notification action type. |
| PERSON_DISMISSAL_ACTN_ID | DOUBLE | N | Uniquely identifies a dismissal action. |
| PERSON_DISMISSAL_ID | DOUBLE | N | Uniquely identifies the person_dismissal to which the action was associated. |
| REASON_CD | DOUBLE | N | The reason for the patient being dismissed at the time of the action. |
| 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 - PERSON_DISMISSAL_ACTN
| Child Column in PERSON_DISMISSAL_ACTN(FK) | Parent Table Name | Parent Column Name | |
|---|---|---|---|
| Parents: | PERSON_DISMISSAL_ID | PERSON_DISMISSAL | PERSON_DISMISSAL_ID |