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

Attachments

2

Activity

Show:

Severin Kohler February 27, 2024 at 8:37 AM

Perfect, that always annoyed me

Thomas Beale May 25, 2015 at 9:17 AM

Yes, seems like an appropriate change.

Ian McNicoll May 25, 2015 at 7:21 AM

I support this.

Koray Atalag May 24, 2015 at 11:56 PM

+1 to Heath

Heath Frankel May 9, 2015 at 5:00 AM

Base don the original intent of the GENERIC_ENTRY, I support the proposal of using ITEM instead of ITEM_STRUCTURE.

Done
Pinned fields
Click on the next to a field label to start pinning.
Details

Reporter

Diego Bosca

Raised By

Diego Bosca

Components

Affects versions

Created May 7, 2015 at 1:50 PM
Updated September 15, 2024 at 10:18 AM
Resolved September 15, 2024 at 10:18 AM