Modification criteria and versions

From Clinical Building Blocks
Jump to: navigation, search


While the currently available building blocks cannot cover all aspects of clinical care, and thus new building blocks will be needed in the future, the team focuses on the adaptation and implementation of the existing work by the NFU and NICTIZ. The modification criteria and versioning that will be used within the Belgian adaptation project will align as much as possible with the modification criteria and versioning used in the Dutch NFU-NICTIZ project "Zorginformatiebouwstenen".

The Modification criteria and versions

The functional manager decides, if necessary in consultation with the proposer and a Core Group member who is an expert in the area concerned, what should be done with the proposer's modification proposal. Depending on the outcome, the version number of the clinical building block will be raised. There are four possibilities:

Situation Settlement Version number
A – No change The proposal is accepted as notified but leads to no change. It may be set aside for consideration for inclusion in a future version. Not applicable
B – Minor change The change that results from the proposal has little or no impact (e.g. non-substantive changes) or concerns a clear bug fix. In this last case the impact is not expected to be large, because the proposer was already aware of the fault. The digit after the point (the 'minor' version number) is raised. For example, from 1.4 to 1.5.
C – Major change within the scope of the project Other, larger changes must be approved by the CBB Core Group. This concerns fundamental changes, additions, removals, etc. This applies both to modifications to the information model and to changes to the content of the clinical building blocks. If the information model is changed, this almost always constitutes a 'major change'. The digit before the point (the 'major' version number) is raised. For instance, from 1.4 to 2.0.
D – Major change or expansion outside the scope of the project This type of change falls outside the scope of the maintenance process, as described here. How to deal with this (start a separate project?) shall be determined in consultation with the CBB Core Group. Not applicable

See also


  • Fred Smeele, members of the core group on Generic Data for Patient Transfers (01-03-2013) Accompanying document. Products. Generic Data for Patient Transfers, Version: 1.00, NICTIZ & NFU, The Hague, The Netherlands.
  • Fred Smeele, leden kerngroep Registratie aan de Bron (20-03-2015) Begeleidend document Zorginformatiebouwstenen Registratie aan de Bron (Producten Generieke Overdrachtsgegevens en Verpleegkundige uitbreiding), Versie: 2.00, The Hague, The Netherlands.
  • Andra Schmohl, Fred Smeele (20-02-2015) Aanvullende beheersafspraken Zorginformatiebouwstenen Generieke Overdrachtsgegevens, Versie: 1.00, , The Hague, The Netherlands. [1]
  • NEN 7522:2010nl, 2010, Medische informatica-Hanteren van code- en andere terminologiestelsels, NEN, Delft