FHIR Chat · adding special-url parameter? · shorthand

Stream: shorthand

Topic: adding special-url parameter?


view this post on Zulip Bob Milius (May 02 2020 at 15:10):

Is there a FSH way to add the special-url parameters in the build/input/ImplementationGuide-foo.json file?

view this post on Zulip Chris Moesel (May 04 2020 at 17:30):

Hi @ Bob Milius -- we're working on a much more robust approach to configuration, due to be released in the next few weeks. This will give you control over all the parameters in the IG JSON file. Until then, SUSHI doesn't provide a suitable way to do what you're asking. You would need to edit the IG JSON after SUSHI generates it. If you're skilled at writing scripts, you could probably write a quick script to do this for you.

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:39):

I had a related question - possibly related to the approach you may take:
will sushi a) merge or b) overwrite the IG?

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:40):

I think merge is better, because in some cases we cannot edit the ig after sushi is done with it and before the publisher picks it up

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:42):

(sorry for slightly deviating from the topic but my question is similar, only a bit more generic - IGs will have several other parameters besides special urls)

view this post on Zulip Chris Moesel (May 04 2020 at 17:45):

@Jose Costa Teixeira -- initial implementation will overwrite, but the new approach should give you control over pretty much everything in ImplementationGuide, so there shouldn't be too many reasons you'd want to maintain another instance of ImplementationGuide separate from the SUSHI configuration that defines all the IG values. Basically, what I'm trying to say is that the new config should have 100% coverage of the whole IG resource.

There may be use cases (or preferences) for another approach (like merging), but given the inherent complexity in such a thing, we prefer to wait until people have tried the new approach to see if there is demand for a merging strategy.

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:46):

i don't want to make my IG in sushi - is that allowed?

view this post on Zulip Chris Moesel (May 04 2020 at 17:48):

If you just want SUSHI to generate profiles, extensions, value sets, etc but not generate the ImplementationGuide JSON or do any of the other IG magic, then yes, that is allowed. If you're asking for SUSHI to generate all those things and merge them into an existing IG JSON then that's not something we've considered, but it is something we could consider as some sort of hybrid strategy.

view this post on Zulip Chris Moesel (May 04 2020 at 17:49):

E.g., generate definitional and instance files and update IG JSON w/ references to them, but don't do anything else IG related (pages, menus, etc).

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:52):

If you just want SUSHI to generate profiles, extensions, value sets, etc but not generate the ImplementationGuide JSON or do any of the other IG magic, then yes, that is allowed. If you're asking for SUSHI to generate all those things and merge them into an existing IG JSON then that's not something we've considered, but it is something we could consider as some sort of hybrid strategy.

No, I just want sushi to run when being called by the publisher with the genonce.bat, without changing the content I already have there - resources, pages, menu, templates, etc.

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:53):

is that how it works when it is being called by the publisher? It just generates sushi artefacts and does not do the rest?

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 17:53):

If so, I think it works

view this post on Zulip Chris Moesel (May 04 2020 at 18:00):

is that how it works when it is being called by the publisher? It just generates sushi artefacts and does not do the rest?

I'll have to check, but I think the answer is "no". Right now, it assumes that if it is being called by the IG publisher then you want the IG features. But that's just what it does right now and is not necessarily how it must be. Part of this is also because SUSHI was initially built assuming that you were building into a clean (empty) folder, so workflows where you purposefully build into existing folders with existing files can cause some issues since it breaks that original assumption.

view this post on Zulip Jose Costa Teixeira (May 04 2020 at 18:03):

Yes, that would be critical because it dictates whether or not my IG should run sushi... I will give it a try to see what it does and the impact - I will post the result in the other stream (integration) - thanks!


Last updated: Apr 12 2022 at 19:14 UTC