Stream: shorthand
Topic: FHIR 4b current build
Giorgio Cangioli (Nov 08 2021 at 17:05):
is there a way to say sushi to use FHIR 4b current build instead of the ballot#1 version ?
David Pyke (Nov 08 2021 at 17:07):
Just set it in the config to use V4.1.0
Jean Duteau (Nov 08 2021 at 17:15):
no, as far as I know, SUSHI and the IG Publisher can only point to the balloted version of R4B (4.1.0)
Gino Canessa (Nov 08 2021 at 17:17):
The way I've done this so far is to manually update my local FHIR cache with the current build.
edit: there should be a thread either in this stream or in #IG creation with the steps, a few of us tinkered with it a while back.
Also, I believe CI builds still don't do that as well, though it hopefully will change soon
Jose Costa Teixeira (Nov 08 2021 at 18:41):
@Giorgio Cangioli If you figure out what to do locally, let me know, we may add it to the github action that you can use if the CI build doesn't support it
Gino Canessa (Nov 08 2021 at 19:04):
@Jose Costa Teixeira Locally, you just need to swap out the 4.1.0 in your local cache for the current build files (core and expansions). I don't think we want to do something like that in a CI build though.
Jose Costa Teixeira (Nov 08 2021 at 19:05):
Right, so it's not downloading a package but it's hacking it's content, right?
Jose Costa Teixeira (Nov 08 2021 at 19:06):
For me, replacing the files in a folder is hacking
David Pyke (Nov 08 2021 at 19:07):
Your a totally elite hackerz if you can copy files.
Gino Canessa (Nov 08 2021 at 19:10):
I agree. I just don't want users going down a path of trying to figure out another process, since it needs to be changed in the build process itself.
edit: lol David, but I think he means "it's not a stable process we want to use", which is what I agree with =)
Giorgio Cangioli (Nov 09 2021 at 09:52):
Thanks all for the suggestions.
Giorgio Cangioli (Nov 09 2021 at 09:55):
Unfortunately I hoped in a 'reliable solution' for a guide for the next January ballot :-)
Jens Villadsen (Nov 09 2021 at 10:22):
You can use this docker image: https://hub.docker.com/layers/163091927/trifork/ig-publisher-base/r4b/images/sha256-5e2ad2dbb8c053a4c3be3f197e885ce1a02d4f11372368e3eee32255ee98f0f0?context=repo
Jens Villadsen (Nov 09 2021 at 10:24):
@Giorgio Cangioli It's used here: https://github.com/hl7-eu/gravitate-health/blob/master/.github/workflows/main.yml
Chris Moesel (Nov 09 2021 at 13:43):
I suspect that if/when the standard HL7 IG Publisher can support a non-ballot version of FHIR R4B, we can make SUSHI follow the same pattern. But until the IG Publisher supports it, it does not make a lot of sense to build special-case logic into SUSHI for it (since it would just fail at the IG Publisher after that).
Last updated: Apr 12 2022 at 19:14 UTC
