HL7 LDP Location Department
HL7 field reference LDP 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 |
|---|---|---|---|---|---|
| LDP.1 | Primary Key Value - LDP | Yes | No | PL | |
| LDP.2 | Location Department | Yes | No | CE | 0264 |
| LDP.3 | Location Service | No | Yes | IS | 0069 |
| LDP.4 | Specialty Type | No | Yes | CE | 0265 |
| LDP.5 | Valid Patient Classes | No | Yes | IS | 0004 |
| LDP.6 | Active/Inactive Flag | No | No | ID | 0183 |
| LDP.7 | Activation Date LDP | No | No | TS | |
| LDP.8 | Inactivation Date - LDP | No | No | TS | |
| LDP.9 | Inactivated Reason | No | No | ST | |
| LDP.10 | Visiting Hours | No | Yes | VH | 0267 |
| LDP.11 | Contact Phone | No | No | XTN | |
| LDP.12 | Location Cost Center | No | No | CE | 0462 |
LDP links a location to a department and defines department-specific location properties.
The standard describes LDP this way: The LDP segment identifies how a patient location room is being used by a certain department. Multiple departments can use the same patient location, so there can be multiple LDP segments following an LOC segment. There must be at least one LDP segment for each LOC segment. This is not intended to include any current occupant information.
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 LDP 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.
LDP-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.
LDP-2 places the master-file record in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
The generated panel links this to HL7 table 0264; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LDP-3 places the master-file record in an organization, facility, department, room, bed, or location group. Keep physical location, owning department, and receiving facility separate when the datatype allows it.
The generated panel links this to HL7 table 0069; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LDP-4 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0265. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
LDP-5 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
Use the agreed value set, starting from HL7 table 0004. A local code without an agreed coding system is a small ambiguity that becomes a mapping problem later.
LDP-6 carries Active/Inactive Flag 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.
The generated panel links this to HL7 table 0183; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LDP-7 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
LDP-8 is a timing field. Send the real source-system precision, do not pad unknown dates or times, and agree how timezone offsets are handled when time of day matters.
LDP-9 qualifies the master-file record rather than identifying it. This is the sort of field receivers often use for branching, filtering, or display grouping.
LDP-10 carries Visiting Hours 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.
The generated panel links this to HL7 table 0267; many real interfaces narrow that list further, so follow the receiver's implementation guide.
LDP-11 carries contact details. Use the datatype components for use code, equipment type, address type, country, and other qualifiers rather than squeezing everything into one formatted string.
LDP-12 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.
The generated panel links this to HL7 table 0462; many real interfaces narrow that list further, so follow the receiver's implementation guide.
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