The PID segment is used by all applications as the primary means of communicating patient identification information. This segment contains permanent patient identifying and demographic information that, for the most part, is not likely to change frequently.
It should be noted that from V2.4 onwards the demographics of animals can also be sent in the PID segment (see PID-35 to PID-38).
The assigning authority, the fourth component of the patient identifiers, is a HD data type that is uniquely associated with the assigning authority that originally assigned the number. A given institution, or group of intercommunicating institutions, should establish a list of assigning authorities that may be potential assignors of patient identification (and other important identification) numbers. The list will be one of the institution's master dictionary lists. Since third parties (other than the assignors of patient identification numbers) may send or receive HL7 messages containing patient identification numbers, the assigning authority in the patient identification numbers may not be the same as the sending and receiving systems identified in the MSH. The assigning authority must be unique across applications at a given site. This field is required in HL7 implementations that have more than a single Patient Administration application assigning such numbers. The assigning authority and identifier type codes are strongly recommended for all CX data types.
With HL7 V2.3, the nomenclature for the fourth component of the patient identifiers was changed from "assigning facility ID" to "assigning authority". While the identifier may be unique to a given healthcare facility (for example, a medical record assigned by facility A in Hospital XYZ), the identifier might also be assigned at a system level (for example a corporate person index or enterprise number spanning multiple facilities) or by a government entity, for example a nationally assigned unique individual identifier. While a facility is usually an assigning authority, not all assigning authorities are facilities. Therefore, the fourth component is referred to as an assigning authority, but retains backward compatibility using the construct of the HD data type (see the note in chapter 2). Additionally, CX data types support the use of assigning facility (HD) as the sixth component.
| Seq# | Data Element Name | DataType | Usage | Vocabulary | Cardinality | Item # | Length | C.LEN | Flags |
|---|---|---|---|---|---|---|---|---|---|
PID
|
|||||||||
1
|
Set ID - PID | SI | O | [0..1] | 00104 | [1..4] | |||
|
2
|
Patient ID | W | [0..1] | 00105 | |||||
|
3
|
Patient Identifier List | CX | R | [1..*] | 00106 | ||||
|
4
|
Alternate Patient ID - PID | W | [0..1] | 00107 | |||||
|
5
|
Patient Name | XPN | R | [1..*] | 00108 | ||||
|
6
|
Mother's Maiden Name | XPN | O | [0..*] | 00109 | ||||
|
7
|
Date/Time of Birth | DTM | O | [0..1] | 00110 | ||||
|
8
|
Administrative Sex | CWE | O | [0..1] | 00111 | ||||
|
9
|
Patient Alias | W | [0..1] | 00112 | |||||
|
10
|
Race | CWE | O | [0..*] | 00113 | ||||
|
11
|
Patient Address | XAD | O | [0..*] | 00114 | ||||
|
12
|
County Code | W | [0..1] | 00115 | |||||
|
13
|
Phone Number - Home | XTN | W | [0..0] | 00116 | ||||
|
14
|
Phone Number - Business | XTN | W | [0..0] | 00117 | ||||
|
15
|
Primary Language | CWE | O | [0..1] | 00118 | ||||
|
16
|
Marital Status | CWE | O | [0..1] | 00119 | ||||
|
17
|
Religion | CWE | O | [0..1] | 00120 | ||||
|
18
|
Patient Account Number | CX | O | [0..1] | 00121 | ||||
|
19
|
SSN Number - Patient | W | [0..1] | 00122 | |||||
|
20
|
Driver's License Number - Patient | W | [0..1] | 00123 | |||||
|
21
|
Mother's Identifier | CX | O | [0..*] | 00124 | ||||
|
22
|
Ethnic Group | CWE | O | [0..*] | 00125 | ||||
|
23
|
Birth Place | ST | O | [0..1] | 00126 | 250 | # | ||
|
24
|
Multiple Birth Indicator | ID | O | [0..1] | 00127 | [1..1] | |||
|
25
|
Birth Order | NM | O | [0..1] | 00128 | 2 | # | ||
|
26
|
Citizenship | CWE | O | [0..*] | 00129 | ||||
|
27
|
Veterans Military Status | CWE | O | [0..1] | 00130 | ||||
|
28
|
Nationality | CWE | W | [0..1] | 00739 | ||||
|
29
|
Patient Death Date and Time | DTM | O | [0..1] | 00740 | ||||
|
30
|
Patient Death Indicator | ID | O | [0..1] | 00741 | [1..1] | |||
|
31
|
Identity Unknown Indicator | ID | O | [0..1] | 01535 | [1..1] | |||
|
32
|
Identity Reliability Code | CWE | O | [0..*] | 01536 | ||||
|
33
|
Last Update Date/Time | DTM | O | [0..1] | 01537 | ||||
|
34
|
Last Update Facility | HD | O | [0..1] | 01538 | ||||
|
35
|
Taxonomic Classification Code | CWE | O | [0..1] | 01539 | ||||
|
36
|
Breed Code | CWE | B | [0..1] | 01540 | ||||
|
37
|
Strain | ST | O | [0..1] | 01541 | 80 | # | ||
|
38
|
Production Class Code | CWE | O | [0..2] | 01542 | ||||
|
39
|
Tribal Citizenship | CWE | O | [0..*] | 01840 | ||||
40
|
Patient Telecommunication Information | XTN | O | [0..*] | 02289 | ||||
Definition: This field contains the number that identifies this transaction. For the first occurrence of the segment, the sequence number shall be one, for the second occurrence, the sequence number shall be two, etc.
Attention: The PID-2 field was retained for backward compatibility only as of v2.3.1 and was withdrawn and removed from this message structure as of v2.7. It is recommended to use PID-3 - Patient Identifier List for all patient identifiers.
Definition: This field contains the list of identifiers (one or more) used by the healthcare facility to uniquely identify a patient (e.g., medical record number, billing number, birth registry, national unique individual identifier, etc.). In Canada, the Canadian Provincial Healthcare Number should be sent in this field. The arbitrary term of "internal ID" has been removed from the name of this field for clarity.
Attention: The PID-4 field was retained for backward compatibility only as of v2.3.1 and was withdrawn and removed from this message structure as of v2.7. It is recommended to use PID-3 - Patient Identifier List for all patient identifiers.
Definition: This field contains one or more of the names of the patient. The XPN.7 Name Type Code, and not the order, conveys how the name should be interpreted. As of v2.7, Name Type Code is Required. Refer to HL7 Table 0200 - Name Type in Chaper 2C, Code Tables, for valid values. Specification of meaning based on sequence is deprecated.
In addition to allowing repetition of this field for transmitting multiple names with different Name Type Codes, repetition also allows for representing the same name in different character sets based on the value in XPN.8 Name Representation Code.
Multiple given names and/or initials are separated by spaces.
For animals, if a Name Type of "R" is used, use "Name Context" to identify the authority with which the animal's name is registered.
Definition: This field contains the family name under which the mother was born (i.e., before marriage). It is used to distinguish between patients with the same last name.
Definition: This field contains the patient's date and time of birth.
Definition: This field contains the patient's sex. Refer to User-defined Table 0001 - Administrative Sex in Chapter 2C, Code Tables, for suggested values.
Attention: The PID-9 field was retained for backward compatibility only as of v2.4 and was withdrawn and removed from this message structure as of v2.7. it is recommended to use PID-5 - Patient Name for all patient names.
Definition: This field refers to the patient's race. Refer to User-defined Table 0005 - Race in Chapter 2C, Code Tables, for suggested values. The second triplet of the CWE data type for race (alternate identifier, alternate text, and name of alternate coding system) is reserved for governmentally assigned codes.
Definition: This field contains the address of the patient. Multiple addresses for the same person may be sent. As of v2.7 the "primary mailing address" constraint as the first sequence has been removed...
Attention: The PID-12 field was retained for backward compatibility only as of v2.3 and was withdrawn and removed from this message structure as of v2.7. The county can now be supported in the county/parish code component of the XAD data type (PID-11 - Patient Address).
Attention: The PID13 field has been retained for backward compatibility as of v 2.7 and withdrawn as of v 2.9. The reader is referrred to section 3.4.2.40, PID-40 – Patient Telecommunication Information instead, which replaces PID-13 – Phone Number - Home with the intention that the components of the XTN data type be used to identify phone usage (Telecommunication use code) and type of equipment (telecommunication equipment type).
This field contains the patient's personal phone numbers. All personal phone numbers for the patient are sent in the following sequence. The first sequence is considered the primary number (for backward compatibility). If the primary number is not sent, then a repeat delimiter is sent in the first sequence. Refer to HL7 Table 0201 - Telecommunication Use Code and HL7 Table 0202 - Telecommunication Equipment Type in Chapter 2C, Code Tables, for valid values.
Attention: The PID-14 field has been retained for backward compatibility only as of v2.7 and withdrawn as of v 2.9.. The reader is referred to section 3.4.2.40, PID-40 – Patient Telecommunication Information instead, which replaces PID-14 – Phone Number - Business with the intention that the components of the XTN data type be used to identify phone usage (Telecommunication use code) and type of equipment (telecommunication equipment type).
This field contains the patient's business telephone numbers. All business numbers for the patient are sent in the following sequence. The first sequence is considered the patient's primary business phone number (for backward compatibility). If the primary business phone number is not sent, then a repeat delimiter must be sent in the first sequence. Refer to HL7 Table 0201 - Telecommunication Use Code and HL7 Table 0202 - Telecommunication Equipment Type in Chapter 2C, Code Tables, for valid values.
Definition: This field contains the patient's primary language. HL7 recommends using ISO table 639 as the suggested values in User-defined Table 0296 - Primary Language within Chapter 2C, Code Tables.
Definition: This field contains the patient's marital (civil) status. Refer to User-defined Table 0002 - Marital Status in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the patient's religion. Refer to User-defined Table 0006 - Religion in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the patient account number assigned by accounting to which all charges, payments, etc., are recorded. It is used to identify the patient's account. Refer to HL7 Table 0061 - Check Digit Scheme in Chapter 2C, Code Tables, for valid values.
Attention: The PID-19 field was retained for backward compatibility only as of v 2.3.1 and was withdrawn and removed from this message structure as of v 2.7. It is recommended to use PID-3 - Patient Identifier List for all patient identifiers.
Attention: The PID-20 field was retained for backward compatibility only as of v 2.5 and was withdrawn and removed from this message structure as of v 2.7. It is recommended to use PID-3 - Patient Identifier List for all patient identifiers.
Definition: This field is used, for example, as a link field for newborns. Typically a patient ID or account number may be used. This field can contain multiple identifiers for the same mother. Refer to HL7 Table 0061 - Check Digit Scheme in Chapter 2C, Code Tables, for valid values.
Definition: This field further defines the patient's ancestry. Refer to User-defined Table 0189 - Ethnic Group in Chapter 2C, Code Tables, for suggested values. The second triplet of the CWE data type for ethnic group (alternate identifier, alternate text, and name of alternate coding system) is reserved for governmentally assigned codes. In the US, a current use is to report ethnicity in line with US federal standards for Hispanic origin.
Definition: This field indicates the location of the patient's birth, for example "St. Francis Community Hospital of Lower South Side". The actual address is reported in PID-11 with an identifier of "N".
Definition: This field indicates whether the patient was part of a multiple birth. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.
Y the patient was part of a multiple birth
N the patient was a single birth
Definition: When a patient was part of a multiple birth, a value (number) indicating the patient's birth order is entered in this field.
This field contains the information related to a person's country citizenship. For country citizenship HL7 recommends using ISO table 3166. For a local definition, User-defined Table 0171 - Citizenship in Chapter 2C, Code Tables, should be used.
This field repeats since persons can be citizens of more than one country. The Name of Coding System component(s) of the CWE datatype should be used to identify the table from which citizenship membership is drawn.
In the Netherlands, this field is used for "Nationaliteit".
Definition: This field contains the military status assigned to a veteran. Refer to User-defined Table 0172 - Veterans Military Status in Chapter 2C, Code Tables, for suggested values.
Attention: The PID-28 field was retained for backward compatibility only as of v 2.4 and was withdrawn and removed from this message structure as of v 2.7. It is recommended to refer to PID-10 - Race, PID-22 - Ethnic group and PID-26 - Citizenship.
Definition: This field contains the date and time at which the patient death occurred.
Definition: This field indicates whether the patient is deceased. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.
Y the patient is deceased
N the patient is not deceased
Definition: This field indicates whether or not the patient's/person's identity is known. Refer to HL7 Table 0136 - Yes/No Indicator in Chapter 2C, Code Tables, for valid values.
Y the patient's/person's identity is unknown
N the patient's/person's identity is known
Definition: This field contains a coded value used to communicate information regarding the reliability of patient/person identifying data transmitted via a transaction. Values could indicate that certain fields on a PID segment for a given patient/person are known to be false (e.g., use of default or system-generated values for Date of Birth or Social Security Number). Refer to User-defined Table 0445 - Identity Reliability Code in Chapter 2C, Code Tables, for suggested values.
Definition: This field contains the last update date and time for the patient's/person's identifying and demographic data, as defined in the PID segment. Receiving systems will use this field to determine how to apply the transaction to their systems. If the receiving system (such as an enterprise master patient index) already has a record for the person with a later last update date/time, then the EMPI could decide not to apply the patient's/person's demographic and identifying data from this transaction.
Definition: This field identifies the facility of the last update to a patient's/person's identifying and demographic data, as defined in the PID segment. Receiving systems or users will use this field to determine how to apply the transaction to their systems. If the receiving system (such as a hospital's patient management system) already has a record for the patient/person, then it may decide to only update its data if the source is a "trusted" source. A hospital might consider other hospitals trusted sources, but not "trust" updates from non-acute care facilities. For example:
...|GOOD HEALTH Hospital|...
Definition: A code representing the taxonomic classification (e.g. species and/or breed) of an organism. This may include the common or scientific name in the description component, based on the coding system(s) used. SNOMED-CT is the recommended coding system. If this field is not valued, a human is assumed. If the specificity of the coding system is insufficient to represent the organism to the degree desired, the most detailed coded value available may be used in this field and additional information sent in the text field, PID-37 – Strain.
For example:
...|L-80700^Canine, NOS^SNM3|...
...|L-80100^Bovine^SNM3|...
...|L-80A00^Feline^SNM3|...
Definition: From v 2.8 onward, this field has been retained for backward compatibility only. The specific breed of animal. This field, unlike Species and Strain is specific to animals and cannot be generally used for all living organisms. SNOMED is the recommended coding system. Refer to User-defined Table 0447 - Breed Code in Chapter 2C, Code Tables, for suggested values.
Conditionality Rule: This field must be valued if PID-37 - Strain is valued.
For example, (showing primary and alternative coding systems, using locally defined "American Kennel Club" nomenclature):
...|L-80733^ Staffordshire bull terrier^SNM3^^American Staffordshire Terrier^99AKC|...
...|L-80900^Weimaraner^SNM3|...
...|L-80439^Peruvian Paso Horse^SNM3|...
Definition: This field contains the specific strain of animal. It can also be expanded to include strain of any living organism and is not restricted to animals.
Example:
...|DeKalb|...
...|Balb/c|...
...|DXL|...
Definition: This field contains the code and/or text indicating the primary use for which the living subject was bred or grown. Refer to User-defined Table 0429 - Production Class Code in Chapter 2C, Code Tables, for suggested values. For example:
...|DA^Dairy^L|...
...|MT^Meat^L|...
...|RA^Racing^L|...
This field contains the information related to a person's tribal citizenship. For tribal citizenship, in the United States, HL7 recommends using the Bureau of Indian Affairs (BIA) Tribal Identity List. For a local definition, User-defined Table 0171 - Citizenship in Chapter 2C, Code Tables should be used.
This field repeats since persons can have tribal membership(s) and can be members of more than one tribe. The Name of Coding System component(s) of the CWE datatype should be used to identify the table from which tribal membership is drawn.
Definition: This field contains the patient's personal telecommunication contact information. This field replaces PID-13 – Phone Number - Home and PID-14 – Phone Number – Business with the intention that the components of the XTN data type be used to identify phone usage (Telecommunication use code) and type of equipment (telecommunication equipment type). Jointly, these components will describe the nature of the telecommunication data contained in this field and removes the sequenced-based assumptions in PID-13 and PID-14.
®© HL7.org 2019+. HL7 v2+ generated on March 23, 2022
Links:
Version History
|
Propose a change
|
License
The Demo site for our new HL7 Version 2+ (plus) Standard
