Stream: implementers
Topic: ValueSet extensibility clarification
Joel Francis (Mar 28 2018 at 15:10):
Hi,
I am creating a profile for the NamingSystem resource and find that the ValueSet for jurisdictions doesn’t have all the values that cater to provinces in Canada. What I mean by this is I would like the codes for the jurisdictions to be more province specific ex: CA-ON, CA-AB, CA-BC etc etc.
Because the binding strength is extensible and from what I can infer from the documentation (https://www.hl7.org/fhir/terminologies.html#extensible), I can use my own codes (as show above) for the jurisdiction.code element. To cater to the NamingSystem.jurisdiction.system, I created a CodeSystem resource with the various jurisdiction codes and will have this as the fixedURI.
Is this this the right approach?
Thanks,
Joel
Robert McClure (Mar 28 2018 at 17:13):
@Rob Hausam and @Grahame Grieve Need to chime in here on how we do this exactly, but what needs to happen is the Jurisdiction value set (https://www.hl7.org/fhir/valueset-jurisdiction.html) Needs to be updated to include Canadian ISO 3166-2 codes. Honestly I don't know if the CLD for this value set actually should have all the 3166-2 codes already or not, seems to me it should since 3166-2 codes are a part of 3166. I'm hoping this is not a situation that needs an extension to comply since the codes really should already be in there, so it's an issue of properly expanding the value set definition.
Grahame Grieve (Mar 28 2018 at 18:56):
I don't see that we should think that the jurisdiction value set should include all states of all countries. So in principle, it's not wrong to use codes outside the value set for this case. That's exactly why the binding is extensible, and why extensible bindings exist. If you want to argue that canadian states should be included in the value set, you can. On the other hand, I would expect that Canada does have a defined code system for states somewhere, and you should use that. @Lloyd McKenzie would know that code system
Lloyd McKenzie (Mar 28 2018 at 19:42):
The codes Joel is proposing are actually ISO codes - they maintain codes for most provinces, territories and states
Grahame Grieve (Mar 28 2018 at 20:34):
well, there's a policy question there; we're using USPS codes for US states....
Lloyd McKenzie (Mar 28 2018 at 22:06):
Yeah, but that doesn't scale terribly nicely when you're talking about a separate code system for every country. ISO's much easier to update from and they manage the change process as new states and territories get registered.
Eric Haas (Mar 28 2018 at 22:33):
no new states in the US since 1959 so I don't think that is a concern. Think it would make sense to ask US implementer how much of a pain in the a** would be to use ISO instead of USPS.
Lloyd McKenzie (Mar 29 2018 at 01:04):
Canada added its last territory in 1999. And other countries change things too. It's better if we just use the ISO code system for everything - then we support the codes for all countries and we don't have to worry about managing the updates. Including a US-specific code system in the international binding and not including equivalents for most other countries is problematic.
Joel Francis (Mar 29 2018 at 14:13):
Canada added its last territory in 1999. And other countries change things too. It's better if we just use the ISO code system for everything - then we support the codes for all countries and we don't have to worry about managing the updates. Including a US-specific code system in the international binding and not including equivalents for most other countries is problematic.
Thanks @Lloyd McKenzie
Lloyd McKenzie (Mar 29 2018 at 14:49):
Joel, can you add a change request to make the change to the ISO code system for states/provinces/territories?
Joel Francis (Apr 03 2018 at 14:49):
Joel, can you add a change request to make the change to the ISO code system for states/provinces/territories?
`
Thanks @Lloyd McKenzie - done -https://gforge.hl7.org/gf/project/fhir/tracker/?action=TrackerItemEdit&tracker_item_id=15869
Lloyd McKenzie (Apr 03 2018 at 17:06):
Thanks
Last updated: Apr 12 2022 at 19:14 UTC
