Comment:

An expansion profile should be used only to constrain the value set expansion member set as per the VSD (defined value set), or to support additional metadata for a value set expansion member (code). Current definition allows the VSD expansion to be generated with a code system version other than the one in the VSD (4.11.3.3) or binding AND to exclude codes from a defined value set by excluding inactive codes, post coordinated codes, those not for the UI). To do so (e.g. constrain the VSD expansion) is in effect creating/defining a new VSD.

Summary:

Expansion profile shouldn't allow creating a new VSD