Previous Page TOC Index Next Page

3.3.2 PID - patient identification segment

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.

Figure 3-2. PID attributes

SEQ

LEN

DT

OPT

RP/#

TBL#

ITEM#

ELEMENT NAME

1

4

SI

O



00104

Set ID - Patient ID

2

20

CX

O



00105

Patient ID (External ID)

3

20

CX

R

Y


00106

Patient ID (Internal ID)

4

20

CX

O

Y


00107

Alternate Patient ID - PID

5

48

XPN

R



00108

Patient Name

6

48

XPN

O



00109

Mother’s Maiden Name

7

26

TS

O



00110

Date/Time of Birth

8

1

IS

O


0001

00111

Sex

9

48

XPN

O

Y


00112

Patient Alias

10

1

IS

O


0005

00113

Race

11

106

XAD

O

Y


00114

Patient Address

12

4

IS

B



00115

County Code

13

40

XTN

O

Y


00116

Phone Number - Home

14

40

XTN

O

Y


00117

Phone Number - Business

15

60

CE

O


0296

00118

Primary Language

16

1

IS

O


0002

00119

Marital Status

17

3

IS

O


0006

00120

Religion

18

20

CX

O



00121

Patient Account Number

19

16

ST

O



00122

SSN Number - Patient

20

25

CM

O



00123

Driver's License Number - Patient

21

20

CX

O

Y


00124

Mother's Identifier

22

3

IS

O


0189

00125

Ethnic Group

23

60

ST

O



00126

Birth Place

24

2

ID

O


0136

00127

Multiple Birth Indicator

25

2

NM

O



00128

Birth Order

26

4

IS

O

Y

0171

00129

Citizenship

27

60

CE

O


0172

00130

Veterans Military Status

28

80

CE

O



00739

Nationality

29

26

TS

O



00740

Patient Death Date and Time

30

1

ID

O


0136

00741

Patient Death Indicator

3.3.2.0 PID field definitions

3.3.2.1 Set ID - patient ID (SI) 00104

Definition: For those messages that permit segments to repeat, the Set ID field is used to identify the repetitions. For example, the swap and query transactions allow for multiple PID segments that would have Set ID values of 1, 2, then 3, etc.

3.3.2.2 Patient ID (external ID) (CX) 00105

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: When the patient is from another institution, outside office, etc., the identifier used by that institution can be shown in this field. This may be a number that multiple disparate corporations or facilities share. Refer to HL7 table 0061 - Check digit scheme in Chapter 2.

3.3.2.3 Patient ID (internal ID) (CX) 00106

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the primary identifier, or other identifiers used by the facility to identify a patient uniquely (e.g., medical record number, billing number, birth registry, etc.). Refer to HL7 table 0061 - Check digit scheme for valid values.

When merging patient IDs (A34 and A36 events), the Patient ID contained in the PID segment cannot repeat.

3.3.2.4 Alternate patient ID - PID (CX) 00107

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Definition: This field contains the third number that may be required to identify a patient. This field may be used to convey multiple patient IDs when more than one exist for a patient. Possible contents might include a visit number, a visit date, or a Social Security Number.

3.3.2.5 Patient name (XPN) 00108

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >

Definition: This field contains the legal name of the patient. All other names for the patient should be sent in PID-9-patient alias. Therefore, the name type code in this field should be "L - Legal." Refer to HL7 table 0200 Name type code for valid values.

3.3.2.6 Mother's maiden name (XPN) 00109

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >

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.

3.3.2.7 Date/Time of birth (TS) 00110

Definition: This field contains the patient’s date and time of birth.

3.3.2.8 Sex (IS) 00111

Definition: This field contains the patient’s sex. Refer to user-defined table 0001 - Sex for suggested values.

User-defined Table 0001 - Sex

Value

Description

F

Female

M

Male

O

Other

U

Unknown

3.3.2.9 Patient alias (XPN) 00112

Components: <family name (ST)> ^ <given name (ST)> ^ <middle initial or name (ST)> ^ <suffix (e.g., JR or III) (ST)> ^ <prefix (e.g., DR) (ST)> ^ <degree (e.g., MD) (ST)> ^ <name type code (ID) >

Definition: This field contains the name(s) by which the patient has been known at some time. Refer to HL7 table 0200 - Name type for valid values.

3.3.2.10 Race (IS) 00113

Definition: This field refers to the patient’s race. Refer to user-defined table 0005 - Race for suggested values.

3.3.2.11 Patient address (XAD) 00114

Components: <street address (ST)> ^ <other designation (ST)> ^ <city (ST)> ^ <state or province (ST)> ^ <zip or postal code(ST)> ^ <country (ID)> ^ < address type (ID)> ^ <other geographic designation (ST)>^ <county/parish code (IS)> ^ <census tract (IS)>

Definition: This field contains the mailing address of the patient. Address type codes are user defined. Multiple addresses for the same person may be sent in the following sequence: The mailing address must be sent first in the sequence; if the mailing address is not sent, then a repeat delimiter must be sent in the first sequence.

3.3.2.12 County code (IS) 00115

Definition: This field has been retained for backward compatibility. This field contains the patient’s county code. The county can now be supported in the county/parish code component of the XAD data type (PID-11-patient address). Refer to user-defined table 0289 - County/parish for suggested values.

3.3.2.13 Phone number - home (XTN) 00116

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^ <telecommunication use code (ID)> ^ <telecommunication equipment type (ID)> ^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>

Definition: This field contains the patient’s personal phone numbers. All personal phone numbers for the patient are sent in this sequence. The first sequence is considered the primary number. If the primary number is not sent, then a repeat delimiter is sent in the first sequence. Refer to HL7 tables 0201 - Telecommunication use code and 0202 - Telecommunication equipment type for valid values.

3.3.2.14 Phone number - business (XTN) 00117

Components: [NNN] [(999)]999-9999 [X99999] [B99999] [C any text] ^<telecommunication use code (ID)> ^ <telecommunication equipment type (ID)>^ <email address (ST)> ^ <country code (NM)> ^ <area/city code (NM)> ^ <phone number (NM)> ^ <extension (NM)> ^ <any text (ST)>

Definition: This field contains the patient’s business telephone numbers. All business numbers for the patient are sent in this sequence. The first sequence is considered the patient’s primary business phone number. If the primary business phone number is not sent, then a repeat delimiter must be sent in the first sequence. Refer to HL7 tables 0201 - Telecommunication use code and 0202 - Telecommunication equipment type for valid values.

3.3.2.15 Primary language (CE) 00118

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the patient’s primary language. HL7 recommends using ISO table 639 as the suggested values in user-defined table 0296 - Language.

3.3.2.16 Marital status (IS) 00119

Definition: This field contains the patient’s marital status. Refer to user-defined table 0002 - Marital status for suggested values.

User-defined Table 0002 - Marital status

Value

Description

A

Separated

D

Divorced

M

Married

S

Single

W

Widowed

3.3.2.17 Religion (IS) 00120

Definition: This field contains the patient’s religion. Refer to user-defined table 0006 - Religion for suggested values.

3.3.2.18 Patient account number (CX) 00121

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

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 2.

3.3.2.19 SSN number - patient (ST) 00122

Definition: This field contains the patient’s social security number. This number may also be an RR retirement number.

3.3.2.20 Driver's license number - patient (DLN) 00123

Components: <license number (ST)> ^ <issuing state, province, country (IS)> ^ <expiration date (DT)>

Definition: This field contains the patient’s drivers license number. Some sites may use this number as a unique identifier of the patient. The default of the second component is the state in which the patient’s license is registered.

3.3.2.21 Mother's identifier (CX) 00124

Components: <ID (ST)> ^ <check digit (ST)> ^ <code identifying the check digit scheme employed (ID)> ^ <assigning authority (HD)> ^ <identifier type code (IS)> ^ <assigning facility (HD)>

Subcomponents of assigning authority: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

Subcomponents of assigning facility: <namespace ID (IS)> & <universal ID (ST)> & <universal ID type (ID)>

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 as defined in Chapter 2.

3.3.2.22 Ethnic group (IS) 00125

Definition: This field further defines the patient’s ancestry. Refer to user-defined table 0189 - Ethnic group for suggested values. ERISA has a published list of ethnic classifications that may be used by local agreement at a site.

3.3.2.23 Birth place (ST) 00126

Definition: This field indicates the location of the patient’s birth.

3.3.2.24 Multiple birth indicator (ID) 00127

Definition: This field indicates whether the patient was part of a multiple birth. Refer to HL7 table 0136 - Yes/No indicator as described in Chapter 2.

3.3.2.25 Birth order (NM) 00128

Definition: When a patient was part of a multiple birth, a value (number) indicating the patient’s birth order is entered in this field.

3.3.2.26 Citizenship (IS) 00129

Definition: This field contains the patient’s country of citizenship. HL7 recommends using ISO table 3166 as the suggested values in user-defined table 0171 - Citizenship.

3.3.2.27 Veterans military status (CE) 00130

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field contains the military status assigned to a veteran. Refer to user-defined table 0172 - Veterans military status for suggested values.

3.3.2.28 Nationality (CE) 00739

Components: <identifier (ST)> ^ <text (ST)> ^ <name of coding system (ST)> ^ <alternate identifier (ST)> ^ <alternate text (ST)> ^ <name of alternate coding system (ST)>

Definition: This field identifies the nation or national group to which the patient belongs. This information may be different than the person’s citizenship in countries in which multiple nationalities are recognized (e.g., Spain: Basque, Catalan, etc.).

3.3.2.29 Patient death date and time (TS) 00740

Definition: This field contains the date and time at which the patient death occurred.

3.3.2.30 Patient death indicator (ID) 00741

Definition: This field indicates whether or not the patient is deceased. Refer to Chapter 2, HL7 table 0136 - Yes/no indicator for valid values.

3.3.2.31 Usage notes: PID patient identification

The assigning facility ID, the fourth component of the patient identifiers, is a string of up to six characters that is uniquely associated with the facility that originally assigned the number. A given institution, or group of intercommunicating institutions, should establish a list of facilities that may be potential assigners 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 assigners of patient identification numbers) may send or receive HL7 messages containing patient identification numbers, the assigning facility ID in the patient identification numbers may not be the same as the sending and receiving systems identified in the MSH. The assigning facility ID must be unique across applications at a given site. This field is required in HL7 implementations that have more than a single ADT/REG application assigning such numbers.

Previous Page TOC Index Next Page