Understanding HL7 v2 PV1-3: Assigned Patient Location in Practice
PV1-3 is a composite field, not a single value — unit, room, bed, and facility are all packed into one caret-delimited string, and it is one of the most common fields to be parsed incompletely because the first two components alone usually look like "enough" during development.
PV1-3 is the third field of the PV1 segment — a composite (PL data type) that identifies where the patient physically is, made up of components like point of care, room, bed, and facility.
What this field contains
Example
The 3rd field (3W^301^B^HOSP) places the patient on unit 3W, room 301, bed B, at facility HOSP. Synthetic patient — not a real person.
Where this trips people up
Bed management integrations built in a single-facility test environment routinely parse only the point-of-care, room, and bed components and skip the facility component entirely, because in one building "301-B" is already unique. The first time that same integration runs against a health system with two campuses that both have a room 301, patients start showing up on the wrong facility's bed board.