XPN: new type code for "patronymic name"
V 2.8 HL7 Proposal
Change Request ID:
File !ame:
Description:
Status:
HL7-Version
Chapter/Section
Sponsoring Person
Sponsoring Business Unit
Date Originated:
Date HL7 approved:
Backward Compatible:
Forward Compatible:
HL7 Status & Date
643
643 XP! patronymic name v01.doc
add a new type code for "patronymic name"
proposed for Phoenix
2.8
2.A.88.7
Frank Oemig
Agfa HealthCare
14/01/10
yes
yes
to be reviewed during January 2010 WGM
Justification Detail
In the Russian environment the concept of "patronymic name" is known and commonly used.
In such a case, an alteration of the father's first name is assigned to the son.
In reality the patronymic name is a part of patient's name so that NK1 for the father is
inappropriate.
In any communication scenario for Russia it is important to indicate this information so that a
separate repetition seems to be the best solution because the current list of components of
XPN does not allow to highlight this information. (A new component seems to be
inappropriate because it is too specific.)
In this case, we need a new type code to introduce this concept.
HL7 Table 0200 - Name Type
Value
A
B
C
D
F
I
K
L
M
N
P
R
S
T
U
Description
Alias Name
Name at Birth
Adopted Name
Display Name
Fathers Name (patronymic name)
Licensing Name
Artist Name
Legal Name
Maiden Name
Nickname /”Call me” Name/Street Name
Name of Partner/Spouse (retained for backward compatibility only)
Registered Name (animals only)
Coded Pseudo-Name to ensure anonymity
Indigenous/Tribal/Community Name
Unspecified
1
Comment
Conformance Levels
Handling it as another repetition allows for using any of the components for that purpose, not
only the given name. (Given it would become necessary.)
Outstanding Issues
none
V3 Implications
In principle, this concept can be applied to V3 as well.
V2 Implications
none
v2.xml Implications
none
2