Re: [IHE/publications] IHE TF-3 Change Proposal 977 (Issue #628)
Oliver Egger
Thopap created an issue (IHE/publications#628)
The change proposal CP-ITI-977 is in status final Text since 2018.
But the corresponding changes
https://docs.google.com/document/d/1ZGQMbiq2uj9Zsb-JXVp9glUoEXclX-n8seems to be missing in the current version
https://github.com/IHE/publications/blob/master/ITI/TF/Volume3/ch-4.2.html#L1970The IHE CP Tracking sheet mention for CP-977 the status of "integrated".
Is there any reason why this is missing or can i simple add a PR to add them?
—
Reply to this email directly, view it on GitHub, or unsubscribe.
You are receiving this because you are subscribed to this thread.
Vassil Peytchev
I have a concern with this CP – the leading zeroes are in my opinion unnecessary, as they are indicators, and nor part of the number. As far as I know, in Europe, 0xx (or 0x, or 0xxx) all designate a regional code, while 00x, 00xx, or 00xxx mean county code. In both cases the code is x, or xx or xxx, the 0 is just the regional designator, just like 00 or the mobile equivalent of + is the country designator. When you list the full country number, the regional designator must be omitted.
Should we disallow leading zeroes in the area/city codes field?
From: iti...@googlegroups.com <iti...@googlegroups.com>
On Behalf Of Oliver Egger
Sent: Saturday, February 7, 2026 12:43 AM
To: IHE/publications <reply+AASNPNFKRFNFJOYQ4I...@reply.github.com>; Thomas Papke <thomas...@icw.de>; Mary Jungers <mjun...@ihe.net>
Cc: IHE ITI Technical Committee <iti...@googlegroups.com>
Subject: [ititech:9994] Re: [IHE/publications] IHE TF-3 Change Proposal 977 (Issue #628)
External Mail. Careful of links / attachments. Submit Helpdesk if unsure.
You are receiving this because you are subscribed to this thread.
Message ID: <IHE/publications/issues/6...@github.com>
--
You received this message because you are subscribed to the Google Groups "IHE ITI Technical Committee" group.
To unsubscribe from this group and stop receiving emails from it, send an email to
ititech+u...@googlegroups.com.
To view this discussion visit
https://groups.google.com/d/msgid/ititech/CAGV710FKqEDYDcxRcGvFYUf5fLcoCCuaHb%2BHzVxLSXL4ySH%2B9Q%40mail.gmail.com.
Mary Jungers
Mary Jungers
Documentation Specialist | IHE International
Integrating the Healthcare Enterprise|IHE.net
Sent: Tuesday, February 10, 2026 11:16 AM
To: Oliver Egger <oliver...@ahdis.ch>; IHE/publications <reply+AASNPNFKRFNFJOYQ4I...@reply.github.com>; Thomas Papke <thomas...@icw.de>; Mary Jungers <mjun...@ihe.net>
Gianluca Pavan
To view this discussion visit https://groups.google.com/d/msgid/ititech/SJ0PR84MB3223149460B142B37F1C4D12FF62A%40SJ0PR84MB3223.NAMPRD84.PROD.OUTLOOK.COM.
Michael Onken
On 11.02.26 Gianluca Pavan wrote:
> I agree with Vassil that the leading zeros are unnecessary plus they
> could lead to a misunderstanding of the phone number.
>
>
> I also noted that in the example
>
> ^PRN^PH^^^^^^^^^^+31 42 1123 4567 (international phone number)
>
> one "^" exceeds
describes the XTN datatype in "Table 4.2.3.1.7-2: Data Types".
Actually, it refers to the HL7 v2.5 XTN data type definition.
The latter requires (e.g. see [1]) that various components for phone
number components are of datatype NM (e.g. XTN.7 Local Number).
However, the examples include the following two entries:
----------------8<----------------------8<--------------------
^PRS^PH^^31^^(042) 1123 4567 (national phone number)
^PRS^PH^^^^+31 42 1123 4567 (international phone number)
----------------8<----------------------8<--------------------
XTN.7 includes spaces which is not permitted in XTN.7's NM datatype
[2].
We encountered related problems in the German EHR (partly XDS-based),
where some users entered spaces in XTN.7 (probably inspired by the
examples) and others failed validating them using off-the-shelve
libraries which validate against HL7 XTN/NM definition.
Maybe the examples should be fixed if one edits the related section anyway.
Note that the ITU E.123 notation for telephone numbers seems to
recommend and sometimes even require spaces...
So one way to go would be to stick with the XTN datatype, fix the
examples and recommend ITU E.123 notation for XTN.12 (Unformatted
Telephone Number) only.
BR Michael
[1] https://hl7-definition.caristix.com/v2/HL7v2.5/DataTypes/XTN
[2] https://hl7-definition.caristix.com/v2/HL7v2.5/DataTypes/NM
Michael Onken
Am 12.02.26 um 18:11 schrieb 'Michael Onken' via IHE ITI Technical
Committee:
> However, the examples include the following two entries:
>
> ----------------8<----------------------8<--------------------
> ^PRS^PH^^31^^(042) 1123 4567 (national phone number)
> ^PRS^PH^^^^+31 42 1123 4567 (international phone number)
>
> ----------------8<----------------------8<--------------------
>
> XTN.7 includes spaces which is not permitted in XTN.7's NM datatype
> [2].
The "+" is fine.
BR Michael