问题
This is in continuation with my other question:
Which DICOM UIDs should be replaced while overwriting pixel data in DICOM?
I am trying to create a new DICOM file (instance) from an existing one, where I change the pixel data.
Form other question mentioned above, I understood what UIDs I need to change.
What other tags except UIDs should I change in order to get a valid DICOM while replacing the pixel data?
UPDATE:
In this case I am working with RT Dose IOD, unfortunately I cannot provide anonymized header but the documentation is describing the attributes.
回答1:
There are a number of DICOM tags that depend on the pixel data. The most common ones are probably the following:
Depending on image dimensions:
Columns/Rows- defines the X/Y dimensions of the imageFrame Number- for multi-frame images, though there are more tags to be adapted depending on the SOP Class- tags that define the physical dimensions of one pixel - depending on the SOP class, this may be
Pixel Spacing,Imager Pixel Spacing, orPixel Aspect Ratio- basically the tag that is already present in your image
Data type related:
Bits Allocated- usually 8 or 16, depending on the number of bytes per data pointBits Stored- the real number of used bits, usually between 8 and 16High Bit-Bits Stored- 1Samples Per Pixel- usually 3 for RGB and 1 for monochrome imagesPixel Representation- 0 for unsigned, 1 for signed dataPhotometric Interpretation- depends on the color model, usuallyRGBfor uncompressed color images, andMonochrome2for b/w images; for compressed data, there is a number of possible values, and also some compression-related tags, but I assume that you are writing uncompressed data
You may also adapt Image Type to be something like DERIVED\SECONDARY\..., and of course the UIDs that are mentioned in the other question.
There are more tags to be considered depending on your SOP Class, but these are probably the basic ones.
来源：https://stackoverflow.com/questions/66132967/which-dicom-tags-other-than-uids-should-be-replaced-while-overwriting-pixel-data