Separate code list from the model to make their lifecycle management independent

Why? In such a way, the lifecycle of the model and the code list are dependant additionally, reusing the code list becomes less convenient

SEMIC PwC Comment: In the current model the code lists are directly included in the model. As such, the lifecycle of the model and the code list are dependant. Additionally, reusing the code list becomes less convenient. Therefore, it is recommended to decouple code lists from the model and publish them separately. Ideally, code lists are published by the Publications Office of the European Union.

University of Bologna’s Comment Using a closed vocabulary is fundamental for having templates of Reporting Requirements and standard queries