Change GENERIC_ENTRY data attribute type from ITEM_TREE to the abstract ITEM class

Description

When transforming archetypes from other standards to openEHR the obligation of creating an ITEM_TREE implies a semantics that in origin may not be the case. Instead generic CLUSTERS and ELEMENTS should be allowed, as grouping classes like clusters or organizers are usually optional in other standards.
e.g. if we have originally An ENTRY->ELEMENT subtree then an empty ITEM_TREE must be created, when probably we could just reproduce the original structure with GENERIC_ENTRY->ELEMENT

Reporter

Diego Bosca

Raised By

Diego Bosca

Components

Affects versions

Configure