在SQL＆HIPAA中存儲DICOM頭文件

Question

我在讀DICOM頭文件並將它們存儲在數據庫中。是否存在需要存儲加密或匿名的DICOM對象列表才能符合HIPAA標準？

這是那種我們存儲DICOM標籤的列表： PatientID，PatientsName，PatientsBirthDate，StudyDate，StudyInstanceUid，SopInstanceUid等..

Answer 1

有趣的問題。我從來沒有遇到過由dicom標籤訂購的特定列表。

有一個作爲Ruby gem（Ruby-Dicom）書寫的dicom標題匿名器。

看着它source code here，我看到，這些都是他們選擇的地址開始圍繞線＃663的字段：

["0008,0012", "20000101", false], # Instance Creation Date 
    ["0008,0013", "000000.00", false], # Instance Creation Time 
    ["0008,0020", "20000101", false], # Study Date 
    ["0008,0023", "20000101", false], # Image Date 
    ["0008,0030", "000000.00", false], # Study Time 
    ["0008,0033", "000000.00", false], # Image Time 
    ["0008,0050", "", true], # Accession Number 
    ["0008,0080", "Institution", true], # Institution name 
    ["0008,0090", "Physician", true], # Referring Physician's name 
    ["0008,1010", "Station", true], # Station name 
    ["0008,1070", "Operator", true], # Operator's Name 
    ["0010,0010", "Patient", true], # Patient's name 
    ["0010,0020", "ID", true], # Patient's ID 
    ["0010,0030", "20000101", false], # Patient's Birth Date 
    ["0010,0040", "N", false], # Patient's Sex 
    ["0020,4000", "", false], # Image Comments 

Answer 2

的GDCM project有一個工具叫gdcmanon也annonymizes數據。 man page中的描述說明該工具聲稱它遵循DICOM規範以外的章節。

The gdcmanon tool is an implementation of PS 3.15/E.1/Basic Application Level Confidentiality Profile (Implementation of E.1.1 De-identify & E.1.2 Re-identify) 

手冊頁有一些DICOM規範的更多鏈接。

The DICOM Standard at the time of releasing gdcmanon is: 
ftp://medical.nema.org/medical/dicom/2008/ 

Direct link to PS 3.15-2008: 
ftp://medical.nema.org/medical/dicom/2008/08_15pu.pdf