After contentious discussion about implicit value sets, it is clear that improvement in the description of what they are and why they exist and are needed must be more readily apparent for the comunity. The gist is that an implicit value set can be deterministically converted to a formal value set definition (ValueSet.compose) in every case, but is easier for IG reference and implementations. Due to the imposition of possible variability in server behaviors in the interpretation and expansion of this implicit definition, they may be a higher risk of variability in the expansion content for implicit value sets than full formal explicit value sets. in addtion, the questions surrounding 'naked expansions' answered by access to the compose remain open with the lack of a formal compose for implicit value sets. What this means to the community is that the risk of the use of the value set may be higher, which is often the case when an easier to implement alternative ways for do something in an HL7 standard is availabvle. This needs clarification in the documentation.