Stream: IG creation
Topic: VSAC Package
Sarah Gaunt (Mar 13 2021 at 01:33):
@Grahame Grieve how do we get a new version of the VSAC package created? Is there an official process to ask for this? Looking here (https://simplifier.net/packages?Text=vsac&fhirVersion=All+FHIR+Versions) it's been 3 months since one was created and there have been some VSAC changes to urls that we'd like to see reflected in the package (causing some errors in an IG we'd like to move forward with publishing). @David deRoode
Sarah Gaunt (Mar 16 2021 at 20:46):
@Grahame Grieve can we get a new download for VSAC?
Sarah Gaunt (Mar 18 2021 at 19:30):
Does anybody know how we go about getting a new VSAC package downloaded to reference in IGs? @Robert McClure @Carol Macumber @Rob Hausam
Robert McClure (Mar 22 2021 at 17:15):
@Sarah Gaunt If you referring to the download @Grahame Grieve created that pulled all the VSAC content into a FHIR bundle - that was never sanctioned and breaks IP. Given the way the publisher works, I assume that IGs that reference VSAC content need to acknowledge that the content is external and can not be rendered in the published IG. If you mean when is VSAC going to update HL7 content in it's system, that is a different issue.
Sarah Gaunt (Mar 22 2021 at 21:45):
@Robert McClure Yes, I was referring to the download. That download doesn't render the external content in the IG.
What it does is put a nice looking reference to the value set in the profile where it is bound. This:
image.png
Instead of this:
image.png
When you click on the links above you still need to put in your API key to log into VSAC.
Most importantly, though, it gives you the ability to validate a slice (or any required binding) based on codes in the VSAC value set. Thus removing IG publisher errors and allowing validation of values in the VSAC value sets.
So are you saying we aren't getting another more recent download?
Robert McClure (Mar 23 2021 at 19:08):
@Sarah Gaunt Ok, that seems useful. Just think if we simply did that for all value sets and continued to use OIDs as identifiers, so many issues we are dealing with given the desire to have "meaningful uri identifiers" for value sets would go away... but I digress. I'm not familiar with the file that I assume @Grahame Grieve creates to support that but I'd say it does not break any IP so I assume it's a resource timing issue.
Grahame Grieve (Mar 30 2021 at 01:28):
sigh. I can't generate a new package without dealing with the APIKey issue. I will put it on my todo list
Sarah Gaunt (Mar 30 2021 at 02:26):
Ok, thanks. They are just warnings in the QA so I'll suppress them for now...
Sarah Gaunt (Jul 15 2021 at 19:07):
So we are trying to publish an IG that is generating several errors due to the fact that the VSAC package hasn't been updated since VSAC made corrections to some code system identifiers. Is there any chance of getting a new package or can we get a dispensation to publish with the errors. @Grahame Grieve @Lloyd McKenzie @Rick Geimer @David deRoode
Mark Iantorno (Jul 15 2021 at 22:22):
I can publish packages if the changes are committed and ready to go
Sarah Gaunt (Jul 15 2021 at 22:43):
I'm referring to the VSAC package that @Grahame Grieve downloads/creates - can you get that and publish it? Would be awesome if you could... :)
Mark Iantorno (Jul 15 2021 at 22:43):
If this is part of the packages that are used to generate IGs
Mark Iantorno (Jul 15 2021 at 22:44):
Then I was instructed on how to do this
Sarah Gaunt (Jul 15 2021 at 22:44):
It's this package: https://simplifier.net/packages?Text=vsac&fhirVersion=All+FHIR+Versions
Sarah Gaunt (Jul 15 2021 at 22:46):
It hasn't been updated for 7 months and there have been VSAC changes to code system urls that need to be updated in the package (i.e. new download).
Sarah Gaunt (Jul 15 2021 at 22:46):
And probably new value sets for that matter.
Mark Iantorno (Jul 15 2021 at 22:46):
I am unsure if this is part of the packages I can update
Mark Iantorno (Jul 15 2021 at 22:57):
I can update this repo
Mark Iantorno (Jul 15 2021 at 22:57):
https://github.com/FHIR/packages
Mark Iantorno (Jul 15 2021 at 22:57):
Specifically, I do an update here: https://github.com/FHIR/packages/tree/master/packages
Sarah Gaunt (Jul 15 2021 at 23:24):
Yeah, I think this is more about downloading/creating the package from VSAC and then updating that repo maybe? Possibly it needs to be @Grahame Grieve that does it?
Sarah Gaunt (Jul 15 2021 at 23:26):
Though, looking at that repo you just linked to - it looks like Grahame did some updates to VSAC like 3 months ago. Maybe that coudl fix our issue - I'll look into it.
Sarah Gaunt (Jul 15 2021 at 23:30):
And no, it looks like it's still 0.4.0: https://github.com/FHIR/packages/blob/master/packages/us.nlm.vsac/package-list.json which is pretty old.
Sarah Gaunt (Jul 15 2021 at 23:36):
BUT it looks like the content in the actual value set files might be correct.
Mark Iantorno (Jul 16 2021 at 00:22):
I can try and do a release tomorrow?
Mark Iantorno (Jul 16 2021 at 00:22):
do you think that would help?
Rob Hausam (Jul 16 2021 at 02:15):
Grahame has already loaded on tx.fhir.org the latest packages repo update that I committed on June 7 for adding the SNOMED CT GPS value set. It doesn't look like there was anything from VSAC that has been committed after that.
Robert McClure (Jul 18 2021 at 02:45):
Folks, I suspect that in part this is in limbo because technically that package violates VSAC and UMLS IP. I've told Graham he should not be using it and I also understand you all need something like this. It is a clash wrt user access to the NLM tool suite. I'd suggest those of you who need this complain to NLM (https://support.nlm.nih.gov/support/create-case/) indicating there needs to be a non-user-specific access to VSAC content available to support FHIR publishing. I know that with the R4 FHIR changes they added open access (no login needed) for RxNorm code system-based value sets. Same is true for COVID-19 content. But I'd agree that is pieccemeal and difficult.
Unfortunely the correct technical approach is to treat all the VSAC content that is not open access as unavialble when publishing.
Sarah Gaunt (Jul 19 2021 at 02:51):
I checked the package and it may be up to date (at least it seems to have the correct code system identifier). Our issue may be because we are waiting for the THO update (the code system in question hasn't been updated there yet so I think that mismatch is causing errors). I think that is going to be sorted when Grahame gets back from his holiday.
Grahame Grieve (Oct 21 2021 at 04:47):
@Sarah Gaunt what IG do you have the references vsac?
Sarah Gaunt (Oct 21 2021 at 04:50):
eCR, BFDR, Vital Records Common Profiles
Eric Haas (Oct 23 2021 at 01:38):
US Core does too.
Last updated: Apr 12 2022 at 19:14 UTC
