Stream: IG creation
Topic: Check for supported code systems for urn:iso:std:iso:3166
Rick Geimer (Jul 15 2020 at 02:13):
In case anyone else runs into this, I had trouble with the IG Publisher hanging on the following line:
Terminology server: Check for supported code systems for urn:iso:std:iso:3166
The solution for me was to delete the .fhir directory in my user directory. It still took a long time to run, but it eventually completed whereas previously I had to cancel the publisher after over an hour.
Grahame Grieve (Jul 15 2020 at 02:39):
that doesn't make any sense at all
Grahame Grieve (Jul 15 2020 at 02:40):
sounds to me like you just used up some extra bandwidth
Grahame Grieve (Jul 15 2020 at 02:40):
turn more logging on, and you'll find that you're loading up the terminology cache
Rich Boyce (Jul 31 2020 at 15:05):
Hi there I have been having the exact same issue but removing the .fhir directory and clearing the terminology cache did not resolve the problem for me. I also removed all instances of "jurisdiction" from the value sets located inside /input/resources but I then get a new error "Terminology server: Check for supported code systems for http://unstats.un.org/unsd/methods/m49/m49.htm
java.lang.NullPointerException
at org.hl7.fhir.utilities.Utilities.pathURL(Utilities.java:644)" for jurisdiction located in other ValueSets.
Rob Hausam (Jul 31 2020 at 15:07):
It can take a very long time (it's been taking over 3 hours to rebuild the cache in our IPS IG).
Rich Boyce (Jul 31 2020 at 18:28):
Time doesn't seem to be the issue at least for our situation, the process just fails
Grahame Grieve (Jul 31 2020 at 20:05):
if your problem is that the publisher is unexpectedly taking a long time, clearing the terminology cache will definitely make that problem worse
Rich Boyce (Aug 04 2020 at 19:24):
Hi @Grahame Grieve -- we are not having an issue with how long the terminology cache is taking --- we are having an issue with the publisher not completing the term validation for our IG when all worked before. We have tried lots of things per the thread and tried to migrate to the templated approach. We have even looked into the code to try and figure out what is going on. I fear we are going to miss the ballot deadline b/c we can't build this thing now when it worked fine before. Would you be willing to please check out of IG and see if you can spot something obviouls we might have missed? So sorry to have to ask.
Grahame Grieve (Aug 04 2020 at 21:09):
this is IPS? I built that yesterday based on what is in github
Rob Hausam (Aug 04 2020 at 21:15):
I don't think it's IPS. I just mentioned that as I thought it might be an example of the issue Rick reported and that Rich might have been having.
Last updated: Apr 12 2022 at 19:14 UTC
