FHIR Chat · Simplifier and current build · implementers

Stream: implementers

Topic: Simplifier and current build

view this post on Zulip Patrick Werner (Apr 12 2021 at 14:28):

When using the IG Publisher i can checkout the current state of another IG and use the #dev version tag. This is nice if you want to build an IG with dependencies to a current build of another IG.

use-case: the other IG will soon release a new version and my dependent IG should be testable before the release of the needed dependency IG.

view this post on Zulip Patrick Werner (Apr 12 2021 at 14:30):

Otherwise people have to start their IGs with dependencies which didn't change for a long time period.

view this post on Zulip Chris Moesel (Apr 12 2021 at 14:56):

Note that the IG Publisher also allows for using the #current version tag, which will just pull the most recent CI build (if the dependency is registered to use the HL7 FHIR CI auto builder). This is nice since it does not require you (the user) to manually pull down and build the dependency yourself.

view this post on Zulip Patrick Werner (Apr 12 2021 at 17:15):

@Ward Weistra could simplifier support #current as well?
I would see #current as an adhoc package of the current project state available through the fhir package server, the second function would be also querying the CI auto builder output.

view this post on Zulip Ward Weistra (Apr 13 2021 at 09:39):

@Patrick Werner There's many aspects to that:

  • On treating a Simplifier.net project as a #urrent package: The basis for that is there, you can for example already use the resolve URL https://simplifier.net/resolve?scope=NictizSTU3-Zib2017@current&canonical=http://fhir.nl/fhir/StructureDefinition/nl-core-patient to go the page for that canonical in the project. It's not a big step to extend that to being able to depend with your Simplifier.net project on another live Simplifier.net project.
    Note that this scope uses the project URL key instead of the package name, because there is no 1-to-1 linking between a project and package. You can release to multiple package lines from a project and release to the same package line from multiple projects.

  • The next question is of course how we do this cross-platform: Depend on a current Simplifier.net project from within an IG Publisher CI build or the other way around. It's a very different thing from the current package server (because the packages aren't fixed). So should every package/IG development system expose their own build-package API which can be used to resolve these special packages?

Last updated: Apr 12 2022 at 19:14 UTC


An HL7 Website -