Entity IM usage of CLUSTER instead ITEM_STRUCTURE

Specifications Entity/demographics
1

Hi everybody,
I was recently reading the demographics IM and came across PARTY descendant classes like PARTY, ROLE and CAPABILITY…etc. I notice they depended on ITEM_STRUCTURE, which gave me the idea that even those classes can be archetyped and queried.
Then I came across Entity IM (which i think is the the future of Demographic IM?), I found that ITEM_STRUCTURE was replaced with CLUSTER.

I am new to openEHR so I am sorry If my question is naive, but can anyone explain to me the reasoning and the logic behind that replacement and how it might affect archetyping and quering these classes ?

Thank you in advance

2

It was originally thought that a variety of structures eg list, tree, table woukd be needed but we found that the itemTree pattern was enough .it is structurally identicsl to Cluster which is used widely so this would have been preferred for new specs.

1 Like
3

Thank you for you reply.