Stream: implementers
Topic: Country Code in ContactPoint
Sean O'Quinn (Dec 03 2020 at 21:56):
The PID segment of an ADT has specific support for a country code. Is there a reason ContactPoint does not have explicit support for a country code? Is the country code just expected to be in the string for the ContactPoint.value?
Vassil Peytchev (Dec 03 2020 at 22:12):
Are you talking about county code or country code? The PID-12 field, County Code, is withdrawn, since all address information (including country code) is now represented in the address by the XAD data type.
Since ContactPoint is for "technology-mediated contact points", I assume you are thinking about the country code in a phone number. In that case, yes, you would have the phone number represented as a sequence of digits, following the + indicator.
Sean O'Quinn (Dec 03 2020 at 22:42):
Vassil Peytchev said:
Are you talking about county code or country code? The PID-12 field,
County Code, is withdrawn, since all address information (including country code) is now represented in the address by the XAD data type.Since
ContactPointis for "technology-mediated contact points", I assume you are thinking about the country code in a phone number. In that case, yes, you would have the phone number represented as a sequence of digits, following the+indicator.
I am talking about the Country Code. PID 40.5 in an ADT.
You did answer my question though concerning the FHIR expectation for the telecom country code
Lloyd McKenzie (Dec 03 2020 at 23:48):
There are standard extensions for breaking out country code, area code, local number and extension from the ContactPoint.value element if needed. (The expectation is that you still send the fully composed string in value though.)
Sean O'Quinn (Dec 04 2020 at 02:16):
Thanks @Lloyd McKenzie ! I didnt catch that extension. Exactly what I needed.
Last updated: Apr 12 2022 at 19:14 UTC
