HL7 LRL Location Relationship
HL7 field reference LRL fields from HL7 v2.5.1 Show fields
These are the generated fields for the version selected at the top of the page. The document stays the same, but the reference panel follows that version.
Fields
| Field | Name | Required | Repeatable | Type | Table |
|---|---|---|---|---|---|
| LRL.1 | Primary Key Value - LRL | Yes | No | PL | |
| LRL.2 | Segment Action Code | No | No | ID | 0206 |
| LRL.3 | Segment Unique Key | No | No | EI | |
| LRL.4 | Location Relationship ID | Yes | No | CE | 0325 |
| LRL.5 | Organizational Location Relationship Value | No | Yes | XON | |
| LRL.6 | Patient Location Relationship Value | No | No | PL |
LRL describes relationships between locations, such as parent/child or service relationships.
The standard describes LRL this way: The LRL segment is used to identify one location's relationship to another location, the nearest lab, pharmacy, etc.
Master-file segments update reference data rather than describing a single patient event. They define locations, staff, providers, test catalogs, charge items, inventory items, languages, certificates, and other shared records.
Because many downstream messages depend on this data, small changes here can have large effects. Use stable identifiers, effective dates, action codes, and clear ownership rules instead of treating a master-file feed like a loose spreadsheet export.
The v2.5.1 structures show LRL in MFN_M05 - Patient location master file, MFR_M05 - Patient location master file, and RSP_Q11 - QBP - Query by parameter requesting an RSP segment pattern response. That tells you where it can appear, but the implementation guide still decides which optional fields are meaningful.
For practical interface work, read the generated field panel for datatype, required, repeatable, and table details, then use the notes below to decide what the field should mean in the receiving workflow.
LRL-1 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
LRL-2 says what action is being taken for this segment or record: add, update, delete, cancel, clear, or another profile-defined operation. It needs to agree with the message trigger and the previous state.
The generated panel links this to HL7 table 0206; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LRL-3 carries Segment Unique Key for this master-file record. Populate it only when the receiver has a clear use for it, and keep the value in the datatype shape shown in the generated field panel.
LRL-4 identifies the Location Relationship ID for this master-file record. Send the identifier that the receiving system actually keys on, and keep the assigning authority or coding system visible when the datatype supports it.
The generated panel links this to HL7 table 0325; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LRL-5 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
This field can repeat. Use repetitions for separate real-world values, not as a workaround for putting several unrelated ideas in one field.
LRL-6 carries a measured, counted, priced, or dosed value. A number without the expected unit, currency, or companion qualifier is much easier to misread than an empty field.
Related links
- MFI - Master File Identification
- MFE - Master File Entry
- MFA - Master File Acknowledgment
- LOC - Location Identification
- STF - Staff Identification
- PRA - Practitioner Detail
- OM1 - General Segment
- CDM - Charge Description Master
- MFN_M05 - Patient location master file
- MFR_M05 - Patient location master file