Preface |
|
xv | |
Introduction |
|
xvii | |
|
|
|
Chapter 1 The Data Management Plan |
|
|
3 | (6) |
|
History of Data Management Plans |
|
|
3 | (1) |
|
|
4 | (1) |
|
|
5 | (1) |
|
|
5 | (1) |
|
|
6 | (1) |
|
|
6 | (1) |
|
Quality Assurance and DMPs |
|
|
7 | (1) |
|
SOPs for DMPs and Study Files |
|
|
7 | (1) |
|
Using Data Management Plans |
|
|
8 | (1) |
|
Chapter 2 CRF Design Considerations |
|
|
9 | (14) |
|
Primary Goals of CRF Design |
|
|
9 | (5) |
|
Collecting Required Data: Visits, Procedures, Fields |
|
|
10 | (2) |
|
|
12 | (1) |
|
Collecting Analyzable Data |
|
|
13 | (1) |
|
Secondary Goal: Reducing Queries |
|
|
14 | (2) |
|
|
14 | (1) |
|
Eliminating Missing or Ambiguous Responses |
|
|
15 | (1) |
|
CRFs with Data Processing Impact |
|
|
16 | (4) |
|
|
17 | (1) |
|
|
18 | (1) |
|
Diagrams and Analog Scales |
|
|
19 | (1) |
|
|
20 | (1) |
|
|
20 | (1) |
|
Quality Assurance for CRFs |
|
|
21 | (1) |
|
|
22 | (1) |
|
Reuse and Refine CRF Modules |
|
|
22 | (1) |
|
Chapter 3 Database Design Considerations |
|
|
23 | (14) |
|
|
23 | (1) |
|
Basic Clinical Database Concepts |
|
|
24 | (8) |
|
|
24 | (1) |
|
|
25 | (1) |
|
|
26 | (2) |
|
|
28 | (1) |
|
|
28 | (2) |
|
|
30 | (1) |
|
Calculated or Derived Values |
|
|
31 | (1) |
|
Tall-Skinny versus Short-Fat Tables |
|
|
32 | (2) |
|
|
34 | (1) |
|
After Deciding on a Design |
|
|
35 | (1) |
|
Quality Assurance for Database Design |
|
|
35 | (1) |
|
|
35 | (1) |
|
Responsibilities in Database Design |
|
|
36 | (1) |
|
|
37 | (6) |
|
|
37 | (2) |
|
|
38 | (1) |
|
|
38 | (1) |
|
|
38 | (1) |
|
Cross-Form or Cross-Page Checks |
|
|
39 | (1) |
|
|
39 | (1) |
|
|
40 | (1) |
|
Quality Assurance of Edit Checks |
|
|
40 | (1) |
|
|
40 | (2) |
|
The Connection to Queries |
|
|
42 | (1) |
|
Chapter 5 Preparing to Receive Data |
|
|
43 | (12) |
|
Overview of Creating Study Databases |
|
|
43 | (1) |
|
Validating Study Databases |
|
|
44 | (1) |
|
|
45 | (1) |
|
|
45 | (1) |
|
|
45 | (1) |
|
|
46 | (1) |
|
How Building Impacts Specifications |
|
|
46 | (1) |
|
|
46 | (2) |
|
|
47 | (1) |
|
|
47 | (1) |
|
|
48 | (1) |
|
|
48 | (1) |
|
|
48 | (1) |
|
Study Database Change Control |
|
|
49 | (2) |
|
Quality Assurance for Building Studies |
|
|
51 | (1) |
|
SOPs for Preparing for Data |
|
|
51 | (1) |
|
Study Creation Is Programming |
|
|
52 | (3) |
|
|
|
Chapter 6 Receiving Data on Paper |
|
|
55 | (10) |
|
|
55 | (2) |
|
|
55 | (1) |
|
|
56 | (1) |
|
|
56 | (1) |
|
How Close a Match to the CRF? |
|
|
57 | (1) |
|
Dealing with Problem Data |
|
|
58 | (1) |
|
|
58 | (1) |
|
|
58 | (1) |
|
|
59 | (1) |
|
Changing Data after Entry |
|
|
59 | (1) |
|
Quality Assurance and Quality Control for Entry |
|
|
60 | (2) |
|
|
60 | (1) |
|
|
61 | (1) |
|
|
62 | (1) |
|
|
62 | (1) |
|
|
62 | (3) |
|
Chapter 7 Overseeing Data Collection |
|
|
65 | (8) |
|
Monitoring EDC Data Collection |
|
|
65 | (1) |
|
Monitoring Paper Data Collection |
|
|
65 | (6) |
|
|
66 | (1) |
|
|
67 | (1) |
|
|
67 | (1) |
|
|
68 | (1) |
|
|
68 | (1) |
|
Studies without Page Numbers |
|
|
68 | (1) |
|
|
69 | (1) |
|
What Pages Do You Expect? |
|
|
69 | (1) |
|
|
70 | (1) |
|
Principal Investigator Signatures |
|
|
71 | (1) |
|
Using Tracking for Quality Assurance and Quality Control |
|
|
71 | (1) |
|
SOPs for Overseeing Data Collection |
|
|
72 | (1) |
|
Tracking throughout the Process |
|
|
72 | (1) |
|
|
73 | (14) |
|
Identifying Discrepancies |
|
|
73 | (2) |
|
|
74 | (1) |
|
|
74 | (1) |
|
Clinical and Listing Review |
|
|
74 | (1) |
|
Problems during Entry from Paper |
|
|
75 | (1) |
|
Discrepancies Identified by External Programs |
|
|
75 | (1) |
|
|
75 | (2) |
|
|
76 | (1) |
|
|
76 | (1) |
|
|
76 | (1) |
|
|
77 | (5) |
|
Resolving Discrepancies Internally |
|
|
77 | (2) |
|
Turning a Discrepancy into a Query |
|
|
79 | (1) |
|
Sending Queries to the Sites |
|
|
80 | (1) |
|
|
80 | (1) |
|
|
81 | (1) |
|
|
81 | (1) |
|
|
82 | (1) |
|
Links to Quality Assurance and Quality Control |
|
|
83 | (1) |
|
SOPs for Discrepancy Management |
|
|
84 | (1) |
|
Using Queries to Improve Efficiency |
|
|
84 | (3) |
|
Chapter 9 Managing Lab Data |
|
|
87 | (10) |
|
|
87 | (4) |
|
Advantages of the Tall-Skinny Format |
|
|
88 | (1) |
|
Disadvantages of the Tall-Skinny Format |
|
|
89 | (1) |
|
|
90 | (1) |
|
|
91 | (1) |
|
|
91 | (2) |
|
|
92 | (1) |
|
|
92 | (1) |
|
|
93 | (1) |
|
|
93 | (1) |
|
|
93 | (1) |
|
|
94 | (1) |
|
|
94 | (1) |
|
|
95 | (1) |
|
Quality Assurance around Lab Data |
|
|
95 | (1) |
|
SOPs for Processing Lab Data |
|
|
96 | (1) |
|
Why Lab Data Needs Special Attention |
|
|
96 | (1) |
|
|
97 | (6) |
|
Receiving Electronic Files from a Vendor |
|
|
97 | (3) |
|
|
97 | (1) |
|
|
98 | (1) |
|
|
98 | (1) |
|
Identifying File Contents |
|
|
99 | (1) |
|
|
100 | (1) |
|
Quality Assurance for External Data |
|
|
101 | (1) |
|
|
101 | (1) |
|
When Non-CRF Data Is outside Data Management |
|
|
102 | (1) |
|
Chapter 11 Collecting Adverse Event Data |
|
|
103 | (10) |
|
Collecting Adverse Events |
|
|
103 | (4) |
|
|
104 | (2) |
|
Special Considerations for Paper AE Forms |
|
|
106 | (1) |
|
Storing and Cleaning AE Data |
|
|
107 | (1) |
|
Coding Adverse Event Terms |
|
|
108 | (1) |
|
Reconciling Serious Adverse Events |
|
|
109 | (1) |
|
Methods for Reconciliation |
|
|
110 | (1) |
|
Easing the Reconciliation Process |
|
|
110 | (1) |
|
Quality Assurance and Quality Control |
|
|
110 | (1) |
|
|
111 | (1) |
|
Impact of AEs on Data Management |
|
|
111 | (2) |
|
Chapter 12 Creating Reports and Transferring Data |
|
|
113 | (10) |
|
|
113 | (2) |
|
|
113 | (1) |
|
|
114 | (1) |
|
|
114 | (1) |
|
Standard and Ad Hoc Reports |
|
|
115 | (1) |
|
|
116 | (2) |
|
|
116 | (1) |
|
|
117 | (1) |
|
Quality Control Review of Printed Reports and Presentations |
|
|
118 | (1) |
|
SOPs for Reports and Transfers |
|
|
118 | (1) |
|
Putting in the Appropriate Effort |
|
|
118 | (5) |
|
SECTION III Study Closeout |
|
|
|
Chapter 13 Study Database Lock |
|
|
123 | (10) |
|
|
123 | (1) |
|
|
124 | (1) |
|
|
124 | (3) |
|
|
124 | (1) |
|
|
125 | (1) |
|
|
126 | (1) |
|
|
127 | (1) |
|
Using a Checklist to Lock a Study |
|
|
127 | (2) |
|
|
129 | (1) |
|
Time to Study Database Lock |
|
|
129 | (1) |
|
Quality Assurance around Lock |
|
|
130 | (1) |
|
|
130 | (1) |
|
Reducing Time to Study Lock |
|
|
131 | (2) |
|
Chapter 14 After Database Lock |
|
|
133 | (6) |
|
|
133 | (1) |
|
|
133 | (1) |
|
|
134 | (1) |
|
|
134 | (2) |
|
|
134 | (1) |
|
|
135 | (1) |
|
Unlocking for Paper Studies |
|
|
135 | (1) |
|
Unlocking for EDC Studies |
|
|
135 | (1) |
|
|
136 | (1) |
|
SOPs for Study Database Unlock |
|
|
136 | (1) |
|
|
136 | (3) |
|
SECTION IV Necessary Infrastructure |
|
|
|
Chapter 15 Standard Operating Procedures (SOPs) |
|
|
139 | (10) |
|
|
139 | (1) |
|
|
140 | (1) |
|
Creating Standard Procedures |
|
|
141 | (2) |
|
|
141 | (2) |
|
Procedures for New CDM Systems |
|
|
143 | (1) |
|
Complying with Standard Procedures |
|
|
143 | (3) |
|
|
144 | (1) |
|
|
144 | (1) |
|
|
145 | (1) |
|
How Data Management SOPs Are Different from Clinical SOPs |
|
|
146 | (1) |
|
|
146 | (1) |
|
|
147 | (2) |
|
|
149 | (6) |
|
Who Gets Trained on What? |
|
|
149 | (1) |
|
|
150 | (2) |
|
|
152 | (1) |
|
|
153 | (1) |
|
|
154 | (1) |
|
Allotting Time for Training |
|
|
154 | (1) |
|
Chapter 17 Controlling Access and Security |
|
|
155 | (6) |
|
|
155 | (2) |
|
|
156 | (1) |
|
|
156 | (1) |
|
|
157 | (1) |
|
|
157 | (2) |
|
|
158 | (1) |
|
|
158 | (1) |
|
SOPs and Guidelines for Accounts |
|
|
159 | (1) |
|
Taking Security Seriously |
|
|
159 | (2) |
|
Chapter 18 Working with CROs |
|
|
161 | (10) |
|
|
161 | (1) |
|
|
162 | (1) |
|
Defining Responsibilities |
|
|
163 | (1) |
|
Oversight and Interaction |
|
|
163 | (3) |
|
|
163 | (1) |
|
|
164 | (2) |
|
|
166 | (1) |
|
|
166 | (1) |
|
CROs as Functional Service Providers |
|
|
167 | (1) |
|
SOPs for Working with CROs |
|
|
167 | (1) |
|
|
167 | (4) |
|
|
|
Chapter 19 Clinical Data Management Systems |
|
|
171 | (4) |
|
CDM System Characteristics |
|
|
171 | (1) |
|
Where CDM Systems Come From |
|
|
172 | (1) |
|
|
172 | (1) |
|
Using CDM Systems Successfully |
|
|
173 | (1) |
|
|
173 | (1) |
|
CDM Systems Are for More than Data Entry |
|
|
174 | (1) |
|
|
175 | (8) |
|
What Makes EDC Systems Different? |
|
|
175 | (3) |
|
|
176 | (1) |
|
|
176 | (1) |
|
Where the Servers Are---Hosting |
|
|
176 | (1) |
|
|
177 | (1) |
|
The Need for Data Repositories |
|
|
177 | (1) |
|
|
178 | (1) |
|
|
179 | (1) |
|
|
179 | (1) |
|
Will Data Management Groups Disappear? |
|
|
180 | (1) |
|
|
181 | (1) |
|
|
181 | (2) |
|
Chapter 21 Choosing Vendor Products |
|
|
183 | (8) |
|
|
183 | (1) |
|
|
184 | (1) |
|
|
184 | (1) |
|
|
185 | (1) |
|
Extended Demos and Pilots |
|
|
185 | (2) |
|
|
186 | (1) |
|
|
186 | (1) |
|
Additional Considerations |
|
|
187 | (2) |
|
|
189 | (1) |
|
Preparing for Implementation |
|
|
189 | (2) |
|
Chapter 22 Implementing New Systems |
|
|
191 | (8) |
|
Overview and Related Plans |
|
|
191 | (1) |
|
|
192 | (1) |
|
Integration and Extensions |
|
|
193 | (1) |
|
|
194 | (1) |
|
|
194 | (2) |
|
|
196 | (1) |
|
Preparation for Production |
|
|
196 | (1) |
|
Successful Implementation |
|
|
196 | (3) |
|
Chapter 23 System Validation |
|
|
199 | (8) |
|
|
199 | (1) |
|
Validation Plans or Protocols |
|
|
200 | (4) |
|
|
200 | (1) |
|
|
201 | (1) |
|
Business Requirements and Functional Specification |
|
|
201 | (1) |
|
|
201 | (1) |
|
|
202 | (1) |
|
|
202 | (1) |
|
|
203 | (1) |
|
|
203 | (1) |
|
|
203 | (1) |
|
Maintaining Validation Plans |
|
|
203 | (1) |
|
Change Control and Revalidation |
|
|
204 | (1) |
|
|
204 | (1) |
|
|
205 | (1) |
|
Requirements and Benefits |
|
|
206 | (1) |
|
Chapter 24 Test Procedures |
|
|
207 | (6) |
|
|
207 | (1) |
|
|
208 | (1) |
|
|
209 | (1) |
|
|
210 | (1) |
|
|
210 | (1) |
|
|
211 | (1) |
|
Retaining the Test Materials |
|
|
212 | (1) |
|
Chapter 25 Change Control |
|
|
213 | (6) |
|
What Changes Should Be Controlled? |
|
|
213 | (1) |
|
Changes to Software Systems |
|
|
213 | (1) |
|
Changes to Study Databases |
|
|
214 | (1) |
|
|
214 | (3) |
|
Describe or Propose the Change |
|
|
215 | (1) |
|
|
215 | (1) |
|
|
216 | (1) |
|
|
216 | (1) |
|
|
217 | (1) |
|
|
217 | (1) |
|
Considering Version Control |
|
|
218 | (1) |
|
The Value of Change Control |
|
|
218 | (1) |
|
Chapter 26 Coding Dictionaries and Systems |
|
|
219 | (10) |
|
Common Coding Dictionaries |
|
|
219 | (1) |
|
|
220 | (1) |
|
|
220 | (1) |
|
|
220 | (4) |
|
|
221 | (1) |
|
|
222 | (1) |
|
|
222 | (2) |
|
Special Considerations for AE Terms |
|
|
224 | (1) |
|
|
225 | (1) |
|
Quality Assurance and Quality Control for Coding |
|
|
226 | (1) |
|
SOPs for Coding and Dictionaries |
|
|
226 | (1) |
|
|
227 | (2) |
|
Chapter 27 Migrating and Archiving Data |
|
|
229 | (6) |
|
Simple Migrations within Systems |
|
|
229 | (1) |
|
Why Migrate between Systems? |
|
|
230 | (1) |
|
|
231 | (1) |
|
|
232 | (1) |
|
|
232 | (1) |
|
|
232 | (2) |
|
|
233 | (1) |
|
|
233 | (1) |
|
Migration and Archive Plans |
|
|
234 | (1) |
|
|
234 | (1) |
Appendix A Data Management Plan Outline |
|
235 | (4) |
Appendix B Clinical Data Management SOPs |
|
239 | (4) |
Appendix C CRO-Sponsor Responsibility Matrix |
|
243 | (4) |
Appendix D Implementation Plan Outline |
|
247 | (2) |
Appendix E Validation Plan Outline |
|
249 | (2) |
Appendix F CDISC and HIPAA |
|
251 | (2) |
Bibliography |
|
253 | (2) |
Index |
|
255 | |