Issue 1245: Value Sets for Coded data elements in the PID segment (pids-rtf2) Source: (, ) Nature: Uncategorized Issue Severity: Summary: Summary: PIDS specification has recommended the HL7 PID segment for standard trait names. The data type for many of the traits in the PID segment (like race, martial status etc.) are CE (Coded). An important aspect of achieving interoperatibility is to make a tight connection between coded fields and the coded vocabulary items that are possible values of the field. For example, the field "Sex" might have the allowable set of values: male, female and ambagious. To achieve that goal HL7 has defined value sets for the various coded fields. In most cases the values sets are from existing standard vocabulary like LOINC, UMLS etc. I was wondering - it will be nice if PIDS specifications also recommended the values sets for the coded fields in the PID segment to be the same as recommended by the HL7 standards. Resolution: Revised Text: Actions taken: April 27, 1998: received issue Discussion: received issue End of Annotations:===== Return-Path: Sender: tim@protocol.com Date: Mon, 27 Apr 1998 12:32:57 -0700 From: Tim Brinson Organization: Protocol Systems, Inc. To: Santosh Gandhi , issues@omg.org CC: pids-rtf@omg.org Subject: New PIDS Issue - Re: Value Sets for Coded data elements in the PID segment References: issues@omg.org - please make this a new issue for the PIDS RTF. Thanx. Santosh Gandhi wrote: > > PIDS specification has recommended the HL7 PID segment for standard > trait names. The data type for many of the traits in the PID segment > (like race, martial status etc.) are CE (Coded). An important aspect > of achieving interoperatibility is to make a tight connection > between coded fields and the coded vocabulary items that are > possible values of the field. For example, the field "Sex" might > have the allowable set of values: male, female and ambagious. To > achieve that goal HL7 has defined value sets for the various coded > fields. In most cases the values sets are from existing standard > vocabulary like LOINC, UMLS etc. I was wondering - it will be nice > if PIDS specifications also recommended the values sets for the > coded fields in the PID segment to be the same as recommended by the > HL7 standards. Santosh, I don't know what the HL7 standard recommends or says about value sets. The way I interpret the PIDS spec in relation to HL7 PID is that what ever HL7 2.3 says should be done for the traits defined in the HL7Version2_3 module. If HL7 2.3 recommends value sets for the CE types used in the PID segment then your request may already be granted. We could make it more explicate in the spec though. Tim Return-Path: Date: Thu, 14 May 1998 11:29:34 -0700 From: "Mark Shafarman" To: issues@omg.org, tim@protocol.com, sgandhi@wpmail.code3.com Cc: mshafarm@oacis.com, pids-rtf@omg.org Subject: New PIDS Issue - Re: Value Sets for Coded data elements in the PID segment Tim: I agree with Santosh, it should be specified precisely! Just getting back to PIDS... can you give me an update on the revision process... I'd like to get the events completed as suggested in my document at the SLC meeting... (should I resubmit that?) ...Mark Mark Shafarman mshafarm@oacis.com Tel:415-925-4570 Fax: 415-925-4455 Medical Information Scientist OACIS Healthcare Systems 100 Drake's Landing Rd. Ste. 200 Greenbrae, CA, 94904 >>> Tim Brinson 04/27 12:32 PM >>> issues@omg.org - please make this a new issue for the PIDS RTF. Thanx. Santosh Gandhi wrote: > > PIDS specification has recommended the HL7 PID segment for standard > trait names. The data type for many of the traits in the PID segment (like > race, martial status etc.) are CE (Coded). An important aspect of achieving interoperatibility is to make a tight connection between coded fields > and the coded vocabulary items that are possible values of the field. For > example, the field "Sex" might have the allowable set of values: male, female and > ambagious. To achieve that goal HL7 has defined value sets for the various coded > fields. In most cases the values sets are from existing standard vocabulary > like LOINC, UMLS etc. I was wondering - it will be nice if PIDS specifications > also recommended the values sets for the coded fields in the PID segment to > be the same as recommended by the HL7 standards. Santosh, I don't know what the HL7 standard recommends or says about value sets. The way I interpret the PIDS spec in relation to HL7 PID is that what ever HL7 2.3 says should be done for the traits defined in the HL7Version2_3 module. If HL7 2.3 recommends value sets for the CE types used in the PID segment then your request may already be granted. We could make it more explicate in the spec though. Tim