LRL - Location Relationship Segment

The Technical Steward for the LRL segment is Patient Administration.

The LRL segment is used to identify one location's relationship to another location, the nearest lab, pharmacy, etc.

HL7 Attribute Table - LRL - Location Relationship Segment

Seq#	Data Element Name	DataType	Usage	Vocabulary	Cardinality	Item #	Length	C.LEN	Flags
LRL
1	Primary Key Value - LRL	PL	R		[1..1]	00943
2	Segment Action Code	ID	O	0206(R) Segment Action Code(Required)	[0..1]	00763	[1..1]
3	Segment Unique Key	EI	O		[0..1]	00764
4	Location Relationship ID	CWE	R	0325 Location Relationship ID	[1..1]	01277
5	Organizational Location Relationship Value	XON	C		[0..*]	01301
6	Patient Location Relationship Value	PL	C		[0..1]	01292

LRL-1: Primary Key Value - LRL (PL) 00943

Definition: This field contains the institution's 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 - MFE), its preceding LOC (LOC-1 - Primary Key Value - LOC), and its preceding LDP (LDP-1 - Primary Key Value - LDP).

LRL-2: Segment Action Code (ID) 00763

Definition: This field indicates whether this repetition of the segment is being added, changed or deleted. 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.10.4.2, "Action code/unique identifier mode update definition.") Refer to HL7 Table 0206 - Segment Action Code in Chapter 2C, Code Tables, for valid values.

LRL-3: Segment Unique Key (EI) 00764

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.

LRL-4: Location Relationship ID (CWE) 01277

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.

LRL-5: Organizational Location Relationship Value (XON) 01301

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 organization's extended name, i.e., the value of this field is conditional on the value of LRL-4 - Location Relationship 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.

LRL-6: Patient Location Relationship Value (PL) 01292

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 - Primary Key Value - LOC 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.