在SQL&中存储DICOM标头HIPAA

时间:2012-08-03 01:54:15

标签: database dicom hipaa

我正在阅读DICOM标题并将它们存储在数据库中。是否有需要存储加密或匿名的DICOM对象列表才能符合HIPAA标准?

这是我们正在存储的DICOM标签列表: PatientID,PatientsName,PatientsBirthDate,StudyDate,StudyInstanceUid,SopInstanceUid等......

2 个答案:

答案 0 :(得分:2)

有趣的问题。我从来没有遇到过由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

答案 1 :(得分:2)

GDCM project有一个名为gdcmanon的工具,它也会对数据进行匿名化。 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