AGUIA: autonomous graphical user interface assembly for clinical trials semantic data services
1 Department of Bioinformatics and Computational Biology, The University of Texas MD Anderson Cancer Center, 1515 Holcombe Blvd, Houston, TX 77030, USA
2 Bioinformatics Laboratory, Laboratório Nacional de Computação Científica, Av Getúlio Vargas, 333 Petrópolis, Rio de Janeiro, Brazil
3 Institute of Chemical and Biological Technology, Universidade Nova de Lisboa, Oeiras, Portugal
4 Instituto Nacional de Metrologia, INMETRO, Av. Nossa Senhora das Graças 50 -prédio 6, 25250-020, Xerém - Duque de Caxias, Rio de Janeiro - Brazil
5 Department of Gastrointestinal Medical Oncology, The University of Texas MD Anderson Cancer Center, 1515 Holcombe Blvd, Houston, TX 77030, USA
6 The University of Texas MD Anderson Cancer Center, 1515 Holcombe Blvd, Houston, TX 77030, USA
7 The University of Texas Medical School, 6431 Fannin St, Houston, TX 77030, USA
BMC Medical Informatics and Decision Making 2010, 10:65 doi:10.1186/1472-6947-10-65Published: 26 October 2010
AGUIA is a front-end web application originally developed to manage clinical, demographic and biomolecular patient data collected during clinical trials at MD Anderson Cancer Center. The diversity of methods involved in patient screening and sample processing generates a variety of data types that require a resource-oriented architecture to capture the associations between the heterogeneous data elements. AGUIA uses a semantic web formalism, resource description framework (RDF), and a bottom-up design of knowledge bases that employ the S3DB tool as the starting point for the client's interface assembly.
The data web service, S3DB, meets the necessary requirements of generating the RDF and of explicitly distinguishing the description of the domain from its instantiation, while allowing for continuous editing of both. Furthermore, it uses an HTTP-REST protocol, has a SPARQL endpoint, and has open source availability in the public domain, which facilitates the development and dissemination of this application. However, S3DB alone does not address the issue of representing content in a form that makes sense for domain experts.