-
Notifications
You must be signed in to change notification settings - Fork 0
Expand file tree
/
Copy pathindex.html
More file actions
167 lines (109 loc) · 3.47 KB
/
Copy pathindex.html
File metadata and controls
167 lines (109 loc) · 3.47 KB
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
<!DOCTYPE html>
<html>
<meta charset="UTF-8"></meta>
<meta
name="viewport"
content="width=device-width, initial-scale=1.0">
</meta>
<style>table, th, td { border: 1px solid black; }</style>
<title>PEDSnet Codeset Library</title>
<link
href="style.css"
rel="stylesheet"
type="text/css"
title="Cool stylesheet">
</link>
<h1>Introduction</h1>
<p>
This site links researchers with the various codesets developed by the PEDSnet team for
identifying patient cohorts, treatments or outcomes in our database. We are making them available
here for both potential collaborators and outside researchers whose work can benefit from what we
have already done.
</p>
<p>
The codesets are based on the
<i>Common Data Model</i>
as described
<a href="https://github.com/PEDSnet/data_science_training/blob/master/reading_materials/session_1/ETL Conventions for use with PEDSnet CDM v3.2 OMOP V5.2.pdf">
here
</a>
. The exception is the “Query Logic” group which contains R files that draw on the codesets and
implement other logic and calculations.
</p>
<p>
Usually codesets will be of the “
<i>iccc</i>
” form,
<i>integer concept_id</i>
and three text fields:
<i>concept_code</i>
,
<i>concept_name</i>
, and
<i>vocabulary_id</i>
. Note that for labs done, the performance of the lab may be listed as a Procedure, but the
results of the lab may be listed as a Measurement.
</p>
<p>Please contact us at [Email goes here] if you wish to:</p>
<ul>
<li>Ask about a codeset you can’t find or understand</li>
<li>Suggest revisions of a codeset</li>
<li>Send us a proposed new codeset</li>
<li>Collaborate in some other way with PEDSnet research</li>
</ul>
<p></p>
<h1>Codeset Groupings</h1>
<div id="root"></div>
<table style="width:100%">
<tbody>
<tr><th>Group</th><th>Brief Description</th><th>Vocabularies Typically Used</th></tr>
<tr>
<td><a href="conditions_list.html">Conditions</a></td>
<td>Diagnoses of interest in the<i>condition_occurrence</i>table</td>
<td>
SNOMED for searching on
<i>condition_concept_id</i>
, ICD 9 and ICD10 for searching on
<i>condition_source_concept_id</i>
. The Nebraska Lexicon is not used.
</td>
</tr>
<tr>
<td>Drugs</td>
<td>Diagnoses of interest in the<i>drug_exposure</i>table</td>
<td>
RxNorm for searching on
<i>drug_concept_id</i>
or, if necessary, on
<i>drug_source_concept_id</i>
</td>
</tr>
<tr>
<td>Procedures, including labs performed</td>
<td>
Specific procedures, including diagnostic tests, performed on a patient as described in the
<i>procedure_occurrence</i>
table
</td>
<td>CPT4, HCPCS, ICD9Proc, ICD10Proc</td>
</tr>
<tr>
<td>Measurements, including lab results</td>
<td>
Specific measurements of interest as described in the
<i>measurements</i>
table. Querying measurments should also check units.
</td>
<td>LOINC for lab results</td>
</tr>
<tr>
<td><a href="r_code_list.html">Query code</a></td>
<td>R or SQL code developed and tested to extract specific estimates (such as Z-scores or estimated Glomerular Flow Rate) or phenotypes (such as Glomerular Disease)</td>
<td>Not applicable</td>
<script
src="main.js"
type="text/javascript">
</script>
</tbody>
</table>
</html>