GDCM

/* Step 4 */ Revision as of 10:42, 13 May 2008 Current revision Line 37: Line 37: Once you hit 'Configure', make sure to turn on: Once you hit 'Configure', make sure to turn on: * GDCM_BUILD_SHARED_LIBS * ... [More] GDCM_BUILD_SHARED_LIBS -this causes the GDCM dlls to be built. You should not change anything else. this causes the GDCM dlls to be built.   * GDCM_BUILD_APPLICATIONS     this causes the GDCM applications to be built (gdcmdump, gdcminfo...).     You should not change anything else, unless you know what you're doing. === Step 5 === === Step 5 === [Less]

/* Things missing from GDCM implementation */ Revision as of 09:32, 7 May 2008 Current revision Line 18: Line 18: ** Fiducials Object ** Fiducials Object ** A Validator (PS 3.3) aka dciodvfy ** A Validator (PS 3.3) aka ... [More] dciodvfy   ** gdcm.PythonDataSet and gdcm.PythonTagToValue are a hack to get around annoying swig issue, need to be fixed ! * Feature request * Feature request ** Papyrus ** Papyrus [Less]

/* Things missing from GDCM implementation */ Revision as of 09:32, 7 May 2008 Current revision Line 18: Line 18: ** Fiducials Object ** Fiducials Object ** A Validator (PS 3.3) aka dciodvfy ** A Validator (PS 3.3) aka ... [More] dciodvfy   ** gdcm.PythonDataSet and gdcm.PythonTagToValue are a hack to get around annoying swig issue, need to be fixed ! * Feature request * Feature request ** Papyrus ** Papyrus [Less]

/* GDCM 2.0.4 */ Revision as of 12:06, 6 May 2008 Current revision Line 112: Line 112: Release: Release: * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575 * ... [More] http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575     === GDCM 2.0.x ===     * reimplement gdcm::UIDGenerator (API is preserved) [Less]

/* GDCM 2.0.4 */ Revision as of 12:06, 6 May 2008 Current revision Line 112: Line 112: Release: Release: * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575 * ... [More] http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575     === GDCM 2.0.x ===     * reimplement gdcm::UIDGenerator (API is preserved) [Less]

/* GDCM 2.0.4 */ Revision as of 12:06, 6 May 2008 Current revision Line 107: Line 107: * gdcm::UIDs implementation * gdcm::UIDs implementation * gdcm::Orientation implementation * gdcm::Orientation implementation     And a ... [More] whole bunch of bug fixes !     Release:   * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575     === GDCM 2.0.x ===     * reimplement gdcm::UIDGenerator (API is preserved) [Less]

/* GDCM 2.0.4 */ Revision as of 13:30, 30 April 2008 Current revision Line 99: Line 99: * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 * ... [More] http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 -=== GDCM 2.0.x === === GDCM 2.0.4 === * Better support for spacing computation in Enhance CT & Enhance MR dataset * Better support for spacing computation in Enhance CT & Enhance MR dataset Line 107: Line 107: * gdcm::UIDs implementation * gdcm::UIDs implementation * gdcm::Orientation implementation * gdcm::Orientation implementation     And a whole bunch of bug fixes !     Release:   * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575 [Less]

/* GDCM 2.0.4 */ Revision as of 13:30, 30 April 2008 Current revision Line 99: Line 99: * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 * ... [More] http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 -=== GDCM 2.0.x === === GDCM 2.0.4 === * Better support for spacing computation in Enhance CT & Enhance MR dataset * Better support for spacing computation in Enhance CT & Enhance MR dataset Line 107: Line 107: * gdcm::UIDs implementation * gdcm::UIDs implementation * gdcm::Orientation implementation * gdcm::Orientation implementation     And a whole bunch of bug fixes !     Release:   * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=595575 [Less]

/* GDCM 2.0.x */ Revision as of 19:27, 28 April 2008 Current revision Line 99: Line 99: * http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 * ... [More] http://sourceforge.net/project/showfiles.php?group_id=137895&package_id=197047&release_id=587192 -=== GDCM 2.0.x === === GDCM 2.0.4 === * Better support for spacing computation in Enhance CT & Enhance MR dataset * Better support for spacing computation in Enhance CT & Enhance MR dataset [Less]

/* MRI (pseudo-)anonymisation and UIDs */ Revision as of 13:29, 28 April 2008 Current revision Line 1,173: Line 1,173: * http://www.ihe.net/Technical_Framework/ * http://www.ihe.net/Technical_Framework/ * ... [More] http://www.ihe.net/Technical_Framework/upload/IHE_TF_Suppl_Teaching_File_Clinical_Trial_Export_TI_2005-04-22.pdf * http://www.ihe.net/Technical_Framework/upload/IHE_TF_Suppl_Teaching_File_Clinical_Trial_Export_TI_2005-04-22.pdf     == deindentifcation typical profile ==     * http://groups.google.com/group/comp.protocols.dicom/msg/bfbebc080b986c6e     <pre>   Mathieu Malaterre wrote:   > Hello,     > I am in the process of removing any patient information burned in   > the image. I made the following changes:     > 1. Replace Value #1 of Image Type by 'DERIVED'     Don't do that ... leave Image Type alone (unless you are changing   the UID ... vide infra).     > 2. Add a Derivation Description with a comment specifying the position   > of the replaced region     Don't do that either, since it is not a derived image ... you could use   the De-identification Method (0012,0063) attribute instead to say   something generic about what you are doing; but it is a Patient level   attribute so it can't contain image-specific information like regions.     Why do you want to retain the region information, by the way ? If you   do need it, you should probably find a standard attribute to encode   it in (rather than a flattened string).     > 3. Add an Item in Source Image Sequence     Don't do that, since this sequence is only used for derived images,   and the reference is to the SOP Instance UID, which you say you   are not going to change. An image can't reference itself in Source   Image Sequence, obviously (I should perhaps add a validator check   for that).     > The question is: I need to *append* any new Item in the Source Image   > Sequence, right ? that is to say my new item should be the last item   > of the sequence at the end of the process.     Whilst Sequence items are defined to be an "ordered set" (PS 3.5 7.5),   the order is not strictly defined to have meaning for this attribute,   since it may either contain multiple references that were combined to   a single image, multiple successive steps, or both (see the notes in   PS 3.3 C.7.6.1.1.4)     But in this use case, that is irrelevant anyway since you are not   changing the UIDs (vide supra).     If you were, you still can't depend on the order as a receiver, but   should add to the end of it, or remove previous content (or keep   previous content but of course re-map the UIDs to their de-identified   versions).     > BTW since my new instance will have the exact same Instance UID, how   > do PACS system handle when both the original and the new instance are   > sent ?     Undefined and unpredictable, so you have to be sure that any PACS never   gets these two "versions" of the same SOP Instance UID.     Note that it is debatable whether or not you should change the UIDs when   de-identifying; for very thorough de-identification you can, as long as   and make sure that they are consistently changed within a set of objects   you reference each other; but there may be cases when it is desirable   to retain the UIDs (e.g. to provide a trace back to the original   modality), or harmless (e.g., a threat to recover identity would require   access to a PACS database to match UIDs to identities anyway).     If you want to maintain both "versions" in conventional PACS, you have to   change the UIDs (and then you could make it derived and use the Source   Image Sequence and Derivation Description).     We are doing some more work on "profiles" for specific de-identification   purposes in DICOM WG 18 to add to PS 3.15, so you may want to be involved   in that activity.   </pre> === Overlays === === Overlays === [Less]