Datatypes R2 Issue 78

Data Types Issue 78: PQ coding rationale

This item had been discussed and resolved of by a Vocab / DataTypes meeting in January 2004 WGM. Unfortunately I have no record of the actual motion and resolution. Someone needs to look for the minutes of Vocab if any exist.

Introduction

PQ is modeled using a CNE unit code which is a CS and in the XML ITS is an attribute.

 <quantity value="200" unit="g"/>

Other unit codes are supported as PhysicalQuantityRepresentation (PQR) which is a CE with the addition of a value on every level of translation (because unit translations commonly necessitate value transformations.)

 <quantity value="200" unit="g">
   <translation value="200" code="GMS" codeSystem="&theirunits;"/>
 </quantity>

 <quantity value="200" unit="g">
   <translation value="7" code="OUNCES" codeSystem="&theirunits;">
     <translation value="7" code="[oz_av]" codeSystem="&UCUM;" xxx="S">
       <translation value="200" code="GMS" codeSystem="&theirunits;">
     </translation>
   </translation>
 </quantity>

Issue

How to distinguish the source of the standard unit?

• In CE translation order determines source and translation (translation is always "nested" inside the source.)
• In the CE, the code in the standard-complient code system can appear anywhere in the nesting.

Possible Solutions

Add a property, e.g., "codingRationale" or "use" code of type SET<CS> with the following table:

• O - originally produced code
• P - post-coding from free text source
• R - required standard code for HL7
• S - source of effective standard code for HL7

Links

Back to Data Types R2 issues