Fig 1 - uploaded by Ruairi O'Reilly
Content may be subject to copyright.
Source publication
Beats-Per-Minute (BPM) is a microservice-based platform that provides a monitoring solution for the continuous acquisition, analysis and visualisation of health related data. BPM combines Commercial Off-The-Self (COTS) Activity Trackers and a scalable cloud-based infrastructure. This paper demonstrates the efficacy, reliability and integrity of BPM...
Contexts in source publication
Context 1
... microservice architecture enables single services to be scaled up and down independently during periods of high demand, thus preventing the development of an unmanageable, monolithic platform. Figure 1 depicts the architectural design of BPM and the services that constitute it. ...
Similar publications
Animal husbandry is an increasingly popular business where cattle are nurtured for food and other products. The productivity of cattle farms is largely affected by the health conditions of the cattle. Cattle with a communicable disease can drastically bring down the productivity of the whole farm. So it is highly recommended to identify unhealthy c...
![Fig 2. Smart Textile [54].](profile/Junaid-Khan-61/publication/343040036/figure/fig1/AS:914526220328960@1595051450122/Smart-Textile-54_Q320.jpg)
The primary function of textile is to shield humans but with advancement in technology, textile industry is rapidly developing with varied special features in addition to its primary function. Smart Textiles are the textile materials that have the ability to sense and hence react to external stimulus with the help of electronic sensors incorporated...
Citations
... Thus, the absence of a microservice architecture in these Health applications limits the reusability of the components of such architectures. Some papers highlight the advantage of using microservice architecture in the Health domain [22,23]. However, by investigating state-of-the-art systems, it has been identified that most legacy Health systems use a software architecture model that hinders the reusability of its components. ...
Traditionally, legacy Health applications use software architecture models that make it difficult to reuse components. Reusability is an essential attribute in the software lifecycle, as it improves the quality of applications and reduces maintenance and development costs. This paper proposes the cloud tool Microservice4EHR, which dynamically generates reusable components from existing software artifacts (e.g., graphical interfaces), while conforming to the standards used in the healthcare domain. A software architecture based on Connectors and Microservice components is specified and made
tangible by means of three algorithms. The use of both components is applied to a real-world scenario (a Brazilian blood donation center) and serves as an example. As a result, it is possible to notice that Health applications achieve greater reusability when they employ the microservice architecture. Thus, Microservice4EHR enables the use of reusable components in Health application architectures (for both new and legacy systems), increasing software reusability in this
context.
... Furthermore, no privacy protocols are studied. Another approach [14] describes a microservice-based platform that uses activity trackers to provide a monitoring solution for health-related data. This is an interesting approach providing elasticity and scalability thanks to the microservices, but no security features are taken into consideration and there is no information about the data standardization for medical data storage. ...
Chatbots are able to provide support to patients suffering from very different conditions. Patients with chronic diseases or comorbidities could benefit the most from chatbots which can keep track of their condition, provide specific information, encourage adherence to medication, etc. To perform these functions, chatbots need a suitable underlying software architecture. In this paper, we introduce a chatbot architecture for chronic patient support grounded on three pillars: scalability by means of microservices, standard data sharing models through HL7 FHIR and standard conversation modelling using AIML. We also propose an innovative automation mechanism to convert FHIR resources into AIML files, thus facilitating the interaction and data gathering of medical and personal information that ends up in patient health records. To align the way people interact with each other using messaging platforms with the chatbot architecture, we propose these very same channels for the chatbot-patient interaction, paying special attention to security and privacy issues. Finally, we present a monitored-data study performed in different chronic diseases, and we present a prototype implementation tailored for one specific chronic disease, psoriasis, showing how this new architecture allows the change, the addition or the improvement of different parts of the chatbot in a dynamic and flexible way, providing a substantial improvement in the development of chatbots used as virtual assistants for chronic patients.
... In this research corpus, several other concerns, such as architecture size/complexity and API versioning dominate over communication heterogeneity. This lower prominence of communication heterogeneity as an issue is on par with experience reports that employ both Web APIs and event-oriented services but either compose them using another service or design the services with the explicit goal of cooperating with one another (Djogic et al., 2018;O'Brien and O'Reilly, 2018;Sarkar et al., 2018). ...
Initial developments in Service-Oriented Computing (SOC) led to the development of Web Services using the SOAP protocol and an extensive set of tools and methods for composing new services from those existing. Subsequently, other types of services also emerged, such as event-oriented services and RESTful services. Nevertheless, all mentioned service types expose data and functionality, and users can benefit from their composition, regardless of the service type chosen for their implementation. In the Internet of Things, it is relevant to employ event-oriented services for sensing and SOAP, RESTful or lightweight web APIs for control. In the emerging field of microservices, heterogeneity is embraced as a design principle and services that are part of a single system may be implemented using heterogeneous technologies and paradigms. The research question of this review is: How heterogeneous services can be composed? There are several surveys that cover service composition with each of the existing service types, but the composition of heterogeneous services is only marginally addressed. This systematic literature review focuses explicitly on the heterogeneity of the aforementioned service types. A total of 66 documents, published from 2005 to 2018, have been surveyed, targeting all possible combinations of the three service types. In addition to summarizing existing works, the specific methods employed for supporting service type heterogeneity are grouped into archetypes and have their limitations and capabilities analyzed. Despite the large number of documents found, there are several open issues on heterogeneous service composition. The results of this review are confronted with emerging fields in service computing, namely microservices, serverless and IoT, yielding additional research directions.
