# openEHR-13606 harmonization CR regarding CLUSTER/TABLE etc and ENTRY/OBSERVATION (Was: ISO 21090 data types too complex?)

**URL:** https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515
**Category:** Technical (archive)
**Created:** [10 November 2010 04:56 UTC](https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515 "2010-11-10T04:56:06Z")
**Posts on this page:** 2
**Page:** 2

<div class="post-metadata">

### Author: ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)
#### Post date: [15 November 2010 21:29 UTC](https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515/21 "2010-11-15T21:29:11Z")

</div>

Hi Eric

I would always use CLUSTER rather than ITEM for the data and other features  
in other classes. The alternative is to have far more versions of archetypes  
as if you allow element at this point you have to version when cluster is  
necessary (which you could argue it always will be at some time in the  
future).

Cheers, Sam

---

<div class="post-metadata">

### Author: ![system](https://discourse.openehr.org/uploads/default/original/2X/f/f0a1dedb20c42747bddcafd6c7df9db5f34f003c.svg) [@system](https://discourse.openehr.org/u/system)
#### Post date: [16 November 2010 09:53 UTC](https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515/22 "2010-11-16T09:53:05Z")

</div>

Hi Zam! 🙂

I was merely trying to keep most of the same semantic power in the  
change suggestion as when the abstract ITEM\_STRUCTURE (that subsumed  
ITEM\_SINGLE, ITEM\_TREE etc) was used rather than ITEM\_TREE in various  
places in the RM model. But you might be completely correct that it  
would be better to point to CLUSTER rather than it's abstract  
superclass ITEM in some or perhaps even all places in the model where  
ITEM\_STRUCTURE is used today. I guess other people on the list will  
have additional good ideas about this.

Did you have any more info (or link) regarding the "pivot"  
semantics/requirements by the way?

Best regards,  
Erik(!) Sundvall  
erik.sundvall@liu.se [http://www.imt.liu.se/~erisu/](http://www.imt.liu.se/~erisu/) Tel: +46-13-286733

[Previous page](https://discourse.openehr.org/t/openehr-13606-harmonization-cr-regarding-cluster-table-etc-and-entry-observation-was-iso-21090-data-types-too-complex/12515.md?page=1)
