You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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?
The text was updated successfully, but these errors were encountered:
For Profiles, Extensions, ValueSets, and CodeSystems, SUSHI defaults
status
to what is insushi-config.yaml
. Similarly, in FSHOnly projects, SUSHI will defaultversion
to what is insushi-config.yaml
for those entities. The IG Publisher will also set these values, so the IG Publisher handles assigning a default toversion
in non-FSHOnly projects.We should consider if it is helpful to assign a default for
status
andversion
for Instances with#definition
usage that have astatus
and/orversion
element. SUSHI already sets a defaulturl
for#definition
instances based on the canonical fromsushi-config.yaml
. Is addingstatus
andversion
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, likefhirVersion
?The text was updated successfully, but these errors were encountered: