Automatic blacout/redact PHI burned in pixel of USG/NM secondary screen captures for annontmization

[yufoo...@gmail.com]

Hello! I am new to DCM4CHE

I am planning to set up a DCM4CHE workstation for anonymization/redaction purpose. The DICOM images of secondary screen capture format of certain modality (e.g ultrasound, nuclear medicine contain PHI burned into the pixels at top portion) once received by the DCM4CHE server, have to be automatically get blackout at the top margin by placing a rectangle to mask it followed by automatic annonymization of patient Name and identity number DICOM tag replaced by Accession number before auto-forwarding to Osirix. I have heard how do achieve the latter part (DICOM-tag field by modifying cstorerq.xsl and forward2 if I am correct) can be achieved but I do not know whether the former is feasible

I have heard of the following script extract (may be incomplete or not fully applicable to my purpose) but I do not know how and where to put it :
 
raster.setPixels(x, y, width, height, pixels);

My purpose is NOT to blackout a batch of existing DICOM files already stored in my hard-disk, BUT to carry out ongoing automatic blackout of upper portion of USG/NM secondary screen capture DICOM files received from PACS server over DICOM network in the future.

I heard the RSNA MIRC Clinical Trial Processor (CTP) can also similar achieve purpose but I am using MAC Yosemite OSX 64bit and heard there is an Advanced Imaging I/O compatibility issue for the Java used in 64bit MAC OS X and anyway I prefer to stick back to DCM4CHE for consistency.

Any advice would be appreciated. Thank you in advance.

[matthe...@netscape.net]

DICOM Cleaner

http://www.dclunie.com/pixelmed/software/webstart/DicomCleanerUsage.html

--
You received this message because you are subscribed to the Google Groups "dcm4che" group.
To unsubscribe from this group and stop receiving emails from it, send an email to dcm4che+u...@googlegroups.com.
To post to this group, send email to dcm...@googlegroups.com.
Visit this group at http://groups.google.com/group/dcm4che.
For more options, visit https://groups.google.com/d/optout.

[yufoo...@gmail.com]

Thank you Matthew you for advice. However, I am looking for on-the-fly blackout after receiving by DCM4CHE. I am aware of the DICOMcleaner that you mentioned and have tried it, but apparently that only works for DICOM files stored in the local computer hard-disk or DICOM files retrieved from a DICOM node via the software.

What I am looking for is method to do this on-the-fly by DCM4CHE after receiving the USG/NM screen-capture DICOM files and then autoforward to another DICOM destination such as Osirix.

Please kindly advise. Thank you again in advance


matthe...@netscape.net於 2015年4月23日星期四 UTC+8下午11時44分06秒寫道：

[Algie Rosario]

Hi Yufoo,

Im not familiar with your scenario, but based on the statements above by matthew with DICOMcleaner, im thinking this flow:

Modality sends to > DCM4CHE PACS Server > a script will be trigger to function DICOM Cleaner > autoforward/ dcmsnd the processed DICOM object/ files to Osirix.

Algie,