Stream: IG creation
Topic: us.nlm.vsac error
Sarah Gaunt (Nov 13 2020 at 03:47):
Getting the following error:
Load Package us.nlm.vsac#0.2.0
Publishing Content Failed: Error reading ValueSet-2.16.840.1.113883.3.666.5.2259.json from package us.nlm.vsac#0.2.0: Malformed XHTML: Found "" expecting "" at line 1368 column 51 (01:27.0761)
I can't figure out if it's something I'm doing or something wrong with the package. I'm leaning towards not me as that value set (2.16.840.1.113883.3.666.5.2259) isn't used anywhere in the IG I'm trying to build.
This is the first time I've added VSAC as a dependency to one of my IGs. I've used PHINVads, and it seemed to work fine.
Sarah Gaunt (Nov 13 2020 at 03:58):
Actually - could be because I'm running in Trifolia. Will try CI Build...
Sarah Gaunt (Nov 13 2020 at 04:06):
No, it failed in the CI build (thought it might be the API key issue): http://build.fhir.org/ig/HL7/case-reporting/branches/master/failure/build.log
Grahame Grieve (Nov 13 2020 at 04:17):
API Keys haven't happened yet. I'm just been getting the external dependencies in place
Sarah Gaunt (Nov 13 2020 at 04:25):
Rolling back to 0.1.0 to see if that works.
Sarah Gaunt (Nov 13 2020 at 04:25):
Yup - works fine with 0.1.0 rather than 0.2.0
Robert McClure (Nov 13 2020 at 18:03):
@Grahame Grieve Bring me up to speed on the status of the VSAC package. Last we skyped, you were going to stop producing it. Has that changed? If so,
1) Are you continuing to produce and make that file available?
2) Seeing you have mentioned API Key, if it remains available for use, are you determining if the user has a valid license?
3) have you stopped improperly constructing invalid compose definitions for value sets the FHIR API can not retrieve?
Grahame Grieve (Nov 13 2020 at 20:04):
the long term plan is to move the APIKey approach. but that doesn't happen by magic; someone - probably me - has to actually do the work. I don't know when I'll get to it. In the meantime, I will continue to support the existing vsac package, such as it is. Including issuing a new version for fixing whatever this problem is
Eric Haas (Nov 13 2020 at 21:54):
@Sarah Gaunt can you share the dependency in your IG resource
Grahame Grieve (Nov 13 2020 at 21:54):
0.2.0 will work in the next release of the IG publisher
Eric Haas (Nov 13 2020 at 22:01):
or @Chris Moesel is there and example using sushi-config.yaml?
Eric Haas (Nov 13 2020 at 22:08):
nm figured it out:
...
dependencies:
us.nlm.vsac:
uri: 'http://fhir.org/packages/us.nlm.vsac/'
version: 0.1.0
id: vsac
...
Chris Moesel (Nov 13 2020 at 23:17):
I think you should also be able to get away with:
...
dependencies:
us.nlm.vsac: 0.1.0
...
if you don't need to use the id in your IG.
Eric Haas (Nov 13 2020 at 23:26):
I am confused, I thought with package I would not get the login screen for vsac...
image.png
Eric Haas (Nov 13 2020 at 23:27):
but when I implemented it here : http://build.fhir.org/ig/HL7/US-Core/branches/master/StructureDefinition-us-core-careteam-definitions.html#CareTeam.participant.role
Eric Haas (Nov 13 2020 at 23:27):
that is what pops up. This is a non-starter for US Core
Eric Haas (Nov 13 2020 at 23:32):
this is the link I am using: https://vsac.nlm.nih.gov/valueset/2.16.840.1.113762.1.4.1099.30/expansion
Is it supposed to be something else?
Eric Haas (Nov 13 2020 at 23:35):
mmm lemme try : http://vsac.nlm.nih.gov/fhir/ValueSet/{oid} ...
Eric Haas (Nov 14 2020 at 00:03):
OK that works and this is very nice :-)
Last updated: Apr 12 2022 at 19:14 UTC
