RESUMO
[This corrects the article DOI: 10.1038/s41746-020-0235-5.].
RESUMO
Storing very large amounts of data and delivering them to researchers in an efficient, verifiable, and compliant manner, is one of the major challenges faced by health care providers and researchers in the life sciences. The electronic health record (EHR) at a hospital or clinic currently functions as a silo, and although EHRs contain rich and abundant information that could be used to understand, improve, and learn from care as part learning health system access to these data is difficult, and the technical, legal, ethical, and social barriers are significant. If we create a microservice ecosystem where data can be accessed through APIs, these challenges become easier to overcome: a service-driven design decouples data from clients. This decoupling provides flexibility: different users can write in their preferred language and use different clients depending on their needs. APIs can be written for iOS apps, web apps, or an R library, and this flexibility highlights the potential ecosystem-building power of APIs. In this article, we use two case studies to illustrate what it means to participate in and contribute to interconnected ecosystems that powers APIs in a healthcare systems.
RESUMO
Collecting and managing data for clinical and translational research presents significant challenges for clinical and translational researchers, many of whom lack needed access to data management expertise, methods, and tools. At many institutions, funding constraints result in differential levels of research informatics support among investigators. In addition, the lack of widely shared models and ontologies for clinical research informatics and health information technology hampers the accurate assessment of investigators' needs and complicates the efficient allocation of crucial resources for research projects, ultimately affecting the quality and reliability of research. In this paper, we present a model for providing flexible, cost-efficient institutional support for clinical and translational research data management and informatics, the research management team, and describe our initial experiences with deploying this model at our institution.