Irma Jongeneel (Holland)

Tom de Jong (Holland)

Robin Zimmerman (USA)

David Rowed (Australia)

Klaus Veil – Moderator (Australia)

1. Review of History and Objectives:

Klaus recalled that this group was formed at the 1999 Orlando Meeting with the goal to prepare a proposal for an internationally acceptable V2.x name datatype based on the XPN. This needs to be completed by Toronto for inclusion into V2.3.2

A number of materials were distributed to the Name group in Orlando:

• A paper "In Search of the Name" by Bidwell/Tracy.
• A proposal by the Dutch delegation outlining their requirements.
• An EMail thread mainly between G. Schadow and F. Hall outlining some issues.

Klaus also pointed out the CEN TC251 paper "Names and Numbers as Identifiers" that has comprehensive coverage of the issue.

The Australian Draft Standard on "Interchange of Client Information" has recently emerged and holds useful information also.

1. Report from V3DT Meetings – What can we use?

Klaus then reported from the recent joint phone conferences with the V3DT Group, which is currently also reviewing the name issue.

The difference with V3 will be a much higher granularity in the naming area. It appears that individual name-parts will be tagged with different "name types" and "name contexts". This does not apply to V2.x where the complete set of components and sub-components has to be repeated within the element. See examples below.

2. What is in V2.3.1?:

The structure of the XPN datatype in the 2.3.1 is:

Components: <family name (ST)> & < last_name_prefix (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) (IS)> ^ <name type code (ID)> ^ <name representation code (ID)>

<name type code (ID)> uses the following table:

Table 0200 - Name type

Value	Description
A	Alias Name
L	Legal Name
D	Display Name
M	Maiden Name
C	Adopted Name
B	Name at Birth
P	Name of Partner/Spouse
S	Coded Pseudo-Name to ensure anonymity
T	Tribal/Community Name
U	Unspecified

Note: The content of Legal Name is country specific. In the US the legal name is the same as the current married name.

The issue of the "Maiden Name" was – again – discussed. Once we move away from its unfortunate cultural overloading, this piece of information is vital. Often it has been the only way a female patient has been able to be trace before and after marriage. Maybe a better name (eg. Name before marriage", "single-name", etc) would help?.

 

^ <name representation code (ID)> selects a name representation mode from the following:

Table 4000 - Name/address representation

Value	Description
I	Ideographic (i.e., Kanji)
A	Alphabetic (i.e., Default or some single-byte)
P	Phonetic (i.e., ASCII, Katakana, Hirigana, etc.)

This allows HL7 to report the same patient’s name both in, say, English and Kanji!

 

3. Use Cases:

Name-part	"display"	"at Birth"
<family name (ST)>	Jongeneel-de Haas	de Haas
<last_name_prefix (ST)>		de
<given name (ST)>	Irma	Irma
<middle initial or name (ST)>	Corine	Corine
<suffix (e.g., JR or III) (ST)>
<prefix (e.g., DR) (ST)>
<degree (e.g., MD) (IS)>
<name type code (ID)>	D	B
<name representation code (ID)>	A	A

<I need help to develop this more...)

 

4. Action Items:

• David to provide use-cases for aboriginal multi-name usage.
• All to review CEN251 document
• Klaus to send out relevant parts of Ch. 2 V2.3.1 (do we need more than the above excerpts?) and Austr. Standard.
• What about the (multiple?) "License name" for physicians in the US?
• What about multiple alaises?