FHIR Chat · Own designations for HL7- ValueSet · implementers

Stream: implementers

Topic: Own designations for HL7- ValueSet


view this post on Zulip Katarina (Jun 25 2019 at 13:10):

I want to use the vaueSet address-use (http://hl7.org/fhir/ValueSet/address-use) and need german labels for the codes. How would I add designations?

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:12):

technically, you write a code system supplement providing german displays

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:12):

I believe that HL7 De wishes to publish their own language variants rather than building them into the base spec.

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:12):

further follow ups should go to https://chat.fhir.org/#narrow/stream/179316-german.2Fterminologien

view this post on Zulip Alexander Henket (Jun 25 2019 at 13:18):

technically, you write a code system supplement providing german displays

Is that supposed to work now? I already filed a tracker with a Dutch supplement. At the time we landed on tooling issues around that

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:18):

supposed to work where?

view this post on Zulip Alexander Henket (Jun 25 2019 at 13:19):

In an IG, or even better: supply it to the main builds so we don't have to explain everyone where it is

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:21):

well, I think it works in my terminology server now, but I don't think it does in an IG. I'm not sure what that would actually mean.

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:22):

and I know it doesn't work like that in the base spec - the tooling needs to be updated for supplements. But like I said, I think that HL7 De doesn't want it in the base build anyway

view this post on Zulip Alexander Henket (Jun 25 2019 at 13:28):

We require people to have Dutch texts in their interfaces rather than just accept the displayName of the day. Those Dutch texts need to come from somewhere. For SNOMED CT/LOINC/ICD/ICPC and then some we have it covered. HL7 terminology is the Achilles heel. So we're looking for ways to distribute Dutch terms for HL7 terminology.

Would supplement be of help and what would you recommend for our workflow/distribution flow?

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:29):

well, the first question is whether you want to distribute through HL7 or directly. I would think that you have the infrastructure to do it directly.

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:30):

e.g. as a package. and then you just need terminology servers that process the supplements correctly.

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:31):

I'm not sure what an IG needs. multi-language support is still on my todo list

view this post on Zulip Alexander Henket (Jun 25 2019 at 13:51):

We do not have a terminology server anywhere that would serve that purpose. I could decorate ART-DECOR with it, but then I'd need to make it obvious for people to go there to that end. I mainly need distribution for others to import. Just like ValueSets

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:52):

but it's a terminology server that prepares the distribution for you...

view this post on Zulip Grahame Grieve (Jun 25 2019 at 13:52):

though I do think that distributing expansions is a flawed model

view this post on Zulip Alexander Henket (Jun 25 2019 at 13:53):

Could be, but just like we craft profiles/valuesets/conceptmaps, I'd also need to craft those supplements. I could then import them into a server and subsequently export them from there for distribution, or... I could use the supplements as is

view this post on Zulip Katarina (Jun 25 2019 at 14:04):

Thank you both!


Last updated: Apr 12 2022 at 19:14 UTC