The Demo site for our new HL7 Version 2+ (plus) Standard
visit the hl7 website

Draft Website - For Review Purposes Only

PL - person location

HL7 Component Table - PL - person location
Seq# Description Implement Flags Cardinality Length C.LEN Vocabulary Data Type
PL
1

Point of Care MAY
True:
False: 		C
[1..1]
[0..1] 		    0302 HD
2 Room [0..1]     0303 HD
3 Bed [0..1]     0304 HD
4 Facility [0..1]     HD
5 Location Status = [0..1]  20 0306 IS
6 Person Location Type = [0..1]  20 0305 IS
7 Building [0..1]     0307 HD
8 Floor [0..1]     0308 HD
9 Location Description # [0..1] 199 ST
10 Comprehensive Location Identifier [0..1]     EI
11 Assigning Authority for Location [0..1]     0363 HD

Components: <Point of Care (HD)> & <Room (HD)> & <Bed (HD)> & <Facility (HD)> & <Location Status (IS)> & <Person Location Type (IS)> & <Building (HD)> & <Floor (HD)> & <Location Description (ST)> & <Comprehensive Location Identifier (EI)> & <Assigning Authority for Location (HD)>

Subcomponents for Point of Care (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Room (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Bed (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Facility (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Building (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Floor (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Comprehensive Location Identifier (EI): <Entity Identifier (ST)> ^ <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Subcomponents for Assigning Authority for Location (HD): <Namespace ID (IS)> ^ <Universal ID (ST)> ^ <Universal ID Type (ID)>

Definition: This data type is used to specify a patient location within a healthcare institution. Which components are valued depends on the needs of the site. For example for a patient treated at home, only the person location type is valued. It is most commonly used for specifying patient locations, but may refer to other types of locations within a healthcare setting.

Note: This data type contains several location identifiers that should be thought of in the following order from the most general to the most specific: facility, building, floor, point of care, room, bed.
Additional data about any location defined by these components can be added in the following components: person location type, location description and location status.


Example: Nursing Unit

A nursing unit at Community Hospital: 4 East, room 136, bed B

4E^136^B^CommunityHospital^^N^^^

Example: Clinic

A clinic at University Hospitals: Internal Medicine Clinic located in the Briones building, 3rd floor.

InternalMedicine^^^UniversityHospitals^^C^Briones^3^

Example: Home

The patient was treated at his home.

^^^^^H^^^

PL-1: Point of Care (HD)

Definition: This component specifies the code for the point where patient care is administered. It is conditional on PL.6 Person Location Type (e.g., nursing unit or department or clinic). After floor, it is the most general patient location designation. Refer to User-defined Table 0302 - Point of Care for suggested values.

PL-2: Room (HD)

Definition: This component specifies the code for the patient's room. After point of care, it is the most general person location designation. Refer to User-defined Table 0303 - Room for suggested values.

PL-3: Bed (HD)

Definition: This component specifies the code for the patient's bed. After room, it is the most general person location designation. Refer to User-defined Table 0304 - Bed for suggested values.

PL-4: Facility (HD)

Definition: This component is subject to site interpretation but generally describes the highest level physical designation of an institution, medical center or enterprise. It is the most general person location designation.

See Section 2.A.33, “HD - hierarchic designator” for discussion of data type.

Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be redefined (given a different user-defined table number and name) by the technical committee responsible for that segment.


PL-5: Location Status (IS)

Definition: This component specifies the code for the status or availability of the location. For example, it may convey bed status. Refer to User-defined Table 0306 - Location Status for suggested values.

PL-6: Person Location Type (IS)

Definition: Person location type is the categorization of the person’s location defined by facility, building, floor, point of care, room or bed. Although not a required field, when used, it may be the only populated field. It usually includes values such as nursing unit, department, clinic, SNF, physician’s office. Refer to User-defined Table 0305 - Person location type for suggested values.

PL-7: Building (HD)

Definition: This component specifies the code for the building where the person is located. After facility, it is the most general person location designation. Refer to User-defined Table 0307 - Building for suggested values.

PL-8: Floor (HD)

Definition: This component specifies the code for the floor where the person is located. After building, it is the most general person location designation. Refer to User-defined Table 0308 - Floor for suggested values.

PL-9: Location Description (ST)

Definition: This component describes the location in free text.

PL-10: Comprehensive Location Identifier (EI)

Definition: The unique identifier that represents the physical location as a whole without regard for the individual components. This accommodates sites that may have a different method of defining physical units or who may code at a less granular level. For example, point of care, room, and bed may be 1 indivisible code.

PL-11: Assigning Authority for Location (HD)

Definition: The entity that creates the data for the individual physical location components. If populated, it should be the authority for all components populated. Refer to User-defined Table 0363 – Assigning Authority for suggested values for the first sub-component of the HD component, <namespace ID>.

This component makes it possible for codes to be differentiated when the field in which this data type is used repeats.

Note: When the HD data type is used in a given segment as a component of a field of another data type, User-defined Table 0300 - Namespace ID (referenced by the first sub-component of the HD component) may be re-defined (given a different user-defined table number and name) by the technical committee responsible for that segment.

By site agreement, implementors may continue to use User-defined Table 0300 – Namespace ID for the first sub-component.