We agree that there is value in providing a mechanism to support auto-population of code displays based on existing terminology. We propose, however, that this would be better implemented as a feature of IG Publisher or FHIR validator rather than a feature of FSH/SUSHI. We propose this for the following reasons: Full implementation of FSH does not currently require any use of a terminology server or complex terminological operations. We are hesitant to add such a requirement for implementers. While the change request suggests that this could be implemented by drawing only on code systems or value sets w/ full code definitions in scope, we feel this would significantly limit the value of such a feature. E.g., it would not work with intentionally defined value sets or popular code systems such as LOINC and SNOMED-CT. Auto-populating code displays would be useful for all FHIR IG projects or FHIR data generators; but implementing in the FSH spec would only benefit FSH projects. Tools such as the IG Publisher and/or FHIR Validator already support terminology operations, so they are already in a prime position to support such a feature. As such, we propose discussing this capability with the FHIR core tooling team to determine a path forward that would work for all projects and use cases. Please submit Git issues against either the IG Publisher and/or Validator to add this as a capability there.