Talk:Digital Imaging and Communications in Medicine

From Wikipedia, the free encyclopedia

You have new messages (last change).

Looking at the log it seems the image is coming from:

 http://www.dicom-solutions.com/sample/

Is it ok not to referenced the orginal file.

Also the jpg is extracted from the DICOM file, why not referenced directly the original file, which would make more sense.

I am changing "set of standards" to "standard" since the DICOM committee itself refers to it as the "DICOM standard" (see the DICOM Strategic Document.) MrSerif 15:33, 29 December 2006 (UTC)

Contents

[edit] DICOM Data Format

Is it strictly correct to say "DICOM files consist of a header with standardized and free-form fields, and a body of image data"? That is, I thought that there isn't really a header -- just a collection of attributes, some of which contain data that would normally appear in a header and typically one notable one (!) that contains the image data.

Agreed and now done Medconn 13:20, 31 December 2006 (UTC)

[edit] Service Classes

I think this is totally wrong: "DICOM is categorized into two different transmissions; DICOM Store and DICOM Print."

Why just two? Aren't there lots of service classes:

  • Verification Service Class
  • Storage Service Class
  • Query/Retrieve Service Class
  • Study Content Notification Service Class
  • Patient Management Service Class
  • Study Management Service Class
  • Results Management Service Class
  • Print Management Service Class
  • Media Storage Service Class
  • Storage Commitment Service Class
  • Basic Worklist Management Service Class
  • Queue Management Service Class
Yes, though many have never beed used - the major ones are now listed on the main page Medconn 13:20, 31 December 2006 (UTC)
Are they? I only find the very confusing section heading "DICOM Services". When I hear DICOM Services I only think of DIMSE Service (like C-STORE and N-GET). I think we should rename this section "DICOM Service Classes" and give each subsection it proper Service Class name. Alternively we should replace "services" in the heading with something else, like "features". Kr-val 13:30, 4 January 2007 (UTC)

[edit] Application protocol?

Is it true that: "This protocol is an application protocol, it uses TCP/IP to communicate between systems."

Doesn't DICOM specify all of the upper-layer protocols, including application layer, presentation layer, and session layer?

In TCP/IP, there is only an application layer. Application, presentation, & session are in the OSI model, not TCP/IP. Cburnett 02:14, 27 April 2006 (UTC)
And the OSI model has now been officialy retired (at last!) Medconn 14:21, 13 July 2006 (UTC)

[edit] List of modalities

The list of modalities takes up a very large proportion of the article, and adds very little ot the value - should it be removed? Medconn 12:21, 31 December 2006 (UTC)

I gives some insight in what areas DICOM can be applied, but I definitely agree that it is way too long. And it definitely does not fit into the history section. Maybe we could pic only a few? Btw, I plan to add some more info into the history section. Kr-val 13:09, 4 January 2007 (UTC)
Retrieved from "http://en.wikipedia.org../../../d/i/g/Talk%7EDigital_Imaging_and_Communications_in_Medicine_01c5.html"