B Trinczek1, F Köpcke2, T Leusch3, R W Majeed4, B Schreiweis5, J Wenk6, B Bergh5, C Ohmann6, R Röhrig4, H U Prokosch2, M Dugas1. 1. Institute of Medical Informatics, University of Münster , Germany. 2. Chair of Medical Informatics, Friedrich-Alexander-University Erlangen-Nuremberg , Germany. 3. Department of Information- and Communication-Technology, Düsseldorf University Hospital , Germany. 4. Department of Anesthesia and Intensive Care Medicine, Justus-Liebig University Gießen , Germany. 5. Center for Information Technology and Medical Engineering, Heidelberg University Hospital , Germany. 6. Coordination Centre for Clinical Trials, Faculty of Medicine, Heinrich Heine University Düsseldorf , Germany.
Abstract
OBJECTIVE: (1) To define features and data items of a Patient Recruitment System (PRS); (2) to design a generic software architecture of such a system covering the requirements; (3) to identify implementation options available within different Hospital Information System (HIS) environments; (4) to implement five PRS following the architecture and utilizing the implementation options as proof of concept. METHODS: Existing PRS were reviewed and interviews with users and developers conducted. All reported PRS features were collected and prioritized according to their published success and user's request. Common feature sets were combined into software modules of a generic software architecture. Data items to process and transfer were identified for each of the modules. Each site collected implementation options available within their respective HIS environment for each module, provided a prototypical implementation based on available implementation possibilities and supported the patient recruitment of a clinical trial as a proof of concept. RESULTS: 24 commonly reported and requested features of a PRS were identified, 13 of them prioritized as being mandatory. A UML version 2 based software architecture containing 5 software modules covering these features was developed. 13 data item groups processed by the modules, thus required to be available electronically, have been identified. Several implementation options could be identified for each module, most of them being available at multiple sites. Utilizing available tools, a PRS could be implemented in each of the five participating German university hospitals. CONCLUSION: A set of required features and data items of a PRS has been described for the first time. The software architecture covers all features in a clear, well-defined way. The variety of implementation options and the prototypes show that it is possible to implement the given architecture in different HIS environments, thus enabling more sites to successfully support patient recruitment in clinical trials.
OBJECTIVE: (1) To define features and data items of a Patient Recruitment System (PRS); (2) to design a generic software architecture of such a system covering the requirements; (3) to identify implementation options available within different Hospital Information System (HIS) environments; (4) to implement five PRS following the architecture and utilizing the implementation options as proof of concept. METHODS: Existing PRS were reviewed and interviews with users and developers conducted. All reported PRS features were collected and prioritized according to their published success and user's request. Common feature sets were combined into software modules of a generic software architecture. Data items to process and transfer were identified for each of the modules. Each site collected implementation options available within their respective HIS environment for each module, provided a prototypical implementation based on available implementation possibilities and supported the patient recruitment of a clinical trial as a proof of concept. RESULTS: 24 commonly reported and requested features of a PRS were identified, 13 of them prioritized as being mandatory. A UML version 2 based software architecture containing 5 software modules covering these features was developed. 13 data item groups processed by the modules, thus required to be available electronically, have been identified. Several implementation options could be identified for each module, most of them being available at multiple sites. Utilizing available tools, a PRS could be implemented in each of the five participating German university hospitals. CONCLUSION: A set of required features and data items of a PRS has been described for the first time. The software architecture covers all features in a clear, well-defined way. The variety of implementation options and the prototypes show that it is possible to implement the given architecture in different HIS environments, thus enabling more sites to successfully support patient recruitment in clinical trials.
Entities:
Keywords:
Clinical trials as topic; hospital information systems; patient identification systems; patient selection; software architecture
Authors: Eugene Fink; Princeton K Kokku; Savvas Nikiforou; Lawrence O Hall; Dmitry B Goldgof; Jeffrey P Krischer Journal: Artif Intell Med Date: 2004-07 Impact factor: 5.326
Authors: Alison M McDonald; Rosemary C Knight; Marion K Campbell; Vikki A Entwistle; Adrian M Grant; Jonathan A Cook; Diana R Elbourne; David Francis; Jo Garcia; Ian Roberts; Claire Snowdon Journal: Trials Date: 2006-04-07 Impact factor: 2.279
Authors: Martin Bialke; Thomas Bahls; Lars Geidel; Henriette Rau; Arne Blumentritt; Sandra Pasewald; Robert Wolff; Jonas Steinmann; Tobias Bronsch; Björn Bergh; Galina Tremper; Martin Lablans; Frank Ückert; Stefan Lang; Tarik Idris; Wolfgang Hoffmann Journal: J Transl Med Date: 2018-09-14 Impact factor: 5.531
Authors: Hans-Ulrich Prokosch; Till Acker; Johannes Bernarding; Harald Binder; Martin Boeker; Melanie Boerries; Philipp Daumke; Thomas Ganslandt; Jürgen Hesser; Gunther Höning; Michael Neumaier; Kurt Marquardt; Harald Renz; Hermann-Josef Rothkötter; Carmen Schade-Brittinger; Paul Schmücker; Jürgen Schüttler; Martin Sedlmayr; Hubert Serve; Keywan Sohrabi; Holger Storf Journal: Methods Inf Med Date: 2018-07-17 Impact factor: 2.176