Hi Gilles
Gilles Mevel wrote:
> Question 1:
> Title for the template 2000 in sup 53 is:" Basic diagnostic imaging
> report".
> This title seems confusing because because some of the relationship
> that are suggested in this template (which at first glance is Basic
> SR) are in fact only valid for Enhanced or Comprehensive templates.
> That is the case for example for a code type value inferred from ETID
> 2001. (node 8 and 9). The value type from ETID 2001 are either Image
> type value or Num type value (if a measurement template is invoked.
> This relationship are only valid for comprehensive SR (Image type
> value) or enhanced SR (Num value type).
Quite so ... the template name has nothing to do with the SOP class(es)
required to use it. The name "basic" in the template implies that one
day there will be more advanced templates defined.
In general, a root template like this one may be used with any SOP
class, except that any optional (U) content items can't be used if
the SOP class you choose doesn't support them.
Confusing I know, but we decided we wanted this flexibility and
commonality (i.e. to use the same template with more than one SOP
class).
> Question 2:
> How to interpret EV (1, UCUM,"1") mean in Template fetus (1008)
> column [Value Set Constraint] ?
> What could we expect to get in a SR in such case ?
The problem here is caused by the fact that every NUM value type has to
have units ... we didn't anticipate this problem when sup 23 was defined
and have been debating how to fix it ever since, ranging from defining
a new value type of ORDINAL or similar, or specifying particular units.
See the options discussed in CP 261:
ftp://medical.nema.org/medical/dicom/cp/cp261_01.pdf
In the case you mention we are designating a particular fetus by number
and there are no meaningful units, so we specify units of "unity" as
defined in UCUM; this means that in the data element stream you will
receive a sequence that contains "1" for code value, "UCUM" for CSD and
"1" for code meaning ... obviously you will want to recognize this
special case and not display the units. SR creators must include this
sequence otherwise they would violate the numeric value type macro
requirements.
david
--
David A. Clunie mailto:dclu...@radpharm.com
Director, Technical Operations http://www.radpharm.com/
RadPharm Work 609-924-1067 Fax 609-924-2094
335 Wall Street Home 570-897-7123 Fax 425-930-0171
Princeton NJ 08540 http://www.dclunie.com/
