FHIR Chat · Location/visibility of us.nlm.vsac package · tooling

Stream: tooling

Topic: Location/visibility of us.nlm.vsac package


view this post on Zulip Morten Ernebjerg (Oct 28 2021 at 08:56):

(My apologies in advance if I am repeating an answered questions - I read a bunch of threads discussing VSAC, but I did not see anything that directly answered this).

The package.json file of the 4.0.0 US Core FHIR package lists a dependency on us.nlm.vsac#0.3.0, but I hit a few obstacles/inconsistencies when trying to actually get this package.

  1. The VSAC package is not listed up as a dependency on the Simplifier page of the US Core 4.0.0 package or on the FHIR registry package page. How come?
  2. I was unable to find it in the FHIR package registry (https://registry.fhir.org/) using manual search. The exact package name or even just "vsac" turn up zero hits, "nlm" returns only some Dutch package with ".nl." in the ID. However, it does seem to be stored somewhere since a Google search lead me to http://fhir.org/packages/us.nlm.vsac/ where the package does seem to be available. Is it because the registry is not informed about these packages?
  3. What is the official place to fetch this package?

view this post on Zulip Morten Ernebjerg (Oct 28 2021 at 12:24):

PS: In the ig-r4.json file of the US core package , I found the dependency declared together with this URL: http://fhir.org/packages/us.nlm.vsac/ImplementationGuide/us.nlm.vsac . However, that does not resolve.

view this post on Zulip Lloyd McKenzie (Oct 28 2021 at 15:05):

@Rob Hausam

view this post on Zulip Rob Hausam (Oct 28 2021 at 15:42):

I'm thinking that @Eric Haas or @Brett Marquard might be the best ones to answer this question? Ultimately the source of truth for VSAC is the NLM site, which requires credentials (should be easily obtainable) to access. But when, how and where this content gets into FHIR package(s) isn't clear to me (yet).

view this post on Zulip Grahame Grieve (Oct 28 2021 at 19:43):

presumably the dependency is not listed on simplifier because simplifier doesn't have the vsac package itself. That would be for firely to comment on. @Marten Smits ?

view this post on Zulip Grahame Grieve (Oct 28 2021 at 19:43):

the package is listed on the backup packages manager: https://packages2.fhir.org/packages/us.nlm.vsac

view this post on Zulip Grahame Grieve (Oct 28 2021 at 19:44):

so simplifier must be rejecting it for a reason, but looking through my email, I don't see any discussion of why it would be doing that

view this post on Zulip Grahame Grieve (Oct 28 2021 at 19:45):

it's on my todo list to get the URLs of the actual implementation guide resources to resolve. this does resolve: http://fhir.org/packages/us.nlm.vsac

view this post on Zulip Alexander Zautke (Oct 28 2021 at 19:48):

CC @Matthijs van der Wielen

view this post on Zulip Marten Smits (Oct 29 2021 at 07:13):

Thanks for the heads up. @Matthijs van der Wielen and the simplifier team are looking into it.

view this post on Zulip Matthijs van der Wielen (Oct 29 2021 at 12:02):

We found the package on Simplifier https://simplifier.net/packages/us.nlm.vsac/0.4.0, it was stuck in processing due to some unexpected versioning(like "C-CDA R2.1 2020-07-13") in some ValueSets in the package. We will fix this in the upcoming release of Simplifier.


Last updated: Apr 12 2022 at 19:14 UTC