For Profiles, Extensions, ValueSets, and CodeSystems, SUSHI defaults status to what is in sushi-config.yaml. Similarly, in FSHOnly projects, SUSHI will default version to what is in sushi-config.yaml for those entities. The IG Publisher will also set these values, so the IG Publisher handles assigning a default to version in non-FSHOnly projects.
We should consider if it is helpful to assign a default for status and version for Instances with #definition usage that have a status and/or version element. SUSHI already sets a default url for #definition instances based on the canonical from sushi-config.yaml. Is adding status and version defaults helpful? Is this something we should only do in FSHOnly projects? Does the IG Publisher set these values by default? Are there other properties we should consider defaulting if the instance has them, like fhirVersion?
For Profiles, Extensions, ValueSets, and CodeSystems, SUSHI defaults
statusto what is insushi-config.yaml. Similarly, in FSHOnly projects, SUSHI will defaultversionto what is insushi-config.yamlfor those entities. The IG Publisher will also set these values, so the IG Publisher handles assigning a default toversionin non-FSHOnly projects.We should consider if it is helpful to assign a default for
statusandversionfor Instances with#definitionusage that have astatusand/orversionelement. SUSHI already sets a defaulturlfor#definitioninstances based on the canonical fromsushi-config.yaml. Is addingstatusandversiondefaults helpful? Is this something we should only do in FSHOnly projects? Does the IG Publisher set these values by default? Are there other properties we should consider defaulting if the instance has them, likefhirVersion?