[Insight-developers] DICOM 0008:0008

[Miller, James V (GE, Research)]

This is more of question of ITK producing images for review in other
DICOM compliant applications.  While ITK applications can use image
orientation to establish a predominant reformation, other applications
use these DICOM fields for populating the image database.

Perhaps the bigger issue is that ITK ALWAYS writes images as
DERIVED\PRIMARY even if the programmer specifies a different value in
the MetaDataDictionary. 


Jim  
_____________________________________
Visualization & Computer Vision
GE Research

-----Original Message-----
From: insight-developers-bounces at itk.org
[mailto:insight-developers-bounces at itk.org] On Behalf Of kent williams
Sent: Wednesday, April 09, 2008 9:56 AM
To: Mathieu Malaterre; Miller, James V (GE, Research)
Cc: ITK
Subject: Re: [Insight-developers] DICOM 0008:0008

ITK bases orientation on the direction cosines, which would make this
flag
irrelevant with respect to orientation.   It might be useful to know the
original scan direction, but that would require all scanners to set this
flag with an accurate value. I have little confidence in that being the
case.

I would also assume almost all applications with ITK would start with
images of known provenance, if something like the original scan
direction was a crucial datum. It's not the roadside is littered with
MRI scans, that applications have to approach like a detective to infer
where they came from and how they were produced.



On 4/9/08 7:59 AM, "Mathieu Malaterre" <mathieu.malaterre at gmail.com>
wrote:

> On Wed, Apr 9, 2008 at 2:22 PM, Miller, James V (GE, Research) 
> <millerjv at crd.ge.com> wrote:
>> 
>> 
>> 
>> The DICOM Image Type (0008:0008) is usually something like:
>> ORIGINAL\PRIMARY\AXIAL when DICOM files are coming off a scanner.  
>> ITK generated files have the Image Type as DERIVED\PRIMARY.  Should 
>> the Image Type be DERIVED\PRIMARY\AXIAL when appropriate?
> 
> Hi Jim,
> 
>   I am guessing you are talking about a CT Image Storage DICOM object,
right ?
>   AFAIK Value #3 of Image Type is optional, so it should not be needed

> (only the first 2 are required). As a side note there is no way for 
> the ITK ImageIO to detect that the image has not been modified 
> (resliced), so I do not believe we should keep the 'AXIAL' Image Type,

> correct ?
> 
> 
> 2 cents,

_______________________________________________
Insight-developers mailing list
Insight-developers at itk.org
http://www.itk.org/mailman/listinfo/insight-developers