PEND_ACTION

Description: |
The PEND_ACTION table lists pending admission, transfer, and discharge actions to be taken.

Primary Key

Column Name | Ordinal Position |
--- | --- | ---
PEND_ID | 1 |

Column Information

| Name | Type | Discontinued? |
--- | --- | --- | --- | ---
1 | PEND_ID | VARCHAR | No |
The unique identifier for the pending action record.
2 | PEND_EVENT_TYPE_C_NAME | VARCHAR | No |
The event type for the pending action.
May contain organization-specific values: No
Category Entries:
Admission
Discharge
Transfer
Leave of Absence Out
Leave of Absence Return
Leave of Absence Update Out
Leave of Absence Update Return
3 | PEND_RECRD_TYPE_C_NAME | VARCHAR | No |
The record type for the pending action.
May contain organization-specific values: Yes
Category Entries:
ED Arrival
Hospital Outpatient
4 | IS_DELETED_YN | VARCHAR | No |
Indicates whether the pending action record is inactive or deleted.
May contain organization-specific values: No
Category Entries:
No
Yes
5 | DELETE_TIME | DATETIME (Local) | No |
The date and time the pending action record was deleted.
6 | PAT_ID | VARCHAR | No |
The unique ID of the patient record for this row. This column is frequently used to link to the PATIENT table.
7 | PAT_ENC_CSN_ID | NUMERIC | No |
A unique serial number for the patient contact of the pending action record. This number is unique across all patient contacts in the system.
8 | REQ_GROUPER | NUMERIC | No |
The numeric index used to group pending action records.
9 | START_TIME | DATETIME (Local) | No |
The date and time the pending action is to start.
10 | END_TIME | DATETIME (Local) | No |
The date and time the pending action is to end.
11 | PEND_PRIORITY_C_NAME | VARCHAR | No |
The priority of the pending action.
May contain organization-specific values: No
Category Entries:
Preference
Reserved
Hold
None
12 | PEND_REASON_C_NAME | VARCHAR | No |
The reason for the pending action.
May contain organization-specific values: Yes
No Entries Defined
13 | PEND_CMNT | VARCHAR | No |
The comments for the pending action.
14 | UNIT_ID_EXTERNAL_NAME | VARCHAR | No |
The external name of the department record. This is often used in patient correspondence such as reminder letters.
15 | ROOM_ID_ROOM_NAME | VARCHAR | No |
The name of the Room record.
16 | BED_ID | VARCHAR | No |
The ID of the bed in which the pending action will occur.
17 | BED_ID_BED_LABEL | VARCHAR | No |
The name of the bed.
18 | PAT_SERVICE_C_NAME | VARCHAR | No |
The service of the patient for whom the pending action will occur.
May contain organization-specific values: Yes
19 | LOC_KEY | VARCHAR | No |
The unique key identifying the unit-room-bed of the pending action.
20 | PAT_CLASS_C_NAME | VARCHAR | No |
The patient type of the patient for whom the pending action will occur.
May contain organization-specific values: Yes
21 | PEND_ATND_PROV_ID_PROV_NAME | VARCHAR | No |
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table.
22 | PEND_ATND_DT | DATETIME | No |
The effective date for the attending provider during the pending action.
23 | LVL_OF_CARE_C_NAME | VARCHAR | No |
The level of care for the patient for whom the pending action will occur.
May contain organization-specific values: Yes
24 | ACCOMMODATION_C_NAME | VARCHAR | No |
The accommodation code of the room for the pending action.
May contain organization-specific values: Yes
25 | ACCOM_REASON_C_NAME | VARCHAR | No |
The accommodation reason for the room for the pending action.
May contain organization-specific values: Yes
26 | INCOMING_OK_USR_ID | VARCHAR | No |
The authorizing user for the incoming patient of the pending transfer. This ID may be encrypted.
27 | INCOMING_OK_USR_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
28 | OUTGOING_OK_USR_ID | VARCHAR | No |
The authorizing user for the outgoing patient of the pending transfer. This ID may be encrypted.
29 | OUTGOING_OK_USR_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
30 | DX_ID_DX_NAME | VARCHAR | No |
The name of the diagnosis.
31 | ADM_COND_C_NAME | VARCHAR | No |
The admission condition of the patient for whom the pending action will occur.
May contain organization-specific values: Yes
32 | RES_PROV_ID_PROV_NAME | VARCHAR | No |
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table.
33 | INTERN_PROV_ID_PROV_NAME | VARCHAR | No |
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table.
34 | EXPECT_LEN_OF_STAY | INTEGER | No |
The expected length of stay in days of the pending admission for this patient contact.
35 | EXPECT_DISCHRG_DT | DATETIME | No |
The expected discharge date for the pending discharge of this patient contact.
36 | PEND_DISP_C_NAME | VARCHAR | No |
The disposition for the pending action.
May contain organization-specific values: No
Category Entries:
Release
Keep
Remove
37 | ON_LIST_TIME | DATETIME | No |
The date and time the pending action is good until.
38 | SVC_PRIORITY_C_NAME | VARCHAR | No |
The bed service priority to use when the pending action is completed.
May contain organization-specific values: Yes
39 | ADT_TRANSFER_RSN | VARCHAR | No |
A single line freetext reason for the transfer pending action.
40 | PEND_TRANSFER_TIME | DATETIME (Local) | No |
The date and time of the transfer pending action.
41 | OLD_BED_PRIORITY_C_NAME | VARCHAR | No |
The priority to use for a pending action to the patient's old bed.
The category values for this column were already listed for column: PEND_PRIORITY_C_NAME
42 | PEND_REQ_STATUS_C_NAME | VARCHAR | No |
The pending bed assignment request status for a pending admission or transfer. I.e., 1-Requested, 2-Assigned, 3-Rejected, 4-Approved.
May contain organization-specific values: No
Category Entries:
Ready to Plan
Assigned
Rejected
Approved
Requested
Preassigned
Bed Ready
43 | REQUEST_TIME | DATETIME (Local) | No |
The date and time that the pending bed assignment was requested.
44 | REQ_BY_USR_ID | VARCHAR | No |
The ID of the user requesting the pending bed assignment.
45 | REQ_BY_USR_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
46 | ASSIGNED_TIME | DATETIME (Local) | No |
The date and time that the pending bed assignment was assigned.
47 | REJECTED_TIME | DATETIME (Local) | No |
The date and time that the pending bed assignment was rejected.
48 | APPROVED_TIME | DATETIME (Local) | No |
The date and time that the pending bed assignment was approved.
49 | REQ_STATUS_RSN_C_NAME | VARCHAR | No |
The pending bed assignment request status reason for a pending admission or transfer.
May contain organization-specific values: Yes
50 | TYPE_OF_ROOM_C_NAME | VARCHAR | No |
The type of room category number for the pend record. This is extracted as the category title.
The category values for this column were already listed for column: ACCOMMODATION_C_NAME
51 | ROOM_REASON_C_NAME | VARCHAR | No |
The category number of the reason for the type of room requested for the pend record. This is extracted as the category title.
May contain organization-specific values: Yes
52 | TYPE_OF_BED_C_NAME | VARCHAR | No |
The type of bed category number for the pend record. This is extracted as the category title.
May contain organization-specific values: Yes
53 | BED_REASON_C_NAME | VARCHAR | No |
The category number of the reason for the type of bed requested for the pend record. This is extracted as the category title.
May contain organization-specific values: Yes
54 | CREATED_BY_USER_ID | VARCHAR | No |
The user who created this PND record.
55 | CREATED_BY_USER_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
56 | ADT_PND_ADMITNG_ID_PROV_NAME | VARCHAR | No |
The name of the service provider. This item may be hidden in a public view of the CLARITY_SER table.
57 | ACUITY_C_NAME | VARCHAR | No |
The category number of the acuity level that will be assigned upon confirmation of the pending event record. This is extracted as the category title.
May contain organization-specific values: Yes
58 | COMPLETED_YN | VARCHAR | No |
This item indicates whether the pending event was used to complete an action.
The category values for this column were already listed for column: IS_DELETED_YN
59 | LINKED_EVENT_ID | NUMERIC | No |
This item holds a link to the Admission, Discharge, Transfer, or Leave of Absence (ADT) event that caused the pending event to become deleted.
60 | DELETE_CAUSE_C_NAME | VARCHAR | No |
Indicates the reason that a pending event record is marked as deleted.
May contain organization-specific values: No
Category Entries:
Manually Freed
Event Performed
Encounter Canceled
Encounter Dismissed
Interface
Event Undone
Purged by batch
Order Canceled
Action Canceled
Batch Cancel
Encounter Rescheduled
Surgical Admit Criteria Failed
HOV Admit Criteria Failed
Duplicate Bed Request
Auto Transfer Failed
New Bed Requested
Moved from ED to L&D
Held Bed Canceled
Patient Discharged
Deleted from Transfer Center
61 | EXPECT_DLVR_METH_C_NAME | VARCHAR | No |
This is the expected delivery method for a mother who is going to deliver.
May contain organization-specific values: Yes
Category Entries:
Vaginal, Spontaneous
C-Section, Low Transverse
Vertical C-Section
C-Section, Unspecified
Vaginal, Vacuum (Extractor)
Vaginal, Forceps
Vaginal, Breech
Non-Spontaneous Vaginal Delivery
VBAC, Spontaneous
C-Section, Low Vertical
C-Section, Classical
Biochemical
62 | TRAN_LD_STAT_YN | VARCHAR | No |
Flag to denote if the encounter is for a mother who will deliver
The category values for this column were already listed for column: IS_DELETED_YN
63 | REQUEST_URGENCY_C_NAME | VARCHAR | No |
The urgency for the pending bed assignment. I.e., A-High, B-Medium, or C-Low.
May contain organization-specific values: No
Category Entries:
A-High
B-Medium
C-Low
64 | ADT_ORDER_ID | NUMERIC | No |
Networked to an order ID when the pending event record was created by an order
65 | HOSPITAL_AREA_ID_LOC_NAME | VARCHAR | No |
The name of the revenue location.
66 | LOA_REASON_C_NAME | VARCHAR | No |
The leave of absence reason category ID for the pending event.
May contain organization-specific values: Yes
67 | READ_DTTM | DATETIME (Local) | No |
Instant when the request was first marked as read.
68 | READY_TO_PLAN_DTTM | DATETIME (Local) | No |
Instant when the request status reached Ready to Plan.
69 | PREASSIGNED_DTTM | DATETIME (Local) | No |
Instant when the request status reached Pre-assigned.
70 | BED_READY_DTTM | DATETIME (Local) | No |
Instant when the request status reached Bed Ready.
71 | DELAY_UNTIL_DTTM | DATETIME (Local) | No |
Time when the current delay expires. At that time, this item is cleared.
72 | REQUEST_DIVISION_C_NAME | VARCHAR | No |
This item stores the division for which this request falls, if any. The request division is used to divide bed requests into different groups which can be worked and managed independently.
May contain organization-specific values: Yes
73 | BP_REQ_READY_MOVE_YN | VARCHAR | No |
Is the bed request currently marked ready to move?
The category values for this column were already listed for column: IS_DELETED_YN
74 | BP_REQ_R2M_MANUAL_YN | VARCHAR | No |
Was this bed request marked ready to move set manually?
The category values for this column were already listed for column: IS_DELETED_YN
75 | BP_R2M_DTTM | DATETIME (Local) | No |
Timestamp of the last time this bed request was marked Ready to Move.
76 | BP_R2M_SET_BY_ID | VARCHAR | No |
User who last marked this bed request Ready to Move.
77 | BP_R2M_SET_BY_ID_NAME | VARCHAR | No |
The name of the user record. This name may be hidden.
78 | PROJ_R2M_DATE | DATETIME | No |
Date when we expect the patient to be ready to move.
79 | PROJ_R2M_TM | DATETIME (Local) | No |
Time when we expect the patient to be ready to move.
80 | EVENT_RECORD_ID | VARCHAR | No |
References the event record for use in bed planning notifications
81 | BED_TYPE_C_NAME | VARCHAR | No |
This item tracks the type of bed a patient will need when a transfer is completed.
May contain organization-specific values: Yes
Category Entries:
Empty
Standard
Crib
Telemetry
Bariatric
82 | OFF_SERVICE_YN | VARCHAR | No |
This column tracks if the bed request was completed as off service or off level of care.
The category values for this column were already listed for column: IS_DELETED_YN
83 | CANCEL_REASON_C_NAME | VARCHAR | No |
This holds the reason the user indicated when cancelling a pending event record.
May contain organization-specific values: Yes
Category Entries:
Created in Error
No Longer Necessary
No Longer Happening Today
84 | REJ_REASON_C_NAME | VARCHAR | No |
Stores the reason the bed request was rejected.
May contain organization-specific values: Yes
No Entries Defined