Stream: committers
Topic: Cached R5 #dev packages?
Chris Moesel (Mar 19 2021 at 16:19):
When we build an IG, the local FHIR cache gets updated with the package result from the local build. For example, building mCODE results in this folder (and contents) being created:
~/.fhir/packages/hl7.fhir.us.mcode#dev/
I've heard reports (here) that the core FHIR build does not do the same (or at least it's not filed under hl7.fhir.r5.core#dev). Does a local FHIR build put a dev package in the FHIR cache somewhere? If so, where?
This is relevant for people who might want to use SUSHI to build a project based on a local versions of FHIR R5. If it's possible, we'd like to support this in SUSHI.
Chris Moesel (Mar 29 2021 at 18:20):
Following this up based on some follow-on conversations to also note that apparently IG Publisher doesn't even support FHIR R5 current version... So even though there is a local current package (which I guess SUSHI made), the FHIR IG doesn't support that either. (Sorry for cross-post, but seemed relevant to note it here too).
Grahame Grieve (Mar 30 2021 at 01:56):
it should create such a package, and getting it to work is on my todo list
Chris Moesel (Mar 31 2021 at 02:55):
OK. And should it be valid for an IG to identify dev or current as their fhirVersion? Those aren't in the value set for fhirVersion and the IG Publisher currently does not accept them. I thought current might work, but apparently not. Is there a different way to identify you want to base your IG on the current build of FHIR or do we have to wait for its version to be bumped to 4.6.0?
Grahame Grieve (Mar 31 2021 at 19:36):
curretn and dev only apply to dependencies on IGs, I think. You have to specify the version of core
Chris Moesel (Apr 13 2021 at 18:57):
This came up again, so just to be sure I understand... If someone needs something that has not yet made it into a published, versioned FHIR Core package (available in the registry), they are just... out of luck?
Lloyd McKenzie (Apr 14 2021 at 04:05):
You mean it's only in the CI-build but not in an official release? Pretty much, yes. Though we do produce connectathon releases 2-3 times per year, so the wait shouldn't be super long...
Chris Moesel (Apr 14 2021 at 12:33):
So I discovered an odd thing yesterday that I had not noticed before. If I indicate the fhirVersion as 4.5.0, the IG Publisher logs it like this:
Core Package hl7.fhir.r5.core#current
So... now I don't know what's going on. If I specify 4.5.0 am I getting "FHIR Release #5: Preview #3" (which is how the publication history labels 4.5.0) or am I actually getting "(last commit)" (which is how the publication history labels current).
Grahame Grieve (Apr 16 2021 at 05:11):
released version
Last updated: Apr 12 2022 at 19:14 UTC
