AOM 1.4 - Archetype.uid a UUID or OID?

Thomas Beale thomas.beale at
Thu Jun 15 18:23:52 EDT 2017

from here 

Two machine identifiers are defined for archetypes. 
The|ARCHETYPE|.|/uid/|attribute defines a machine identifier equivalent 
to the human readable|ARCHETYPE|.|/archetype_id/|.|/semantic_id/|, 
i.e.|ARCHETYPE_HRID|up to its major version, and changes whenever the 
latter does. It is defined as optional but to be practically useful 
would need to be mandatory for all archetypes within a custodian 
organisation where this identifier was in use. It could in principle be 
synthesised at any time for a custodian that decided to implement it.

The|ARCHETYPE|.|/build_uid/|attribute is also optional, and if used, is 
intended to provide a unique identifier that corresponds to any change 
in version of the artefact. At a minimum, this means generating a new 
UUID for each change to:







For every change made to an archetype inside a controlled repository 
(for example, addition or update of meta-data fields), this field should 
be updated with a new UUID value, generated in the normal way.

- thomas

On 15/06/2017 23:09, Bert Verhees wrote:
> Seems that the story is not finished yet. Someone in a project I work 
> made the joke to rename HIER_OBJECT_ID to ANY_KIND_OF_ID, because it 
> can represent almost any type of id.
> What is the official defined purpose of the Archetype.uid property?

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <>

More information about the openEHR-technical mailing list