Bert picked up an anomaly in this PR that I think should probably be fixed. ARCHETYPE.uid is of type UUID in the AOM2 spec, but of type HIER_OBJECT_ID in the AOM1.4 spec (the latter type is the openEHR type for OIDs). However it appears that all ADL1.4 archetypes that have a uid have it as a Guid (i…

Never saw an OID in any tool I tested and I tested most of the open tools. I would say UUID is the industry standard here :slight_smile:

Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID, ISO_OID or INTERNET_ID. The bigger issue is the HIER_OBJECT_ID is incompatible with UUID from a …

Hi, double checked the specs. Small correction to Heath, AOM 1.4 Archetype.uid is HIER_OBJECT_ID, value have both root: UID and extension: String, more or less an II of HL7. But, he is right, UID can be UUID or OID. Ref: http://openehr.org/releases/1.0.2/architecture/rm/support_im.pdf page 32. A…

Although the OID and UUID as used in the archetypes are (in the most simple (one arc) OID-occurrence) technical interchangeable is their semantical meaning completely different. So what do we want to express here? Is it ever used in the way a OID is meant to be used? (to trace back the organization …

Hi Thomas, Your statement that the use of HIER_OBJECT_ID in the AOM1.4 spec is used for OIDs is incorrect. HIER_OBJECT_ID is a complex type with a value attribute of type UID, which may be either UUID, ISO_OID or INTERNET_ID.

That is right, the loadValue function creates a UUID from the root-value if it has that specific string-pattern. So the root of a

Hi Bert, when using ISO OIDs, UUIDs are not one arc OIDs since they have to start with a specific arc 1. or 2. http://www.oid-info.com/cgi-bin/display?tree=

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?

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 opt…

AOM 1.4 - Archetype.uid a UUID or OID?

Technical (archive)

system (system) 15 June 2017 17:43 9

In 1.4 the description of Archetype.uid saying “OID…” is incorrect. It should say “UID root with no extension”.

Topic		Replies	Views
openEHR artefact namespace identifiers Technical (archive)	26	1	29 April 2011
Usage of Blood glucose archetype for self-monitoring Clinical (archive)	52	22	14 December 2012
archetype UIDs Technical (archive)	4	2	18 November 2014
loss of type information in ID classes Implementers (archive)	18	2	4 March 2007
openEHR-clinical Digest, Vol 11, Issue 3 Clinical (archive)	36	6	9 January 2013
Could the specs group consider making uid mandatory? Technical (archive)	20	11	20 December 2016
poor version management in archetype editor Clinical (archive)	20	4	8 December 2008
RM Versions Technical (archive)	22	4	9 February 2009
VERSIONED_OBJECT<T> uid question Implementers (archive)	6	2	15 September 2008
archetype node_ids again - looking for final solution Technical (archive)	2	3	28 November 2013

AOM 1.4 - Archetype.uid a UUID or OID?

Related topics