HL_REQ_INFO

Description: |
Hospital Logistics Requests Information.

Primary Key

Column Name | Ordinal Position |
--- | --- | ---
HLR_ID | 1 |

Column Information

| Name | Type | Discontinued? |
--- | --- | --- | --- | ---
1 | HLR_ID | NUMERIC | No |
The unique identifier for the request record.
2 | HLR_NAME | VARCHAR | No |
Record name
3 | HLR_TYPE_C_NAME | VARCHAR | No |
The Hospital Logistics Request type.
May contain organization-specific values: No
Category Entries:
Request
Group
Job
4 | REQ_TEMPLATE_TASK_ID | NUMERIC | No |
The Logistics Task Template this Request is linked to. This Task defines the meaning of this Request and provides configuration info for the Request.
5 | REQ_TEMPLATE_TASK_ID_TASK_NAME | VARCHAR | No |
The name of the task.
6 | REQ_START_UTC_DTTM | DATETIME (UTC) | No |
This Logistics Request's UTC start instant.
7 | REQ_PRIORITY_C_NAME | VARCHAR | No |
This Logistics Request's priority.
May contain organization-specific values: No
Category Entries:
Stat
High
Normal
Low
8 | REQ_START_PLF_ID_RECORD_NAME | VARCHAR | No |
The name of the PLF record.
9 | REQ_DYNAMIC_START_TYPE_C_NAME | VARCHAR | No |
This Logistics Request's dynamic start location type. This indicates what changes (like updates to the patient's bed or current location) will update the Request's start location.
May contain organization-specific values: No
Category Entries:
Specified Location
Current Location
Current Bed
Preassignment
Procedure Room
10 | REQ_END_PLF_ID_RECORD_NAME | VARCHAR | No |
The name of the PLF record.
11 | REQ_DYNAMIC_END_TYPE_C_NAME | VARCHAR | No |
This Logistics Request's dynamic end location type. This indicates what changes (like updates to the patient's bed) will update the Request's end location.
The category values for this column were already listed for column: REQ_DYNAMIC_START_TYPE_C_NAME
12 | REQ_TECHS_NUM | INTEGER | No |
The number of Logistics Technicians required to work on this Logistics Request.
13 | REQ_MODE_C_NAME | VARCHAR | No |
This Logistics Request's mode. Technicians need to use this mode to complete this Request.
May contain organization-specific values: Yes
14 | REQ_STATUS_C_NAME | VARCHAR | No |
The current status of this Logistics Request.
May contain organization-specific values: No
Category Entries:
Unplanned
Planned
Assigned
Acknowledged
At Start Location
In Progress
At End Location
Completed
Canceled
Skipped
15 | REQ_CANCEL_RSN_C_NAME | VARCHAR | No |
When this Logistics Request or Job's status (I HLR 160) is Canceled or Skipped, this item contains the cancel or skip reason.
May contain organization-specific values: Yes
Category Entries:
Automatically Canceled (Default)
Linked Appointment Canceled
Linked Admission PND Canceled
Linked Discharge PND Canceled
Linked Transfer PND Canceled
Linked LOA Out PND Canceled
Linked LOA Return PND Canceled
Planned Break Canceled
Reducing Required Technicians
Canceled By Utility
Linked Transport Request Canceled
Linked ADT Event Canceled
Maintenance Clean Replaced By Bed Clean
Linked Bed Clean Canceled (Room Clean)
Linked Appointment Time Changed
Canceled by Contact Move
Linked Appointment Department Changed
Linking To Adjacent Appointment In Department
Linked Appointment Patient No Show
Linked Appointment Patient Left Without Being Seen
Technician No Longer Needed
Linked Procedural Preassignment Canceled
Linked Case Tracking Event Canceled
16 | REQ_START_APPT_PAT_ENC_CSN_ID | NUMERIC | No |
The contact serial number (CSN) of the appointment that this Logistics Request is going to.
17 | REQ_END_APPT_PAT_ENC_CSN_ID | NUMERIC | No |
The contact serial number (CSN) of the appointment this Logistics Request is coming from.
18 | REQ_ADMISSION_PAT_ENC_CSN_ID | NUMERIC | No |
The contact serial number (CSN) of the admission this Logistics Request is associated with.
19 | REQ_PEND_ID | VARCHAR | No |
The Pending Event linked to this Logistics Request.
20 | REQ_EVENT_ID | NUMERIC | No |
The event linked to this Logistics Request.
21 | REQ_FIRST_STAGE_HLR_ID | NUMERIC | No |
The Logistics Request that serves as the first stage of this Multi-Stage Request.
22 | REQ_NEXT_STAGE_HLR_ID | NUMERIC | No |
The Logistics Request that serves as the next stage of this Multi-Stage Request.
23 | REQ_STAGE_NUM | INTEGER | No |
The stage number for this Logistics Request.
24 | REQ_IS_CONCURRENT_STAGE_YN | VARCHAR | No |
Indicates if this Logistics Request can be worked on concurrently with the previous stage.
May contain organization-specific values: No
Category Entries:
No
Yes
25 | REQ_REGION_SEC_ID | NUMERIC | No |
The Logistics Region that this Logistics Request belongs to.
26 | REQ_REGION_SEC_ID_RECORD_NAME | VARCHAR | No |
The name of this cleaning sector.
27 | REQ_SECTOR_SEC_ID | NUMERIC | No |
The Logistics Sector that this Logistics Request belongs to.
28 | REQ_SECTOR_SEC_ID_RECORD_NAME | VARCHAR | No |
The name of this cleaning sector.
29 | REQ_DEPARTMENT_ID_EXTERNAL_NAME | VARCHAR | No |
The external name of the department record. This is often used in patient correspondence such as reminder letters.
30 | REQ_HOSP_LOC_ID_LOC_NAME | VARCHAR | No |
The name of the revenue location.
31 | REQ_SERV_AREA_ID_LOC_NAME | VARCHAR | No |
The name of the revenue location.
32 | REQ_CREATION_SOURCE_C_NAME | VARCHAR | No |
Indicates whether this Logistics Request was created manually or automatically, and if created automatically, which automatic process created the Request.
May contain organization-specific values: No
Category Entries:
Manual
Automatic - Appointment
Automatic - Ready To Move
Automatic - Scheduled TSK
Automatic - Action
Automatic - Maintenance Clean
Manual - Multiple Maintenance Clean
Automatic - Bed Type
Automatic - Room Clean
Automatic - ADT Event
Automatic - Case Tracking Event
33 | REQ_PAT_ID | VARCHAR | No |
The Patient (EPT) linked to this Logistics Request.
34 | REQ_BED_TYPE_C_NAME | VARCHAR | No |
This Logistics Request's associated bed type. This indicates that a bed of this type is being moved with this Request. When this Request is completed, the destination's bed type will be updated to this bed type.
May contain organization-specific values: Yes
Category Entries:
Empty
Standard
Crib
Telemetry
Bariatric
35 | REQ_FUNC_COMP_UTC_DTTM | DATETIME (UTC) | No |
Stores the instant that a Logistics Request can be considered functionally complete in UTC.
36 | REQ_ACTIVATION_UTC_DTTM | DATETIME (UTC) | No |
The instant that a Logistics Request is eligible to be assigned.
37 | REQ_FUNC_COMP_LOCAL_DTTM | DATETIME (Local) | No |
Stores the instant that a Logistics Request can be considered functionally complete in local time.
38 | JOB_ACT_LINK_LOCATION_EVNT_ID | NUMERIC | No |
The Patient Location Event record created by the Update Patient Location action on this Logistics Request.
39 | REQ_TASK_SUBTYPE_C_NAME | VARCHAR | No |
Subtype of the request, used to broadly classify the type of request this is.
May contain organization-specific values: No
Category Entries:
Patient Transport
Bed Clean
Maintenance Clean
Inspection
Other
40 | REQ_BED_ID | VARCHAR | No |
For Bed Clean and Maintenance Clean requests, this is the ID of the bed being cleaned.
41 | REQ_BED_ID_BED_LABEL | VARCHAR | No |
The name of the bed.
42 | RECORD_STATUS_C_NAME | VARCHAR | No |
The record status category ID for the hospital logistics request.
May contain organization-specific values: No
Category Entries:
Soft Deleted
Hidden
Hidden and Soft Deleted
43 | PRIMARY_LINKED_EVENT_C_NAME | VARCHAR | No |
Indicates the primary event linked to this Logistics request.
May contain organization-specific values: No
Category Entries:
None
Start Location Appointment
End Location Appointment
Admission
Pending Admission
Pending Transfer
Pending Discharge
Pending LOA Out
Pending LOA Return
Transfer
Discharge
LOA Out
Procedural Preassignment
Surgical Log
44 | REQ_PROC_HELD_NUM | INTEGER | No |
The number of minutes that the associated Logistics Task specified that this request should be held before being activated.