Id2.16.840.1.113883.3.1937.777.10.15.76Effective Date2013‑02‑10
Statusactive ActiveVersion Label
NameXPN_datatypeDisplay NameXPN - Extended person name
Description

Replaces PN as of v 2.3.

Internationalization Note: In countries using ideographic or syllabic (phonetic) character sets, it is sometimes necessary to send the name in one or both of these formats, as well as an alphabetic format. The switching between the different character sets can be accomplished using a character set such as JIS X 0202 - ISO 2022 which provides an escape sequence for switching among different character sets and among single-byte and multi-byte character representations. When the name field is repeated, the different repetitions of the name may be represented by these different character sets. The details are as follows. (See also Section 2.9.2, "Escape sequences supporting multiple character sets for PN, XPN, XCN, XON, XAD, FT, ST and TX data types.")

HL7 supports the following standards for Japanese characters:

  • JIS X 0201 for ISO-IR 13 (Japanese Katakana)
  • JIS X 0201 for ISO-IR 14 (Japanese Romaji)
  • JIS X 0208 for ISO-IR 87 (Japanese Kanji, Hiragana and Katakana)
  • JIS X 0212 for ISO-IR 159 (supplementary Japanese Kanji)

HL7 supports the following standards for European characters:

  • ISO 8859 (1-9) for ISO-IR 100, 101, 109, 110, 144,127, 126, 138 and 148.

Character sets are referenced in HL7 as ASCII, 8859/1,8859/2, ISO IR14, ISO IR87, and ISO IR159. DICOM uses codes laid out in ISO 2375, of the form 'ISO-IR xxx'. HL7 supports this naming as well, to facilitate interoperability.

HL7 uses the Basic G0 Set of the International Reference Version of ISO 646:1990 (ISO IR-6) as the default character repertoire for character strings. This is a single-byte character set, identical to ASCII.

Each repetition of a XPN, XON, XCN, or XAD field is assumed to begin with the default character set. If another character set is to be used, the HL7 defined escape sequence used to announce that character set must be at the beginning of the repetition, and the HL7 defined escape sequence used to start the default character set must be at the end of the repetition. Note also that several character sets may be intermixed within a single repetition as long as the repetition ends with a return to the default character set.

An application must specify which character sets it supports in the field "MSH-18 Character Sets" and which character set handling scheme it supports in the field MSH-20-Alternate character set handling scheme. It is assumed that the sending and receiving applications are aware of how to map character set names (i.e., ISO-IR xxx) to escape sequences.

For example, in many Japanese messages there is a mix of Romaji (i.e., Roman characters), Katakana (phonetic representation of foreign words), Hiragana (phonetic representation of Japanese words) and Kanji (pictographs). Such a message would require 4 character sets be specified in the MSH.

References for Internationalization of Name
ReferenceDescription
1."Understanding Japanese Information Processing" by Ken Lunde, O’Reilly Press
2.NEMA PS3.5 - DICOM Part 5: Data Structure and Semantics
3.ANSI X3.4:1986ASCII character set
4.ISO 646:1990Information Processing - ISO 7-bit coded character set for information interchange
5.ISO/IEC 2022:1994Information Technology - Character code structure and extension techniques
6.ISO 2375:1986Data Processing - Procedure for the registration of escape sequences
7.ISO 6429:1990Information Processing - Control functions for 7-bit and 8-bit coded character sets
8.ISO 8859 (1-9)Information Processing - 8-bit single-byte coded graphic character sets - parts 1-9
9.ENV 41 503:1990Information systems interconnection - European graphic character repertoires and their coding
10.ENV 41 508:1990Information systems interconnection - East European graphic character repertoires and their coding
11.JIS X 0201-1976Code for Information Exchange
12.JIS X 0212-1990Code of the supplementary Japanese Graphic Character set for information interchange
13.JIS X 0208-1990Code for the Japanese Graphic Character set for information interchange
14.RFC 1468Japanese Character Encoding for Internet Messages

Character Repertoires supported by DICOM are defined in Part 5, section 6.1. The DICOM Standard is available free on the Internet at http://medical.nema.org/.

Examples of names requiring only one iteration of the field where the XPN is applied:

Example 1: Adam A. Everyman III PhD

|Everyman^Adam^A^III^DR^^L^^^^^^^PHD|

Example 2:Ludwig van Beethoven

|Beethoven&van^Ludwig^^^^^L|

Example 3: Hermann Egon Mayer zur alten Schildesche

|Mayer^Hermann^Egon^zur alten Schildesche|

Example 4: Sister Margot

|^Margot^^^Sister^^C|

Example 5: Dr Patrick John Flannery AO. MBBS. ASCTS. A physician who holds an Honorarium, an academic degree and a board certificate. Professional suffixes are displayed as concatenated. (AO = Order of Australia (Honorarium), MBBS = Bachelor of Medicine and Bachelor of Surgery, ASCTS = Australian Society of Cardiothoracic Surgeons

|Flannery^Patrick^John^^Dr^L^^^^^^^^ AO.MBBS.ASCTS|

Example 6: Nancy N. Nightingale, RN, PHN, BSN, MSN. A registered nurse who is a Public Health Nurse with 2 academic degrees, BSN and MSN.

|Nightingale^Nancy^N^^^^^^^^^^RN, PHN, BSN, MSN|

Example 7: T.Thomas Ackerson Jr., RN, CNP. A registered nurse who is a certified nurse practitioner.

|Ackerson^Thomas^T^Jr^^^^^^^^^^ RN, CNP|

Example 8: Mevrouw Irma Jongeneel de Haas. An individual whose birth name (geboortenaam) is de Haas and whose partner's name is Jongeneel.

|Jongeneel-de Haas&de&Haas&&Jongeneel^Irma^^^Mevrouw^^L|

Examples of names requiring more than one iteration of the field where the XPN is applied:

Example 9: Herr Prof. Dr. med. Joachim W. Dudeck

|Dudeck^Joachim^W.^^Dr.med.^^L^^^^^^^ MD ~Dudeck^J.W.^^^Herr Prof.Dr.^^D|

Example 10: Herr Dr. Otto Graf Lambsdorff mdB a.D. According to German law "Adelstitel" like "Graf" or "Baron" belongs to the family name and therefor must be encoded in the family name field separated by blanks.

|Graf Lambsdorff&Graf&Lambsdorff^Otto^^^Dr.^^L~Graf Lambsdorff&Graf&Lambsdorff^Otto^^mdB a.D.^Herr Dr.^^D|

Example 11: Walter Kemper genannt (named) Mölleken

|Kemper^Walter^^^^^L~Mölleken^Walter^^^^^A|

Example 12: Herr Dr. med. Dr. h.c. Egon Maier

|Maier^Egon^^^Dr.med. Dr.h.c.^^L^^^^^^^MD~Maier^Egon^^^Herr Dr.med. Dr.h.c^^D|

Example 13: Herr Dipl.Ing. Egon Maier

|Maier^Egon^^^^^L^^^^^^^ DIPL~Maier^Egon^^^Herr Dipl.Ing.^^D|

Example 14: Frau Gerda Müller geb. Maier, verheiratet seit 16.2.2000

|Müller^Gerda^^^Frau^^L^^^^^20000216~Maier^Gerda^^^Frau^^M|

Example 15: President Adam A Everyman III, president from 1997 until 2001, aka Sonny Everyman

|Everyman^Adam^A.^III^President^^L~^^^^Mr. President^^D^^^^^19970816^20010320~Everyman^Sonny^^^^^A|

Example 16: Michio Kimura

This example doesn’t use title and degrees, but shows the repetition of this name for different purposes.

|Kimura^Michio^^^^^L^I~Kimura^Michio^^^^^L^P~ Kimura^Michio^^^^^L^A|

ClassificationHL7 V2/V3 Datatype Level Template
Open/ClosedOpen (other than defined elements are allowed)
Used by / Uses
Used by 0 transactions and 142 templates, Uses 7 templates
Used by as NameVersion
2.16.840.1.113883.3.1937.777.10.12.5linkactive ADR^A19 - Patient query2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.6linkactive ADT^A01 - Admit/visit notification2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.7linkactive ADT^A02 - Transfer a patient2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.8linkactive ADT^A03 - Discharge/end visit2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.9linkactive ADT^A05 - Pre-admit a patient2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.10linkactive ADT^A06 - Change an outpatient to an inpatient2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.11linkactive ADT^A09 - Patient departing - tracking2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.12linkactive ADT^A12 - Cancel transfer2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.13linkactive ADT^A15 - Pending transfer2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.14linkactive ADT^A16 - Pending discharge2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.15linkactive ADT^A17 - Swap patients2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.16linkactive ADT^A18 - Merge patient information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.18linkactive ADT^A21 - Patient goes on a "leave of absence"2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.19linkactive ADT^A24 - Link patient information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.20linkactive ADT^A30 - Merge person information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.21linkactive ADT^A37 - Unlink patient information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.22linkactive ADT^A38 - Cancel pre-admit2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.23linkactive ADT^A39 - Merge person - patient ID2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.24linkactive ADT^A43 - Move patient information - patient identifier list2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.25linkactive ADT^A45 - Move visit information - visit number2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.26linkactive ADT^A50 - Change visit number2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.27linkactive ADT^A52 - Cancel leave of absence for a patient2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.28linkactive ADT^A54 - Change attending doctor2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.29linkactive ADT^A60 - Update allergy information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.30linkactive ADT^A61 - Change consulting doctor2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.31linkactive BAR^P01 - Add patient accounts2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.32linkactive BAR^P02 - Purge patient accounts2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.33linkactive BAR^P05 - Update account2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.34linkactive BAR^P06 - End account2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.35linkactive BAR^P10 - BAR/ACK -Transmit Ambulatory Payment Classification(APC)2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.36linkactive BAR^P12 - Update Diagnosis/Procedure2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.37linkactive BPS^O29 - Blood product dispense status2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.38linkactive BRP^O30 - Blood product dispense status acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.39linkactive BRT^O32 - Blood product transfusion/disposition acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.40linkactive BTS^O31 - Blood product transfusion/disposition2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.41linkactive CRM^C01 - Register a patient on a clinical trial2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.42linkactive CSU^C09 - Automated time intervals for reporting, like monthly2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.43linkactive DFT^P03 - Post detail financial transaction2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.44linkactive DFT^P11 - Post Detail Financial Transactions - New2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.45linkactive DOC^T12 - Document query2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.59linkactive MDM^T01 - Original document notification2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.60linkactive MDM^T02 - Original document notification and content2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.63linkactive MFN^M02 - Master file - staff practitioner2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.82linkactive OMB^O27 - Blood product order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.83linkactive OMD^O03 - Diet order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.84linkactive OMG^O19 - General clinical order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.85linkactive OMI^O23 - Imaging order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.86linkactive OML^O21 - Laboratory order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.87linkactive OML^O33 - Laboratory order for multiple orders related to a single specimen2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.88linkactive OML^O35 - Laboratory order for multiple orders related to a single container of a specimen2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.89linkactive OMN^O07 - Non-stock requisition order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.90linkactive OMP^O09 - Pharmacy/treatment order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.91linkactive OMS^O05 - Stock requisition order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.92linkactive ORB^O28 - Blood product order acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.93linkactive ORD^O04 - Diet order acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.94linkactive ORF^R04 - Response to query; transmission of requested observation2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.95linkactive ORG^O20 - General clinical order response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.96linkactive ORI^O24 - Imaging order response message to any OMI2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.97linkactive ORL^O22 - General laboratory order response message to any OML2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.98linkactive ORL^O34 - Laboratory order response message to a multiple order related to single specimen OML2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.99linkactive ORL^O36 - Laboratory order response message to a single container of a specimen OML2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.100linkactive ORM^O01 - Order message (also RDE, RDS, RGV, RAS)2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.101linkactive ORN^O08 - Non-stock requisition acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.102linkactive ORP^O10 - Pharmacy/treatment order acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.103linkactive ORR^O02 - Order response (also RRE, RRD, RRG, RRA)2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.104linkactive ORS^O06 - Stock requisition acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.105linkactive ORU^R01 - Unsolicited transmission of an observation message2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.106linkactive ORU^R30 - Unsolicited Point-Of-Care Observation Message Without Existing Order - Place An Order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.108linkactive OSR^Q06 - Query for order status2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.109linkactive OUL^R21 - Unsolicited laboratory observation2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.110linkactive OUL^R22 - Unsolicited Specimen Oriented Observation Message2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.111linkactive OUL^R23 - Unsolicited Specimen Container Oriented Observation Message2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.112linkactive OUL^R24 - Unsolicited Order Oriented Observation Message2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.113linkactive PEX^P07 - Unsolicited initial individual product experience report2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.114linkactive PGL^PC6 - PC/ goal add2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.115linkactive PMU^B01 - Add personnel record2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.116linkactive PMU^B03 - Delete personnel re cord2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.117linkactive PMU^B04 - Active practicing person2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.118linkactive PMU^B07 - Grant Certificate/Permission2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.119linkactive PMU^B08 - Revoke Certificate/Permission2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.120linkactive PPG^PCG - PC/ pathway (goal-oriented) add2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.121linkactive PPP^PCB - PC/ pathway (problem-oriented) add2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.122linkactive PPR^PC1 - PC/ problem add2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.123linkactive PPT^PCL - PC/ pathway (goal-oriented) query response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.124linkactive PPV^PCA - PC/ goal response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.125linkactive PRR^PC5 - PC/ problem response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.126linkactive PTR^PCF - PC/ pathway (problem-oriented) query response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.141linkactive RAR^RAR - Pharmacy administration information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.142linkactive RAS^O17 - Pharmacy/treatment administration2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.143linkactive RCI^I05 - Request for patient clinical information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.144linkactive RCL^I06 - Request/receipt of clinical data listing2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.145linkactive RDE^O11 - Pharmacy/treatment encoded order2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.146linkactive RDR^RDR - Pharmacy dispense information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.147linkactive RDS^O13 - Pharmacy/treatment dispense2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.149linkactive REF^I12 - Patient referral2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.150linkactive RER^RER - Pharmacy encoded order information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.151linkactive RGR^RGR - Pharmacy give information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.152linkactive RGV^O15 - Pharmacy/treatment give2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.153linkactive ROR^ROR - Pharmacy prescription order query response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.154linkactive RPA^I08 - Request for treatment authorization information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.155linkactive RPI^I01 - Request for insurance information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.156linkactive RPI^I04 - Request for patient demographic data2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.157linkactive RPL^I02 - Request/receipt of patient selection display list2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.158linkactive RPR^I03 - Request/receipt of patient selection list2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.159linkactive RQA^I08 - Request for treatment authorization information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.160linkactive RQC^I05 - Request for patient clinical information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.161linkactive RQI^I01 - Request for insurance information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.162linkactive RQP^I04 - Request for patient demographic data2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.164linkactive RRA^O18 - Pharmacy/treatment administration acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.165linkactive RRD^O14 - Pharmacy/treatment dispense acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.166linkactive RRE^O12 - Pharmacy/treatment encoded order acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.167linkactive RRG^O16 - Pharmacy/treatment give acknowledgment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.168linkactive RRI^I12 - Patient referral2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.170linkactive RSP^K21 - Get person demographics response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.171linkactive RSP^K23 - Get corresponding identifiers response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.172linkactive RSP^K25 - Personnel Information by Segment Response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.173linkactive RSP^K31 - Dispense History Response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.174linkactive RSP^Z82 - Pharmacy Dispense Message2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.175linkactive RSP^Z86 - Pharmacy Information Comprehensive2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.176linkactive RSP^Z88 - Pharmacy Dispense Information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.177linkactive RSP^Z90 - Lab Results History2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.180linkactive SIU^S12 - Notification of new appointment booking2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.182linkactive SQM^S25 - Schedule query message and response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.183linkactive SQR^S25 - Schedule query message and response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.184linkactive SRM^S01 - Request new appointment booking2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.185linkactive SRR^S01 - Request new appointment booking2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.193linkactive VXR^V03 - Vaccination record response2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.194linkactive VXU^V04 - Unsolicited vaccination record update2013‑02‑10
2.16.840.1.113883.3.1937.777.10.12.195linkactive VXX^V02 - Response to vaccination query returning multiple PID matches2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.26Containmentactive CON - Consent Segment2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.30Containmentactive CTD - Contact Data2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.50Containmentactive GOL - Goal Detail2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.53Containmentactive GT1 - Guarantor2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.54Containmentactive IAM - Patient Adverse Reaction Information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.56Containmentactive IN1 - Insurance2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.57Containmentactive IN2 - Insurance Additional Information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.71Containmentactive MRG - Merge Patient Information2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.76Containmentactive NK1 - Next of Kin / Associated Parties2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.99Containmentactive PEO - Product Experience Observation2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.101Containmentactive PID - Patient Identification2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.106Containmentactive PRD - Provider Data2013‑02‑10
2.16.840.1.113883.3.1937.777.10.13.139Containmentactive STF - Staff Identification2013‑02‑10
Uses as NameVersion
2.16.840.1.113883.3.1937.777.10.15.5Containmentactive CE - Coded elementDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.18Containmentactive DR - Date/time rangeDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.26Containmentactive FN - Family nameDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.64Containmentactive TS - Time stampDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.83Containmentactive ID - Coded value for HL7 defined tablesDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.84Containmentactive IS - Coded value for user-defined tablesDYNAMIC
2.16.840.1.113883.3.1937.777.10.15.89Containmentactive ST - StringDYNAMIC
ItemDTCardConfDescriptionLabel
hl7v2:XPN.1
FN0 … 1This component allows full specification of the surname of a person. Where appropriate, it differentiates the person's own surname from that of the person's partner or spouse, in cases where the person's name may contain elements from either name. It also permits messages to distinguish the surname prefix (such as "van" or "de") from the surname root. See section 2.A.30, "FN - family name".
Contains 2.16.840.1.113883.3.1937.777.10.15.26 FN - Family name (DYNAMIC)
XPN_dotstype
@Type
0 … 1FFN
@LongName
0 … 1FFamily Name
hl7v2:XPN.2
ST0 … 1First name.
Contains 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMIC)
XPN_dotstype
@Type
0 … 1FST
@LongName
0 … 1FGiven Name
hl7v2:XPN.3
ST0 … 1Multiple middle names may be included by separating them with spaces.
Contains 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMIC)
XPN_dotstype
@Type
0 … 1FST
@LongName
0 … 1FSecond and Further Given Names or Initials Thereof
hl7v2:XPN.4
ST0 … 1Used to specify a name suffix (e.g., Jr. or III).
Contains 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMIC)
XPN_dotstype
@Type
0 … 1FST
@LongName
0 … 1FSuffix (e.g., JR or III)
hl7v2:XPN.5
ST0 … 1Used to specify a name prefix (e.g., Dr.).
Contains 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMIC)
XPN_dotstype
@Type
0 … 1FST
@LongName
0 … 1FPrefix (e.g., DR)
hl7v2:XPN.6
IS0 … 1

Retained for backward compatibility only as of v 2.5. See Professional Suffix component.

Used to specify an educational degree (e.g., MD). Refer to User-defined Table 0360 – Degree for suggested values.


Contains 2.16.840.1.113883.3.1937.777.10.15.84 IS - Coded value for user-defined tables (DYNAMIC)
XPN_dotstype
@Type
0 … 1FIS
@Table
0 … 1FHL70360
@LongName
0 … 1FDegree (e.g., MD)
hl7v2:XPN.7
ID0 … 1A code that represents the type of name. Refer to HL7 Table 0200 - Name type for valid values.
Contains 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMIC)
XPN_dotstype
@Type
0 … 1FID
@Table
0 … 1FHL70200
@LongName
0 … 1FName Type Code
hl7v2:XPN.8
ID0 … 1

Different <name/address types> and representations of the same <name/address> should be described by repeating of this field, with different values of the <name/address type> and/or <name/address representation> component.

Note: This new component remains in "alphabetic" representation with each repetition of the field using these data types, i.e., even though the name may be represented in an ideographic character set, this component will remain represented in an alphabetic character set.

Refer to HL7 Table 0465 – Name/address representation for valid values.

In general this component provides an indication of the representation provided by the data item. It does not necessarily specify the character sets used. Thus, even though the representation might provide an indication of what to expect, the sender is still free to encode the contents using whatever character set is desired. This component provides only hints for the receiver, so it can make choices regarding what it has been sent and what it is capable of displaying.


Contains 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMIC)
XPN_dotstype
@Type
0 … 1FID
@Table
0 … 1FHL70465
@LongName
0 … 1FName Representation Code
hl7v2:XPN.9
CE0 … 1This component is used to designate the context in which a name is used. The main use case is in Australian healthcare for indigenous patients who prefer to use different names when attending different healthcare institutions. Another use case occurs in the US where health practitioners can be licensed under slightly different names and the reporting of the correct name is vital for administrative purposes. Refer to User-defined Table 0448 – Name context for suggested values.
Contains 2.16.840.1.113883.3.1937.777.10.15.5 CE - Coded element (DYNAMIC)
XPN_dotstype
@Type
0 … 1FCE
@Table
0 … 1FHL70448
@LongName
0 … 1FName Context
hl7v2:XPN.10
DR0 … 1

This component cannot be fully expressed. Identified as v 2.4 erratum. Retained for backward compatibility only as of v 2.5. Refer to Effective Date and Expiration Date components.

This component contains the start and end date/times, which define the period during which this name was valid. See section 2.A.20, "DR - date/time range" for description of subcomponents.


Contains 2.16.840.1.113883.3.1937.777.10.15.18 DR - Date/time range (DYNAMIC)
XPN_dotstype
@Type
0 … 1FDR
@LongName
0 … 1FName Validity Range
hl7v2:XPN.11
ID0 … 1A code that represents the preferred display order of the components of this person name. Refer to HL7 0444 – Name assembly order for valid values.
Contains 2.16.840.1.113883.3.1937.777.10.15.83 ID - Coded value for HL7 defined tables (DYNAMIC)
XPN_dotstype
@Type
0 … 1FID
@Table
0 … 1FHL70444
@LongName
0 … 1FName Assembly Order
hl7v2:XPN.12
TS0 … 1The first date, if known, on which the person name is valid and active.
Contains 2.16.840.1.113883.3.1937.777.10.15.64 TS - Time stamp (DYNAMIC)
XPN_dotstype
@Type
0 … 1FTS
@LongName
0 … 1FEffective Date
hl7v2:XPN.13
TS0 … 1The last date, if known, on which the person name is valid and active.
Contains 2.16.840.1.113883.3.1937.777.10.15.64 TS - Time stamp (DYNAMIC)
XPN_dotstype
@Type
0 … 1FTS
@LongName
0 … 1FExpiration Date
hl7v2:XPN.14
ST0 … 1Used to specify an abbreviation, or a string of abbreviations denoting qualifications that support the person’s profession, (e.g., licenses, certificates, degrees, affiliations with professional societies, etc.). The Professional Suffix normally follows the Family Name when the Person Name is used for display purposes. Please note that this component is an unformatted string and is used for display purposes only. Detailed information regarding the contents of Professional Suffix is obtained using appropriate segments in Chapter 15, Personnel Management.
Contains 2.16.840.1.113883.3.1937.777.10.15.89 ST - String (DYNAMIC)
XPN_dotstype
@Type
0 … 1FST
@LongName
0 … 1FProfessional Suffix