See discussion in Zulip:
https://chat.fhir.org/#narrow/stream/48-terminology/topic/Defining.20a.20ValueSet.20including.20all.20versions.20of.20a.20CodeSystem

Original Question:

How do I define a ValueSet that allows all codes from all versions of a CodeSystem, e.g.
if I have multiple versions of ICD-10 and thus multiple CodeSystem resources with the same url=http://hl7.org/fhir/sid/icd-10-de but different versions ("2017", "2016" etc) .
The proper Version always depends on context (like encounter admission date), so when profiling, I don't want to bind to any particular version of the catalogue, just to icd-10 in general.

How do I define a valueSet that includes all ICD-10 Codes regardless of version? Do I need to include all versions explicitly , like

<compose>
<include> <system value="http://hl7.org/fhir/sid/icd-10-de" /> <version value = "2017"/> </include> <include> <system value="http://hl7.org/fhir/sid/icd-10-de" /> <version value = "2016"/> </include> <include> <system value="http://hl7.org/fhir/sid/icd-10-de" /> <version value = "2015"/> </include> ... </compose>

or do I just omit the version altogether and the tx server will automagically expand the valueset to include all versions?

Suggestion to resolve:

*Lloyd McKenzie*5:28 PM

This seems like something that should have an easier convention. It's also problematic if you want to allow for future versions as you can't really reference those in advance and it would be challenging from a maintenance perspective to have to update the value set every time a new version comes out. We have a convention for referencing versions of [canonicalURL]|[businessVersion]. Would it make sense to use a convention of [canonicalUrl]|* if you wanted to include all versions? Obviously those who want a particular range of versions would need to enumerate, but this would cover a lot of use-cases.