Request from the IPS Coordinating Committee - IPS-191 IHE to assess the implications of any person.name changes

[Michael Nusbaum]

Hello, IHE colleagues.

As you may know, I represent IHE International on the Joint Initiative Council’s (JIC) IPS Coordination Committee (IPSCC).  A JIRA ticket has been raised that has been forwarded to IHE for comment.  Click on “View Issue” below to see details, plus all of the commentary provided by IPSCC members.  Please advise if the link does not work for you.

Can you weigh in on how we should best represent person names in a non-alphabetic environment?  IHE’s comments will be considered alongside those of the other SDOs participating.

Please provide a response that I can forward by Friday October 31st (Happy Halloween!)

With thanks,

Mike.

___________________________

Michael Nusbaum

M.H. Nusbaum & Associates Ltd.

81 Howe St., Victoria BC Canada V8V 4K2

Home/Office: +1-250-384-0001

Mobile: +1-786-603-9137

mic...@mhnusbaum.com

www.mhnusbaum.com

IHE to assess the implications of any person.name changes  View issue

[Michael Nusbaum]

My apologies… I’ve been advised that you aren’t able to access the JIRA text directly.  I’ve copied it all below:

Key details

Description

We request clarification in regards to https://jira.hl7.org/browse/FHIR-51419. ISO states under Person.name:

“In case of non-alphabetic representations of the names, at least one alphabetic representation SHALL be provided.” Can this requirement be programmatically enforced? And if so, how is it intended? The most common text encoding is UTF-which includes non-alphabetical characters and many languages. Would non-Latin alphabetic characters be acceptable (e.g. cyrillic alphabet) but things like Kanji ( ) would not?

In advance of clarification, the IPS project workgroup is disposing the FHIR IG IPS as shown in ticket https://jira.hl7.org/browse/FHIR-51419, which is to limit guidance. If clarification can be provided, the IPS project at HL7 can re-evaluate how this can best be implemented.

IPS Assessment Questions

All SDO’s to assess the implications of any changes to the person.name requirements on other standards, not just the IPS Artefacts.

We request clarification in regards to [+https://jira.hl7.org/browse/FHIR-51419+|https://jira.hl.org/browse/FHIR-]. ISO states under Person.name: “In case of non-alphabetic representations of the names, at least one alphabetic representation SHALL be provided.” Can this requirement be programmatically enforced? And if so, how is it intended? The most common text encoding is UTF-which includes non-alphabetical characters and many languages. Would non-Latin alphabetic characters be acceptable (e.g. cyrillic alphabet) but things like Kanji ([https://en.wikipedia.org/wiki/Kanji|https://en.wikipedia.org/wiki/Kanji|smart-link] ) would not? In advance of clarification, the IPS project workgroup is disposing the FHIR IG IPS as shown in ticket [+https://jira.hl7.org/browse/FHIR-51419+|https://jira.hl7.org/browse/FHIR-51419], which is to limit guidance. If clarification can be provided, the IPS project at HL7 can re-evaluate how this can best be implemented.

All SDO’s to assess the implications of any changes to the person.name requirements on other standards, not just the IPS Artefacts.

Mike

___________________________

Michael Nusbaum

M.H. Nusbaum & Associates Ltd.

81 Howe St., Victoria BC Canada V8V 4K2

Home/Office: +1-250-384-0001

Mobile: +1-786-603-9137

mic...@mhnusbaum.com

www.mhnusbaum.com