A preliminary study of telemedicine for patients with hepatic glycogen storage disease and their healthcare providers:from bedside to home site monitoring

BackgroundThe purpose of this project was to develop a telemedicine platform that supports home site monitoring and integrates biochemical, physiological, and dietary parameters for individual patients with hepatic glycogen storage disease (GSD). Methods and resultsThe GSD communication platform (GCP) was designed with input from software developers, GSD patients, researchers, and healthcare providers. In phase 1, prototyping and software design of the GCP has occurred. The GCP was composed of a GSD App for patients and a GSD clinical dashboard for healthcare providers. In phase 2, the GCP was tested by retrospective patient data entry. The following software functionalities were included (a) dietary registration and prescription module, (b) emergency protocol module, and (c) data import functions for continuous glucose monitor devices and activity wearables. In phase 3, the GSD App was implemented in a pilot study of eight patients with GSD Ia (n=3), GSD IIIa (n=1), and GSD IX (n=4). Usability was measured by the system usability scale (SUS). The mean SUS score was 64/100 [range: 38-93]. ConclusionsThis report describes the design, development, and validation process of a telemedicine platform for patients with hepatic GSD. The GCP can facilitate home site monitoring and data exchange between patients with hepatic GSD and healthcare providers under varying circumstances. In the future, the GCP may support cross-border healthcare, second opinion processes and clinical trials, and could possibly also be adapted for other diseases for which a medical diet is the cornerstone

IT-Enabled Knowledge Creation for Open Innovation

Open innovation is increasingly important for researchers and practitioners alike. Open innovation is closely linked to knowledge creation in that, with open innovation, knowledge inflows and outflows are exploited for innovation. In the information systems field, open innovation has been closely linked to open source software development teams. However, the literature has not yet identified how open source software development teams use information technologies to create knowledge to bring about open innovation. This study fills in this gap by asking the following research questions: RQ1) How do innovative open source software development teams create knowledge?, and RQ2) What types of information technologies do innovative open source software development teams rely on for enabling knowledge creation? I answer these research questions with a revelatory case study. The findings contribute to the knowledge management theory by identifying how three of the four knowledge creation modes identified by Nonaka and Takeuchi (1995) manifest through different behaviors in the IT-enabled open innovation setting compared to behaviors observed in the organizational setting. The findings also contribute to information systems theory by identifying the role of information technologies in enabling knowledge creation for open innovation. This study further provides researchers and practitioners with ways of identifying knowledge creation by analyzing information technology artifacts, such as mailing lists, issue trackers, and software versioning tools

Type Checking for Reliable APIs

In this paper, we propose to configure at compiletime the checking associated with Application ProgrammingInterfaces' methods that can receive possibly malformed values (e.g. erroneous user inputs and problematic retrieved recordsfrom databases) and thus cause application execution failures. To achieve this, we design a type system for implementing apluggable checker on the Java's compiler and find at compile timeinsufficient checking bugs that can lead to application crashesdue to malformed inputs. Our goal is to wrap methods whenthey receive external inputs so that the former generate checkedinstead of unchecked exceptions. We believe that our approachcan improve Java developers' productivity, by using exceptionhandling only when it is required, and ensure client applications'stability. We want to evaluate our checker by using it to verifythe source code of Java projects from the Apache ecosystem. Also, we want to analyze stack traces to validate the identifiedfailures by our checker

Breaking Down Barriers: This is your community, here's how to participate!

Presentation at the SPARC Open Access DSpace Users Group Meeting 2014 in Kansas City, Missouri, March 5, 2014.The presenter, a DSpace Committer, covers the importance of community participation in the development of DSpace open-source software products. He includes ways in which one can participate in DSpace development and lists several current projects

Learning in the Large - An Exploratory Study of Retrospectives in Large-Scale Agile Development

Many see retrospectives as the most important practice of agile software development. Previous studies of retrospectives have focused on pro- cess and outcome at team level. In this article, we study how a large-scale agile development project uses retrospectives through an analysis of retrospective reports identifying a total of 109 issues and 36 action items as a part of a longitudinal case study. We find that most of the issues identified relate to team-level learning and improvement, and discuss these findings in relation to current advice to improve learning outcome in large-scale agile development.Learning in the Large - An Exploratory Study of Retrospectives in Large-Scale Agile DevelopmentpublishedVersio