Details
Description
I can't find explicit guidance around binding strength and versions. Some of the text inFHIR_Guide_to_Designing_Resources suggests that a (normative) binding to an unversioned value set implies that the set cannot change, but the value set design says that unspecified version just means "get the latest."
Lloyd: If the data type for a fixed binding is "code", you're locked to the version as it was published in the same release as the structure definition. However, it would be good if the tooling made that explicit
1. need clarification: Does "as it was published in the same release as the structure definition" imply that the SD "short" enumeration constrains the values, or that the SD "valueset" is constrained to the edition it's published in? If the latter, it's not articulated in the current syntax.
2. where this clarification should be published: I'd like to see it in datatypes.html#code, but as the type is primitive, there's not a lot of structure there. Perhaps Using Codes in Resources.
Attachments
Issue Links
- mentioned in
-
Page Loading...