The LRL segment is used identify one locations relationship to another location, the nearest lab, pharmacy, etc.
Figure 8-15. LRL attributes
SEQ |
LEN |
DT |
OPT |
RP/# |
TBL# |
ITEM# |
ELEMENT NAME |
1 |
80 |
PL |
R |
00943 |
Primary Key Value - LRL |
||
2 |
3 |
ID |
O |
0206 |
00763 |
Segment Action Code |
|
3 |
80 |
EI |
O |
00764 |
Segment Unique Key |
||
4 |
80 |
CE |
R |
0325 |
01230 |
Location Relationship ID |
|
5 |
80 |
XON |
C |
01231 |
Organizational Location Relationship Value |
||
6 |
80 |
PL |
C |
01292 |
Patient Location Relationship Value |
8.8.4.0 LRL field definitions
Components: <point of care (IS)> ^ <room (IS)> ^ <bed (IS)> ^ <facility (HD)> ^ <location status (IS)> ^ <person location type (IS)> ^ <building (IS)> ^ <floor (IS)> ^ <location description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Definition: This field contains the institutions identification code for the location. The identifying key value. This field has the same components as the patient location fields in the PV1 segment (except that bed status is not included here). At least the first component of this field is required. The contents of this field must exactly match the content of its preceding MFE ( MFE-4-primary key value), its preceding LOC (LOC-1-LOC primary key value), and its preceding LDP (LDP-1-LDP primary key value).
Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. This repetition of the repeating segment must be identified using FT1-25-segment unique key. The action code adds a validation check to indicate, from the point of view of the sending system, whether this repetition of a segment is being added, changed or deleted. This and the following field are used to implement the "unique key" mode of updating repeating segments. (See Chapter 2, Section 2.23.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 table 0206 - Segment action code for valid values.
Components: <entity identifier (ST)> ^ <namespace ID (IS)> ^ <universal ID (ST)> ^ <universal ID type (ID)>
Definition: This field contains a unique identifier for one of the multiple repetitions of this segment, to be used in conjunction with the preceding field. Each of the repetitions of the segment will be uniquely identified by this unique key field for the purposes of updates.
Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>
Definition: This field contains an identifier code to show WHICH relationship is being communicated with this segment. Refer to user-defined table 0325 - Location relationship ID for suggested values.
User-defined Table 0325 - Location relationship ID
Value |
Description |
RX |
Nearest Pharmacy |
RX2 |
Second Pharmacy |
LAB |
Nearest Lab |
LB2 |
Second Lab |
DTY |
Nearest Dietary |
ALI |
Location Alias(es) |
PAR |
Parent Location |
Components: <organization name (ST)> ^ <organization name type code (IS)> ^ <ID number (NM)> ^ <check digit (NM)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility ID (HD)>
Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Definition: This field is conditional on the value of LRL-4-location relationship ID. When LRL-4-location relationship ID contains "RX"- Nearest Pharmacy, "RX2"- Other Pharmacy, "LAB"- Nearest Lab, "LB2"- Other Lab, or "DTY"- Dietary, this field holds that organizations extended name I.e., the value of this field is conditional on the value of LRL-4-location relation ID. For example, for an inpatient location, this could be an in-house department ID code using only the third component of this data type. For an outpatient location, this could be the nearest external pharmacy.
Components: <nursing unit or department or clinic (ID)> ^ <room (ST)> ^ <bed (ST)> ^ <facility (HD)> ^ <status (ID)> ^ <person location type (ID)> ^ <building (ID)> ^ <floor (ST)> ^ <location description (ST)>
Subcomponents of facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>
Definition: This field is conditional on the value of LRL-4-location relationship ID. When LRL-4-location relationship ID contains "ALI"- Location aliases or "PAR"- Parent location this field holds the value of the associated patient location
When LRL-4-location relationship ID contains "PAR"- Parent, this field holds the value of the parent location to allow for nested entries. For example, a bed entry can point to its containing room or nurse unit. The value for the parent location should match the LOC-1-IPL primary key value of the parent entry. Not intended to be used for multiple designations of the same physical location, but for identifying the larger physical locations (supersets) which include this physical location as a subset. Aliases should be put in LOC-20-location aliases.