This wiki has undergone a migration to Confluence found Here

P579 Remove inappropriate Universal ID Types from Table 0301

From HL7Wiki
Revision as of 18:49, 14 April 2008 by Ajulian (talk | contribs)
(diff) ← Older revision | Latest revision (diff) | Newer revision → (diff)
Jump to navigation Jump to search

This is a page of type Category:InM Closed Action Items.

P579 Remove inappropriate Universal ID Types from Table 0301

Sponsoring Person

 Harry Solomon


Remove inappropriate Universal ID Types from Table 0301, and change examples in Section 2.A.33.


Accepted by INM on motion by __/__ (00-00-00)


Table 0301, used in the EI and HD data types and derivative data types, identifies an Assigning Authority for instance IDs. Several defined values are inappropriate, or require comments:

HCD: The CEN Healthcare Coding Scheme Designator (in accordance with CEN EN 106:2005, which by the way has not yet been implemented), does not identify an Assigning Authority, but rather a Coding System for concept IDs. The distinction is clear in the text of Section 2.A.33: The "assigning authority" defined by the HD is similar in its role to the coding system (and version) part of the coded element data types: both identify a set of more discrete instance identifiers. The difference is that the set of HD-defined discrete instances contain identifiers of "real-world" things such as patient or clinical orders, while the coded element-defined set of discrete instances contains concept identifiers (codes).

HL7: HL7 has not established its own scheme for identifying Assigning Authorities, but rather assigns ISO OIDs for that purpose.

Random: A randomly assigned identifier for an Assigning Authority is semantically identical to a local identifier. Random identifier assignments apply generally to the instances, not to the Assigning Authority. This should be deprecated.

GUID, UUID: Since GUID is the same as UUID, it should be deprecated as it is an arbitrarily different method of encoding the same information. Further, the 8-4-4-4-12 canonical representation should be recommended.

Proposed Solution:

The solution is documented in P579.doc,k and includes changes to Table 301 as well as the examples.