1

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

这是我们正在存储的 DICOM 标签列表：PatientID、PatientName、PatientBirthDate、StudyDate、StudyInstanceUid、SopInstanceUid 等...

4

2 回答 2

2

有趣的问题。我从未遇到过按 dicom 标签排序的特定列表。

有一个以 Ruby gem (Ruby-Dicom) 形式编写的 dicom 标头匿名器。

在这里查看它的源代码，我看到这些是他们选择从第 #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
于 2012-08-07T18:08:54.233 回答
2

GDCM项目有一个名为 gdcmanon 的工具，它也可以匿名化数据。手册页中的描述描述了该工具声称它遵循 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
于 2012-12-06T15:56:26.713 回答