Stream: IG creation
Topic: Terminology Errors
Sarah Gaunt (Nov 20 2019 at 06:27):
Has something changed with the Terminology server? I'm getting errors I wasn't getting last week and they don't seem to be valid errors e.g.:
unable to find code 772146005 in http://snomed.info/sct for 'http://snomed.info/sct#772146005'
That is definitely a valid snomed code: https://browser.ihtsdotools.org/?perspective=full&conceptId1=772146005&edition=MAIN/2019-07-31&release=&languages=en (I checked both international and US versions in case that might be an issue).
Sarah Gaunt (Nov 20 2019 at 06:29):
Also getting:
Error from server: Unable to provide support for code system http://hl7.org/fhir/sid/cvx
Grahame Grieve (Nov 20 2019 at 06:44):
can you clear your terminology cache and try again?
Sarah Gaunt (Nov 20 2019 at 06:46):
It's the CI build... Have never run it locally - have no cache to clear...
Sarah Gaunt (Nov 20 2019 at 23:04):
@Grahame Grieve still getting these errors in the CI build.
Grahame Grieve (Nov 21 2019 at 04:56):
on my list but I'm at DevDays so basically just building the list at the moment
Grahame Grieve (Nov 24 2019 at 15:56):
can you try again please
Sarah Gaunt (Nov 25 2019 at 04:24):
All errors now gone except for this one: unable to find code 772146005 in http://snomed.info/sct for 'http://snomed.info/sct#772146005'
http://build.fhir.org/ig/HL7/case-reporting/branches/master/qa.html
Sarah Gaunt (Nov 26 2019 at 21:39):
@Grahame Grieve still getting the one SNOMED error... Why does it hate pertussis so much!?
Grahame Grieve (Nov 27 2019 at 04:56):
it's on my list. Have you cleared out your cache?
Grahame Grieve (Nov 27 2019 at 04:56):
it works for me on my local dev tx server, and I restarted the main server just before I flew...
Grahame Grieve (Nov 27 2019 at 04:56):
in transit now
Sarah Gaunt (Nov 27 2019 at 04:57):
I'm not working locally - it's the CI build. Will try again now.
Sarah Gaunt (Nov 27 2019 at 05:10):
Still erroring. Seems odd that it's just that one code...
Grahame Grieve (Nov 28 2019 at 17:37):
fixed
Sarah Gaunt (Nov 29 2019 at 02:18):
Thanks! Tried to rebuild but IG Publisher seems to be failing now (haven't changed anything, just hit the rebuild button).
Fetching:Publishing Content Failed: Error fetching package directly (http://hl7.org/fhir/us/core/3.0.0/package.tgz), or fetching package list for hl7.fhir.us.core from http://hl7.org/fhir/us/core/package-list.json: null (00:12.0633)
Laxmi Singh (Jun 22 2021 at 06:51):
I have added the attached xml file under examples folder in my IG.
ValueSet-DocRef-classcodes.xml
When I run publisher after adding above xml file I get below Error:
image.png
Even when I change url in xml file it gives the same error. What I am doing wrong ??
Rob Hausam (Jun 22 2021 at 12:05):
I've seen this error recently on another IG, even when the terminology server clearly is available, but I'm not sure yet exactly when or why it occurs. @Grahame Grieve?
Grahame Grieve (Jun 22 2021 at 12:49):
some communication error?
Giorgio Cangioli (Jun 22 2021 at 12:57):
I don't know if it is the same problem, but this is what I'm getting now ..
Connect to Terminology Server at http://tx.fhir.org (00:26.0061)
Publishing Content Failed: Unable to connect to terminology server. Error = Error fetching the server's capability statement: Connect timed out (00:43.0384)
Jose Costa Teixeira (Jun 22 2021 at 13:33):
same here. Is the server down?
Jose Costa Teixeira (Jun 22 2021 at 13:52):
@Grahame Grieve
Grahame Grieve (Jun 22 2021 at 13:52):
back
Giorgio Cangioli (Jun 22 2021 at 14:28):
it worked for a while..but now it seems to be down again (same "Unable to connect to terminology server" error)
Grahame Grieve (Jun 22 2021 at 14:39):
well, back. I'm watching it now.
Laxmi Singh (Jun 23 2021 at 05:13):
Is it up now ?
Grahame Grieve (Jun 23 2021 at 07:10):
yes
Last updated: Apr 12 2022 at 19:14 UTC