Stream: shorthand
Topic: FHIR version
Bas van den Heuvel (Mar 06 2020 at 09:29):
Can I use shorthand/sushi to define and generate STU3 based profiles?
Chris Moesel (Mar 06 2020 at 13:08):
In theory, there's nothing about the shorthand language that is tied to any specific version of FHIR (except maybe that DSTU2 does not have CodeSystems). SUSHI, however, currently supports R4 only. We felt it was important to nail down the features and functionality in a single version of FHIR before introducing the complexity of multi-version support. We're still working on that (features and functionality) -- so no near-term plans for DSTU2 or STU3.
Bas van den Heuvel (Mar 09 2020 at 08:08):
thx Chris
Catherine Hosage Norman (Mar 09 2022 at 16:57):
What is the version number for the current build? If I use 5.0.0-snapshot1 I get "Accessing non-existent property 'INVALID_ALT_NUMBER'..." if I use "current" I get "error The sushi-config.yaml must specify a supported version of FHIR...." if use 4.6.0, I get the May 2021 ballot version.
Chris Moesel (Mar 09 2022 at 17:01):
Hi @Catherine Hosage Norman. What version of SUSHI are you using? I'm using SUSHI 2.3.0 and both fhirVersion: 5.0.0-snapshot1 and fhirVersion: current work for me. 5.0.0-snapshot1 is preferred since I don't think the IG Publisher doesn't actually supports current.
Catherine Hosage Norman (Mar 09 2022 at 17:10):
See the log attached sushi-runs.txt
Chris Moesel (Mar 09 2022 at 18:00):
OK. I see now. So a couple of things.
First, don't worry about INVALID_ALT_NUMBER. That's an issue that happens w/ Node 14 and above, but does not affect the output of SUSHI. You can safely ignore it.
Now, on to the error you get when running the IG Publisher. I see this in your log:
Run Sushi on C:\FHIR-us-pq-cmc (00:00.0023)
Sushi: npx: installed 901 in 117.697s (02:01.0587)
Sushi: info Running SUSHI v2.0.0-beta.3 (implements FHIR Shorthand specification v1.1.0) (02:02.0428)
Notice that the last line says it is running SUSHI v2.0.0-beta.3. That's not the SUSHI you want. I bet you have a fsh.ini file in that folder that specifies a different SUSHI version. If that's the only thing in the fsh.ini file, then I recommend just deleting that file. If the fsh.ini also has another property (e.g., setting a timeout) then you can just remove the line that specifies the old SUSHI version.
Elliot Silver (Mar 09 2022 at 18:08):
Chris Moesel said:
First, don't worry about
INVALID_ALT_NUMBER. That's an issue that happens w/ Node 14 and above, but does not affect the output of SUSHI. You can safely ignore it.
@Chris Moesel , would it be helpful to put a message in the output indicating that that message can be ignored? Is there a way to intercept the (I assume) stderr output, and filter that message out? I think it trips up every new user until they learn they can disregard it.
Chris Moesel (Mar 09 2022 at 18:20):
@Elliot Silver -- I don't think we can easily intercept it (although I haven't looked into it). We could potentially detect the Node version and output a message saying you can ignore it... We're working on a SUSHI 3.0 that will require Node 14 and above and will also remove the INVALID_ALT_NUMBER message -- but it's not ready quite yet.
Catherine Hosage Norman (Mar 09 2022 at 23:50):
I am getting this message
Publishing Content Failed: Error Parsing File C:\FHIR-us-pq-cmc\fsh-generated\resources\ImplementationGuide-hl7.fhir.us.pq-cmc.json: C:\FHIR-us-pq-cmc\fsh-generated\resources\ImplementationGuide-hl7.fhir.us.pq-cmc.json (The system cannot find the file specified) (00:05.0993)
The IG tool is looking for this file: ImplementationGuide-hl7.fhir.us.pq-cmc.json It is named ImplementationGuide-pqcmc_ig.json
What controls the name of the output json file?
Catherine Hosage Norman (Mar 10 2022 at 01:40):
Found it in the ig.ini file. Next problem:
onGenerate.jira.setup:
[xslt] Processing C:\FHIR-us-pq-cmc\template\onGenerate-ig-updated.xml to C:\FHIR-us-pq-cmc\template\properties.txt
[xslt] Loading stylesheet C:\FHIR-us-pq-cmc\template\scripts\onGenerate.genProperties.xslt
When using the HL7 template, the IG id must start with "hl7." - found pqcmc_ig
[xslt] C:\FHIR-us-pq-cmc\template\scripts\onGenerate.genProperties.xslt:35:7: Fatal Error! Processing terminated by xsl:message at line 35 in onGenerate.genProperties.xslt
[xslt] Failed to process C:\FHIR-us-pq-cmc\template\onGenerate-ig-updated.xml
Publishing Content Failed: Fatal error during transformation using C:\FHIR-us-pq-cmc\template\scripts\onGenerate.genProperties.xslt: Processing terminated by xsl:message at line 35 in onGenerate.genProperties.xslt; SystemID: file:/C:/FHIR-us-pq-cmc/template/scripts/onGenerate.genProperties.xslt; Line#: 35; Column#: 7 (03:23.0637)
(03:23.0641)
This error was created by the template (03:23.0644)
Chris Moesel (Mar 10 2022 at 02:39):
Ooohhh... Jira file issues are definitely not my strength. I'm going to have to summon @Lloyd McKenzie and @Jose Costa Teixeira for that one.
Lloyd McKenzie (Mar 10 2022 at 03:33):
The id and package-id of your IG need to be hl7.fhir.us.pq-cmc.
Chris Moesel (Mar 10 2022 at 04:32):
@Catherine Hosage Norman -- If you have a sushi-config.yaml file, then this means you want to set its id to what Lloyd suggested. E.g.:
id: hl7.fhir.us.pq-cmc
If you allow SUSHI to create your ImplementationGuide, then this will affect the _name_ of your ImplementationGuide file (since it has the id in its name). And if the ImplementationGuide file's name changes, then you need to update the path in ig.ini to reflect that.
Catherine Hosage Norman (Mar 10 2022 at 05:25):
Well, that is sorted out. It is processing. Still running, but I am calling it a night. Thanks for your help.
Martin Höcker (Mar 10 2022 at 12:10):
Random idea from the side: Maybe sushi could emit a warning if fsh.ini specifies a different sushi version? I have sushi installed globally (most people do, I believe), and I have run into issues with sushi-versions when switching between projects...
Chris Moesel (Mar 10 2022 at 13:14):
Hi @Martin Höcker -- soon SUSHI will check to see if you are running the most recent version and display a message if a more recent version is available. I expect that will help a lot with things like this.
Michaela Ziegler (Apr 06 2022 at 08:57):
(deleted)
Last updated: Apr 12 2022 at 19:14 UTC
