Stream: committers
Topic: Terminology Server trouble?
Jean Duteau (Dec 07 2016 at 19:57):
I'm running the IG Publisher and it appears to be stalling while accessing the terminology server. The connect works, but the step where it is doing expansions is stalling. (I do have Lloyd's "turbo-charged" version of the publisher environment, but I'm hoping that this is something that the regular build also calls and would also stall on.)
Grahame Grieve (Dec 07 2016 at 19:59):
I restarted the server - try again
Grahame Grieve (Dec 07 2016 at 19:59):
well, wait a few minutes and try again - I've moved to a cheaper EC2 unit that makes start up take 3 minutes instead of 30 seconds
Jean Duteau (Dec 07 2016 at 19:59):
:)
Jean Duteau (Dec 07 2016 at 20:03):
thanks, that fixed it
Jean Duteau (Dec 07 2016 at 20:51):
when the IGPublisher is expanding a value set, I'm getting some weird errors that seem to be terminology-related...
Error expanding ValueSet "http://infoway-inforoute.ca/fhir/ValueSet/ca-bodysite: Error unmarshalling resource: Invalid pointer operation"
and
Error expanding ValueSet "http://infoway-inforoute.ca/fhir/ValueSet/ca-bodysite: Error unmarshalling resource: Access violation at address 000000000062144F in module 'FHIRServer.exe'. Read of address FFFFFFFFFFFFFFFF
Grahame Grieve (Dec 07 2016 at 21:03):
can you send me the source for ca-bodysite, and I'll investigate
Jean Duteau (Dec 07 2016 at 21:04):
done via email
Grahame Grieve (Dec 07 2016 at 21:10):
hm works for me
Grahame Grieve (Dec 07 2016 at 21:10):
I
Grahame Grieve (Dec 07 2016 at 21:11):
I'll investigate more later. Which version of the IG publisher are you using?
Jean Duteau (Dec 07 2016 at 23:09):
FHIR Implementation Guide Publisher (1.7.0-10183)
Jean Duteau (Dec 07 2016 at 23:59):
Definitions 1.4.0-8139
Grahame Grieve (Dec 08 2016 at 00:44):
you need to update to the current build
Jean Duteau (Dec 08 2016 at 00:46):
i just did and I get the following error, using the current publisher and the igpack.zip from http://hl7.org/fhir/2016May/igpack.zip:
org.hl7.fhir.exceptions.FHIRFormatError: Error parsing dataelements.xml:Unknown Content exampleCode @ START_TAG seen ... <exampleCode value="text/plain; charset=UTF-8, image/png"/>... @2024:70
Jean Duteau (Dec 08 2016 at 00:48):
of course it works with the latest igpack from build.fhir.org, but I want the STU2 definitions
Grahame Grieve (Dec 08 2016 at 00:51):
the STU2 definitions work just fine. what you want to is the less well supported non-stu2-non-stu3 definitions
Grahame Grieve (Dec 08 2016 at 00:51):
I'll have to do some work for that
Jean Duteau (Dec 08 2016 at 00:52):
ah right, i forget that stu2 is 1.0.2 not 1.4
Grahame Grieve (Dec 08 2016 at 00:54):
@Eric Haas can you please commit the allergy intolerance example you overlooked when you edited the tests/ig10 project
Eric Haas (Dec 08 2016 at 17:58):
@Grahame Grieve fixed that and fixed broken links . (still 6 left) but QA errors which I can't figure out they don't make sense to me since the resources seem valid.
Grahame Grieve (Dec 08 2016 at 18:59):
which IG?
Eric Haas (Dec 08 2016 at 22:22):
the test/ig10
Eric Haas (Dec 08 2016 at 22:24):
btw did you ever get the codesystem in DSTU2 to work. I was considering manually adding it in to Argo -DSTU2 output at the very end if not.
Grahame Grieve (Dec 08 2016 at 22:25):
yeah should work. set up a test case in ig10
Grahame Grieve (Dec 08 2016 at 22:26):
Complete output from Jekyll: jekyll 3.1.6 | Error: Included file '_includes/list-allergyintolerances.xhtml' not found
Eric Haas (Dec 08 2016 at 22:27):
that ( codesystem did not work for me and i tried a versions on SVN before and after my commits. no codesystem fragments are being generated
Eric Haas (Dec 08 2016 at 22:30):
I updated the ig.json to recognize the examples folder and the example source names. Its sound like your ig.json is different.
Grahame Grieve (Dec 08 2016 at 22:44):
it was. so I reverted it, and you still haven't committed ai-example.xml
Grahame Grieve (Dec 08 2016 at 22:45):
and you won't get code systems in v1.0.2 - they'
Grahame Grieve (Dec 08 2016 at 22:45):
they'll be in their value sets
Eric Haas (Dec 08 2016 at 23:51):
1) moved example to resources
2) re codesystems in V2 - OK
Grahame Grieve (Dec 08 2016 at 23:54):
ok all good. is the CodeSystem issue sorted then?
Last updated: Apr 12 2022 at 19:14 UTC
