This wiki has undergone a migration to Confluence found Here

V2 proposal 617

From HL7Wiki
Jump to navigation Jump to search

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

20100120: Tony Julian V2 Proposal 617 Remove L, M, N as Universal ID Types

V 2.8 HL7 Proposal Change Request ID: File Name: Remove_LMN_UniversalIDTypes.doc Description: Status: proposed HL7-Version 2.8 Chapter/Section 2.A.33; 2.C.2.141 Table 0301 Sponsoring Person Harry Solomon Sponsoring Business Unit GE Healthcare Date Originated: 11/25/08 Date HL7 approved: Backward Compatible: Forward Compatible: HL7 Status & Date Justification Detail A Universal Identifier is by definition not a local identifier. There should be no use of L,M, or N as a Universal ID Type. At this point in time, there is no need to have local pseudo-universal identifier schemes for assigning authorities with the availability of OID, UUID, DNS, and URI schemes that are broadly understood and used.

This proposal was submitted as part of the v2.7 Ballot, but ruled that this change should be done through the proposal process for v2.8. Proposal 2.A.33 HD - hierarchic designator … Example 4: Local use only: a HD that looks like an IS data type |LAB1| |RX.PIMS.SystemB.KP.CA.SCA| Note that the syntax of the first component is not defined by HL7 but by the site according to its own needs: the only requirement is that the first component’s structure is allowed by the HL7 string (ST) data type, which is used for values by the IS data type. Example 5: Local identifier using components 2 and 3 only (Deprecated as of v2.8) |^RX.PIMS.SystemB.CA.SCA^M| An alternate way to encode the previous example, illustrating the use of the third component value of "M" (see HL7 Table 0301 - Universal ID type below) to identify a locally-defined identifier set. The second component has the same value as the previous example but is now defined to be a member of a set of allowable values defined by a site for the identifier set “M”. The use of local coding schemes as Universal ID Types is deprecated as of v2.8; assigning authorities should be identified with true Universal IDs. Example 6: Local identifier with 2nd and 3rd components populated. |PathLab^PL.UCF.UC^L| The ‘PathLab’ application is identified by the namespace component but it is also identified by the 2nd and 3rd components, (i.e., by the locally-defined UID system "L"). The two identifiers are equivalent This is a more complex HD in which the middle component, which is locally defined, is itself structured. As with the ISO example above, the middle component’s structure is not defined by HL7 but by the site according to its own needs: the only requirement is that the middle component’s structure is allowed by the HL7 string (ST) data type. Example 76: local identifier and universal ID types: |LAB1^2.16.840.1.113883.^ISO| A HD with an ISO "object Identifier" as a UID and a locally defined system name. Both the first component and the second and third (taken together) refer to the same entity. This example shows that the local value and the universal ID value may be transmitted with a single HD field.

2.C.2.142 0301 - Universal ID type

HL7 Table 0301 - Universal ID type Value Description Comment … L,M,N Locally defined coding entity identifier. Retained for backward compatibility only as of v2.8 …

V3 Implications none v2.xml Implications none

  • 20100120: Tony will notify other tc's. Item will remain open until 2.8 is published.