...
- retain CLUSTER and ELEMENT classes, since they remain useful, are already defined, and map cleanly to 13606-1
- support efficient, shortest possible path to a summary data item (e.g. 'smoking status' = Smoker)
- ensure that if the summary item is added at runtime, e.g. by populating the new CLUSTER.value attribute, the paths of the underlying detailed items don't change
- ensure that if an ELEMENT is changed to a CLUSTER at runtimearchetype design time, the path of the value attribute does not change - means that AQL queries are preserved.
Changes
The value properties from ELEMENT are moved to ITEM.
Diagram
The following shows the adjusted CLUSTER/ELEMENT part of the model. 
Impact Analysis
Component | Impact |
|---|---|
On RM |
|
On existing archetypes |
|
On archetype tooling |
|
On existing RM-1.0.2 based software |
|
On existing RM 1.0.2 data |
|
...