Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Consider defaulting values in Instances based on sushi-config.yaml values #1457

Open
jafeltra opened this issue Apr 18, 2024 · 0 comments
Open

Comments

@jafeltra
Copy link
Collaborator

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?

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant