-
Notifications
You must be signed in to change notification settings - Fork 0
/
faq.html
183 lines (152 loc) · 5.2 KB
/
faq.html
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
58
59
60
61
62
63
64
65
66
67
68
69
70
71
72
73
74
75
76
77
78
79
80
81
82
83
84
85
86
87
88
89
90
91
92
93
94
95
96
97
98
99
100
101
102
103
104
105
106
107
108
109
110
111
112
113
114
115
116
117
118
119
120
121
122
123
124
125
126
127
128
129
130
131
132
133
134
135
136
137
138
139
140
141
142
143
144
145
146
147
148
149
150
151
152
153
154
155
156
157
158
159
160
161
162
163
164
165
166
167
168
169
170
171
172
173
174
175
176
177
178
179
180
181
182
183
<!DOCTYPE html>
<html lang="en">
<head>
<title>DICOM+</title>
<link rel="stylesheet"
href="../../../bootstrap/3.3.6/css/bootstrap.min.css" />
<link rel="stylesheet"
href="../../../bootstrap/3.3.6/css/bootstrap-theme.min.css" />
<script src="../../../jquery/1.11.3/jquery.min.js"></script>
<script src="../../../bootstrap/3.3.6/js/bootstrap.min.js"></script>
<style>
body {
max-width: 1024px;
}
@media ( min-width : 768px) {
.sidebar-nav .navbar .navbar-collapse {
padding: 0;
max-height: none;
}
.sidebar-nav .navbar ul {
float: none;
display: block;
}
.sidebar-nav .navbar li {
float: none;
display: block;
}
.sidebar-nav .navbar li a {
padding-top: 12px;
padding-bottom: 12px;
}
}
</style>
</head>
<body>
<div style="margin-top: 20px;margin-bottom: 50px;" class="row">
<div class="col-md-3 col-md-offset-1">
<h1 class="fill">
<a href="index.html"> <img
src="../../../images/DICOM+.png" height="232"/>
</a>
</h1>
<div class="sidebar-nav">
<div class="navbar navbar-default" role="navigation">
<div class="navbar-header">
<button type="button" class="navbar-toggle" data-toggle="collapse"
data-target=".sidebar-navbar-collapse">
<span class="sr-only">Toggle navigation</span> <span
class="icon-bar"></span> <span class="icon-bar"></span> <span
class="icon-bar"></span>
</button>
<span class="visible-xs navbar-brand">Sidebar menu</span>
</div>
<div class="navbar-collapse collapse sidebar-navbar-collapse">
<ul class="nav navbar-nav">
<li><a href="index.html">Starting the
program</a></li>
<li><a href="main.html">Main Window Layout</a></li>
<li><a href="preview.html">Previewing Files</a></li>
<li><a href="anonymizingFiles.html">Anonymizing Files</a></li>
<li><a href="anonymizeOptions.html">Anonymize Options</a></li>
<li><a href="edit.html">Editing</a></li>
<li><a href="quickTips.html">Quick Start and Tips</a></li>
<li><a href="faq.html">Frequently Asked Questions</a></li>
<li><a href="commandLine.html">Running as a command line
program</a></li>
<!-- <li><a style="margin-left:40px;" href="preload.html">Saving and loading a session</a> TODO </li> -->
<li><a
href="http://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_6.2.html#table_6.2-1" target="_blank">DICOM
Value Representations (from the DICOM standard)</a></li>
<li><a href="valueMultiplicity.html">DICOM Value
Multiplicity</a></li>
</ul>
</div>
<!--/.nav-collapse -->
</div>
</div>
</div>
<div class="col-md-8">
<h2>Frequently Asked Questions</h2>
<p />
<br />
<strong>Will DICOM+ over-write my existing files?</strong>
<br />
In general, no - The program is designed to preserve existing files. Both
anonymization and editing create new copies of the files. Before a new
file is written, the program checks to make sure that the name it is
using is unique.
<br />
The only exceptions are:
<ul>
<li>When editing a file, the user overrides the default and indicates that the
original file should be over-written.</li>
<li>When the user repeatedly saves during an edit session, the
same destination file is used.</li>
</ul>
<p />
Note that if the same series is anonymized multiple times, it will
result in multiple sets of files. This is by design, as a common use
case is to anonymize the same set of files multiple times with different
user IDs to create test data.
<p />
<br />
<strong>How does DICOM+ anonymize UIDs?</strong>
<br />
It replaces all of them with new ones, maintaining the cross-references
between files. This is especially important in radiotherapy, where a
patient often has a set of files including images (CT, MR, etc.),
RTSTRUCT, RTPLAN, RTDOSE, and other files that share UIDs between
series.
<p />
To maintain the cross-references, all files for a given patient must be
anonymized in the same session.
<p />
This is also required by the DICOM specification. See the DICOM
standard:
<p />
<ul>
<li><a href="http://dicom.nema.org/medical/dicom/current/output/chtml/part05/sect_6.2.html#table_6.2-1">Supplement
55: Attribute Level Confidentiality (including De-identification)</a></li>
<li><a
href="ftp://medical.nema.org/medical/dicom/final/sup142_ft.pdf">Supplement
142:Clinical Trial De-identification Profiles</a></li>
</ul>
<p />
<p />
<br />
<strong>How does DICOM+ construct file names?</strong>
<br />
File names are constructed so as to be human readable, and are formatted
with the following fields (if they are present in the source DICOM file)
separated by underscore:
<ul>
<li>Patient ID</li>
<li>Modality</li>
<li>Series Number</li>
<li>Instance Number</li>
</ul>
If the resulting file already exists, an integer is appended to the name
to make it unique.
<p />
<br />
<strong>Does DICOM+ use 32 or 64 bit?</strong>
<br />
Either. The version of the Java runtime on your machine determines which
will be used, but DICOM+ uses the same BAT and library files regardless.
The advantage of 64 bit is the ability to work with larger data sets,
but otherwised they behave identically.
</div>
</div>
</body>
</html>