Apologies to those who were not informed that the meeting scheduled for April 1 was postponed due to the Easter holiday.

The agreement to expand the scope of the "middle initial or name" component to "second and further given names or initials thereof" has been confirmed.

The solution to the Dutch "Call-me name" issue to expand the HL7 Table 200 "Name Type" by "N" for "Nickname/Call-me name" has been reviewed by HL7 Netherlands, and they believe that the solution is workable.

Irma still has some concerns about needing an extra XPN component for the Dutch Call-me Name requirement. Klaus explained that we need to be looking for solutions that go beyond local requirements but are globally applicable in core issues such as naming. Electronic transmission of patient demographics across borders is imminent. (The Work Group had previously found consensus on the above.)

Irma/Klaus to seek comment from Mark Shafarman.

It was suggested to expand the Name Type codes (HL7 Table 200) with "N" for Nick Name/Call-me Name/Street Name.

The requirement to enable XPN to identify the context in which a name is used has been identified:

• The initial use case was in Australian healthcare of mainly indigenous patients who prefer to use different names when attending different healthcare institutions.
• Another use case is in family planning clinics where patients often use an fake name or - with problematic implications - the name of a friend
• A different use case is in the US where health practitioners may have been licensed under slightly different names and the reporting of the correct name is vital for administrative purposes.
• Also, some users have implemented systems which keep a record of the source of patient names in combined or merged records (a "name stack"), in case these need to be unmerged at a later date.

It was agreed that a new "Name Context" component be added at the end of XPN. The following datatype components were identified: Context ID, Context Description, Context Type Code & Context Type Description.
Various HL7 datatypes were reviewed and the lack of a "Context Type Code" subcomponent identified. As we do not want to introduce a new datatype, David and Klaus will look to map the requirement into a suitable HL7 data-type. Else we will use CE.

It was agreed that this description is misleading and invites confusion with Next-of-Kin. The actual use for this name-type is "Name part adopted from Partner/Spouse". As this is a means of identifying parts of the Family Name (similart to the Last Name Prefix), it was suggested to add a XPN component for this and obsolete the "P" name type.

It may also be appropriate to add a "Partner/Spouse Family Name Prefix" to cover the use case of a De Jong marrying a De Haas.

• Klaus/David to finalise data type for "Name Context" component.
• Irma/Tom to draft descriptions for "Given Name" and "Second and further Given Names or Initials thereof".
• Irma/Tom to revisit "Call-me Name" issue and contact Mark Shafarman; Klaus to contact Mark.

As we have V2.3.2 Draft publishing requirements, we need to get closure on remaining issues at the next meeting.

• Finalise "name context" component.
• Finalise Partner/Spouse Name components
• Plan for PAFM TC Meeting in Toronto

The next tele-conference is on Thursday, April 15, at 4pm EST, 10pm in Holland and 6am (Friday) in Australia