Skip to content

Commit 3e80522

Browse files
committed
Submitted version
1 parent e11b060 commit 3e80522

11 files changed

+261
-11
lines changed

paper/clinicalcodes.pdf

100755100644
-209 KB
Binary file not shown.

paper/clinicalcodes.tex

Lines changed: 11 additions & 11 deletions
Original file line numberDiff line numberDiff line change
@@ -122,13 +122,13 @@ \section*{Reporting of codes in the current literature}
122122

123123
A large component of total EMR research is made up by primary care database (PCD) studies and UK PCDs are among the most researched in the world. Figure \ref{figure1_articles_per_year} shows that research outputs with UK PCDs appears to be increasing at an exponential rate, while figure \ref{figure2_PCD_map} shows that research using UK PCDs is being conducted in universities, pharmaceutical companies and research hospitals around the world, and is not just limited to the UK. As one of the largest and most important resources for EMR-based research, it seems reasonable to expect reporting of code lists in UK PCD-based studies to be at least as comprehensive as in other EMR studies. To evaluate levels of transparency in the reporting of clinical code lists, we took a representative sample of UK PCD studies and assessed each study on its extent of reporting of the clinical codes used.
124124

125-
We took a sample of 450 papers from the original 1359 identified from a PubMed search. Of these, 392 (87\%) had both the full text accessible to the University of Manchester library and were examples of primary PCD research. Only 35 (9\% of 392) studies published the entire set of clinical codes needed to reproduce the study (usually in an online appendix), while only an additional 47 (12\% of 392) stated explicitly that the clinical codes are available upon request \ref{tab:table1_percentages}.
125+
We took a sample of 450 papers from the original 1359 identified from a PubMed search. Of these, 392 (87\%) had both the full text accessible to the University of Manchester library and were examples of primary PCD research. Only 35 (9\% of 392) studies published the entire set of clinical codes needed to reproduce the study (usually in an online appendix), while only an additional 47 (12\% of 392) stated explicitly that the clinical codes are available upon request (table \ref{tab:table1_percentages}).
126126

127127

128128
\section*{The need for transparency in clinical code usage}
129129

130130

131-
We identify four main consequences of lack of transparency of clinical code lists. First, if code lists are not made available or not published alongside the primary research using them, they represent an important part of a study methodology that is not subject to scrutiny or peer review. In the extreme case, there is no way of assessing the validity of the diagnosis definition used in a study and clinical decisions could be based on invalid results derived from an incorrect patient base. This could happen despite rigorous downstream statistical analysis. Second, the effective replication of EMR studies is dependent on the availability of the clinical codes from the original study. If all of the codes are not available, it is impossible to tell if differences found in study replications are due to artefactual differences in code lists or if they are genuine. Third, if code-lists are unknown, comparisons between studies addressing the same clinical question are potentially invalidated. Condition definitions change over time and GP coding practice may also change with respect to regulations and incentives \cite{Hippisley-Cox2006}. Also, different studies may use different types of codes for a condition; some studies, for example, include medication and monitoring codes as part of their definition of a patient with diabetes (e.g. \cite{Mulnier2006}) while others do not (e.g. \cite{Kontopantelis2014}). Not having access to code-lists means that it is difficult to know whether fair comparisons are being made between studies. Fourth, building code lists is a time consuming process; having access to historical code lists would mean that new lists could be built incrementally and iteratively, saving much `reinvention of the wheel' while increasing consistency, and potentially accuracy, of definitions across studies.
131+
We identify four main consequences of lack of transparency of clinical code lists. First, if code lists are not made available or not published alongside the primary research using them, they represent an important part of a study methodology that is not subject to scrutiny or peer review. In the extreme case, there is no way of assessing the validity of the diagnosis definition used in a study and clinical decisions could be based on invalid results derived from an incorrect patient base. This could happen despite rigorous downstream statistical analysis. Second, the effective replication of EMR studies is dependent on the availability of the clinical codes from the original study. If all of the codes are not available, it is impossible to tell if differences found in study replications are due to artifactual differences in code lists or if they are genuine. Third, if code-lists are unknown, comparisons between studies addressing the same clinical question are potentially invalidated. Condition definitions change over time and GP coding practice may also change with respect to regulations and incentives \cite{Hippisley-Cox2006}. Also, different studies may use different types of codes for a condition; some studies, for example, include medication and monitoring codes as part of their definition of a patient with diabetes (e.g. \cite{Mulnier2006}) while others do not (e.g. \cite{Kontopantelis2014}). Not having access to code-lists means that it is difficult to know whether fair comparisons are being made between studies. Fourth, building code lists is a time consuming process; having access to historical code lists would mean that new lists could be built incrementally and iteratively, saving much `reinvention of the wheel' while increasing consistency, and potentially accuracy, of definitions across studies.
132132

133133

134134

@@ -189,15 +189,15 @@ \subsection*{Database Architecture and Web Interface}
189189
\section*{Acknowledgments}
190190
We are thankful to Matt Ford for extensive technical support. Thanks to the Research team at CPRD for fruitful discussions in the development stage.
191191

192-
\subsection*{Funding statement}
193-
This work is funded by the National Institute for Health Research (NIHR) School for Primary Care Research (SPCR).
192+
%\subsection*{Funding statement}
193+
%This work is funded by the National Institute for Health Research (NIHR) School for Primary Care Research (SPCR).
194194

195-
\subsection*{Disclaimer}
196-
This article presents independent research funded by the National Institute for Health Research (NIHR). The views expressed are those of the author(s) and not necessarily those of the NHS, the NIHR or the Department of Health.
195+
%\subsection*{Disclaimer}
196+
%This article presents independent research funded by the National Institute for Health Research (NIHR). The views expressed are those of the author(s) and not necessarily those of the NHS, the NIHR or the Department of Health.
197197

198-
\section*{Author Contributions}
198+
%\section*{Author Contributions}
199199

200-
Conceived, designed and built the website and software: DAS. Data collection: DAS, DR, EK, IO, RP, DA, EC. Data Analysis: DAS. Wrote the manuscript DAS. Edited the manuscript DAS, DR, EK, IO, RP, DA, EC.
200+
%Conceived, designed and built the website and software: DAS. Data collection: DAS, DR, EK, IO, RP, DA, EC. Data Analysis: DAS. Wrote the manuscript DAS. Edited the manuscript DAS, DR, EK, IO, RP, DA, EC.
201201

202202
%\section*{References}
203203
% The bibtex filename
@@ -234,7 +234,7 @@ \section*{Figure Legends}
234234

235235
\begin{figure}[!ht]
236236
\begin{center}
237-
\includegraphics[width=4in]{figure/articles_per_year.eps}
237+
%\includegraphics[width=4in]{figure/articles_per_year.eps}
238238
\end{center}
239239
\caption{
240240
{\bf Number of UK Primary Care Database publications.}
@@ -244,7 +244,7 @@ \section*{Figure Legends}
244244

245245
\begin{figure}[!ht]
246246
\begin{center}
247-
\includegraphics[width=6in]{figure/PCD_world.eps}
247+
% \includegraphics[width=6in]{figure/PCD_world.eps}
248248
\end{center}
249249
\caption{
250250
{\bf Locations of primary affiliated departments.}
@@ -254,7 +254,7 @@ \section*{Figure Legends}
254254

255255
\begin{figure}[!ht]
256256
\begin{center}
257-
\includegraphics[width=6in]{figure/clinicalcodes_screenshot.eps}
257+
% \includegraphics[width=6in]{figure/clinicalcodes_screenshot.eps}
258258
\end{center}
259259
\caption{
260260
{\bf Screenshot of the ClinicalCodes website showing articles with uploaded code lists.}

paper/clinicalcodes_with_pix.pdf

297 KB
Binary file not shown.

paper/collection.sty

Lines changed: 85 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,85 @@
1+
%% start of file `collection.sty'.
2+
%% Copyright 2013-2013 Xavier Danaux ([email protected]).
3+
%
4+
% This work may be distributed and/or modified under the
5+
% conditions of the LaTeX Project Public License version 1.3c,
6+
% available at http://www.latex-project.org/lppl/.
7+
8+
9+
%-------------------------------------------------------------------------------
10+
% identification
11+
%-------------------------------------------------------------------------------
12+
\NeedsTeXFormat{LaTeX2e}
13+
\ProvidesPackage{collection}[2013/03/28 v1.0.0 collections]
14+
15+
16+
%-------------------------------------------------------------------------------
17+
% requirements
18+
%-------------------------------------------------------------------------------
19+
20+
21+
\RequirePackage{ifthen}
22+
23+
24+
%-------------------------------------------------------------------------------
25+
% code
26+
%-------------------------------------------------------------------------------
27+
28+
% creates a new collection
29+
% usage: \collectionnew{<collection name>}
30+
\newcommand*{\collectionnew}[1]{%
31+
\newcounter{collection@#1@count}}
32+
33+
% adds an item to a collection
34+
% usage: \collectionadd[<optional key>]{<collection name>}{<item to add>}
35+
\newcommand*{\collectionadd}[3][]{%
36+
\expandafter\def\csname collection@#2@item\roman{collection@#2@count}\endcsname{#3}%
37+
\if\relax\noexpand#1\relax% if #1 is empty
38+
\else\expandafter\def\csname collection@#2@key\roman{collection@#2@count}\endcsname{#1}\fi%
39+
\stepcounter{collection@#2@count}}
40+
41+
% returns the number of items in a collection
42+
% usage: \collectioncount{<collection name>}
43+
\newcommand*{\collectioncount}[1]{%
44+
\value{collection@#1@count}}
45+
46+
% gets an item from a collection
47+
% usage: \collectiongetitem{<collection name>}{<element id>}
48+
% where <element id> is an integer between 0 and (collectioncount-1)
49+
\newcommand*{\collectiongetitem}[2]{%
50+
\csname collection@#1@item\romannumeral #2\endcsname}
51+
52+
% gets a key from a collection
53+
% usage: \collectiongetkey{<collection name>}{<element id>}
54+
% where <element id> is an integer between 0 and (collectioncount-1)
55+
\newcommand*{\collectiongetkey}[2]{%
56+
\csname collection@#1@key\romannumeral #2\endcsname}
57+
58+
% loops through a collection and perform the given operation on every element
59+
% usage: \collectionloop{<collection name>}{<operation sequence>}
60+
% where <operation sequence> is the code sequence to be evaluated for each collection item,
61+
% code which can refer to \collectionloopid, \collectionloopkey, \collectionloopitem and
62+
% \collectionloopbreak
63+
\newcounter{collection@iterator}
64+
\newcommand*{\collectionloopbreak}{\let\iterate\relax}
65+
\newcommand*{\collectionloop}[2]{%
66+
\setcounter{collection@iterator}{0}%
67+
\loop\ifnum\value{collection@iterator}<\value{collection@#1@count}%
68+
\def\collectionloopid{\arabic{collection@iterator}}%
69+
\def\collectionloopitem{\collectiongetitem{#1}{\collectionloopid}}%
70+
\def\collectionloopkey{\collectiongetkey{#1}{\collectionloopid}}%
71+
#2%
72+
\stepcounter{collection@iterator}%
73+
\repeat}
74+
75+
% loops through a collection and finds the (first) element matching the given key
76+
% usage: \collectionfindbykey{<collection name>}{key>}
77+
\newcommand*{\collectionfindbykey}[2]{%
78+
\collectionloop{#1}{%
79+
\ifthenelse{\equal{\collectionloopkey}{#2}}{\collectionloopitem\collectionloopbreak}{}}}
80+
81+
82+
\endinput
83+
84+
85+
%% end of file `collection.cls'.

paper/coverletter.pdf

18.3 KB
Binary file not shown.

paper/coverletter.tex

Lines changed: 32 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,32 @@
1+
\documentclass{letter}
2+
\signature{David A Springate \\ Research Fellow \\ Institute of Population Health \\ University of Manchester}
3+
\begin{document}
4+
\begin{letter}{Institute of Population Health \\ University of Manchester \\ UK}
5+
\opening{Dear Sirs,}
6+
7+
We would like the editors to consider our article entitled ``ClinicalCodes: An online clinical codes repository to improve the validity and reproducibility of research using electronic medical records'' for publication in PLoS One.
8+
9+
In this manuscript, we describe a new online database for lists of clinical codes (www.clinicalcodes.org) for use by researchers using electronic medical records (EMRs). This resource will allow for clinical researchers to better validate electronic medical records studies, build on previous clinical code lists and compare condition definitions across studies. It will also assist health informaticians in replicating database studies, tracking changes in disease definitions or clinical coding practice through time and sharing clinical code information across platforms and data sources as research objects.
10+
11+
Despite accurate definitions of medical conditions being a prerequisite for valid EMR studies and these definitions depending upon careful selection of clinical codes, the publication of clinical codes is rarely, if ever, a requirement for obtaining grants, validating protocols or publishing research. We evaluated the levels of transparency in the reporting of clinical code lists in a representative study of UK primary care database studies. Of the 392 studies we examined, only 35 (9\%) published the entire set of clinical codes lists needed to reproduce or validate the study. These were most often published in online appendices.
12+
13+
We identify four main consequences of lack of transparency of clinical codes lists:
14+
15+
\begin{enumerate}
16+
\item Code lists are not subject to scrutiny or peer review
17+
\item It is impossible to tell if differences in found in study replications are genuine or due to artifactual differences in code lists
18+
\item Comparisons between studies of the same clinical conditions are potentially invalidated
19+
\item Lack of access to historical code lists leads to much wasted effort on the part of researchers
20+
\end{enumerate}
21+
22+
23+
The database described here will provide a centralised repository for EMR researchers to deposit their codes and this will lead to greater transparency, reproducibility and validity in this important area of research.
24+
25+
We believe this submission fits all the PLoS ONE criteria for database papers, namely utility, validity and availability. The resource will be of great use to the EMR community and we expect the paper to be highly referenced and the ClinicalCodes database to becomes the de facto repository for clinical code lists across EMR research. The database is an effective repository for clinical code lists and we are aware no similar open repositories for clinical codes. The database is written entirely using open source software and is freely available for access, upload and download. In addition, we have developed open source software to access the database programmatically and to download research objects for integration with other systems.
26+
27+
We would like to recommend Irene Petersen from UCL as an Academic Editor.
28+
29+
\closing{Yours Faithfully,}
30+
\end{letter}
31+
\end{document}
32+

paper/data/categorised_papers.xlsx

115 KB
Binary file not shown.

paper/letterbuild

Lines changed: 1 addition & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1 @@
1+
pdflatex coverletter

0 commit comments

Comments
 (0)