Stream: shorthand
Topic: how to indicate version 4b ?
Giorgio Cangioli (May 12 2021 at 09:00):
Does SUSHI support version 4b ?
I tried to indicate fhirVersion: 4.1.0, but it fails.
Giorgio Cangioli (May 12 2021 at 09:02):
It works with 'current' but I believe this is taking the latest FHIR build ..
Nick Freiter (May 12 2021 at 13:41):
I'm not seeing an available package for 4.1.0 on http://packages.fhir.org/ or http://packages2.fhir.org/, and since as you mentioned current gets the most recent FHIR build, either 4.1.0 needs to be added to one of the package servers, or you will have to download the package manually and place it in your FHIR cache (~/.fhir). Then when you use it with SUSHI, SUSHI should find it in the cache and not attempt to download it.
Giorgio Cangioli (May 12 2021 at 13:46):
thanks
Chris Moesel (May 12 2021 at 13:46):
@Nick Freiter -- I know that manually putting it in the FHIR cache will keep SUSHI happy, but do you know if the IG Publisher will be happy with it?
Nick Freiter (May 12 2021 at 13:57):
My understanding was the IG Publisher also just looked in the FHIR cache. But I did not have a chance to test it out
Grahame Grieve (May 13 2021 at 00:14):
I will have to investigate why r4b is not available to the package system
Ward Weistra (May 25 2021 at 13:03):
The package server can only pick up packages using new FHIR versions once they are built into Simplifier.net. Currently we're only supporting official FHIR releases in Simplifier.net, so once stable R4B is out and built into the Firely .NET SDK we'll bring it to Simplifier and start publishing those packages.
Normally I'd say you can download them from http://hl7.org/fhir/2021Mar/downloads.html, but it seems those links are 404-ing.
The download links ARE available in the HL7 package feed: http://hl7.org/fhir/package-feed.xml
Gino Canessa (May 25 2021 at 14:12):
You can grab the package off the directory. Specifically, R4B has a core package and an expansions. It does not have some of the 'other' packages (e.g., examples).
Giorgio Cangioli (Jun 21 2021 at 09:21):
I suppose I have locally installed the 4b package
Giorgio Cangioli (Jun 21 2021 at 09:22):
but when I try to compile with sushi it fails..
info Checking local cache for hl7.fhir.r5.core#4.1.0...
info Did not find hl7.fhir.r5.core#4.1.0 in local cache.
info Downloading hl7.fhir.r5.core#4.1.0...
error Failed to load hl7.fhir.r5.core#4.1.0: Request failed with status code 404
error Valid StructureDefinition resource not found. The FHIR package in your local cache may be corrupt. Local FHIR cache can be found at <home-directory>/.fhir/packages. For more information, see https://wiki.hl7.org/FHIR_Package_Cache#Location.
Giorgio Cangioli (Jun 21 2021 at 09:22):
suggestions ?
Chris Moesel (Jun 21 2021 at 12:38):
Hi @Giorgio Cangioli -- I think SUSHI is likely expecting anything > 4.0.x is R5. That's why you see it trying to find hl7.fhir.r5.core#4.1.0. We will need to update SUSHI to special-case 4.1.x as R4B. In the mean time, if you want to hack it, you could probably get away w/ renaming hl7.fhir.r4b.core#4.1.0 to hl7.fhir.r5.core#4.1.0 so SUSHI can find it. Not a good long-term solution, but might fill the gap until we fix it in SUSHI.
@Grahame Grieve -- do we know what the version number of the final R4B will be? I'd like SUSHI to be aware of that too, but it's hard to predict given that there is already a 4.2.0 out there.
Giorgio Cangioli (Jun 21 2021 at 12:50):
Thank you so much @Chris Moesel . I'll follow your suggestion. :-)
Grahame Grieve (Jun 21 2021 at 13:03):
I'll advise
Giorgio Cangioli (Jun 21 2021 at 13:56):
This allowed me to have sushi running, but not apparently the IG publisher...
Publishing Content Failed: Error: the IG declares that is based on version 4.1.0 but this IG publisher only supports publishing the following versions: 1.0.2, 1.4.0, 3.0.2, 4.0.1, 4.6.0 (00:13.0223)
I'll move this to the IG stream
Grahame Grieve (Jun 24 2021 at 09:12):
I believe that R4B will 4.3.0 when published
Grahame Grieve (Jun 24 2021 at 09:48):
note that the R4B package is only available on packages2.fhir.org/packages, not in packages.fhir.org
Chris Moesel (Jun 24 2021 at 12:26):
Ah, OK. Thanks, Grahame. That is helpful on both accounts!
Grahame Grieve (Jun 24 2021 at 12:29):
note also that soon we will be changing the way we do versions
Grahame Grieve (Jun 24 2021 at 12:30):
further drafts of R4B will all be published as 4.3.0-SOMETHING where SOMETHING represents their status as a candidate for R4B. The final R4B will be 4.3.0.
This scheme will apply to all specifications in time
Chris Moesel (Jun 24 2021 at 12:33):
Ah! More in line w/ true semantic versioning. I love it!
Jens Villadsen (Aug 14 2021 at 10:14):
Giorgio Cangioli said:
This allowed me to have sushi running, but not apparently the IG publisher...
Publishing Content Failed: Error: the IG declares that is based on version 4.1.0 but this IG publisher only supports publishing the following versions: 1.0.2, 1.4.0, 3.0.2, 4.0.1, 4.6.0 (00:13.0223)
I'll move this to the IG stream
FYI @Giorgio Cangioli I got it to work
Last updated: Apr 12 2022 at 19:14 UTC
