Stream: terminology
Topic: ISO 3166
Elliot Silver (Nov 16 2020 at 05:29):
http://hl7.org/fhir/ValueSet/iso3166-1-2 appears to be a FHIR-defined URL for two-character country codes, but using it results in broken links in my IG. What is the correct way to refer to this value set?
Also, is there FHIR-defined value set I can use for urn:iso:std:iso:3166:-2 (subnational divisions)?
David McKillop (Nov 16 2020 at 06:53):
@Elliot Silver the following is how we use it:
<jurisdiction>
<coding>
<system value="urn:iso:std:iso:3166"/><code value="AU"/>
</coding>
</jurisdiction>
Elliot Silver (Nov 16 2020 at 07:14):
Sorry, I wasn’t clear — my issue is binding a CodeableConcept or Coding to those valuesets.
Lin Zhang (Nov 16 2020 at 11:32):
In your profile?
Elliot Silver (Nov 16 2020 at 14:19):
I have a logical model and a questionnaire, and want to be able to bind particular elements (or for the questionnaire, items) to these value sets.
Lin Zhang (Nov 16 2020 at 14:42):
As a newbie for this (I mean myself), I think the binding should be represented in your profile.
Jose Costa Teixeira (Nov 16 2020 at 23:12):
For 3166, the only valuesets I see in the core spec are 2-letter, 3-letter, and numeric
Elliot Silver (Nov 16 2020 at 23:17):
That was what I noticed too. FHIR discusses the 3166:-2 code system, but doesn't seem to create a value set for it.
Elliot Silver (Nov 16 2020 at 23:18):
Separately, the FHIR defined 3166-1-2 value set that appears to be defined, doesn't resolve.
Jose Costa Teixeira (Nov 16 2020 at 23:48):
where are you using it? in which resource is that jurisdiction thing?
Elliot Silver (Nov 16 2020 at 23:50):
I'm trying to set the valueset of a CodeableConcept in a logical model, and the answer value set in a questionnaire.
Jose Costa Teixeira (Nov 16 2020 at 23:51):
I was afraid you'd be using this in the ig.xml
Elliot Silver (Nov 16 2020 at 23:52):
No, using a particular value in the IG jurisdiction seems to work (I think...let me confirm).
Elliot Silver (Nov 17 2020 at 00:06):
Confirmed -- setting the IG jurisdiction to a particular 3166-1 (e.g., CA or CAN) value works.
Jose Costa Teixeira (Nov 17 2020 at 00:09):
My reasoning was: the ig jurisdiction is what determines the snomed release to use, so if that is not the same valueset, it could give errors
Elliot Silver (Nov 17 2020 at 00:10):
Hmm, I did not know that. But I don't think it's related.
Grahame Grieve (Nov 17 2020 at 00:11):
the ig jurisdiction is what determines the snomed release to use
not so - it's a specific configuration item
so if that is not the same valueset, it could give errors
I'd be surprised if the snomed edition was related to 3166 usage.
Grahame Grieve (Nov 17 2020 at 00:11):
how do I reproduce this?
Elliot Silver (Nov 17 2020 at 00:19):
https://github.com/openhie/covid-ig/tree/es-working -- there are other issues in there right now, but you should be able to see it.
Grahame Grieve (Nov 17 2020 at 04:50):
so this is an internal problem in the generation of the FHIR core NPM package. The next release of the IG publisher will work around it
Elliot Silver (Nov 17 2020 at 05:36):
Thank you.
Last updated: Apr 12 2022 at 19:14 UTC
