-
Notifications
You must be signed in to change notification settings - Fork 1
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
Review extensibility of Value Sets #214
Comments
it really is an exceptional situation when it is fixed. But when it is it is pretty important. I've noticed this in FHIR as well. Essentially fixed valuesets are usually control data that is vital to the meta data or infrastructure or standard itself. but it is not necessarily always the case. |
I agree with that, but I think we might have swung a little too far that direction. For example:
I'd say that one should be fixed. |
good catch. I trust your judgement. Please fix the ones that you feel should be fixed. In practice we will learn if we need to make things more flexible. I suppose we should err on the side of fixed if we cannot foresee any reasonable reason to make it extensible. |
Only a few of our value sets are fixed. Is that correct? I am writing some validation for values, but it may not be worth it...
The text was updated successfully, but these errors were encountered: